From: "David S. Miller" <davem@davemloft.net>
To: chrisw@osdl.org
Cc: andystewart@comcast.net, linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.13 BUG tg3.c:2805 = crash (this one isn't tainted)
Date: Tue, 13 Sep 2005 16:29:35 -0700 (PDT) [thread overview]
Message-ID: <20050913.162935.53822111.davem@davemloft.net> (raw)
In-Reply-To: <20050913222830.GG7991@shell0.pdx.osdl.net>
From: Chris Wright <chrisw@osdl.org>
Date: Tue, 13 Sep 2005 15:28:30 -0700
> Might help to copy netdev on the report. Seems you've had a bit of luck
> in reproducing. Any chance on narrowing down to last known good kernel?
> There's been a fair bit of change in that driver between 2.6.12 and
> 2.6.13.
Michael Chan has already sent him a test patch for the tg3
driver to try and narrow this one down. We think his chipset
is reordering MMIO's and the patch he's been sent tries to
confirm/deny that theory.
next prev parent reply other threads:[~2005-09-13 23:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 2:43 Kernel 2.6.13 BUG tg3.c:2805 = crash Andy Stewart
2005-09-13 3:48 ` Kernel 2.6.13 BUG tg3.c:2805 = crash (this one isn't tainted) Andy Stewart
2005-09-13 22:28 ` Chris Wright
2005-09-13 23:29 ` David S. Miller [this message]
2005-09-13 23:48 ` Chris Wright
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=20050913.162935.53822111.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andystewart@comcast.net \
--cc=chrisw@osdl.org \
--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 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®