From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Dave Jones <davej@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: e100 problems in .23rc8 ?
Date: Wed, 26 Sep 2007 11:10:11 -0700 [thread overview]
Message-ID: <46FAA083.9020604@intel.com> (raw)
In-Reply-To: <20070926150447.GA3761@redhat.com>
Dave Jones wrote:
> Last night, I hit this bug during boot up..
> http://www.codemonkey.org.uk/junk/e100-2.jpg
>
> This morning, I got a mail from a Fedora user of the same
> .23-rc8 based kernel that has seen a different trace
> also implicating e100..
>
> http://www.codemonkey.org.uk/junk/e100.jpg
>
> It may be that the two problems are unrelated, and it's
> just coincidence that both reports happen to be on an e100,
> but the timing is odd. Have there been other reports
> of similar problems recently ?
there hasn't been a change to e100 in two months now - perhaps something slipped
into the stack that broke it? If this reproduces, could you bisect?
Auke
next prev parent reply other threads:[~2007-09-26 18:10 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 [this message]
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
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=46FAA083.9020604@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=davej@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).