linux-kernel - Re: WARNING: at net/sched/sch_generic.c:219 dev

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081120053746.GB15168@1wt.eu>
Date:	Thu, 20 Nov 2008 06:37:47 +0100
From:	Willy Tarreau <w@....eu>
To:	Matt Carlson <mcarlson@...adcom.com>
Cc:	Roger Heflin <rogerheflin@...il.com>,
	Peter Zijlstra <peterz@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>,
	netdev <netdev@...r.kernel.org>
Subject: Re: WARNING: at net/sched/sch_generic.c:219 dev_watchdog+0xfe/0x17e() with tg3 network

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

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