[Xen-bugs] [Bug 119] run away, unkillable domain

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=119





------- Additional Comments From ryanh@xxxxxxxxxx  2005-07-28 15:46 -------
I left some doms running over night, 3 of 4 are 100% cpu:

root@bebop:/boot # xm list
Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)  Console
Domain-0           0      507    0      2   r----    117.4
debian_sarge_1     1      128    1      4   -----   7216.8     9601
debian_sarge_2     7      128    1      4   -----   8693.7     9607
debian_sarge_3     4      128    1      4   -b---      8.8     9604
debian_sarge_4     6      128    1      4   -----   1764.5     9606

And dumping the cpu state from serial conn:
(XEN) 'd' pressed -> dumping registers
(XEN) CPU:    1
(XEN) EIP:    0061:[<c02b0ddc>] ???
(XEN) EFLAGS: 00000246   CONTEXT: guest
(XEN) eax: 00000001   ebx: c0341504   ecx: 00000001   edx: 00000001
(XEN) esi: c03f4000   edi: 00000000   ebp: c03f5f64   esp: c03f5e74
(XEN) cr0: 8005003b   cr3: 20c5d000
(XEN) ds: 007b   es: 007b   fs: 0000   gs: 0000   ss: 0069   cs: 0061
(XEN) Guest stack trace from esp=c03f5e74:
(XEN)    c117fea0 c0349a00 c010cff1 c03f5f64 c0107f5d c03cc118 00000003 00000001
(XEN)    00000000 00000000 00000001 00000003 00d9ff60 c03f4000 35d56b6e 00000000
(XEN)    c010cfc8 c030b680 c1225aa0 c03c4020 c75a3f68 c02af987 c030b680 c02af9bc
(XEN)    00000002 c02afd8b c117fea0 c0349a00 00000000 c03f5f64 c013fe04 00000108
(XEN)    00000000 c03f5f64 00000000 00000108 00000108 c0349a00 00000000 c0349a1c
(XEN)    c013ff37 00000108 c03f4000 00000001 c117fea0 c03f5f64 00000000 fbf94000
(XEN)    00000040 00000000 c010f02d c01063e6 0000003f 00000040 00000001 c03f4000
(XEN)    c03f4000 00000000 c010a67c c03f5f64 00000001 00002010 000275de c03f4000
(XEN)    c03f4000 00000000 00000000 0000007b 0000007b 00000108 c0107f5d 00000061
(XEN)    00000286 c0373a00 00000000 c010802e c0373a00 00000002 01000800 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000

Running some of those addresses through System.map shows:

root@bebop:/boot # grep c02b0d *xenU*
System.map-2.6.12-xenU-smp:c02b0d30 T _write_trylock
System.map-2.6.12-xenU-smp:c02b0d70 T _spin_lock
System.map-2.6.12-xenU-smp:c02b0df0 T _spin_lock_irqsave
root@bebop:/boot # grep c010cf *xenU*
System.map-2.6.11.12-xenU-smp:c010cfa0 T destroy_context
System.map-2.6.12-xenU-smp:c010cfd0 T sched_clock
System.map-2.6.12-xenU-smp:c010cfe0 T timer_interrupt
root@bebop:/boot # grep c0107f *xenU*
System.map-2.6.12-xenU-smp:c0107f00 T disable_hlt
System.map-2.6.12-xenU-smp:c0107f10 T enable_hlt
System.map-2.6.12-xenU-smp:c0107f20 T xen_idle
System.map-2.6.12-xenU-smp:c0107fb0 T cpu_idle
root@bebop:/boot # grep c010cf *xenU*
System.map-2.6.11.12-xenU-smp:c010cfa0 T destroy_context
System.map-2.6.12-xenU-smp:c010cfd0 T sched_clock
System.map-2.6.12-xenU-smp:c010cfe0 T timer_interrupt




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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