linux-kernel - r8169 NETDEV WATCHDOG: eth0: transmit timed out [0/8]

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-next>] [day] [month] [year] [list]

Message-ID: <b410963b0908290216x19206aa6o4458bb55b5578a04@mail.gmail.com>
Date:	Sat, 29 Aug 2009 12:16:43 +0300
From:	roma1390 <roma1390@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: r8169 NETDEV WATCHDOG: eth0: transmit timed out [0/8]

Using 3 different r8169 devices on 2 servers (from 2 server so 100% of
population) we getting

NETDEV WATCHDOG: eth0: transmit timed out

with all bad consequences (stalled transmition) about up to 2 minutes or more.

Server doing up to 20Mbps. Mysql + apache + php. about 500 http
request / second.
These stall's is related only to r8169 (device or driver). Change to
other r8169 doesn't help. Helps only change to e1000 (other netcards
not tried, but maybe they will work too).

Attached logs from 2 servers. On srv5 motherboard was changed with
integrated r8169 but problem persist.

This behavior is know on internet, with no know workaround. Please
mark this driver as unstable/experimental or please move it to staging
tree.

Thanks in advance.
--
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/