This bug report was marked as Incomplete and has not had any updated
comments for quite some time. As a result this bug is being closed.
Please reopen if this is still an issue in the current Ubuntu release
http://www.ubuntu.com/getubuntu/download . Also, please be sure to
provide any requested in
It seems that the same problem existed for Windows HVM guests:
http://old.nabble.com/BSOD-%22A-clock-interrupt-was-not-recevied-ona-
secondary-processor-within-the-allocated-time-
interval%22-td21200747.html
A solution could possibly be to disable the cpu watchdog timer, but I
have not tested it
This bug persists - ubuntu 8.04.3 running on xenserver 5.5u1
interestingly the bug only happens on i386 machines (system completely up2date
with full-upgrade), the amd64 machines don't crash - at least for several days
now they didn't.
--
xen dom0 crashes with "BUG: soft lockup - CPU#0 stuck fo
This bug persists in the latest 2.6.24-24-xen kernel package that was
recently released for Hardy running in a domU on an Intel Xeon CPU
L5335.
I can provoke the crash by downloading something with wget that pins the
ethernet interface.
--
xen dom0 crashes with "BUG: soft lockup - CPU#0 stuck fo
This is not a bug in the linux-meta package, moving to the linux
package.
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
--
xen dom0 crashes with "BUG: soft lockup - CPU#0 stuck for 11s!"
https://bugs.launchpad.net/bugs/238549
You received this bug notification because you are a membe
My workarround is: Dont use 2.6.24. Im now using Xen 3.3.1 + Linux
2.6.27-hg (From HG repository) and i dont have any kind of problems with
Xen now (Even DMRAID over Xen, now works well).
--
xen dom0 crashes with "BUG: soft lockup - CPU#0 stuck for 11s!"
https://bugs.launchpad.net/bugs/238549
You
I'm having the same problems with linux 2.6.24-23-xen on a dual P4 Xeon
system in my dom0.
Apart from the amd64 kernel, has anybody found a workaround for this
bug?
--
xen dom0 crashes with "BUG: soft lockup - CPU#0 stuck for 11s!"
https://bugs.launchpad.net/bugs/238549
You received this bug not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This problem does not appear in same hardware reported by me when i
use Debian Lenny dom0 with Xen 3.3.1 and kernel 2.6.27 hg version.
Maybe a version issue?
Fran Boon escreveu:
> ** Attachment added: "lspci-vvnn.log.bz2"
>http://launchpadlibraria
** Attachment added: "lspci-vvnn.log.bz2"
http://launchpadlibrarian.net/23302922/lspci-vvnn.log.bz2
--
xen dom0 crashes with "BUG: soft lockup - CPU#0 stuck for 11s!"
https://bugs.launchpad.net/bugs/238549
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
I have the same problem in my DomUs (Dom0 is fine).
I need to destroy/create the VMs to recover.
Host:
# uname -a
Linux sahana 2.6.24-23-xen #1 SMP Mon Jan 26 03:12:59 UTC 2009 i686 GNU/Linux
Guests:
# uname -a
Linux sahana1 2.6.24-23-xen #1 SMP Mon Jan 26 03:12:59 UTC 2009 i686 GNU/Linux
dmesg.
I have a Dell 6650 running whatever the latest xen server image is (and
I run update/upgrade/dist-upgrade frequently). One DomU locks up pretty
regularly with "BUG: soft lockup - CPU#1 stuck for 11s!", usually during
large file transfers. DomU Kernel version is 2.6.24-19. The bug
*requires* destroy
In my case is domU which is crashing.
It's a fresh Ubuntu server install with kernel is 2.6.24-21-xen and the
hardware is a Xeon Core Duo (cpuinfo attached).
Also tried to disable AppArmor but still the same problem.
It's interesting that I have two domU running (one for mysql and other for
apa
I have been getting the same crash on a Pentium D machine running kernel
2.6.24-19-xen when I try to start a domU using 'xm create'. I have just
stopped AppArmor and 'xm create' no longer causes the crash.
It may be worth testing with AppArmor not running on the dom0.
--
xen dom0 crashes with "B
James Troup (Canonical IS) reports that using an amd64 dom0 kernel works
around the problem.
--
xen dom0 crashes with "BUG: soft lockup - CPU#0 stuck for 11s!"
https://bugs.launchpad.net/bugs/238549
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
See https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/259487
(duplicate i think).
This is really a bad problem and needs to be addressed very very soon..
--
xen dom0 crashes with "BUG: soft lockup - CPU#0 stuck for 11s!"
https://bugs.launchpad.net/bugs/238549
You received this bug notifi
Like https://bugs.launchpad.net/bugs/240903 im reporting here my
hardware too.
** Attachment added: "lshw"
http://launchpadlibrarian.net/16927988/lshw.txt
--
xen dom0 crashes with "BUG: soft lockup - CPU#0 stuck for 11s!"
https://bugs.launchpad.net/bugs/238549
You received this bug notificati
Like https://bugs.launchpad.net/bugs/240903 im reporting here my
hardware too.
** Attachment added: "lshw"
http://launchpadlibrarian.net/16927987/lshw.txt
--
xen dom0 crashes with "BUG: soft lockup - CPU#0 stuck for 11s!"
https://bugs.launchpad.net/bugs/238549
You received this bug notificati
** Attachment added: "version.log"
http://launchpadlibrarian.net/16686403/version.log
--
xen dom0 crashes with "BUG: soft lockup - CPU#0 stuck for 11s!"
https://bugs.launchpad.net/bugs/238549
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Attachment added: "uname-a.log"
http://launchpadlibrarian.net/16686400/uname-a.log
--
xen dom0 crashes with "BUG: soft lockup - CPU#0 stuck for 11s!"
https://bugs.launchpad.net/bugs/238549
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/16686399/lspci-vvnn.log
--
xen dom0 crashes with "BUG: soft lockup - CPU#0 stuck for 11s!"
https://bugs.launchpad.net/bugs/238549
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
One Athlon64.
** Attachment added: "cpuinfo.log"
http://launchpadlibrarian.net/16686394/cpuinfo.log
--
xen dom0 crashes with "BUG: soft lockup - CPU#0 stuck for 11s!"
https://bugs.launchpad.net/bugs/238549
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
I think I may have seen the same bug. At least, the Xen dom0 will
occasionally completely freeze up. Moving the mouse does not cause the
cursor to move in X11, pressing keys doesn't produce any visible result
(in X11 or console), ssh sessions freeze up (to host and guest), other
services are not r
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
does not yet have enough information.
Please include the following additional information, if you have not already
done so (pay attention to lspci's addition
I can confirm this bug with 2.6.24-18-xen and 2.6.24-19-xen on a late
Pentium D. It usually happens within two days of runtime when the
system is loaded. My cpuinfo is attached.
This glitch on my computer usually trashes I/O and results in several
"faulty removed" components in MD arrays.
** A
By the way, no problem with 2.6.18-generic
--
xen dom0 crashes with "BUG: soft lockup - CPU#0 stuck for 11s!"
https://bugs.launchpad.net/bugs/238549
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
sorry, 2.6.24-18-generic
--
xen dom0 crashes with "BUG: soft lockup - CPU#0 stuck for 11s!"
https://bugs.launchpad.net/bugs/238549
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
26 matches
Mail list logo
