On Wed, 2006-08-16 at 05:42 +0200, Udo van den Heuvel wrote:
> Hello,
Greetings,
> Again my CL6000 Oopsed.
> Again named was involved.
> Again I cannot locate the cause.
> The log is below as it was pushed through ksymoops, providing a map and
> vlinux file.
>
> How can I proceed to find the cause?
>
> Kidn regards,
> Udo
(these oopsen would be a heck of a lot easier to look at if the
timestamp junk was stripped off)
> Aug 16 04:05:35 epia kernel: BUG: unable to handle kernel paging request
> at virtual address 4e2aad0b
> Aug 16 04:05:35 epia kernel: printing eip:
> Aug 16 04:05:35 epia kernel: 4e2aad0b
The oops doesn't help much. Once again, eip is in lala land, not the
kernel.
Given that you're the only person posting this kind of explosion, I
would cast a very skeptical glance toward my hardware. I'd suggest
reverting to a known good kernel first, to verify that you really don't
have a hardware problem cropping up.
After I did that, I'd enable stack check thingies under kernel hacking,
and if that didn't turn up anything, I'd try slab and page allocator
debugging options and hope to catch someone scribbling where they're not
supposed to.
-Mike
-
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]
