This bug was fixed in the package linux - 2.6.35-28.50
---
linux (2.6.35-28.50) maverick-proposed; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #734399
[ Corentin Chary ]
* SAUCE: (drop after 2.6.38) eeepc-wmi: reorder keymap
- LP: #689393
* SAUCE: (drop
Stefan, your workaround would almost be acceptable if this were the only
bug in play. However, for those of us booting Maverick AMIs for PV-
grub, and then using cloud-init to auto-downgrade the kernel to Karmic's
or auto-upgrade to Natty's (because let's face it, so far Lucid and
Maverick have ye
I am using another VPS provider using Xen and after I did a 10.04 to 10.10
upgrade last week I ran into this issue of reboot's hanging. Today I enabled
proposed and pulled in a few updates and reboot's are working with
linux-image-2.6.35-28-virtual (2.6.35-28.50 Ubuntu:10.10/maverick-proposed
Reboot works timely again and halt moves the session into terminated as
expected.
** Tags added: verification-done-maverick
** Tags removed: verification-needed-maverick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed'
to 'verification-done'.
If verification is not done by one week from today, this fix will b
** Branch linked: lp:ubuntu/lucid-proposed/linux-lts-backport-maverick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727814
Title:
[Maverick] Reboot of linux-virtual hangs on EC2
--
ubuntu-bugs ma
There is kind of a workaround (though slow). The reboot must be
initiated from outside (either the web interface or the ami tools ec2
-reboot-instances) and one has to wait 5 minutes in that case (this is a
timeout of the xen commands). After that the instance comes up again.
--
You received this
Anyone have a userland workaround (other than ec2-reboot-instances of own
instance-id, which requires auth keys on the node...) for getting an ec2 node
on these kernels to reboot itself successfully?
Also: note that once we have a release kernel w/ the fix, new Maverick
AMIs will have to go out
** Changed in: linux (Ubuntu Maverick)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727814
Title:
[Maverick] Reboot of linux-virtual hangs on EC2
--
ub
** Patch added: "Proposed fix"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/727814/+attachment/1880885/+files/0001-xen-don-t-bother-to-stop-other-cpus-on-shutdown-rebo.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Does not affect Natty as fix was added with 2.6.37-rc1.
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
** Changed in: linux (Ubuntu)
Assignee: Stefan Bader (stefan-bader-canonical) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bug
11 matches
Mail list logo