Of course I updated my source tree since Ibuilt this kernel, so the stacktrace isn't so usefull. Can you try again with the kernel I've put at ftp://asim.lip6.fr/outgoing/bouyer/amd64/netbsd-INSTALL_XEN3_DOMU.gz thanks BTW, what is your hardware, Xen version and domU config ?
This machine had some hardware issues with memory. That can be source of my problems I thought that they are resolved, but nobody knows.
hardware: Processor is: cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 75 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ stepping : 2 cpu MHz : 2000.000 cache size : 512 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 fpu : yes fpu_exception : yes cpuid level : 1 wp : yesflags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm cr8_legacy
bogomips : 4038.90 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc Dmesg attached. XEN : # xm info host : xena2 release : 2.6.20.4version : #3 SMP Tue Apr 10 18:27:16 Local time zone must be set--see zic
machine : x86_64 nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 2009hw_caps : 178bfbff:ebd3fbff: 00000000:00000010:00002001:00000000:0000001f
total_memory : 4031 free_memory : 969 xen_major : 3 xen_minor : 1 xen_extra : .0xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
cc_compiler : gcc version 4.1.1 (Gentoo 4.1.1-r3)
cc_compile_by : root
cc_compile_domain : at.fiit.stuba.sk
cc_compile_date : Wed Jul 4 09:56:13 CEST 2007
xend_config_format : 4
DomU config attached.
I got this panic with your new kernel.
Kernelized RAIDframe activated
Status: Finishedpanic: HYPERVISOR_mmu_update failed
Command: /sbin/dhclient -q -pf /tmp/dhclnt.pid -lf /tmp/
dhclient.leases xenn
Stopped in pid 34.1 (dhclient) at 0xffffffff8026d9b9: ret db> bt ?() at 0xffffffff8026d9b9 ?() at 0xffffffff8027b1f9 ?() at 0xffffffff80274954 ?() at 0xffffffff802767c5 ?() at 0xffffffff801c6a09 ?() at 0xffffffff801ca692 ?() at 0xffffffff801f1408 ?() at 0xffffffff801ff0ba ?() at 0xffffffff80200526 ?() at 0xffffffff801f607c ?() at 0xffffffff8027835d db> sh reg ds 0x9 es 0xbf5c fs 0x7bfc gs 0xc02f rdi 0 rsi 0xd rbp 0xffffa0000ad84b20 rbx 0x1 rdx 0 rcx 0 rax 0x1 r8 0xffffffff808e9780 r9 0 r10 0xffffa0000ad84940 r11 0xffffffff80282e30 r12 0x100 r13 0xffffffff802b7bfc r14 0xffffa0000ac46040 r15 0xffffa000099329a0 rip 0xffffffff8026d9b9 cs 0xe030 rflags 0x246 rsp 0xffffa0000ad84a28 ss 0xe02b 0xffffffff8026d9b9: retI got this panic only when I run dhclient from sysinst. If I configure network from /bin/sh and then run sysinst everything works fine. I have installed system with this little hack and tested your yesterday domu-kernel. I got this panic with it.
Starting file system checks: uvm_fault(0xffffa00009931758, 0x0, 1) -> e kernel: page fault trap, code=0Stopped in pid 17.1 (mount_ffs) at 0xffffffff80245a23: movl 0x18(%ra
x),%eax ?() at 0xffffffff80245a23 ?() at 0xffffffff8031dcb7 ?() at 0xffffffff8031e293 ?() at 0xffffffff8036cad8 ds 0x1e40 es 0 fs 0x54c0 gs 0x2 rdi 0xffffa000099256e0 rsi 0xffffa00009939c00 rbp 0xffffa0000acdcc90 rbx 0x7f7fffffe9f0 rdx 0xffffa00000411400 rcx 0xffffa0000acf1e40 rax 0 r8 0x5 r9 0xffffffff80245ef3 r10 0 r11 0 r12 0x16 r13 0xffffa00000526000 r14 0xffffa000003dd060 r15 0xffffa0000ac86320 rip 0xffffffff80245a23 cs 0xe030 rflags 0x10206 rsp 0xffffa0000acdcb90 ss 0xe02b 0xffffffff80245a23: movl 0x18(%rax),%eax Sorry for this very long message.
Attachment:
dom0.dmesg
Description: Binary data
Attachment:
netbsd.xen.cfg
Description: Binary data
Regards Adam.