kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

SixedUp, Thank you for taking the time to report this bug and helping to
make Ubuntu better. However, I am closing it because as per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268113/comments/5
the bug has been fixed in the latest development version of Ubuntu -
Trusty Tahr.

This is a significant bug in Ubuntu. If you need a fix for the bug in
previous versions of Ubuntu, please perform as much as possible of the
SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

** Changed in: linux (Ubuntu)
       Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268113

Title:
  [LENOVO ThinkPad X201] suspend/resume failure

Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  Fresh install of 13.10 on new SSD.  System previously running 12.10
  (on a HDD) without problem.

  Symptoms are that system is now extremely fragile when using suspend/resume to memory. Symptoms exhibit themselves in two main ways:
  (a) System will often (~ more than 1 time in 3) fail to fully resume from suspend. When the error occurs, the graphical console appears to always hang at a black screen, at which point text consoles (CTRL-ALT-F1 etc) are no longer responsive either.  Only option at this point is to force a power-off-restart. Often (about 50% of the time) this first restart also fails to boot cleanly, and fails to get as far as the greeter screen. However, CTRL-ALT-F1 etc are active at this point, and the system appears to be up, just NOT the graphical subsystem. A further reboot from one of the text consoles *usually* (but not always) brings up the system cleanly.

  (b) System will sometimes apparently power off during suspend. Suspend
  appears to work correctly, but on returning to the system some time
  later, the system will be powered completely off.

  In both cases, the use of a docking station appears to exacerbate the
  problem (so, suspending in the docking station, then removing the
  laptop from the dock, and then resuming *seems* to increase the
  likelihood of (a), and suspending off the docking station, plugging
  back into the dock *seems* to increase the likelihood of (b)).

  I'm on the latest Lenovo BIOS, and all OS fixes/updates are applied.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-15-generic
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from resuming properly.
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  richard    2575 F.... pulseaudio
  CurrentDmesg:
   [   14.401329] init: plymouth-stop pre-start process (1774) terminated with status 1
   [   15.937910] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
   [   15.937970] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  Date: Sat Jan 11 10:01:33 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  ExecutableTimestamp: 1386693790
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=a1896162-7e68-42e3-9cec-5835e1aedd0f
  InstallationDate: Installed on 2014-01-03 (8 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
  InterpreterPath: /usr/bin/python3.3
  MachineType: LENOVO 3626AZ8
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcCwd: /
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=/dev/mapper/Ubuntu-RootVol ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/1f199eb6-b2ad-4014-9f8d-41954bf1a417,lvm=Ubuntu quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware                             1.116
  SourcePackage: linux
  Title: [LENOVO 3626AZ8] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626AZ8
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:svnLENOVO:pn3626AZ8:pvrThinkPadX201:rvnLENOVO:rn3626AZ8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3626AZ8
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268113/+subscriptions