l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2002 Mar 24 19:55

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] need to debug boot crash
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] need to debug boot crash

Peter Jay Salzman wrote:

> remember that not every "error" is a real error.  for instance, a micro
> channel driver can search your system buses for a micro channel device
> and not find one.  it'll print something vaguely error-ish to screen.
> you didn't say if your kernel is panicking or not.
> assumming your kernel isn't panicked, you can do shift-pageup to scroll
> up on the console.

Its not panicking.  I'm doing an nfs mount of the os, and something went
wrong init the initscripts.  The shift-pageup is a really good idea, I didn't
know about that.  The problem is that so many errors spewed out that I
coulldn't get far enough back.

> you can also look in /var/log/messages or dmesg | less.
> note that most module related errors upon boot don't make it into the
> error log.  some kernel developers are working on that.  there's a good
> reason for it (but i can't recall).
> if your kernel is panicking, your options are a bit more limited.  the
> easiest way (assumming you're not henry house who knows how to do the
> serial console thing) is to take a picture of your monitor with a
> digital camera.  however, most kernel panics usually don't print tons of
> error messages for this exact reason.  if the problem is a root
> filesystem that can't be found or a bona-fide "oops", you'll see 2 or 3
> lines of error at most.
> note, a very, very, very, very worthwhile thing is to extend the buffer
> that your kernel allocates for the scrollback.  it's in the linux FAQ.
> basically, you need to recompile your kernel and define something like:

I will do this.  The picture thing is a good idea.  I was finally able to get
a handle on things by putting a call to bash in the first init script.  Now I
can look at the initialization, by putting the call to bash in different
places, and finding where it goes wrong.  Thanks. ;~)

> (this isn't it -- you'll have to look up the exact define).  i do it
> each time i compile a new kernel.  it gives you ALOT more scroll back
> buffer space.
> pete
> begin eric nelson <en77@pacbell.net>
> > I have an error occuring during boot.  However, the pertinant
> > information flys by, and I just get a long list of error messages on the
> > screen.  Is there a way to record the messages during the late part of
> > kernel boot, or to make it slow down, or require a prompt, or something?
> >
> > _______________________________________________
> > vox-tech mailing list
> > vox-tech@lists.lugod.org
> > http://lists.lugod.org/mailman/listinfo/vox-tech
> _______________________________________________
> vox-tech mailing list
> vox-tech@lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox-tech

vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Sunset Systems
Who graciously hosts our website & mailing lists!