| View previous topic :: View next topic |
| Author |
Message |
w00t08
n00b
Joined: 21 Aug 2008
Posts: 1
|
 Posted: Thu Aug 21, 2008 9:15 am Post subject: r8168 driving me nuts: Intermittent Network Freezing |
 |
|
Hey,
this is the second machine I'm having trouble with an Realtek r8168 NIC and Gentoo. The first one totally froze randomly. I had to set up Debian  to get it out to the customer in time. Anyway, I'm now having a similar problem on a dedicated server I'm administering. Fortunately, it doesn't completely lock up this time, the issue is more subtle but no less annoying.
| Code: | Reply from xxx.xxx.xxx.144: bytes=32 time=74ms TTL=56
Reply from xxx.xxx.xxx.144: bytes=32 time=75ms TTL=56
Reply from xxx.xxx.xxx.144: bytes=32 time=72ms TTL=56
Reply from xxx.xxx.xxx.144: bytes=32 time=72ms TTL=56
Request timed out.
Reply from xxx.xxx.xxx.144: bytes=32 time=72ms TTL=56
Reply from xxx.xxx.xxx.144: bytes=32 time=77ms TTL=56
Reply from xxx.xxx.xxx.144: bytes=32 time=77ms TTL=56
Reply from xxx.xxx.xxx.144: bytes=32 time=72ms TTL=56
Reply from xxx.xxx.xxx.144: bytes=32 time=78ms TTL=56
Reply from xxx.xxx.xxx.144: bytes=32 time=72ms TTL=56
Request timed out.
Reply from xxx.xxx.xxx.144: bytes=32 time=73ms TTL=56
Request timed out.
Reply from xxx.xxx.xxx.144: bytes=32 time=72ms TTL=56
Reply from xxx.xxx.xxx.144: bytes=32 time=72ms TTL=56
Request timed out.
Reply from xxx.xxx.xxx.144: bytes=32 time=71ms TTL=56
Reply from xxx.xxx.xxx.144: bytes=32 time=77ms TTL=56
Reply from xxx.xxx.xxx.144: bytes=32 time=78ms TTL=56
Reply from xxx.xxx.xxx.144: bytes=32 time=71ms TTL=56
Reply from xxx.xxx.xxx.144: bytes=32 time=75ms TTL=56
Reply from xxx.xxx.xxx.144: bytes=32 time=71ms TTL=56 |
When connected via SSH, the console practically freezes randomly for about 1 to 10 seconds (at the same time the ICMP packets are lost). This also happens to any other TCP connections. Funny enough, it has been running fine for about two days (although there were some issues where the server rebooted for no reason, which may be related). Now it's totally wonky all the time.
I had to switch to the vanilla kernel instead of hardened to get the r8168 from Realtek up and running instead of the r8169 driver that comes with the Kernel, but that didn't really help much. Here are my specs:
| Code: | 00:00.0 Host bridge: Intel Corporation DRAM Controller (rev 10)
00:01.0 PCI bridge: Intel Corporation PCI Express Root Port (rev 10)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)
00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) SATA IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01) |
| Code: | ~ # ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000033 (51)
Link detected: yes
~ # ethtool -i eth0
driver: r8168
version: 8.008.00
firmware-version:
bus-info: 0000:03:00.0
~ # ethtool -S eth0
NIC statistics:
tx_packets: 12610
rx_packets: 17007
tx_errors: 0
rx_errors: 0
rx_missed: 0
align_errors: 0
tx_single_collisions: 0
tx_multi_collisions: 0
unicast: 9190
broadcast: 7802
multicast: 15
tx_aborted: 0
tx_underrun: 0
~ # ethtool -k eth0
Offload parameters for eth0:
rx-checksumming: on
tx-checksumming: on
scatter-gather: off
tcp segmentation offload: off
udp fragmentation offload: off
generic segmentation offload: off
|
I should also mention that I have another machine running (without a single issue EVER) with | Code: | | 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01) |
but that has | Code: | | bus-info: 0000:02:00.0 |
where all machines that caused trouble have | Code: | | bus-info: 0000:03:00.0 |
.
Any advice? Please, I'm pretty much lost. (And no, I can't replace the NIC )
Thanks a million
Edit: Just to clarify, this seems to happen with the hardened Kernel and the shipped r8169 driver as well as with the r8168 driver I downloaded from Realtek (which I had to switch to vanilla sources for to compile). |
|
| Back to top |
|
 |
xgregx
Apprentice
Joined: 17 Dec 2004
Posts: 181
Location: Cheshire, CT
|
| Posted: Mon Apr 27, 2009 3:24 pm Post subject: |
|
|
If you run the dmesg command, do you see more than 2 or 3 "r8169: eth0: link up" messages? I was dozens a day. I think the system is trying to sleep the NIC to save power.
I was having a similar issue - I think it's power save option for the different devices.
I went into the bios on my mobo and disabled PCI-e powersaving(mine is an onboard gigabit nic on the PCI-e bus). Problem seems to have gone away for me.
_________________
Half-life/Source/Urban Terror/Unreal control panel -> www.opengamepanel.org
Linux user #347899
Gentoo has USE flags for a highly configurable system.
Microsoft has SUE flags to stifle innovation |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
