All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.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 17:07:35 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0707101650390.4603@blonde.wat.veritas.com> (raw)
In-Reply-To: <20070709220848.GA6782@widomaker.com>

On Mon, 9 Jul 2007, Charles Shannon Hendrix 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 NULL 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.

Something simple you can do, which I didn't see mentioned yet:
look up the entries before and after c01ace66 in that 2.6.20
kernel's System.map, then post the output of
objdump -d --start-address=0xbefore --stop-address=0xafter vmlinux
so people here can see the function name and the oopsing instruction
in its context.  May not help at all, but well worth trying.

Hugh

      parent reply	other threads:[~2007-07-10 16:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 22:08 BUG: kernel crash report, odd Charles Shannon Hendrix
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 [this message]

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=Pine.LNX.4.64.0707101650390.4603@blonde.wat.veritas.com \
    --to=hugh@veritas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.