Re: recent dom0 kernels reboot on loading?

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Fri, Aug 31, 2007 at 04:02:27PM +0300, Mikolaj Golub wrote:
> 
> May be this will be helpful for resolving the issue.... Booting xen kernel
> with serial console and DOM0 with vga, I get at serial console:
> 
> (XEN) Xen is relinquishing VGA console.                                      
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to 
> Xen).
> (XEN) traps.c:390:d0 Unhandled general protection fault fault/trap [#13] in 
> domain 0 on VCPU 0 [ec=0000]
> (XEN) domain_crash_sync called from entry.S (ff16a0fd)        
> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:                     
> (XEN) ----[ Xen-3.1.0  x86_32  debug=y  Not tainted ]----     
> (XEN) CPU:    0                                               
> (XEN) EIP:    e019:[<c04d4f84>]                               
> (XEN) EFLAGS: 00000246   CONTEXT: guest                       
> (XEN) eax: c0964264   ebx: 000003cf   ecx: 00000001   edx: c0964264
> (XEN) esi: 00000000   edi: c0964260   ebp: c0a66b0c   esp: c0a66ad0
> (XEN) cr0: 8005003b   cr4: 000006d0   cr3: 1ea63000   cr2: 00000000
> (XEN) ds: e021   es: e021   fs: 0000   gs: 0000   ss: e021   cs: e019
> (XEN) Guest stack trace from esp=c0a66ad0:

Next would be to find where 0xc04d4f84 is in the kernel. The easiest is to
build a kernel with makeoptions    DEBUG="-g",
reboot with it a see what the EIP is when it crash. Then use
gdb on netbsd.gdb to get the source info:
list *0xc04d4f84 (or whatever EIP is when the debug kernel crash).


-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--