uswsusp causes failed boots for particular disk configuration

Bug #1201167 reported by Ian Turner
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
uswsusp (Ubuntu)
Confirmed
Undecided
Unassigned

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).
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
 Home directory /home/vectro not ours.
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: vectro 3351 F.... pulseaudio
 /dev/snd/seq: timidity 2874 F.... timidity
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xdf600000 irq 46'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10ec0269,10431ac3,00100100 HDA:80862805,80860101,00100000'
   Controls : 25
   Simple ctrls : 12
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=f25f6ee9-424f-4333-89cd-777082da00d9
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4)
MachineType: ASUSTeK Computer Inc. K53SV
MarkForUpload: True
NonfreeKernelModules: bbswitch
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-44-generic root=/dev/mapper/internal-root_crypt ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-44.69-generic 3.2.44
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/vectro not ours.
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-44-generic N/A
 linux-backports-modules-3.2.0-44-generic N/A
 linux-firmware 1.79.9
StagingDrivers: rts5139 mei
Tags: precise staging
Uname: Linux 3.2.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 11/11/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K53SV.320
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: K53SV
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK53SV.320:bd11/11/2011:svnASUSTeKComputerInc.:pnK53SV:pvr1.0:rvnASUSTeKComputerInc.:rnK53SV:rvr1.0:cvnASUSTeKComputerInc.:ct9:cvr1.0:
dmi.product.name: K53SV
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

Ian Turner (vectro)
tags: added: boot
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1201167

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: precise
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: Problems booting with linux-image-3.2.0-49-generic

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.11 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/v3.11-rc1-saucy/

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: regression-update
Revision history for this message
Ian Turner (vectro) wrote :

Tested with linux-image-3.11.0-999-generic_3.11.0-999.201307240405_amd64.deb; issue was still present.

Ian Turner (vectro)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Revision history for this message
Ian Turner (vectro) wrote :

Still seeing this issue in the following packages:
linux-image-53-generic
linux-image-54-generic
linux-image-55-generic
linux-image-56-generic

Revision history for this message
penalvch (penalvch) wrote :

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
Revision history for this message
Ian Turner (vectro) wrote :

This is still an issue; the problem occurs with both linux-image-3.13.0-999-generic_3.13.0-999.201312270405 and linux-image-3.2.0-56-generic.

I tried booting today's trusty-desktop-amd64.iso, and the system did not boot (although seemingly not due to this specific issue). I got a message of, "The installer encountered an unrecoverable error", followed by a system hang. If you like I can open a separate bug for that problem.

tags: added: kernel-bug-exists-upstream-v3.11.0 kernel-bug-exists-upstream-v3.13.0
removed: needs-kernel-logs
Revision history for this message
Ian Turner (vectro) wrote : AcpiTables.txt

apport information

tags: added: apport-collected staging
description: updated
Revision history for this message
Ian Turner (vectro) wrote : AlsaDevices.txt

apport information

Revision history for this message
Ian Turner (vectro) wrote : AplayDevices.txt

apport information

Revision history for this message
Ian Turner (vectro) wrote : BootDmesg.txt

apport information

Revision history for this message
Ian Turner (vectro) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Ian Turner (vectro) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Ian Turner (vectro) wrote : Card0.Codecs.codec.3.txt

apport information

Revision history for this message
Ian Turner (vectro) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Ian Turner (vectro) wrote : IwConfig.txt

apport information

Revision history for this message
Ian Turner (vectro) wrote : Lspci.txt

apport information

Revision history for this message
Ian Turner (vectro) wrote : Lsusb.txt

apport information

Revision history for this message
Ian Turner (vectro) wrote : PciMultimedia.txt

apport information

Revision history for this message
Ian Turner (vectro) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Ian Turner (vectro) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Ian Turner (vectro) wrote : ProcModules.txt

apport information

Revision history for this message
Ian Turner (vectro) wrote : RfKill.txt

apport information

Revision history for this message
Ian Turner (vectro) wrote : UdevDb.txt

apport information

Revision history for this message
Ian Turner (vectro) wrote : UdevLog.txt

apport information

Revision history for this message
Ian Turner (vectro) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote : Re: Problems booting with linux-image-3.2.0-49-generic

Ian Turner, thank you for your comments. Could you please test the latest mainline (not the daily folder) via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc5-trusty/ and advise to the results?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-upstream-testing
removed: kernel-bug-exists-upstream kernel-bug-exists-upstream-v3.11.0 kernel-bug-exists-upstream-v3.13.0
tags: added: latest-bios-320
tags: added: needs-bisect
Revision history for this message
Ian Turner (vectro) wrote :

Apologies. With linux-image-3.13.0-031300rc5, the system fails to load init, so I'm unable to tell if this bug applies.

This is the console message I get trying to boot that kernel:

request-module: renaway loop modprobe binfmt-464c
Failed to execute /init (error -8)
Starting init: /bin/sh exists but couldn't execute it (error -8)
Kernel panic - not syncing: No working init found.

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-v3.13-rc5
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Ian Turner, thank you for performing the requested test. The next step would be to fully commit bisect from linux-image-3.2.0-45-generic to linux-image-3.2.0-49-generic in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-upstream-testing
removed: kernel-bug-exists-upstream
Revision history for this message
Ian Turner (vectro) wrote :

While trying to do the kernel bisect, I noticed that reinstalling 3.2.0-45-generic I saw the same bug. It turns out that this is not an issue with the linux kernel package at all, but rather with uswsusp. Removing the uswsusp package and rebuilding the initrd seems to solve the issue, even for 3.2.0-58-generic, so over to uswsusp.

affects: linux (Ubuntu) → uswsusp (Ubuntu)
Changed in uswsusp (Ubuntu):
status: Incomplete → New
summary: - Problems booting with linux-image-3.2.0-49-generic
+ uswsusp causes failed boots for particular disk configuration
penalvch (penalvch)
Changed in uswsusp (Ubuntu):
importance: High → Undecided
Steve Langasek (vorlon)
tags: removed: regression-update
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in uswsusp (Ubuntu):
status: New → Confirmed
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.