Since recent upgrade from kernel 3.5.0-26 to 3.5.0-27 my machine hangs very early in boot with hard drive activity leds flickering.
Booting back into -26 doesn't have the issue.
---
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC3: pieter 2555 F.... pulseaudio
/dev/snd/controlC0: pieter 2555 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 12.10
HibernationDevice: RESUME=UUID=381a20d3-7d8d-4e04-823f-e10f4165c98b
InstallationDate: Installed on 2012-03-10 (397 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
MachineType: Gigabyte Technology Co., Ltd. GA-MA780G-UD3H
MarkForUpload: True
Package: linux 3.5.0.27.43
PackageArchitecture: amd64
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-26-generic root=/dev/mapper/hostname-root ro rootflags=subvol=@ quiet splash
ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
RelatedPackageVersions:
linux-restricted-modules-3.5.0-26-generic N/A
linux-backports-modules-3.5.0-26-generic N/A
linux-firmware 1.95
RfKill:
Tags: quantal
Uname: Linux 3.5.0-26-generic x86_64
UpgradeStatus: Upgraded to quantal on 2012-10-24 (169 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
dmi.bios.date: 08/12/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F4
dmi.board.name: GA-MA780G-UD3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd08/12/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA780G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA780G-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA780G-UD3H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1168147
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.