From: Mike Galbraith <efault@gmx.de>
To: Udo van den Heuvel <udovdh@xs4all.nl>
Cc: linux-kernel@vger.kernel.org,
Folkert van Heusden <folkert@vanheusden.com>
Subject: Re: And another Oops / BUG? (2.6.17.8 on VIA Epia CL6000)
Date: Wed, 16 Aug 2006 07:35:39 +0000 [thread overview]
Message-ID: <1155713739.6011.30.camel@Homer.simpson.net> (raw)
In-Reply-To: <44E29415.4040400@xs4all.nl>
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
next prev parent reply other threads:[~2006-08-16 5:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 3:42 Udo van den Heuvel
2006-08-16 7:35 ` Mike Galbraith [this message]
2006-08-19 16:04 ` Udo van den Heuvel
2006-08-20 8:53 ` Mike Galbraith
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=1155713739.6011.30.camel@Homer.simpson.net \
--to=efault@gmx.de \
--cc=folkert@vanheusden.com \
--cc=linux-kernel@vger.kernel.org \
--cc=udovdh@xs4all.nl \
/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®