> 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
> 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
> 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
> 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
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
