3.2.0-20 fails to boot

Bug #963491 reported by Phil Wieland
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

3.2.0-17 works fine, but since the upgrade to 3.2.0-20 tyhe machine fails to boot, freezing with a blank screen.

Selecting 3.2.0-17 from the grub screen works fine.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-20-generic-pae 3.2.0-20.32
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.95-0ubuntu1
Architecture: i386
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.values: Error: command ['amixer', '-c', '0'] failed with exit code 1: amixer: Mixer hw:0 load error: Invalid argument
Date: Fri Mar 23 21:37:34 2012
HibernationDevice: RESUME=UUID=ce7bbd4f-f33e-4edc-8ca1-4e0c40590393
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Gigabyte Tecohnology Co., Ltd. H61M-S2PV
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic-pae root=UUID=5e8fddba-ff55-4437-ac7e-4664b8772518 ro quiet splash vt.handoff=7
RfKill:

SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/19/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FA
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-S2PV
dmi.board.vendor: INTEL Corporation
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Tecohnology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA:bd12/19/2011:svnGigabyteTecohnologyCo.,Ltd.:pnH61M-S2PV:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61M-S2PV:rvrx.x:cvnGigabyteTecohnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: H61M-S2PV
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Tecohnology Co., Ltd.

Revision history for this message
Phil Wieland (launchpad-philwieland) wrote :
Revision history for this message
Phil Wieland (launchpad-philwieland) wrote :

"blank screen" above is actually a plain purple wash.

Restarting in safe mode stops at

[0.624507] [<c15aeebe>] kernel_thread_helper + 0x6/0x10

Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-20.32)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: New → Confirmed
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-20.32
Revision history for this message
Phil Wieland (launchpad-philwieland) wrote :

I am reporting a failure with 3.2.0-20 which is the latest. Machine running on 3.2.0-17 in order to create report.

Changed in linux (Ubuntu):
status: Incomplete → 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.