RTL8139 NIC doesn't work on booting in Ubuntu after a windows hibernate

Bug #123358 reported by Timo van Roermund
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Surbhi Palande

Bug Description

Binary package hint: linux-image-2.6.20-16-generic

I have the following configuration:
- HP omnibook xt6200 with BIOS version EG.M2.42 (the most recent one)
- Kubuntu Feisty using kernel 2.6.20-16-generic
- a RTL8139 onboard NIC (using the 8139too driver)

The problem I encounter is the following: if I start my notebook without an ethernet cable connected and later on try to connect a cable, the NIC won't work. It is being seen by the driver dut just doesn't work (no data is being sent or received). The NIC will only start working again when I hard reset my notebook (that is, disconnect it from the adapter and remove the battery) and boot it with a network cable connected. Only soft resetting (=shutdown and restart) does not solve the problem; in that case the NIC continues to fail.

However, the problem does not occur if I start Kubuntu with the pci=routeirq kernel switch. In that case, the NIC will work regardless of whether a cable was connected during boot (the way it should be).

Also I tried to boot with the (backported) Gutsy kernel (2.6.22-7-generic). Using that kernel it always works, so the bug seems to be solved already upstream.

Revision history for this message
Chuck Short (zulcss) wrote : Re: RTL8139 NIC doesn't work if no cable is connected at boot-time

Please attach the output of lspci -vnn

Changed in linux-source-2.6.20:
status: New → Incomplete
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote :

This is the output of the "lspci -vnn" command.

Revision history for this message
Chuck Short (zulcss) wrote :

Can you attach the output of dmesg when this happens?

Thanks
chuck

Changed in linux-source-2.6.20:
assignee: nobody → ubuntu-kernel-team
status: Incomplete → Confirmed
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote :

This is the dmesg output when the NIC fails to connect.

However, it took me a while to reproduce this bug: for some reason the NIC worked after rebooting and restarting without the pci-routeirq switch (and the cable disconnected during boot time of course).

I finally reproduced the situation as follows:
- connect a cable
- start Windows XP (it is a dual boot system)
- hibernate Windows
- disconnect the ethernet cable
- start Kubuntu

When I look into the dmesg output, it says "[ 48.106230] eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1" while no cable is connected!

So maybe the NIC requires a status reset at startup or something like that?

Revision history for this message
Timo van Roermund (timo-van-roermund) wrote :

I also found out that now the pci-routeirq switch does not seem to make a diference anymore (I have no clue why that seemed to solve it a few days ago).

So it seems like a NIC reset is required at startup. It should be possible to fix this, as in Windows it works correctly after waking up from hibernation mode.

Revision history for this message
Timo van Roermund (timo-van-roermund) wrote :

Here I found someone with a similar problem:
http://www.linuxquestions.org/questions/showthread.php?p=2690333#post2690333

He also mentiones that starting Windows helps is (hard) resetting the NIC.

Revision history for this message
Timo van Roermund (timo-van-roermund) wrote :

And here is another person who is encountering exactly the same:

http://forums.gentoo.org/viewtopic.php?t=323844#2313404

It seems like Windows XP disables the LAN interface when it hibernates. Is there any possibility to let the 8139too driver re-enable (if necessary) the interface at boot time?

Revision history for this message
Gionn (giovanni.toraldo) wrote :

Same problem with r8169 module. I don't have tried Gusty kernel ,only Feisty.

02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 01)
        Subsystem: ASUSTeK Computer Inc. Unknown device [1043:11f5]
        Flags: bus master, fast devsel, latency 0, IRQ 16
        I/O ports at c800 [size=256]
        Memory at fe0ff000 (64-bit, non-prefetchable) [size=4K]
        Expansion ROM at fe0e0000 [disabled] [size=64K]
        Capabilities: [40] Power Management version 2
        Capabilities: [48] Vital Product Data
        Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable-
        Capabilities: [60] Express Endpoint IRQ 0
        Capabilities: [84] Vendor Specific Information

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote : Re: RTL8139 NIC doesn't work if no cable is connected at boot-time

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Timo van Roermund (timo-van-roermund) wrote :

Tested it on Intrepid (Kubuntu 8.10 - kernel 2.6.27-7), the bug still exists.

Changed in linux:
status: Incomplete → New
Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote : Re: RTL8139 NIC doesn't work if no cable is connected at boot-time

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote :

Confirmed: the problem still exists in Kubuntu (10.04) with kernel 2.6.31-10.

Scenario in which the bug exists:
- hibernate Windows -> start Kubuntu -> ethernet connection *is not* possible

Scenario in which the bug does not occur:
- shutdown Windows (or remove and reinsert battery before starting Kubuntu) -> start Kubuntu -> ethernet connection *is* possible

Revision history for this message
Timo van Roermund (timo-van-roermund) wrote :

Oops, I mentioned the wrong versions...

