[patch] Re: r8169 locks up in 2.6.16.5

2006-04-18 Thread Francois Romieu
Thomas A. Oehser <[EMAIL PROTECTED]> : [...] > It is actually about a 30GB transfer, it was just after the first > 170Mb that it failed. The command in question is just a simple > "nc -l -p 12345|buffer|cpio -iumdB", and the sender may well be > able to generate the data faster than the receiving

Re: r8169 locks up in 2.6.16.5

2006-04-17 Thread Thomas A. Oehser
> Thanks for the report. It is quite clear. The device is (almost surely) > killed by a rx fifo overflow. Expect a patch shortly. > I wonder why it overflows in the first place though. How much time does > the 170 Mb transfer need ? It is actually about a 30GB transfer, it was just after the fi

Re: r8169 locks up in 2.6.16.5

2006-04-17 Thread Francois Romieu
Thomas A. Oehser <[EMAIL PROTECTED]> : [...] > Ok, here it all is, the attached archive has: > > - .before is right after the interface came up > - .mid is after flooding it with ping -f commands from 2 machines at once > - .bad is after doing the cpio over nc that killed it after 170MB > - .back

Re: r8169 locks up in 2.6.16.5

2006-04-16 Thread Thomas A. Oehser
> How much long was the card under load ? A few seconds ? > The same 1500 bytes mtu is used everywhere and the issue can not be > reproduced with a simple ping -f -q -l 64 -s what_you_want aimed at > the 8169, right ? Correct, > > What next? > > ethtool -d/-S before and after failure, .confi

Re: r8169 locks up in 2.6.16.5

2006-04-16 Thread Francois Romieu
Thomas A. Oehser <[EMAIL PROTECTED]> : [...] > > I'll welcome a complete dmesg after you have recovered through > > ifconfig down/up though. > > _Nothing_ on dmesg. Huh... Nothing appears when you issue 'dmesg' ? [...] > eth1 Link encap:Ethernet HWaddr 00:E0:4C:13:A9:56 > inet

Re: r8169 locks up in 2.6.16.5

2006-04-16 Thread Thomas A. Oehser
> I'll welcome a complete dmesg after you have recovered through > ifconfig down/up though. _Nothing_ on dmesg. > No problem. One more question: have you enabled NAPI ? If not, you > should. Doesn't seem to make a difference. Here, with it on, after failing it: --- 192.168.99.100 ping stati

Re: r8169 locks up in 2.6.16.5

2006-04-16 Thread Francois Romieu
Thomas A. Oehser <[EMAIL PROTECTED]> : [...] > I tested with everything turned off (no SMP, no swap, no > USB, no firewire, no iptables, no lmsensors, flat 1G memory, > etc. etc. etc.) except the bare minimum (LSI new Megaraid for the > SCSI and SATA raid arrays, both of which use the same driver,

Re: r8169 locks up in 2.6.16.5

2006-04-16 Thread Thomas A. Oehser
> Which motherboard and filesystem do you use ? It's an MSI using EXT3. > Can you send before and after the ping takes 9000 ms: > - ifconfig output > - registers dump via ethtool > > 9000ms seems quite close to the watchdog timeout (6 s) + ping > interval. Complete dmesg and .config will be we

Re: r8169 locks up in 2.6.16.5

2006-04-15 Thread Francois Romieu
Thomas A. Oehser <[EMAIL PROTECTED]> : [...] > On a dual Athlon 2600+ MP with 2GB RAM, and nothing else running. ^^ Which motherboard and filesystem do you use ? [...] > Should I just give these cards away and forget I ever heard of RealTeK? I don't think so. > Is it kno

r8169 locks up in 2.6.16.5

2006-04-15 Thread Thomas A. Oehser
Hi, The r8169 driver seems not to be able to handle high loads? On a dual Athlon 2600+ MP with 2GB RAM, and nothing else running. I'm doing: nc -l -p 12345|buffer|cpio -iuvmdB On the other machine, also with a gigabit card, I'm doing: find .|cpio -o -Hnewc -B|nc 192.168.111.1