Realtek 8111F silently drops after some use

Bug #1195493 reported by Derek Wood
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I have an Asus M5A97 LE R2.0 motherboard with an integrated Realtek 8111F ethernet chipset, and after a period of time ( 10-20 minutes, although it seems shorter under heavy use ) the ethernet stops responding. The main symptoms of this are a lack of DNS responses (bind is installed locally and configured as recursive), and general internet access (e.g, "ping 8.8.8.8" or "ping 192.168.1.1"). I'm able to fix this with "ifconfig <interface> down, ifconfig <interface> up, dhclient -d", but the issue does come back.

It's worth noting that some of my research suggested that this could possibly be related to IOMMU being enabled, although this is an unacceptable solution as disabling IOMMU seems to also disable USB.

There are no obvious signs of error from the kernel in the "dmesg" output or the various system logs (kern.log, syslog), even with the verbose and debug options added to the kernel options from the grub boot screen.

I was able to find someone with similar issues on the kernel mailing list, and there is a short patch [1] that does appear to fix the issue I had. I applied this patch to the raring kernel (via apt-get source linux-image) and ethernet has been uninterrupted for about a day now. However, this patch does not appear to be integrated into the 3.10 linux kernel as of now [2].

This has been tested on the most current raring kernel from the linux-image package as well as the mainline kernel that was current as of yesterday ( linux-image-3.10.0-999-generic_3.10.0-999.201306260405_amd64 ).

[1] https://lkml.org/lkml/2013/4/10/549
[2] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/net/ethernet/realtek/r8169.c?id=refs/tags/v3.10-rc7#n4192

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-25-generic 3.8.0-25.37
ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
Uname: Linux 3.8.0-25-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-25-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Date: Thu Jun 27 15:24:54 2013
HibernationDevice: RESUME=UUID=620dbcbf-ae16-47b7-b3d1-c868d3ad54e8
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: To be filled by O.E.M. To be filled by O.E.M.
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=rxvt-unicode-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=2b918b5d-084c-4d73-979b-e5d662ad0e36 ro splash quiet
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-25-generic N/A
 linux-backports-modules-3.8.0-25-generic N/A
 linux-firmware 1.106
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2013-05-11 (47 days ago)
WifiSyslog:
 Jun 27 08:21:36 yavin dhclient: DHCPREQUEST of 192.168.1.2 on p4p1 to 192.168.1.1 port 67 (xid=0x7a9a1da7)
 Jun 27 08:21:36 yavin dhclient: DHCPACK of 192.168.1.2 from 192.168.1.1
 Jun 27 08:21:36 yavin dhclient: bound to 192.168.1.2 -- renewal in 37687 seconds.
dmi.bios.date: 01/11/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1503
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 LE R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd01/11/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

Revision history for this message
Derek Wood (ddwood) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: saucy
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
tags: added: kernel-da-key
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Do you happen to know if the patch author plans on submitting this patch into the mainline kernel? If he does, it's best for him to Cc: <email address hidden> Then the patch will make it's way into Raring and the other stable kernels through the normal update process.

Revision history for this message
John Jamison (desperado665) wrote :

I also have same issue with Asus M5A97 R2.0 (non LE, same chipset)

Revision history for this message
randomei (randomei) wrote :

Ubuntu 13.10 x64 also affected.

penalvch (penalvch)
tags: added: cherry-pick
Revision history for this message
penalvch (penalvch) wrote :

Derek Wood, as per http://www.asus.com/Motherboards/M5A97_LE_R20/#support an update is available for your BIOS (2006). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

tags: added: bios-outdated-2006
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
randomei (randomei) wrote :

With latest bios and latest saucy updates, I have no such problem anymore.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.