The bug still exists in Kubuntu 9.10 (karmic) with kernel version 2.6.31-20-generic.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Timo,
     Thanks for confirming for Karmic, would you also mind testing against the daily Lucid? I'd really like for us to get a handle on what could be causing this and see if there is a way we can address it. Also, if you do encounter this on Lucid, would you mind running 'apport-collect -p linux 123358' so that I can get some detailed logging added to the bug?

Thanks!

~JFo

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote : apport-collect data

Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: A5451 [ALI 5451], device 0: ALI 5451 [ALI 5451]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: timo 2375 F.... knotify4
                      timo 2694 F.... kmix
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'A5451'/'ALI 5451 at 0x1000, irq 11'
   Mixer name : 'Realtek ALC200,200P rev 0'
   Components : 'AC97a:414c4710'
   Controls : 37
   Simple ctrls : 23
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=cf3b1c2b-a12e-43cd-83c1-59cd74664002
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Hewlett-Packard HP OmniBook PC
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   3.3V 32-bit PC Card
ProcCmdLine: root=UUID=07bac071-950e-42b3-ad1b-ee7acefcecb2 ro quiet splash vga=791
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=
ProcVersionSignature: Ubuntu 2.6.31-20.57-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-20-generic N/A
 linux-firmware 1.26
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Uname: Linux 2.6.31-20-generic i686
UserGroups:

WpaSupplicantLog:

XsessionErrors: (polkit-gnome-authentication-agent-1:2742): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
dmi.bios.date: 03/31/04
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: qEG.M0.72
dmi.board.name: HP OmniBook PC
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 6200EG
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrqEG.M0.72:bd03/31/04:svnHewlett-Packard:pnHPOmniBookPC:pvrHPOmniBook6200EG:rvnHewlett-Packard:rnHPOmniBookPC:rvr6200EG:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP OmniBook PC
dmi.product.version: HP OmniBook 6200 EG
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Timo van Roermund (timo-van-roermund) wrote : AlsaDevices.txt
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote : AplayDevices.txt
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote : BootDmesg.txt
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote : Card0.Amixer.values.txt
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote : Card0.Codecs.codec97.0.ac97.0.0.txt
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote : Card0.Codecs.codec97.0.ac97.0.0.regs.txt
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote : CurrentDmesg.txt
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote : IwConfig.txt
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote : Lspci.txt
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote : PciMultimedia.txt
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote : ProcCpuinfo.txt
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote : ProcInterrupts.txt
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote : ProcModules.txt
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote : UdevDb.txt
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote : UdevLog.txt
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote : WifiSyslog.gz
Changed in linux (Ubuntu):
status: Incomplete → New
tags: added: apport-collected
Revision history for this message
Timo van Roermund (timo-van-roermund) wrote : Re: RTL8139 NIC doesn't work if no cable is connected at boot-time

Hi Jeremy,

I can confirm that the bug still exists in Lucid (I downloaded today's Ubuntu Lucid LiveCD image). Unfortunately, I was not able to run apport-collect under Lucid, since I had no working network connection available (the wireless connection also didn't work in the Lucid LiveCD). Therefore, I ran apport-collect from Kubuntu Karmic 9.10.

Best regards,

Timo

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Timo,
    Thank you for following up on this bug and attaching the logging. I'll work with the kernel team to look into the issue.

Thanks!

~JFo

Changed in linux (Ubuntu):
status: New → Triaged
Revision history for this message
Surbhi Palande (csurbhi) wrote :

changed the summary, after the comment #4

summary: - RTL8139 NIC doesn't work if no cable is connected at boot-time
+ RTL8139 NIC doesn't work after booting in Ubuntu after a windows
+ hibernate
summary: - RTL8139 NIC doesn't work after booting in Ubuntu after a windows
- hibernate
+ RTL8139 NIC doesn't work on booting in Ubuntu after a windows hibernate
Surbhi Palande (csurbhi)
Changed in linux-source-2.6.20 (Ubuntu):
assignee: nobody → Surbhi Palande (csurbhi)
Changed in linux (Ubuntu):
assignee: nobody → Surbhi Palande (csurbhi)
Changed in linux-source-2.6.20 (Ubuntu):
assignee: Surbhi Palande (csurbhi) → nobody
Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
komputes (komputes)
affects: linux-source-2.6.20 (Ubuntu) → null
Changed in linux (Ubuntu):
status: Won't Fix → Triaged
Revision history for this message
komputes (komputes) wrote :

This issue still exists in 11.04 with the following cards which contain the same family chip:

Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10)
Workaround:
Use pci=routeirq kernel option

D-Link System Inc RTL8139 Ethernet [1186:1300] (rev 10) - from Bug #22084
Workaround:
Shutdown, power down. Unplug your host (this cuts power to the card if wake-on-lan power is maintained). Wait 15 seconds. Plug in. Boot ubuntu.

Curtis Hovey (sinzui)
no longer affects: null
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
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.