mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: shannon@widomaker.com (Charles Shannon Hendrix)
To: linux-kernel@vger.kernel.org
Subject: BUG: kernel crash report, odd...
Date: Mon, 9 Jul 2007 18:08:49 -0400	[thread overview]
Message-ID: <20070709220848.GA6782@widomaker.com> (raw)


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.

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.

Is there anything I can do, in case this happens again, to try and
capture more information?

-- 
shannon           | An Irishman is never drunk as long as he can hold onto 
                  | one blade of grass and not fall off the face of the earth.

             reply	other threads:[~2007-07-09 22:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 22:08 Charles Shannon Hendrix [this message]
2007-07-09 22:19 ` Jesper Juhl
2007-07-09 22:29   ` Jesper Juhl
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=20070709220848.GA6782@widomaker.com \
    --to=shannon@widomaker.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome