kernel-packages team mailing list archive

[Bernie Innocenti <bernie@xxxxxxxxxxx>]

On 08/14/2013 03:40 PM, Joseph Salisbury wrote:
> I'd like to perform a bisect to figure out what commit caused this
> regression. We need to identify the earliest kernel where the issue
> started happening as well as the latest kernel that did not have this
> issue.
> 
> Can you test the following kernels and report back? We are looking for
> the first kernel version that exhibits this bug:
> 
> v3.8 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-raring
> v3.9 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-saucy
> v3.10 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-saucy
> v3.11-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/

Tested with 3.11.0-2-generic: works.

*however*, I had to take care to manually select the same kernel I was
running at hibernation time in the Grub boot menu.

This may be what happened last time: a new kernel got installed, then I
hibernated my machine and grub picked the new kernel.

In Fedora, when you hibernate your system, on the next boot grub skips
the menu and automatically boots the same kernel that was used before.

Additionally, I feel that the user should be shown an error message when
dehibernation failed. I was puzzled when I got a lightdm login screen
instead of my old session.

-- 
 _ // Bernie Innocenti
 \X/  http://codewiz.org

-- 
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/1212266

Title:
  [LENOVO 4291AK7] hibernate/resume failure

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I typed pm-hibernate in a terminal.Hibernation appeared to work just
  fine, but aAfter powering up the system, it just booted into a new
  session.

  Hibernate used to work with raring on the same hardware. Note that my
  /home filesystem is a luks volume.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-2-generic 3.11.0-2.5
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  Annotation: This occured during a previous hibernate and prevented it from resuming properly.
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  bernie     2377 F.... pulseaudio
  Date: Wed Aug 14 09:45:17 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=128962f7-fa8f-448f-99ff-95bf45f8c7b2
  InterpreterPath: /usr/bin/python3.3
  MachineType: LENOVO 4291AK7
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=f77eb20c-0808-4845-b5a2-30c0475683a9 ro quiet splash resume=LABEL=swap pcie_aspm=force vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-2-generic N/A
   linux-backports-modules-3.11.0-2-generic  N/A
   linux-firmware                            1.113
  SourcePackage: linux
  Title: [LENOVO 4291AK7] hibernate/resume failure
  UpgradeStatus: Upgraded to saucy on 2013-07-03 (41 days ago)
  UserGroups: pkcs11
  dmi.bios.date: 07/19/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET63WW (1.33 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291AK7
  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:bvr8DET63WW(1.33):bd07/19/2012:svnLENOVO:pn4291AK7:pvrThinkPadX220:rvnLENOVO:rn4291AK7:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4291AK7
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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