Re: Xen3 domU functionnal

[Stephane Bortzmeyer <stephane%sources.org@localhost>]

On Fri, Mar 24, 2006 at 08:57:34PM +0100,
 Stephane Bortzmeyer <stephane%sources.org@localhost> wrote 
 a message of 63 lines which said:

> xbd0 at xenbus0 id 769: Xen Virtual Block Device Interface
> panic: kernel diagnostic assertion "(flags & UVM_KMF_TYPEMASK) == 
> UVM_KMF_WIRED || (flags & UVM_KMF_TYPEMASK) == UVM_KMF_PAGEABLE || (flags & 
> UVM_KMF_TYPEMASK) == UVM_KMF_VAONLY" failed: file 
> "/Volumes/data/bouyer/current/src/sys/uvm/uvm_km.c", line 525
> Stopped in pid 2.1 (xenbus_probe) at    netbsd:cpu_Debugger+0x4:        popl  
>   %
> ebp
> db> 

This crash is when I use the ordinary image (not the INSTALL one). 

xm info says:

system                 : Linux
host                   : aslan
release                : 2.6.12.6-xen0
version                : #1 Sun Dec 4 22:21:21 GMT 2005
machine                : i686
nr_cpus                : 1
nr_nodes               : 1
sockets_per_node       : 1
cores_per_socket       : 1
threads_per_core       : 1
cpu_mhz                : 231
hw_caps                : 0080f9ff:00000000:00000000:00000040
total_memory           : 192
free_memory            : 15
xen_major              : 3
xen_minor              : 0
xen_extra              : .0
xen_caps               : xen-3.0-x86_32
platform_params        : virt_start=0xfc000000
xen_changeset          : Sun Dec  4 17:24:24 2005 +0100 8240:64cd054aa143
cc_compiler            : gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7)
cc_compile_by          : xenod
cc_compile_domain      : cl.cam.ac.uk
cc_compile_date        : Sun Dec  4 20:20:45 GMT 2005

The debugger says:

db> ps  
 PID           PPID     PGRP        UID S   FLAGS LWPS          COMMAND    WAIT
 5                0        0          0 2 0x20200    1           xenbus        
 4                0        0          0 2 0x20200    1         xenwatch   evtsq
 3                0        0          0 2 0x20200    1        cryptoret crypto_
>2                0        0          0 2 0x20200    1     xenbus_probe        
 1                0        0          0 2 0x20000    1             init initexe
 0               -1        0          0 2 0x20200    1          swapper  cfpend
db> trace                                                                      
cpu_Debugger(c0402bc6,c624fd88,0,c02a5705,0) at netbsd:cpu_Debugger+0x4
panic(c0433240,c03f2e90,c041ec00,c041e920,20d) at netbsd:panic+0x12c   
__assert(c03f2e90,c041e920,20d,c041ec00,c624fdec) at netbsd:__assert+0x2e
uvm_km_alloc(c0452960,1000,0,10,c071a038) at netbsd:uvm_km_alloc+0x20a   
xbd_xenbus_resume(c071a000,c071a000,c624fef4,c03983f4,0) at netbsd:xbd_xenbus_re
sume+0x3c                                                                       
config_attach_loc(c06ddec0,c04356a0,0,c624fef4,c03978f0) at netbsd:config_attach
_loc+0x35c                                                                      
config_found_ia(c06ddec0,c03f23e0,c624fef4,c03978f0,c0672ca8) at netbsd:config_f
ound_ia+0x32                                                                    
xenbus_probe_device_type(c043e868,c0672ca8,c03ff419,c624ff38,c624ff3c) at netbsd
:xenbus_probe_device_type+0x122                                                 
xenbus_probe_devices(c043e868,0,c0403c6f,0,0) at netbsd:xenbus_probe_devices+0x7
2                                                                               
xenbus_probe(0,0,0,c01004ae,c5a0be70) at netbsd:xenbus_probe+0x20
xenbus_probe_init(c5a0be70,4f8000,c0502000,0,c01001cc) at netbsd:xenbus_probe_in
it+0x66                                                                         

Do you want other information from the debugger? (I'm very poor and
very green at kernel debugging.)