|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] Help Debugging a Crash on PV DomU Creation
I've got a system that's been acting up over the last few days-- it would
automatically reboot after I loaded a VM. After playing around with it, I've
guessed that the crash occurs when I hit a certain threshold of vCPUs.
After they released me from the hospital, I hit the rack and got a Xen debug
from the terminal server, which follows.
The system itself is a dual Opteron 8356 (so, 8 cores) with 12G of RAM in a
Tyan board. I'm running Arch Linux on both dom0 and most of the domUs, with a
single NetBSD install for PF.
I'm going to start by nailing a CPU to the dom0, something I've been planning
on doing for a while in any case. If that doesn't help, I'll be upgrading the
packages and the dom0 kernel. The CPU which locks up seems to change every
time, so I don't think disabling a core or puling one of the processors would
help, but I may try it.
I guess if someone can take a look at this and see if it looks like something
software or hardware related, even in a vague sense, that would go a long way
toward pointing me in the right direction.
Thanks!
--------
close blk: backend=/local/domain/0/backend/vbd/7/51713 node=device/vbd/51713
close blk: backend=/local/domain/0/backend/vbd/7/51714 node=device/vbd/51714
go!
mapping kernel into physical memory
about to get started...
(XEN) traps.c:2502:d7 Domain attempted WRMSR 00000000c0010004 from
0x0000f802b979638a to 0x000000000000abcd.
(XEN) grant_table.c:1159:d7 Expanding dom (7) grant table from (4) to (5)
frames.
(XEN) grant_table.c:1159:d7 Expanding dom (7) grant table from (5) to (6)
frames.
(XEN) Assertion '!in_atomic()' failed at softirq.c:61
(XEN) ----[ Xen-4.2-unstable x86_64 debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: e008:[<ffff82c480122874>] do_softirq+0xd/0x28
(XEN) RFLAGS: 0000000000010202 CONTEXT: hypervisor
(XEN) rax: 0000000000000001 rbx: ffff8300bfcdf000 rcx: 0000000000000000
(XEN) rdx: ffff82c4802d86a0 rsi: 0000000000000000 rdi: 0000000000000001
(XEN) rbp: ffff82c48029ff08 rsp: ffff82c48029ff08 r8: 00000000deadbeef
(XEN) r9: 00000000deadbeef r10: 00000000deadbeef r11: 0000000000000246
(XEN) r12: ffffffff815449e8 r13: ffffffff8149bfd8 r14: ffffffffffffffff
(XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000006f0
(XEN) cr3: 0000000128d6e000 cr2: ffff880002daca78
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008
(XEN) Xen stack trace from rsp=ffff82c48029ff08:
(XEN) 00007d3b7fd600c7 ffff82c4802148a6 0000000000000000 ffffffffffffffff
(XEN) ffffffff8149bfd8 ffffffff815449e8 ffffffff8149bed0 ffffffff8149a000
(XEN) 0000000000000246 0000000100002706 0000000000000000 0000000000000000
(XEN) 0000000000000000 ffffffff810093aa 0000000000000000 00000000deadbeef
(XEN) 00000000deadbeef 0000010000000000 ffffffff810093aa 000000000000e033
(XEN) 0000000000000246 ffffffff8149beb8 000000000000e02b 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) ffff8300bfcdf000 0000000000000000 0000000000000000
(XEN) Xen call trace:
(XEN) [<ffff82c480122874>] do_softirq+0xd/0x28
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Assertion '!in_atomic()' failed at softirq.c:61
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
Press <SpaceBar> to update BIOS.
--
Sam Mulvey
Tacoma Telematics
sam@xxxxxxxxxxxxxxxxxxxx
(253) 883-3030 x110
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |