Bug 605559 - Windows driver "green ethernet" mode causes problems with Realtek R8169 network card
Summary: Windows driver "green ethernet" mode causes problems with Realtek R8169 netwo...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-18 09:24 UTC by Derkjan de Haan
Modified: 2012-04-16 07:23 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 18:30:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Output of lspci -v (7.25 KB, text/plain)
2010-06-18 09:24 UTC, Derkjan de Haan
no flags Details
dmesg output (43.64 KB, text/plain)
2010-06-18 09:25 UTC, Derkjan de Haan
no flags Details

Description Derkjan de Haan 2010-06-18 09:24:56 UTC
Created attachment 425057 [details]
Output of lspci -v

Description of problem:

Onboard Realtek R8169 card is not working

Version-Release number of selected component (if applicable):

2.6.33.3-85.fc13.x86_64 on Fedora Live CD

How reproducible:

Always

Steps to Reproduce:
1. boot with Live CD
2. Network management applet show no available network hardware
3.
  
Actual results:

Network card is recognised but not enabled, see 'Additional Info'

Expected results:

Network card working

Additional info:

r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:02:00.0: Refused to change power state, currently in D3
r8169 0000:02:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
r8169 0000:02:00.0: cache line size of 64 is not supported
r8169 0000:02:00.0: PCI INT A disabled
r8169: probe of 0000:02:00.0 failed with error -22

- This happens always, when booting from power off, rebooting, rebooting from Windows makes no difference
- Mainboard is Asus M4A785TD-V EVO
- This started happening with one of the latest F12 kernels, and I kind of hoped it was solved in F13.

Comment 1 Derkjan de Haan 2010-06-18 09:25:46 UTC
Created attachment 425058 [details]
dmesg output

Comment 2 Derkjan de Haan 2010-06-25 19:08:52 UTC
Problem solved. 

It was caused by the Windows driver for this hardware, which supports a 'Green Ethernet' mode. 

When enabled, it adaptively lowers the output voltage of the UTP port, which - in my case - leads to lower transmission speeds: It negotiates 10Mbit or not at all with my 3Com Gigabit Officeconnect desktop switch, depending on the cable used.
 
Furthermore it enables some kind of 'deep sleep' power save mode on the card, which the Linux driver is apparently unable to resurrect it from.

Comment 3 Edouard Bourguignon 2010-07-21 13:20:42 UTC
how did you solve this problem?

Here we are obliged to add "pcie_aspm=off" on the cmdline, without that network is not working.

Comment 4 Derkjan de Haan 2010-07-22 14:02:58 UTC
After I found out the cause of the problem, I simply disabled the 'Green Ethernet' option in the Windows driver, and all was well.

Comment 5 Francois Romieu 2010-07-22 20:10:45 UTC
The output of lspci is barely usable.

Is this a 8168d ?

-- 
Ueimor

Comment 6 Derkjan de Haan 2010-07-23 06:39:35 UTC
Now that the card works again, lspci suddenly gives full output:

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
        Subsystem: ASUSTeK Computer Inc. M4A785TD Motherboard
        Flags: bus master, fast devsel, latency 0, IRQ 25
        I/O ports at d800 [size=256]
        Memory at fdfff000 (64-bit, prefetchable) [size=4K]
        Memory at fdff8000 (64-bit, prefetchable) [size=16K]
        Expansion ROM at feaf0000 [disabled] [size=64K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [70] Express Endpoint, MSI 01
        Capabilities: [ac] MSI-X: Enable- Count=4 Masked-
        Capabilities: [cc] Vital Product Data
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel
        Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
        Kernel driver in use: r8169
        Kernel modules: r8169

Hope this is what you need, if not please let me know.

Comment 7 Bug Zapper 2011-06-02 10:23:28 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Bug Zapper 2011-06-27 18:30:53 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 9 Rona Dini Hari 2012-04-16 07:23:02 UTC
I found this bug report while looking for solution for my problem.

I have these symptoms:
1. Ethernet will not naturally work after halt (shutdown, restart, hibernate, suspend). Must hard reset the laptop first, and only work on first boot.
2. eth0 renamed to p3p1. Must use kernel parameter biosdevname=0 to change back. and it was working.
3. Other problem with Linux PCI Express Power Management is my Broadcom 4312 WLAN sometimes fell asleep while download big file. I have to pause download, reconnect to AP, then resume the download.

My laptop is Compaq Presario CQ40-108TU. I think it began when I was still using Gentoo.

At that time the only problem I had was resume from suspend, when resuming, the disk is locked. The GUI is functional but when opening file or even running a command, none is accessible. I then fix it by upgrading BIOS to F.66 A.

This my posting in gentoo forum about it:
http://forums.gentoo.org/viewtopic-t-898354-start-0.html

Then I thought it will be fine to stop using gentoo and going back binary based distribution. Ubuntu 11.10 Xfce is not compatible, It cannot shutdown, restart, and hibernate, suspend and resume worked, so I was for days can only suspend the laptop. I thought because the kernel is newer it needs a new BIOS, so I flashed again to F.67. It didn't fix it. Then I tried using Fedora 16 Xfce, it was working perfectly.

I think it was after the first kernel update I began to experience problems with my RTL8102E. First it will not link when the cable is connected. The lights are on but there is not any connection. I found out from other people using the same class as my Realtek RTL8102E that it was "Green Ethernet"/"LAN Power Saving" feature problem. The solution was to clear the electrical current from the laptop by removing all RAM modules and Battery, and put them back in again, and start normally. For windows users they have the option to turn off this feature from driver. For desktop mainboard users, they have the option to turn off the feature in BIOS Setup Screen. HP do not give the option for my laptop.

This is my posting about the Ethernet problem:
http://forums.fedoraforum.org/showthread.php?t=278238

Right now I just want my onboard Ethernet back. I believe it is still there sleeping in Deep Slumber Mode (that's what they called it).

This is my current lspci, Ethernet is gone:
(1) lspci
    -----
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
02:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
04:00.0 System peripheral: JMicron Technology Corp. SD/MMC Host Controller
04:00.2 SD Host controller: JMicron Technology Corp. Standard SD Host Controller
04:00.3 System peripheral: JMicron Technology Corp. MS Host Controller
04:00.4 System peripheral: JMicron Technology Corp. xD Host Controller

I have to wait until regression against pcie_aspm boot parameter is cleared. I think pcie_aspm is working now. But I still do not get the expected result.

dmesg | grep -i aspm
--------------------
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.3.1-5.fc16.x86_64 root=UUID=b0e8212c-b526-4de2-ae38-05b007785de6 ro quiet rhgb selinux=0 panic=5 pceipnp.debug=1 pcie_aspm=off
[    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.3.1-5.fc16.x86_64 root=UUID=b0e8212c-b526-4de2-ae38-05b007785de6 ro quiet rhgb selinux=0 panic=5 pceipnp.debug=1 pcie_aspm=off
[    0.000000] PCIe ASPM is disabled

This is a record of lspci when the Ethernet still working naturally, taken from my posting in gentoo forum that I mentioned earlier:
(2) lspci
    -----
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
03:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
05:00.0 System peripheral: JMicron Technology Corp. SD/MMC Host Controller
05:00.2 SD Host controller: JMicron Technology Corp. Standard SD Host Controller
05:00.3 System peripheral: JMicron Technology Corp. MS Host Controller
05:00.4 System peripheral: JMicron Technology Corp. xD Host Controller 

Additional valuable experience:
I have tried downgrading the BIOS to F.11 E:
1. Ethernet still gone.
2. Suspend problem back. This time using newer kernel there is the libata.noacpi kernel boot parameter to fix disk lock after suspend.
3. For the problem with shutdown, restart, hibernate hang/freeze there is the idle=nomwait boot parameter.
4. With newer BIOS there is the Processor C State option in BIOS screen. If that is set to disabled, and idle=nomwait is removed, the problem in number three comes back.

Will this be enough to reopen?


Note You need to log in before you can comment on or make changes to this bug.