Ubuntu
linux package

Ethernet is showing up as disconnected

Bug #1152194 reported by Laura Czajkowski
278
This bug affects 6 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

I've just noticed as have access to a lan connection that the Ethernet is showing up as disconnected. there is no way to make this active so have to use wifi.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-11-generic 3.8.0-11.20
ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
Uname: Linux 3.8.0-11-generic x86_64
ApportVersion: 2.9-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: czajkowski 2062 F.... pulseaudio
Date: Thu Mar 7 14:19:49 2013
HibernationDevice: RESUME=UUID=39ffc27c-0543-4453-912b-36884a1b6f4c
InstallationDate: Installed on 2011-12-26 (436 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: TOSHIBA SATELLITE Z830
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic root=UUID=ce6ea08d-b7a1-41cb-9678-b534afddd7e8 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-11-generic N/A
 linux-backports-modules-3.8.0-11-generic N/A
 linux-firmware 1.103
SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2013-02-10 (24 days ago)
dmi.bios.date: 07/31/2012
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.70
dmi.board.asset.tag: 0000000000
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.70:bd07/31/2012:svnTOSHIBA:pnSATELLITEZ830:pvrPT22LE-00F004EN:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: SATELLITE Z830
dmi.product.version: PT22LE-00F004EN
dmi.sys.vendor: TOSHIBA

Revision history for this message
Laura Czajkowski (czajkowski) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc1-raring/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key
Tomas (tomasvandenooijevaer)
information type: Public → Public Security
Revision history for this message
Tomas (tomasvandenooijevaer) wrote :

Joseph, I had the same problem with the 3.8 kernel (seemingly random occurences at least once every day, though it might have something to do with hibernate/suspend) and have tested the 3.9 kernel. After multiple reboots, suspends and hibernates I cannot seem to reproduce the bug with the new kernel, so I will tag this as 'kernel-fixed-upstream'.

Thanks for the clear instructions.

tags: added: kernel-fixed-upstream
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

@Laura, can you also confirm this bug is fixed in v3.9-rc1, so we know this is the same issue Thomas is seeing?

If it is fixed in v3.9-rc1, I can perform a reverse bisect to identify the commit that fixes this.

Revision history for this message
Tomas (tomasvandenooijevaer) wrote :

@Joseph, the backport has not been done yet then?
Over the past few weeks I've used the 3.8 kernel but have not been able to reproduce the problem anymore. I assumed this got fixed somewhere along the line.

Just letting you know so you won't have to spend time on this if the problem has been solved.

Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Luis Henriques (henrix) wrote :

This could be related with the e1000e driver power management bug that was present in the 3.8 (raring) kernel. Basically, the ethernet card couldn't detect carrier signal if it was on deep sleep state (e.g., the laptop was on battery, not on AC).

Can you please confirm if you're still having this issue and if connecting the laptop to AC solves the problem?

Revision history for this message
Tomas (tomasvandenooijevaer) wrote :

@Luis, I haven't had the LAN card problem in weeks. Unless @Laura or anyone else still has this problem, feel free to close it.

Thanks for your explanation, sounds plausible to me :)

Revision history for this message
Luis Henriques (henrix) wrote :

Thanks. I've uploaded a test kernel here: http://people.canonical.com/~henrix/e1000e-pm-bug/
Basically, it contains the fix for the e1000e PM issue. This fix is already in Raring kernel master-next branch, and should be released soon.

Anyone still hitting this bug, please test this kernel. Thanks.

Revision history for this message
Jorge (jorge-vila) wrote :

Hi,

I do not know whether it is the same bug, but it is with e1000e as well. My computer is a desktop, not a laptop.

Could you review https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1205843??

Thank you
JORGE

To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.