From: Willy Tarreau <w@1wt.eu>
To: Matt Carlson <mcarlson@broadcom.com>
Cc: Roger Heflin <rogerheflin@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: WARNING: at net/sched/sch_generic.c:219 dev_watchdog+0xfe/0x17e() with tg3 network
Date: Thu, 20 Nov 2008 06:37:47 +0100 [thread overview]
Message-ID: <20081120053746.GB15168@1wt.eu> (raw)
In-Reply-To: <20081120031101.GD26448@xw6200.broadcom.net>
Hello Matt,
On Wed, Nov 19, 2008 at 07:11:01PM -0800, Matt Carlson wrote:
> > My tg3 is just PCI-based, no PCIe in this beast. I can send more
> > info when I turn it on. I don't think that the tg3 driver changes
> > often, so most likely digging through the changes between 2.6.25
> > and 2.6.27 should not take much time. I just don't know if I can
> > reliably reproduce the issue right now.
>
> Willy, this problem description sounds a little different than the
> original report. There was a bug where the driver would wait 2.5
> seconds for a firmware event that would never get serviced. That
> fix has already landed in the 2.6.27 tree though.
>
> I glanced over the changes between 2.6.25 and 2.6.27.6. There are quite
> a few changes related to phylib support for an upcoming device, but not
> so many changes that affect older devices. What device are you using?
I think it's a 5704, but I will check this this morning when I'm at
work. I also want to try to reliably reproduce the problem. After
that, I see only 29 patches which differ from the two kernels, it
should be pretty easy to spot the culprit.
If you think it's a different bug than original report (though I
really thought it was the same), I'll post my findings in a separate
thread not to mix investigations.
Thanks,
Willy
next prev parent reply other threads:[~2008-11-20 5:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <491954E1.2050002@gmail.com>
2008-11-11 11:31 ` WARNING: at net/sched/sch_generic.c:219 dev_watchdog+0xfe/0x17e() with tg3 network Peter Zijlstra
2008-11-15 4:01 ` Roger Heflin
2008-11-18 6:50 ` Willy Tarreau
2008-11-20 3:11 ` Matt Carlson
2008-11-20 5:37 ` Willy Tarreau [this message]
2008-11-20 18:43 ` Matt Carlson
2008-11-20 21:26 ` Willy Tarreau
2008-11-20 21:53 ` Matt Carlson
2008-11-21 17:55 ` Willy Tarreau
2008-11-24 13:27 ` Willy Tarreau
2008-11-24 21:52 ` Willy Tarreau
2008-11-25 1:52 ` Matt Carlson
2008-11-25 5:31 ` Willy Tarreau
2008-11-25 17:54 ` Matt Carlson
2008-11-26 21:12 ` Willy Tarreau
2008-11-26 22:54 ` Matt Carlson
2008-11-27 5:16 ` Willy Tarreau
2008-11-27 10:06 ` Frantisek Hanzlik
2008-11-27 20:33 ` Willy Tarreau
2008-12-02 22:55 ` Willy Tarreau
2008-11-20 3:00 ` Matt Carlson
2008-11-20 10:07 ` Roger Heflin
2008-11-20 17:11 ` Matt Carlson
2008-11-21 9:34 ` Roger Heflin
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=20081120053746.GB15168@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=mcarlson@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rogerheflin@gmail.com \
/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).