Linux-Kernel 3.9.0-0.4 doen't boot

[Thomas Schweikle]

Kernel 3.9.0-0.4 as found in linux-image-3.9.0-0-generic doesn't boot. It hangs right after grub transfers control.

Older kernel do boot. This is the very same as found in fedora or others trying to use the 3.9.y-Series of kernels. They hang, right after grub transfered control.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-generic 3.9.0.0.1
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
AlsaDevices:
 total 0
 crw-rw---T 1 root audio 116, 1 Mai 7 11:25 seq
 crw-rw---T 1 root audio 116, 33 Mai 7 11:25 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.10-0ubuntu1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Tue May 7 11:32:26 2013
HibernationDevice: RESUME=UUID=11418218-bfa6-42d5-925e-2acecf18ac78
InstallationDate: Installed on 2012-12-12 (145 days ago)
InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
MachineType: VMware, Inc. VMware Virtual Platform
MarkForUpload: True
PciMultimedia:

ProcEnviron:
 TERM=screen-bce
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-19-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.108
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-02-11 (84 days ago)
dmi.bios.date: 07/02/2012
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2012:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

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

[Thomas Schweikle (tps)]

I've compiled and installed the plain vanilla kernel from kernel.org. As far as it is compiled with the same config-set as the ubuntu-saucy one it has the same problem – it doesn't boot. I've tried with default config (make defconfig) and did not have success either.
I've tested on
- VMware Workstation 9
- VMware Workstation 6
- VirtualBox 4
- KVM, QEMU

And on some real hardware:
- Acer TravelMate 6292
- HP 6200 Desktop Station
- HP Proliant
- Some Dell system equiped with an i7-Core from Intel and
- Some Dell system equiped with an AMD-Processor

In all cases: didn't matter booting from CD or HD, from SATA or IDE – system hangs as soon as grub transfers control to the loaded kernel. This is for all kernels 3.9.y and later! Kernels running on the very same hardware are 3.8.y or older. The latest beta of systemrescuecd (using 3.9.0-kernel as alternate one) doesn't boot if the alternate kernel (3.9.0) is selected, while booting with the standard kernel (build on 3.4.y).
Switching to UEFI doesn't solve the problem. These 3.9.y and younger ones won't boot (on the Dell systems I could try using UEFI).

[Joseph Salisbury (jsalisbury)]

The 3.10-rc2 kernel is now available. Can you test this kernel to see if it still exhibits this bug?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc2-saucy/

[Thomas Schweikle (tps)]

The latest kernels boot again.

[Joseph Salisbury (jsalisbury)]

Thanks for the update, Thomas. This bug should be fixed when Saucy is rebased to the upstream 3.10 kernel.

[Julian Wiedmann (jwiedmann)]

Thomas Schweikle,

could you please test if this issue has been resolved with the latest kernel available for saucy?

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]