Comment 29 for bug 138611

Revision history for this message
treffer (rtreffer) wrote :

Update....

NOAPIC (as mentioned on gentoo-wiki.com) didn't help. Patching the kernel with the original marvell driver (available via http://www.marvell.com/drivers/search.do ) didn't work. Changing the sysctl.conf (matching the senders sysctl) seemed to helped slightly, as well as playing around with ethtool. However I didn't get a stable connection with 100MBit. Odd. The best run was ~1GB till failure.

I'll add a pci 100MBit card and recheck - I've added a new switch/device (wrt150n with dd-wrt) so I'll have to recheck my network's hardware.... Everything else was stable till now :( (transfering terrabytes of data)

However I can confirm that the card seems to work like a charm at lower rates/higher latencies... Wired....

Happy hunting, I'm going to add a 100MBit card :( (this won't keep me from testing - the gbit card is onboard - asus p5k-vm for the record)

Oh, my tests worked like this:
"scp -r <user>@192.168.1.66:/usr/src ./" /usr/src on the host machine is filled with 3 compiled kernels (make-kpkg buildpackage on all kernel trees). Failure occured @ ~500MB (sometimes sooner, sometimes later). 192.168.1.66 is my laptop with
00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
connected via
<notebook/realtek chip> <-- 100MBit/Patch cable --> <cheap 100MBit switch> <-- 100MBit/Patch cable --> <wrt150n with ddwrt> <-- 100MBit/Cross --> <normal box/marvell 88E8056>

I'll recheck the network chain with a 100MBit card - but I wouldn't expect a network problem....

Hope this helps.