precise kernels do not boot on ec2 without idle=halt
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Stefan Bader |
Bug Description
I tried booting a precise kernel today on EC2, and heres what I found, considering
the ubuntu-
$ dpkg -S /boot/vmlinuz-
linux-image-
PASS: amd64 | inst | m1.large
FAIL: amd64 | ebs_ | m1.large
FAIL: amd64 | ebs_ | t1.micro
FAIL: i386__| inst | m1.small
FAIL: i386__| ebs_ | t1.micro
Thats all I bothered testing. I'll attach the successful log and as many logs as I can, but some of them produced empty console output.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-
ProcVersionSign
Uname: Linux 3.1.0-1-virtual x86_64
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Oct 24 19:49 seq
crw-rw---- 1 root audio 116, 33 Oct 24 19:49 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 1.24-0ubuntu1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
CurrentDmesg: [13893341.485666] eth0: no IPv6 routers present
Date: Mon Oct 24 20:04:00 2011
Ec2AMI: ami-db2ae5b2
Ec2AMIManifest: ubuntu-
Ec2Availability
Ec2InstanceType: m1.large
Ec2Kernel: aki-825ea7eb
Ec2Ramdisk: unavailable
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: root=LABEL=
ProcModules: acpiphp 24080 0 - Live 0x0000000000000000
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
- Ben Howard (community): Approve
- Diff: 0 lines
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
status: | Incomplete → Confirmed |
Changed in linux (Ubuntu): | |
assignee: | nobody → Stefan Bader (stefan-bader-canonical) |
status: | Confirmed → Triaged |
summary: |
- precise kernels do not boot on ec2 + precise kernels do not boot on ec2 without idle=halt |
t1.micro log of failed boot at: http:// paste.ubuntu. com/718188/
My failed boots did not produce console output even after reboot or terminate.