You are not logged in.

Pages: 1

#1 2014-01-20 17:15:14

Intestinal Fortitude
Member
Registered: 2014-01-20
Posts: 2

[SOLVED] Realtek ethernet cuts out every 10 minutes

Hi all.  This is my first post.  I'm a new user to Arch Linux but have been using Linux, mostly Slackware, since the libc5 days.  I'd appreciate any suggestions for finding a solution to my networking problem.

My Arch Linux PC is a desktop PC I built to fiddle with.  It has an ECS Z87H3A4 motherboard with a built-in Realtek gigabit ethernet adapter.  I have run into a real stumper.  The ethernet regularly cuts out for about 40 seconds every 10 minutes.  I did a search and found that a lot of people have issues with Realtek, but didn't see anyone with a problem like mine.  I have swapped ports on the switch, and have another PC on the same LAN and it does not have problems, so I know it isn't a problem with the switch.

The system defaulted to the r8169 driver and common advice was to switch to the r8168 driver.  I did that but there was no change.

netstat -i doesn't show any dropped packets or error packets.
dmesg and the system log don't show any ethernet errors.

uname -r:

3.12.7-2-ARCH

Output of lspci -vv:

04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
	Subsystem: Elitegroup Computer Systems Device 8116
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 46
	Region 0: I/O ports at e000 [size=256]
	Region 2: Memory at f7c00000 (64-bit, non-prefetchable) [size=4K]
	Region 4: Memory at f0000000 (64-bit, prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee0f00c  Data: 4122
	Capabilities: [70] Express (v2) Endpoint, MSI 01
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 4096 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 unlimited, L1 <64us
			ClockPM+ Surprise- LLActRep- BwNot-
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR+, OBFF Via message/WAKE#
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled
		LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
		Vector table: BAR=4 offset=00000000
		PBA: BAR=4 offset=00000800
	Capabilities: [d0] Vital Product Data
		Unknown small resource type 00, will not decode more.
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		AERCap:	First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
	Capabilities: [140 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=01
			Status:	NegoPending- InProgress-
	Capabilities: [160 v1] Device Serial Number 00-00-00-00-68-4c-e0-00
	Capabilities: [170 v1] Latency Tolerance Reporting
		Max snoop latency: 71680ns
		Max no snoop latency: 71680ns
	Kernel driver in use: r8168
	Kernel modules: r8169, r8168

Here's what I see when I ping my router:

505 ares:~# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.694 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.712 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.699 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.711 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.695 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=0.700 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=0.716 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=0.699 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=0.590 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=0.721 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=0.667 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=0.606 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=0.679 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=0.617 ms
64 bytes from 192.168.1.1: icmp_seq=55 ttl=64 time=0.703 ms
64 bytes from 192.168.1.1: icmp_seq=56 ttl=64 time=0.641 ms
64 bytes from 192.168.1.1: icmp_seq=57 ttl=64 time=0.592 ms
64 bytes from 192.168.1.1: icmp_seq=58 ttl=64 time=0.614 ms
64 bytes from 192.168.1.1: icmp_seq=59 ttl=64 time=0.629 ms
64 bytes from 192.168.1.1: icmp_seq=60 ttl=64 time=0.566 ms
64 bytes from 192.168.1.1: icmp_seq=61 ttl=64 time=0.643 ms
64 bytes from 192.168.1.1: icmp_seq=62 ttl=64 time=0.693 ms
64 bytes from 192.168.1.1: icmp_seq=63 ttl=64 time=0.687 ms
64 bytes from 192.168.1.1: icmp_seq=64 ttl=64 time=0.603 ms
64 bytes from 192.168.1.1: icmp_seq=65 ttl=64 time=0.682 ms
64 bytes from 192.168.1.1: icmp_seq=66 ttl=64 time=0.689 ms
64 bytes from 192.168.1.1: icmp_seq=67 ttl=64 time=0.673 ms
64 bytes from 192.168.1.1: icmp_seq=68 ttl=64 time=0.702 ms
64 bytes from 192.168.1.1: icmp_seq=69 ttl=64 time=0.595 ms
64 bytes from 192.168.1.1: icmp_seq=70 ttl=64 time=0.687 ms
64 bytes from 192.168.1.1: icmp_seq=71 ttl=64 time=0.673 ms


^C
--- 192.168.1.1 ping statistics ---
71 packets transmitted, 31 received, 56% packet loss, time 69997ms
rtt min/avg/max/mdev = 0.566/0.663/0.721/0.055 ms
506 ares:~#

Last edited by Intestinal Fortitude (2014-01-28 15:45:08)

Offline

#2 2014-01-20 17:26:33

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [SOLVED] Realtek ethernet cuts out every 10 minutes

When posting configs, code or command output, please use [ code ] tags https://bbs.archlinux.org/help.php#bbcode

like this

It makes the code more readable and - in case of longer listings - more convenient to scroll through.

Offline

#3 2014-01-28 12:23:08

Intestinal Fortitude
Member
Registered: 2014-01-20
Posts: 2

Re: [SOLVED] Realtek ethernet cuts out every 10 minutes

Solved the problem.  Stupid mistake on my part.  I had an IP address conflict with another device on the LAN.

I was running tcpdump on the problem PC and another PC while testing and noticed the pings stopped working right after an arp request for the problem PCs address and started again after another arp request.  Then noticed the HW addresses in the arp responses were different.

Last edited by Intestinal Fortitude (2014-01-28 12:23:28)

Offline

#4 2014-01-28 15:38:53

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,414

Re: [SOLVED] Realtek ethernet cuts out every 10 minutes

Intestinal Fortitude wrote:

Solved the problem.  Stupid mistake on my part.  I had an IP address conflict with another device on the LAN.

D'oh!

Glad you got things straightened out here.  Please mark your thread as [Solved] so that we can keep our forums (somewhat) tidy.  This can be done by editing the first post.

Offline

Pages: 1

Board footer

Powered by FluxBB