networking dead after resume from sleep

Bug #1435498 reported by Jerry Quinn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

On resume, networking was disabled and I could not reenable it. There are warnings in the kernel log that are concerning. Networking used to be stable on resume. This kernel or perhaps a previous one seems to have made it less so.

jlquinn@tiamat:~/x1carbon$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.10
Release: 14.10
Codename: utopic

jlquinn@tiamat:~/x1carbon$ apt-cache policy linux-image-3.16.0-33-generic
linux-image-3.16.0-33-generic:
  Installed: 3.16.0-33.44
  Candidate: 3.16.0-33.44
  Version table:
 *** 3.16.0-33.44 0
        500 http://us.archive.ubuntu.com/ubuntu/ utopic-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ utopic-security/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu/ utopic-proposed/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-33-generic 3.16.0-33.44
ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7
Uname: Linux 3.16.0-33-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jlquinn 2435 F.... pulseaudio
 /dev/snd/controlC0: jlquinn 2435 F.... pulseaudio
CurrentDesktop: Unity
Date: Mon Mar 23 14:50:01 2015
HibernationDevice: RESUME=UUID=650995f4-6763-4d42-966e-5c0689b207ea
InstallationDate: Installed on 2014-10-08 (166 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: LENOVO 20A8S0SG00
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=95206ff2-9e2a-4ea3-b390-c5235863b247 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-33-generic N/A
 linux-backports-modules-3.16.0-33-generic N/A
 linux-firmware 1.138.1
SourcePackage: linux
UpgradeStatus: Upgraded to utopic on 2015-02-28 (23 days ago)
dmi.bios.date: 09/02/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GRET40WW (1.17 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20A8S0SG00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGRET40WW(1.17):bd09/02/2014:svnLENOVO:pn20A8S0SG00:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A8S0SG00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20A8S0SG00
dmi.product.version: ThinkPad X1 Carbon 2nd
dmi.sys.vendor: LENOVO

Revision history for this message
Jerry Quinn (jlquinn) 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 :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 kernel[0].

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/v4.0-rc5-vivid/

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Jerry Quinn (jlquinn) wrote :

I just received a kernel update:

3.16.0-34-generic

I'm going to give this a chance first. If I still get failures, I'll try the upstream kernel.

Thanks
Jerry

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.