Wired Ethernet gone after resume from suspend -- Realtek 8168

[Manowar]

Binary package hint: gnome-network-admin

I am using a new HP dv7 laptop. To isolate the problem, I have formatted the hard drive and performed a CLEAN installation. Here is the version information:

/etc/issue:
Ubuntu 8.10 \n \l

uname -a:
Linux Ubu 2.6.27-7-generic #1 SMP Fri Oct 24 06:40:41 UTC 2008 x86_64 GNU/Linux

I perform only three actions on the clean system

(1) Install all updates. For today, this includes base-files, linux-*-2.6.27-7*, linux-libc-dev, procps.

(2) To get suspend working I need to make sure the keyboard/mouse fuctions. I have needed this fix from 8.04 and it is still a problem in 8.10, but this easy work-around has worked fine for months: Add the file "25i8042" to /etc/pm/sleep.d/

(3) Finally, my NIC comes up as a Realtek r8169, instead of r8168. This is another long-known about bug, so I follow the RealTek directions from their website and then blacklist the r8169. Here are some output to show success:

lsmod | grep r816
=====================================================
r8168 45968 0

dmesg | grep r816
=====================================================
[ 15.366988] r8168 Gigabit Ethernet driver 8.009.00-NAPI loaded
[ 15.367025] r8168 0000:0a:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[ 15.367051] r8168 0000:0a:00.0: setting latency timer to 64
<snip>
[ 31.867892] r8168: eth0: link up

At this stage everything is working on eth0. Also, but I believe unrelated, I can connect to wlan0 without issue.

Next, I go into suspend and come back. eth0 is "grayed out" on the Network Manager drop-down and neither a modprobe -r r8168, modprobe r8168 nor a reboot will bring eth0 back to life. Wireless, however is still okay. Currently nothing is showing in ifconfig for eth0.

I have spent hours and hours looking at other similar bugs with potential fixes, and nothing seems to help. Hopefully, I've just missed something - but at this stage I am asking for some help to resolve. If any other information is required, please let me know.

[Manowar (talon7)]

Updating this bug based on new information on migration to 9.04 (which leave it still broken). I hope someone looks at this....

[Ryan (carbonfreeze)]

Also experiencing this on an HP tx2-1020us with "09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)"

After a suspend-resume cycle, this card appears to be connected in nm-applet, and I can try running dhclient on the interface (it gets an ip address!), but i cannot ping other devices on the network. reinserting the module has no effect. The only way i have found to resolve it is to reboot.

I have had this problem from 8.10 thru 10.04.

[iMac (imac-netstatz)]

There's another bug, I suspect is this one, but newer with upstream links.

https://bugs.launchpad.net/linux/+bug/771857

[penalvch (penalvch)]

Manowar, thank you for reporting this and helping make Ubuntu better. Intrepid reached EOL on April 30, 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

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 kernel in 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 and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

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.

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

where VERSION-NUMBER is the version number of the kernel you tested.

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

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

[Launchpad Janitor (janitor)]

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