Re: BUG: kernel crash report, odd...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux