ec2 kernel hang on XENBUS: Waiting for devices to initialize

Bug #660163 reported by Scott Moser on 2010-10-13
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

Today was the first time I've seen this bug.

I launched a t1.micro instance and was unable to ssh to it. Checking the console log showed:
[ 0.216369] lo: Disabled Privacy Extensions^M
[ 0.216682] NET: Registered protocol family 17^M
[ 0.216795] registered taskstats version 1^M
[ 5.310016] XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...

It did not respond to a reboot-instances, and hung in shutting-down on 'terminate-instances' request.

instance was launched at '2010-10-13T17:21:33.000Z' it is now 20:11:24, so plenty of time was given for that apparent last 120s.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-virtual 2.6.35-22.33
Regression: No
Reproducible: No
ProcVersionSignature: User Name 2.6.35-22.33-virtual
Uname: Linux 2.6.35-22-virtual x86_64
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
 [ 202.405066] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
 [ 202.413498] SGI XFS Quota Management subsystem
 [ 202.656020] Btrfs loaded
Date: Wed Oct 13 19:44:19 2010
Ec2AMI: ami-548c783d
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1d
Ec2InstanceType: t1.micro
Ec2Kernel: aki-427d952b
Ec2Ramdisk: unavailable
Frequency: Once a month.

Lsusb: Error: command ['lsusb'] failed with exit code 1:
ProcCmdLine: root=LABEL=uec-rootfs ro console=hvc0
 PATH=(custom, user)
SourcePackage: linux

Scott Moser (smoser) wrote :
Jeremy Foshee (jeremyfoshee) wrote :

Hi Scott,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Scott Moser (smoser) wrote :

testing upstream is non-trivial on ec2. additionally the rarity of which it occurs would prove nothing.

Changed in linux (Ubuntu):
importance: Undecided → Low
status: Incomplete → New
Changed in linux (Ubuntu):
status: New → Triaged

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

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

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers