Realtek RTL8111/8169 LAN (r8169) falls back from Gigabit to 100Mb/s after waking up from Suspend(S3)

I confirm this on Mainboard Gigabyte GA-P35-DS4 with r8169.
After resume from S3 speed is 100Mbit/s.

root@k1:/home/kede# ethtool eth0
Settings for eth0:
 Supported ports: [ TP MII ]
 Supported link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         1000baseT/Half 1000baseT/Full
 Supports auto-negotiation: Yes
 Advertised link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
 Advertised auto-negotiation: Yes
 Speed: 100Mb/s
 Duplex: Full
 Port: MII
 PHYAD: 0
 Transceiver: internal
 Auto-negotiation: on
 Supports Wake-on: pumbg
 Wake-on: g
 Current message level: 0x00000033 (51)
 Link detected: yes

The following command brings back 1000Mbit:
root@k1:/home/kersten# ethtool -s eth0 speed 1000

The onboard LEDs and the switch indicate 1000 Mbit now.
The network-manager-applet from gnome however still shows 100mbit.

root@k1:/home/kersten# ethtool eth0
Settings for eth0:
 Supported ports: [ TP MII ]
 Supported link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         1000baseT/Half 1000baseT/Full
 Supports auto-negotiation: Yes
 Advertised link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         1000baseT/Half 1000baseT/Full
 Advertised auto-negotiation: Yes
 Speed: 1000Mb/s
 Duplex: Full
 Port: MII
 PHYAD: 0
 Transceiver: internal
 Auto-negotiation: on
 Supports Wake-on: pumbg
 Wake-on: g
 Current message level: 0x00000033 (51)
 Link detected: yes

also affects 2.6.28-11-generic (jaunty)

mii-tool -vv eth0

Using SIOCGMIIPHY=0x8947
eth0: negotiated 100baseTx-FD flow-control, link ok
  registers for MII PHY 32:
    1000 796d 001c c912 0de1 c5e1 000f 2001
    c5e1 0000 0000 0000 1007 f880 0000 3000
    0060 6c40 0000 6c42 1060 0000 c009 2108
    2740 8c00 0040 0162 846c 8000 0123 0000
  product info: vendor 00:07:32, model 17 rev 2
  basic mode: autonegotiation enabled
  basic status: autonegotiation complete, link ok
  capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
  advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
  link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control

After setting it back to Gigabit:

Using SIOCGMIIPHY=0x8947
eth0: negotiated 100baseTx-FD flow-control, link ok
  registers for MII PHY 32:
    1000 796d 001c c912 0de1 c5e1 000f 2001
    c5e1 0000 0000 0000 1007 f880 0000 3000
    0060 6c40 0000 6c42 1060 0000 c009 2108
    2740 8c00 0040 0162 846c 8000 0123 0000
  product info: vendor 00:07:32, model 17 rev 2
  basic mode: autonegotiation enabled
  basic status: autonegotiation complete, link ok
  capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
  advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
  link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control

sorry... it didn't copy to the clipboard...

After setting it back to Gigabit:

Using SIOCGMIIPHY=0x8947
eth0: negotiated 1000baseT-FD flow-control, link ok
  registers for MII PHY 32:
    1000 796d 001c c912 0de1 c5e1 000d 2001
    4a2d 0300 3800 0000 1007 f880 0000 3000
    0060 acc0 0000 0000 1060 0000 0008 2108
    2740 8c00 0040 0106 097c 8000 0123 0000
  product info: vendor 00:07:32, model 17 rev 2
  basic mode: autonegotiation enabled
  basic status: autonegotiation complete, link ok
  capabilities: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
  advertising: 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
  link partner: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control

I have this same issue on a Debian install, using linux 2.6.29 which I compiled myself from kernel.org source - so it doesn't have anything to do with any patches or an older kernel.

Hardware is an RTL8111 on Gigabyte MA770-UD3 motherboard

After running
ethtool -s eth0 speed 1000
I get the same output as kede, but copying over the network shows it's still limited to 100mbit.

