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: Sun, 20 Aug 2006 08:53:20 +0000 [thread overview]
Message-ID: <1156064000.6690.69.camel@Homer.simpson.net> (raw)
In-Reply-To: <44E7369D.2010707@xs4all.nl>
On Sat, 2006-08-19 at 18:04 +0200, Udo van den Heuvel wrote:
> Mike Galbraith wrote:
> > 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?
Hard to say. I'd run it at least twice as long as your longest
explosion free interval.
-Mike
prev parent reply other threads:[~2006-08-20 6:45 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
2006-08-20 8:53 ` Mike Galbraith [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=1156064000.6690.69.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