linux-kernel - Re: WARNING: at net/sched/sch_generic.c:256 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: <20120205223527.GA19001@redhat.com>
Date:	Sun, 5 Feb 2012 17:35:27 -0500
From:	Dave Jones <davej@...hat.com>
To:	"Justin P. Mattock" <justinmattock@...il.com>
Cc:	Larry Finger <Larry.Finger@...inger.net>,
	linux-kernel@...r.kernel.org
Subject: Re: WARNING: at net/sched/sch_generic.c:256
 dev_watchdog+0x1f2/0x200()

On Sun, Feb 05, 2012 at 02:29:46PM -0800, Justin P. Mattock wrote:
 
 > > > [ 2270.546572] WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x1f2/0x200()
 > > > [ 2270.546576] Hardware name: 0914
 > > > [ 2270.546580] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
 > > 
 > > The error clearly comes from r8169, not from ath9k. If you unload r8169 before 
 > > suspending, does this still happen? My suspicion is that NM is getting confused.
 > > 
 > as a quick test I unloaded r8169 and did not see this message, but I also added it in and suspended
 > and no warning message as well.

FWIW, we've been seeing reports of this in Fedora since last summer.
https://bugzilla.redhat.com/show_bug.cgi?id=715137

(We have reports on other chips too, but this bug is just the r8169 reports)

	Dave

--
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/