From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Charles Shannon Hendrix" <shannon@widomaker.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: kernel crash report, odd...
Date: Tue, 10 Jul 2007 00:29:54 +0200 [thread overview]
Message-ID: <9a8748490707091529j153d7202s47596b78b7aac612@mail.gmail.com> (raw)
In-Reply-To: <9a8748490707091519g3a0a098dx1e9188083c5a74b4@mail.gmail.com>
Forgot a few things, see below...
On 10/07/07, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> On 10/07/07, Charles Shannon Hendrix <shannon@widomaker.com> wrote:
> >
> > A system I was using a few minutes ago dumped this to the syslog:
> >
> > Jul 9 17:50:38 daydream kernel: [76022.613000] BUG: unable to handle
> > kernel NUL
> > L pointer dereference at virtual address 00000010
> > Jul 9 17:50:38 daydream kernel: [76022.613000] printing eip:
> > Jul 9 17:50:38 daydream kernel: [76022.613000] c01ace66
> > Jul 9 17:50:38 daydream kernel: [76022.613000] *pde = 00000000
> > Jul 9 17:50:38 daydream kernel: [76022.613000] Oops: 0000 [#1]
> >
> >
> > There was no other information either before or after.
> >
> > What I saw was my KDE desktop stopped responding to events.
> >
> > Machine didn't respond to power switch.
> >
> > Unfortunately, that's all I know.
> >
> > In the past when I had bugs like this, I got a fairly extensive kernel
> > error message, but this time the above is the only thing I saw.
> >
> It does look a little short... probably the rest just didn't make it to disk...
>
> > I have not had kernel bugs like this until I started running 2.6.20 on a
> > new Kubuntu install.
> >
> > Same hardware, but Slackware and my own custom 2.6.19 kernel never
> > crashed.
> >
> Different kernel source version, different configuration, probably
> different compiler, Slackware doesn't patch the vanilla kernel - I
> believe (k)ubuntu does. All in all that equals a significantly
> different kernel binary you have been running in those two cases.
>
A different userspace could also be the cause. In theory, userspace
should never be able to crash the kernel, but in real life bugs happen
and sometimes userspace manages to cause a kernel crash. So, a
different userspace environment in your new distribution could in
theory expose a bug that didn't surface with your previous
distribution.
> > Is there anything I can do, in case this happens again, to try and
> > capture more information?
> >
> 0. Make sure the kernels loglevel is set so that you get all messages.
>
0.5. Perhaps increase the size of the kernels log buffer (the
LOG_BUF_SHIFT config option)
> 1. Make sure syslog is setup to capture all kernel messages, both
> errors, warnings, notices, debug messages etc.
>
> 2. If you can, check output of 'dmesg' instead of just what made it to syslog.
>
> 3. If you have a second PC, setup serial console or netconsole to
> capture kernel messages on that second box. This can sometimes capture
> messages that don't make it to disk.
>
> 4. Build a custom kernel with some (or all) of the debug options under
> the Kernel Hacking menu enabled.
>
> 5. Even when the system hangs you may in some cases be able to get
> some info (or just sync the disks and do a reboot) via magic sysrq.
>
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2007-07-09 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 22:08 Charles Shannon Hendrix
2007-07-09 22:19 ` Jesper Juhl
2007-07-09 22:29 ` Jesper Juhl [this message]
2007-07-09 22:44 ` Randy Dunlap
2007-07-10 16:07 ` Hugh Dickins
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=9a8748490707091529j153d7202s47596b78b7aac612@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shannon@widomaker.com \
/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
all inboxes | Powered by JetHome®