dropped packets with realtek nic - Mandriva
This is a discussion on dropped packets with realtek nic - Mandriva ; I'm seeing dropped packets on eth0 (wired connection).
I installed a x86_64 2.6.24.7 kernel (2008.1) because i read it may help
that problem but in my case after rebooting to the new kernel things are
the same. I power cycled ...
-
dropped packets with realtek nic
I'm seeing dropped packets on eth0 (wired connection).
I installed a x86_64 2.6.24.7 kernel (2008.1) because i read it may help
that problem but in my case after rebooting to the new kernel things are
the same. I power cycled the router "just in case" but that didnt change
anything, also other pc's connected to the router are ok and not showing
any dropped packets at all.
If i run: watch -n 1 'ifconfig' the dropped packet count can be seen
rising over 120 million per second. This has to be bogus, I can ssh to the
system, open web pages and so on without any trouble. But it bugs me. Here
are two snapshots taken 10 seconds apart. The onboard nic is a
Realtec 'RTL8111/8168B PCI Express Gigabit Ethernet controller rev 02'
eth0 Link encap:Ethernet HWaddr 00:E0:4D:8F:E4:79
inet addr:192.168.xx.xx Bcast:192.168.x.255 Mask:255.255.255.0
inet6 addr: fe80::2e0:4dff:fe8f:e479/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:784 errors:0 dropped:54482220763 overruns:0 frame:0
TX packets:599 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:278146 (271.6 KiB) TX bytes:49114 (47.9 KiB)
Interrupt:250
eth0 Link encap:Ethernet HWaddr 00:E0:4D:8F:E4:79
inet addr:192.168.xx.xx Bcast:192.168.x.255 Mask:255.255.255.0
inet6 addr: fe80::2e0:4dff:fe8f:e479/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:790 errors:0 dropped:55731675282 overruns:0 frame:0
TX packets:599 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:278655 (272.1 KiB) TX bytes:49114 (47.9 KiB)
Interrupt:250
Any ideas?
Thanks
Eric
-
Re: dropped packets with realtek nic
Eric wrote:
> I'm seeing dropped packets on eth0 (wired connection).
> I installed a x86_64 2.6.24.7 kernel (2008.1) because i read it may help
> that problem but in my case after rebooting to the new kernel things are
> the same. I power cycled the router "just in case" but that didnt change
> anything, also other pc's connected to the router are ok and not showing
> any dropped packets at all.
> If i run: watch -n 1 'ifconfig' the dropped packet count can be seen
> rising over 120 million per second. This has to be bogus, I can ssh to the
> system, open web pages and so on without any trouble. But it bugs me. Here
> are two snapshots taken 10 seconds apart. The onboard nic is a
> Realtec 'RTL8111/8168B PCI Express Gigabit Ethernet controller rev 02'
>
> eth0 Link encap:Ethernet HWaddr 00:E0:4D:8F:E4:79
> inet addr:192.168.xx.xx Bcast:192.168.x.255 Mask:255.255.255.0
> inet6 addr: fe80::2e0:4dff:fe8f:e479/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:784 errors:0 dropped:54482220763 overruns:0 frame:0
> TX packets:599 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:278146 (271.6 KiB) TX bytes:49114 (47.9 KiB)
> Interrupt:250
>
> eth0 Link encap:Ethernet HWaddr 00:E0:4D:8F:E4:79
> inet addr:192.168.xx.xx Bcast:192.168.x.255 Mask:255.255.255.0
> inet6 addr: fe80::2e0:4dff:fe8f:e479/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:790 errors:0 dropped:55731675282 overruns:0 frame:0
> TX packets:599 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:278655 (272.1 KiB) TX bytes:49114 (47.9 KiB)
> Interrupt:250
>
> Any ideas?
> Thanks
> Eric
Ok, i solved it. I downloaded the realtek kernel module from the realtek web
site, compiled it, installed it and no more dropped packets.
Eric
-
Re: dropped packets with realtek nic
Eric wrote:
> Ok, i solved it. I downloaded the realtek kernel module from the realtek
> web site, compiled it, installed it and no more dropped packets.
> Eric
FWIW I had the same problem (and solution) with 2007.1 and 2008.0, but
2008.1 seemed to fix it.
--
Dave