kernel-packages team mailing list archive

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

Ian Turner, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the working kernel from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

** Tags added: needs-kernel-logs

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

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

Title:
  Problems booting with linux-image-3.2.0-49-generic

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hi, starting from linux-image-3.2.0-49-generic, my system no longer
  boots. Reverting to 3.2.0-45-generic works fine.

  In recovery mode, the hang happens just after "unable to access resume
  device /dev/dm-4" -- this message is actually expected since my swap
  partition is random-key encrypted. Even in recovery mode, the console
  hangs at this point, I can't press ENTER to force the system to boot
  or otherwise interact with the console.

  System: Ubuntu 12.04.2 LTS
  Hardware: ASUS K53SV, Intel i7-2630QM

  Storage layout:
  /dev/sda -> Main hard disk
  /dev/sda1 -> Factory Windows recovery partition
  /dev/sda2 -> LVM physical volume for volume group "internal"
  /dev/dm-0 AKA /dev/mapper/internal-boot -> Boot device
  /dev/dm-1 AKA /dev/mapper/internal-root -> Encrypted device for root filesystem
  /dev/dm-2 AKA /dev/mapper/internal-swap -> Encrypted device for swap (random key)
  /dev/dm-3 AKA /dev/mapper/internal-root_crypt -> Plaintext of /dev/dm-1 for root filesystem, mounted on /
  /dev/dm-4 AKA /dev/mapper/internal-swap_crypt -> Plaintext of /dev/dm-2 for swap

  I've marked this as "linux", but it could also be a problem with
  initramfs-tools (although that wasn't upgraded recently, AFAICT).

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