Thread (9 messages) flat view 9 messages, 3 authors, 2011-03-10

Re: Mass udp flow reboot linux with RealTek RTL-8169 Gigabit

From: Seblu <hidden>
Date: 2011-02-13 17:27:35
Also in: lkml

Possibly related (same subject, not in this thread)

On Sun, Feb 13, 2011 at 2:56 PM, Francois Romieu [off-list ref] wrote:
Eric Dumazet [off-list ref] :
If it still does not perform better, please include the XID line of
the r8169 driver from dmesg.
I've tryed on archlinux i686 distro with 2.6.37 and host reboot like
under debian.

After this, i tryed  wiith a 2.6.38-rc4 (amd64), which include your
recent patchs.

# dmesg|grep -i xid
r8169 0000:04:00.0: eth0: RTL8168b/8111b at 0xffffc90005260000,
1c:6f:65:56:d9:17, XID 0c200000 IRQ 47

NIC seems to be reset frequently but host stop rebooting. \o//

r8169 0000:04:00.0: eth0: link up
net_ratelimit: 317 callbacks suppressed
r8169 0000:04:00.0: eth0: link up
...
net_ratelimit: 312 callbacks suppressed
r8169 0000:04:00.0: eth0: link up

i noticed a strange behaviour:
I run an iperf from computer A (gigabit plugged).
I run an ping -f from computer A.
A lot of pintk like previous one is printed on console (dmesg -n 8)

if i run an iperf from a computer B (fast eth plugged)
pings is not answered (computer A) and printk message disapear (on target)

if i run this 2nd iperf from computer A, disable iperf from computer
B, printk and ping answers are back.

i attached dmesg output.

Regards,

-- 
Sébastien Luttringer
www.seblu.net

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help