From: Eric Sandeen <sandeen@redhat.com>
To: David Mack <dmack@juniper.net>
Cc: Dave Jones <davej@redhat.com>,
"Kok, Auke" <auke-jan.h.kok@intel.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
netdev@vger.kernel.org, esandeen@redhat.com
Subject: Re: e100 problems in .23rc8 ?
Date: Mon, 22 Oct 2007 09:59:53 -0500 [thread overview]
Message-ID: <471CBAE9.6010406@redhat.com> (raw)
In-Reply-To: <7DCDA0F058071B49AED9D3D7886C41BE0A43B10E@muon.jnpr.net>
David Mack wrote:
> Then I got very, very lucky, since I have successfully rebooted
> 2.6.23.1-23.fc8 four times (zero panics) and this is the first time a
> 2.6.23 kernel has not panicked on me in months.
>
> This does not fill me with confidence in the theory that the panics I've
> been seeing are due to a race condition.
I'll agree with the testing results, at least. I booted successfully
*60* times with 2.6.23.1-23.fc8, booting the stock F8test3 kernel would
oops every 5 or 6 boots.
It may well be a race, but if so something is apparently opening/closing
the window on us! :)
-Eric
next prev parent reply other threads:[~2007-10-22 15:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 15:04 e100 problems in .23rc8 ? Dave Jones
2007-09-26 18:10 ` Kok, Auke
2007-09-26 18:18 ` Dave Jones
2007-09-27 6:58 ` Herbert Xu
2007-10-11 0:36 ` Dave Jones
2007-10-11 1:25 ` Herbert Xu
2007-10-11 16:10 ` Kok, Auke
2007-10-11 17:25 ` Dave Jones
2007-10-11 18:56 ` Eric Sandeen
2007-10-12 14:54 ` David Mack
2007-10-12 15:35 ` Herbert Xu
2007-10-12 15:51 ` David Mack
2007-10-13 2:35 ` Herbert Xu
2007-10-16 14:33 ` Eric Sandeen
2007-10-16 14:35 ` Herbert Xu
2007-10-16 15:47 ` Eric Sandeen
2007-10-16 16:39 ` David Mack
2007-10-12 17:04 ` Kok, Auke
2007-10-18 17:51 ` David Mack
2007-10-18 17:59 ` Kok, Auke
2007-10-18 18:17 ` Chuck Ebbert
2007-10-22 1:04 ` Dave Jones
2007-10-22 3:10 ` Herbert Xu
2007-10-22 14:05 ` David Mack
2007-10-22 14:59 ` Eric Sandeen [this message]
2007-10-22 14:44 ` Chuck Ebbert
2007-10-11 23:24 ` Herbert Xu
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=471CBAE9.6010406@redhat.com \
--to=sandeen@redhat.com \
--cc=auke-jan.h.kok@intel.com \
--cc=davej@redhat.com \
--cc=dmack@juniper.net \
--cc=esandeen@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@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.