Date: Thu, 20 Nov 2008 13:53:18 -0800
From: "Matt Carlson" <mcarlson@broadcom.com>
To: "Willy Tarreau" <w@1wt.eu>
cc: "Matthew Carlson" <mcarlson@broadcom.com>,
       "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
Message-ID: <20081120215318.GB27907@xw6200.broadcom.net>
References: <491954E1.2050002@gmail.com>
 <1226403067.7685.1598.camel@twins> <491E49AA.60407@gmail.com>
 <20081118065006.GC24654@1wt.eu>
 <20081120031101.GD26448@xw6200.broadcom.net>
 <20081120053746.GB15168@1wt.eu>
 <20081120184310.GB27712@xw6200.broadcom.net>
 <20081120212637.GB23844@1wt.eu>
MIME-Version: 1.0
In-Reply-To: <20081120212637.GB23844@1wt.eu>
User-Agent: Mutt/1.5.16 (2007-06-09)
Content-Type: text/plain;
 charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1989
Lines: 40

On Thu, Nov 20, 2008 at 01:26:37PM -0800, Willy Tarreau wrote:
> On Thu, Nov 20, 2008 at 10:43:10AM -0800, Matt Carlson wrote:
> > On Wed, Nov 19, 2008 at 09:37:47PM -0800, Willy Tarreau wrote:
> > > 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.
> > 
> > O.K.  Let me know how it goes.
> 
> Today, with the notebook connected to a gig switch, I could not reproduce
> the problem, even after one hour of approximately the same workload. I'll
> retry with the original 100 Mbps switch on monday.

Was it really a 5704 that you were using?


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/