netdev - Re: 3.4-rc: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

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: <20120501172748.GA17117@electric-eye.fr.zoreil.com>
Date:	Tue, 1 May 2012 19:27:48 +0200
From:	Francois Romieu <romieu@...zoreil.com>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	netdev@...r.kernel.org
Subject: Re: 3.4-rc: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

Stefan Richter <stefanr@...6.in-berlin.de> :
[...]
> I switched from 3.3 to 3.4-rc5 yesterday and am getting the following warning
> some time after boot (e.g. this time about two hours after boot).  What's up
> with that?

The device stopped being able to transmit anything at some point (netdev
watchdog message). The warnings always look the same. If the device does
not recover, we have a problem. Do we ?

[...]
> There are no noticeable issues, but I don't run anything demanding on the
> interface right now which would make any downtime obvious.

I don't understand: is it a low traffic interface or a no traffic one ?

> It is an RTL8168(?) on an Asus M3A78-EM motherboard.

dmesg | grep XID should identify the chipset. You may consider sending
an 'ethtool eth0' and 'ethtool -i eth0'.

-- 
Ueimor
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html