From: "Nick Van Vlaenderen" <nick.vanvlaenderen@pandora.be>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: question about logging kernel problems when kernel blows up
Date: Mon, 26 Jan 2004 18:44:58 +0100 [thread overview]
Message-ID: <000b01c3e434$1e1f83c0$bc00a8c0@NOTEBOOK> (raw)
In-Reply-To: <Pine.LNX.4.58.0401261014530.889@Bear.bresnan.net>
Maybe the problem is in your /etc/fstab ? Or the root partition isn't
properly defined in your boot loader?
----- Original Message -----
From: "Scott Berry" <scott@drscott.dyndns.biz>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, January 26, 2004 6:15 PM
Subject: Re: question about logging kernel problems when kernel blows up
> Well it wasn't wanting to mount the root system. I have a friend trying
> to get a look at it and see if we can get it going. He is more
> experienced then I am at kernels.On Mon, 26 Jan 2004, Nick Van Vlaenderen
> wrote:
>
> > Hi Scott,
> >
> > By default, you can check the dmesg output by entering 'dmesg' on the
> > console. This will show the boot process. You can also write the output
to a
> > file (since it's too much information for 1 screen) using 'dmesg >
file'.
> >
> > Also, look in /var/log/messages.
> >
> > By the way, what problem do you have with your kernel?
> >
> > Nick
> > ----- Original Message -----
> > From: "Scott Berry" <scott@drscott.dyndns.biz>
> > To: "Speakup is a screen review system for Linux."
<speakup@braille.uwo.ca>
> > Cc: <blinux-list@redhat.com>
> > Sent: Monday, January 26, 2004 5:43 PM
> > Subject: question about logging kernel problems when kernel blows up
> >
> >
> > > Hi there,
> > >
> > > I have a friend who is trying to help me debug a kernel problem. I am
> > > wondering if there is any way to log the problems that the kernel
> > > encounters when you load it and it blows up. He needs this to help me
> > > debug what is wrong. Thanks for the help.
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> > >
> >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Scott Berry
` Nick Van Vlaenderen
` Scott Berry
` Nick Van Vlaenderen [this message]
` Jude DaShiell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000b01c3e434$1e1f83c0$bc00a8c0@NOTEBOOK' \
--to=nick.vanvlaenderen@pandora.be \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).