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>] [day] [month] [year] [list]
Date:	Sat, 29 Aug 2009 12:21:33 +0300
From:	roma1390 <roma1390@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: r8169 NETDEV WATCHDOG: eth0: transmit timed out [7/8]

On Sat, Aug 29, 2009 at 12:16, roma1390<roma1390@...il.com> wrote:
> 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.
>

View attachment "srv5-dmesg.txt" of type "text/plain" (57296 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