I've also seen the problem stay between reboots, however shutting down the computer completely (coldboot rather than hot boot) will reset it.

rmmod r8169 ; modprobe r8169 resets the device to 1gbit speeds.

Putting this in /etc/pm/sleep.d/99realtek and chmod +x /etc/pm/sleep.d/99realtek should work as a workaround.

Still happens with Ubuntu 9.10.

I tried the workaround but it caused more trouble:
Speed was 1000Mbit now, but network manager shows it is not connected. After running dhclient it works again.

Having the same problem on my MSI Wind Nettop. Tried the work around script and it gave me the same problems as kede. Any other ideas?

Anybody figure this bug out yet?

Solution---> http://www.linuxquestions.org/questions/linux-networking-3/gigabit-speed-lost-after-resuming-from-suspend-777107/#post3799302

The bug still occurs in Ubuntu 10.04 (Lucid Lynx) with Kernel 2.6.32-22-generic x86_64.

The bug still occurs in Ubuntu 10.10 (Maverick Meerkat) with Kernel 2.6.35-22-generic x86_64.

Was going to check this during the week. Thanks for the heads up.

On Mon, Oct 18, 2010 at 10:38 AM, LKaestner <email address hidden>wrote:

> The bug still occurs in Ubuntu 10.10 (Maverick Meerkat) with Kernel
> 2.6.35-22-generic x86_64.
>
> --
> Realtek RTL8111/8169 LAN (r8169) falls back from Gigabit to 100Mb/s after
> waking up from Suspend(S3)
> https://bugs.launchpad.net/bugs/331699
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The Linux Kernel: In Progress
> Status in “linux” package in Ubuntu: Confirmed
>
> Bug description:
> System Environment: http://www.sysprofile.de/id42117
> Mainboard: Gigabyte GA-P35-DS3P
> Component: Realtek 8111/8169 LAN with r8169 driver
> OS: Always the latest stable Ubuntu
>
> The Problem:
> When I boot the PC, Ubuntu connects at 1000Mb/s but after waking up from
> suspend to ram (S3) the connection speed is only 100Mb/s. That occurs in
> Ubuntu 8.10 and 9.04 Alpha 4.
> I use a reliable Gigabit router and Cat6 cables, so that should not be the
> reason.
>
> More Info:
> http://ubuntuforums.org/showthread.php?t=579312
>
>
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/linux/+bug/331699/+subscribe
>

LKaestner, 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 provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

As well, 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 Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: danne 1953 F.... pulseaudio
 /dev/snd/controlC0: danne 1953 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xf6a00000 irq 48'
   Mixer name : 'Realtek ALC269VB'
   Components : 'HDA:10ec0269,10431b33,00100100'
   Controls : 23
   Simple ctrls : 12
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xf4080000 irq 17'
   Mixer name : 'Nvidia GPU 15 HDMI/DP'
   Components : 'HDA:10de0015,10de0101,00100100'
   Controls : 24
   Simple ctrls : 4
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=b25ecb2a-3286-499e-b312-61551d85c5fa
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: ASUSTeK Computer Inc. G74Sx
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic root=UUID=eb790f05-6327-46f4-a123-7d3c735e8013 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-32-generic N/A
 linux-backports-modules-3.2.0-32-generic N/A
 linux-firmware 1.79.1
StagingDrivers: rts5139 mei
Tags: precise running-unity staging
Uname: Linux 3.2.0-32-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-04-28 (173 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
dmi.bios.date: 09/23/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G74Sx.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G74Sx
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG74Sx.203:bd09/23/2011:svnASUSTeKComputerInc.:pnG74Sx:pvr1.0:rvnASUSTeKComputerInc.:rnG74Sx:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: G74Sx
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Ubuntu 12.04, bug is still there. x86_64, 3.2.0-32-generic.

rmmod r8169 ; modprobe r8169 # still works as a workaround

Sorry about the involuntary attachment spamming.

Also, this is pretty much the same as the old Wont-Fix https://bugs.launchpad.net/ubuntu/+source/linux/+bug/347530

Dan B, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs

When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding.