Bug#526983: 'official' realtek driver works for me
On 08/15/2010 10:59 AM, Carlos Fonseca wrote: Zach Sadecki wrote: I built and installed the Realtek 8168 driver version 8.018.00 from the Realtek site and the problem has gone away. Thanks for the suggestion. I have downloaded version 8.018.00 of the r8101 driver (my chip is an RTL8101e) from the Realtek site, and have tried it with kernel linux-image-2.6.32-5-amd64 version 2.6.32-20. FWIW, I'm running a stock Lenny kernel: z...@mercury:~$ uname -a Linux mercury 2.6.26-2-686 #1 SMP Mon Jun 21 05:58:44 UTC 2010 i686 GNU/Linux I may still be witnessing possibly similar behavior when accessing the NFS share on this server (occasional pauses during large transfers). But it's not nearly as bad (pauses are much shorter in length), and as you said nothing shows up in the kern.log when this happens. Maybe it's just that timeouts/retries are much shorter with the Realtek driver and they're hiding their bad behavior by simply not logging it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526983: 'official' realtek driver works for me
Zach Sadecki wrote: I built and installed the Realtek 8168 driver version 8.018.00 from the Realtek site and the problem has gone away. Thanks for the suggestion. I have downloaded version 8.018.00 of the r8101 driver (my chip is an RTL8101e) from the Realtek site, and have tried it with kernel linux-image-2.6.32-5-amd64 version 2.6.32-20. However, the problem persists: the network card hangs shortly after starting a large rsync. The main difference is that dmesg shows nothing, but suspending to RAM and resuming fixes it just as with the default driver. In addition, while testing the Realtek r8101 driver, I got the following rsync error once, right after enting the password for the remote machine: Received disconnect from UNKNOWN: 2: Corrupted MAC on input. rsync: writefd_unbuffered failed to write 4 bytes to socket [generator]: Broken pipe (32) rsync error: unexplained error (code 255) at io.c(1530) [generator=3.0.7] rsync error: received SIGUSR1 (code 19) at main.c(1306) [receiver=3.0.7] On the second try, the network just hung... I am going back to using the default driver. Carlos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526983: 'official' realtek driver works for me
I had the same problem on my Intel D945GCLF2D board running Lenny. Heavy NFS traffic caused the NETDEV WATCHDOG errors. I built and installed the Realtek 8168 driver version 8.018.00 from the Realtek site and the problem has gone away. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
