[Xen-users] "BUG: soft lockup detected on CPU#n", results in very slow domU's

[Rink Springer <mail@xxxxxxx>]

Hello,

Recently, I've installed Xen 3.2 (fresh from Mercurial) on a Compaq
Proliant DL580 machine with 4x 700MHz Pentium III Xeon CPU's and 4GB of
RAM. However, whenever I boot Xen, I see the following messages in my
dom0's dmesg:

BUG: soft lockup detected on CPU#3!
 [<c0151479>] softlockup_tick+0x99/0xe0
 [<c010990a>] timer_interrupt+0x30a/0x6e0
 [<c0130244>] __mod_timer+0xa4/0xd0
 [<ee084c5a>] e100_watchdog+0x1aa/0x3e0 [e100]
 [<c013066c>] run_timer_softirq+0x3c/0x1f0
 [<c01517f3>] handle_IRQ_event+0x33/0xb0
 [<c0151913>] __do_IRQ+0xa3/0x120
 [<c010779f>] do_IRQ+0x3f/0xa0
 [<c024c4f5>] evtchn_do_upcall+0xc5/0x1e0
 [<c0105c0d>] hypervisor_callback+0x3d/0x45
 [<c0108edb>] raw_safe_halt+0x9b/0x110
 [<c01047a9>] xen_idle+0x29/0x60
 [<c01036e1>] cpu_idle+0x71/0xd0
BUG: soft lockup detected on CPU#1!
 [<c0151479>] softlockup_tick+0x99/0xe0
 [<c010990a>] timer_interrupt+0x30a/0x6e0
 [<c0130100>] lock_timer_base+0x20/0x50
 [<ee0b5380>] e1000_watchdog+0x0/0x6e0 [e1000]
 [<c0130244>] __mod_timer+0xa4/0xd0
 [<c013066c>] run_timer_softirq+0x3c/0x1f0
 [<c01517f3>] handle_IRQ_event+0x33/0xb0
 [<c0151913>] __do_IRQ+0xa3/0x120
 [<c010779f>] do_IRQ+0x3f/0xa0
 [<c024c4f5>] evtchn_do_upcall+0xc5/0x1e0
 [<c0105c0d>] hypervisor_callback+0x3d/0x45
 [<c0108edb>] raw_safe_halt+0x9b/0x110
 [<c01047a9>] xen_idle+0x29/0x60
 [<c01036e1>] cpu_idle+0x71/0xd0
BUG: soft lockup detected on CPU#3!
 [<c0151479>] softlockup_tick+0x99/0xe0
 [<c010990a>] timer_interrupt+0x30a/0x6e0
 [<c011d629>] __wake_up_common+0x39/0x70
 [<c013066c>] run_timer_softirq+0x3c/0x1f0
 [<c01517f3>] handle_IRQ_event+0x33/0xb0
 [<c0151913>] __do_IRQ+0xa3/0x120
 [<c010779f>] do_IRQ+0x3f/0xa0
 [<c024c4f5>] evtchn_do_upcall+0xc5/0x1e0
 [<c0105c0d>] hypervisor_callback+0x3d/0x45
 [<c0108edb>] raw_safe_halt+0x9b/0x110
 [<c01047a9>] xen_idle+0x29/0x60
 [<c01036e1>] cpu_idle+0x71/0xd0
BUG: soft lockup detected on CPU#2!
 [<c0151479>] softlockup_tick+0x99/0xe0
 [<c010990a>] timer_interrupt+0x30a/0x6e0
 [<c011ea21>] try_to_wake_up+0x41/0x380
 [<c01517f3>] handle_IRQ_event+0x33/0xb0
 [<c0151913>] __do_IRQ+0xa3/0x120
 [<c013e6c6>] ktime_get+0x16/0x40
 [<c010779f>] do_IRQ+0x3f/0xa0
 [<c024c4f5>] evtchn_do_upcall+0xc5/0x1e0
 [<c0105c0d>] hypervisor_callback+0x3d/0x45
 [<c0108edb>] raw_safe_halt+0x9b/0x110
 [<c01047a9>] xen_idle+0x29/0x60
 [<c01036e1>] cpu_idle+0x71/0xd0

The result is that whenever I launch a domU, it regularly freezes until
I hit some key; for example, holding spacebar allows the domU to boot,
otherwise it just pauses during startup scripts :-(

I've seen this behaviour with Xen 3.0, 3.1 and 3.2; I'm using Debian 4.0
with self-built Xen 3.2, which runs kernel 2.6.18.8-xen.

Does anyone have a clue what is going on? The machine works fine without
a Xen kernel...

Regards,

-- 
Rink P.W. Springer                                - http://rink.nu
"Anyway boys, this is America. Just because you get more votes doesn't
 mean you win." - Fox Mulder

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users