I've had domU's hickup a few times with latest unstable, and I guess this can 
be expected. Is there a procedure in place to report these problems?
For exampe:
Unable to handle kernel paging request at virtual address c12b46c0
 printing eip: cpanel cpanel.mydomain
c02555f7
*pde = ma 7e9fc067 pa 00002067
*pte = ma 00000000 pa 55555000
Oops: 0002 [#1]
PREEMPT SMP
Modules linked in:
CPU: 0
EIP: 0061:[<c02555f7>] Not tainted VLI
EFLAGS: 00010212 (2.6.12.6-xenU)
EIP is at netif_poll+0x337/0x760
eax: c12b46c0 ebx: c11ba580 ecx: c12b405e edx: c12b46c0
esi: c033fecc edi: c12b4000 ebp: c11ba580 esp: c033fe9c
ds: 007b es: 007b ss: 0069
Process swapper (pid: 0, threadinfo=c033e000 task=c0302200)
Stack: ffffffff 00000119 c010cc1c 00000001 00000000 00000001 00000040 00000001
 00000001 000016af 000016af c127a240 c033fecc c033fecc 00000000 00000001
 00000000 c127a2bc c127a240 00000000 c127a104 c127a000 c033e000 c033e000
Call Trace:
 [<c010cc1c>] timer_interrupt+0x1ac/0x2b0
 [<c026288d>] net_rx_action+0x14d/0x230
 [<c012599a>] __do_softirq+0xaa/0x160
 [<c0125ad5>] do_softirq+0x85/0xa0 1,1 
All
 [<c0125be5>] irq_exit+0x45/0x50
 [<c010eb52>] do_IRQ+0x22/0x30
 [<c0104a10>] evtchn_do_upcall+0x90/0x100
 [<c010a310>] hypervisor_callback+0x2c/0x34
 [<c0107b86>] xen_idle+0x56/0xd0
 [<c0107c63>] cpu_idle+0x63/0xc0
 [<c03409e8>] start_kernel+0x1b8/0x210
 [<c0340320>] unknown_bootoption+0x0/0x240
Code: 8b 95 94 00 00 00 39 d1 0f 87 b1 01 00 00 8b 85 8c 00 00 00 8b bd 88 00 
00 00 29 f8 83 f8 0f 0f 8e 9a 01 00 00 8b 83 94 00 00 00 <c7> 00 01 00 00 00 
8b 83 94 00 00 00 c7 40 04 00 00 00 00 8b 83
 <0>Kernel panic - not syncing: Fatal exception in interrupt
Kind Regards,
-- 
Ian P. Christian ~ http://pookey.co.uk

Attachment: pgprNZd5v1as0.pgp
Description: PGP signature

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