No link on RTL8111D - also breaks link on Windows

[Loïc Minier]

MY Realtek RTL8111D onboard ethernet this doesn't work in Ubuntu 10.10. Network Manager shows the adapter as disconnected and ip link show eth0 gives:
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000

The adapter works under Windows 7. If one has booted Linux once, then the adapter doesn't work under Windows 7 anymore, even after a power off/power on cycle. One needs to power off and *turn off the power supply* (on/off power supply switch or remove power cable) for e.g. 5 mn to get the adapter to work again under Windows.

WORKAROUND: modprobe -r r8169 && modprobe r8169

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic-pae 2.6.35-22.35
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lool 1666 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfbff8000 irq 52'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,1458a002,00100001'
   Controls : 38
   Simple ctrls : 21
Card1.Amixer.info:
 Card hw:1 'Generic'/'HD-Audio Generic at 0xfbcfc000 irq 53'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Mon Nov 8 05:10:29 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 eth1 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic-pae root=UUID=d1acbdf3-500b-4c57-8705-8649813e6e26 ro quiet splash
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:

SourcePackage: linux
dmi.bios.date: 08/10/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F11
dmi.board.name: P55A-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P55A-UD3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Loïc Minier (lool)]

NB: This happens with both the original BIOS (F8) and latest BIOS (F11).

[Loïc Minier (lool)]

I reproduced this bug with a mainline build of 2.6.37-rc1 which has the latest r8169.c changes from mainline.

[Loïc Minier (lool)]

Couple of additional things worth mentioning: doing a tcpdump while running dhclient eth0 shows no packet going in or out; both LEDs are also off.

[Loïc Minier (lool)]

Hmm color-me stupid, but with 2.6.37-rc1 after boot I can get the driver working with modprobe -r r8169 && modprobe r8169.

[Loïc Minier (lool)]

And this problem which was 100% reproducible isn't reproducible at all anymore now that I did this modprobe -r / modprobe.

[Loïc Minier (lool)]

Actually I managed to reproduce one time again; modprobe did the trick. I'm not sure how to reset the system to the state where I can see the bug 100% of the time.

Also wanted to mention that other people are affected: http://ubuntuforums.org/showthread.php?t=1548422

[Harry (harry33)]

Yes I can confirm this.
There are also other Realtek ethernet cards suffering this very problem.
And it has been around at least from Jauntys 2.6.28 kernel.

This softreset failure occurs every now and then, at irregular intervals.
Also, a kernel update/upgrade may trigger this.
After the failure, the ethernet card is somehow locked.
The only cure is the hard reset, complete power off.
I use the power switch of my power supply to do this.

[fotoryder (tex-monahans)]

I'm also affected by this bug. I just installed Ubuntu 10.10, and am unable to activate the built in NIC. The motherboard is an MSI 770-C45. The ethernet connection is a built in RealTek RTL8111DL. The motherboard also has built in HD sound by RealTek - ALC888S.

I did have the ethernet working under KUBUNTU 10.04. but upgraded to Kubuntu 10.10to attempt to get the audio working. During the upgrade to 10.10, the ethernet quit working, and won't work under the Kubuntu 10.04 Live CD. The ethernet is recognized and automatically configured under Linux Mint 8 Live CD. The Linux Mint 8 Live CD is also using the r8169 driver/module, as do Ubuntu/Kubunto 10.04 and 10.10.

[fotoryder (tex-monahans)]

Update - I tried several things to get this resolved, and finally had some success. A full cold reset of the system did work. This required disconnecting the power cord for several minutes, and then restarting the system under Ubuntu 10.10. This is effective until a system reboot.

I had best results after I disabled Network Manager, and manually configured the network interface. This was effective through a number of reboots, and several weeks time. Unfortunately, this motherboard is currently dedicated for another purpose, and is not available for testing.

[Polarman (mathias-ferraton)]

I have a Gigabyte GA-P55-UD3 motherboard which comes with a builtin Realtek RTL8111D onboard ethernet:

sudo lshw -C network :

description: Ethernet interface
       product: RTL8111/8168B PCI Express Gigabit Ethernet controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: eth0
       version: 03
       serial: 6c:f0:49:09:xx:xx
       size: 10Mbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half latency=0 link=no multicast=yes port=MII speed=10Mbit/s
       resources: irq:45 ioport:de00(size=256) memory:fbeff000-fbefffff memory:fbef8000-fbefbfff memory:fbe00000-fbe1ffff

I have the same problem on 11.04 and on 10.10

[penalvch (penalvch)]

Loïc Minier, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.