All of lore.kernel.org
 help / color / mirror / Atom feed
From: Udo van den Heuvel <udovdh@xs4all.nl>
To: linux-kernel@vger.kernel.org
Cc: Mike Galbraith <efault@gmx.de>,
	Folkert van Heusden <folkert@vanheusden.com>
Subject: Re: And another Oops / BUG? (2.6.17.8 on VIA Epia CL6000)
Date: Sat, 19 Aug 2006 18:04:45 +0200	[thread overview]
Message-ID: <44E7369D.2010707@xs4all.nl> (raw)
In-Reply-To: <1155713739.6011.30.camel@Homer.simpson.net>

Mike Galbraith wrote:
> On Wed, 2006-08-16 at 05:42 +0200, Udo van den Heuvel wrote:
>> Again my CL6000 Oopsed.
>>
>> How can I proceed to find the cause?
>>
> (these oopsen would be a heck of a lot easier to look at if the
> timestamp junk was stripped off)

Will try to do that next time.

> The oops doesn't help much.  Once again, eip is in lala land, not the
> kernel.

Hmm. At least that is consistent, as is the named involvement and the
rest of the effects.

> 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.

How long should I run a 2.6.16.* kernel to be sure enough it is not my
hardware?

> 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.

OK, will try that.

  reply	other threads:[~2006-08-19 16:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16  3:42 And another Oops / BUG? (2.6.17.8 on VIA Epia CL6000) Udo van den Heuvel
2006-08-16  7:35 ` Mike Galbraith
2006-08-19 16:04   ` Udo van den Heuvel [this message]
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=44E7369D.2010707@xs4all.nl \
    --to=udovdh@xs4all.nl \
    --cc=efault@gmx.de \
    --cc=folkert@vanheusden.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 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.