Bas Verhoeven
2008-Apr-23 11:01 UTC
[Xen-users] Unhandled page fault in domain <x> on VCPU 0 (ec=0002)
Hi, I finally managed my raid controller to work (not corrupt data) under Xen - see my previous thread. But now, when I start an earlier created domain (which worked fine previously), strange things happen. p-dom0:/etc/xen# xm create p-file.cfg -c Using config file "./p-file.cfg". Started domain p-file (no console shows up) p-dom0:/etc/xen# xm dmesg (XEN) Unhandled page fault in domain 285 on VCPU 0 (ec=0002) (XEN) Pagetable walk from 00000000: (XEN) L3[0x000] = 0000000000000000 ffffffff (XEN) domain_crash_sync called from entry.S (ff1851ee) (XEN) Domain 285 (vcpu#0) crashed on cpu#3: (XEN) ----[ Xen-3.2.0 x86_32p debug=n Not tainted ]---- (XEN) CPU: 3 (XEN) EIP: e019:[<c0300ef0>] (XEN) EFLAGS: 00000246 CONTEXT: guest (XEN) eax: 00000000 ebx: 03040800 ecx: 0000e307 edx: c03b2000 (XEN) esi: c0444000 edi: 00000000 ebp: c0389ff8 esp: c0389fb4 (XEN) cr0: 8005003b cr4: 000026f0 cr3: 001bdca0 cr2: 00000000 (XEN) ds: e021 es: e021 fs: 0000 gs: 0000 ss: e021 cs: e019 (XEN) Guest stack trace from esp=c0389fb4: (XEN) 00000002 c0300ef0 0001e019 00010046 c038e59b 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 03040800 c0444000 (XEN) 00000000 00000000 00000000 c038e5a5 c038e5ad c038e5b5 c01032e1 c0103361 (XEN) c01033db c0103696 c01036fd c010390b c0104656 c02fe2e4 c02fe2f5 c02fe304 (XEN) c02fe30e c0104ae5 c0104c77 c0104fa1 c0105024 c01054f8 c01065d9 c01077d8 (XEN) c01078b1 c01078ba c0107c4e c0107c57 c0107c9c c0107ca8 c0107cba c0107eb3 (XEN) c0107ebc c0107ecd c0107eea c0107f39 c0107f51 c0107f5a c0108125 c0108147 (XEN) c0108ab2 c0108aea c0108b38 c0108f79 c01098d9 c0109dc2 c010a14e c010a251 (XEN) c010a372 c010a3b3 c010a4bd c010a53d c0395770 c010c5d6 c010c5de c010c6c3 (XEN) c010c6cb c039631d c0396325 c010cfed c010d607 c010d61a c010d620 c010d633 (XEN) c010d646 c010d79b c010d7f4 c010d888 c010d99a c03967cd c0396867 c039689c (XEN) c03968b5 c0396a11 c0396a95 c0396ace c0396ad4 c0396b07 c0396dc3 c0396dd8 (XEN) c0396de2 c0396fe6 c039706f c0397312 c039739c c03973a1 c03973b2 c0397475 (XEN) c039749e c0397524 c010e212 c010e2a6 c010e2b8 c010e2ce c010e2e8 c010ea59 (XEN) c010ea79 c010eadb c010eb43 c03978eb c010f833 c010f8ed c010f9de c010fa08 (XEN) c010fd93 c010fdea c01114c6 c01116e6 c03982fe c0398310 c0111827 c039849a (XEN) c0398667 c0111941 c0111963 c0111b73 c0111e81 c01124ad c011252c c01125ff (XEN) c0112650 c0112658 c01126b6 c0112e08 c0113503 c011352b c0113c43 c0113c7e (XEN) c011407e c0114fa2 c0115da7 c0115fd5 c0399609 c01197e9 c011ab66 c011ac67 (XEN) c011aca2 c011b49e c011b5fc c011b767 c011b786 c011b890 c011bc61 c011c043 (XEN) Unhandled page fault in domain 286 on VCPU 0 (ec=0002) (XEN) Pagetable walk from 00000000: (XEN) L3[0x000] = 0000000000000000 ffffffff (XEN) domain_crash_sync called from entry.S (ff1851ee) (XEN) Domain 286 (vcpu#0) crashed on cpu#3: (XEN) ----[ Xen-3.2.0 x86_32p debug=n Not tainted ]---- (XEN) CPU: 3 (XEN) EIP: e019:[<c0300ef0>] (XEN) EFLAGS: 00000246 CONTEXT: guest (XEN) eax: 00000000 ebx: 03040800 ecx: 0000e307 edx: c03b2000 (XEN) esi: c0444000 edi: 00000000 ebp: c0389ff8 esp: c0389fb4 (XEN) cr0: 8005003b cr4: 000026f0 cr3: 001bdca0 cr2: 00000000 (XEN) ds: e021 es: e021 fs: 0000 gs: 0000 ss: e021 cs: e019 (XEN) Guest stack trace from esp=c0389fb4: (XEN) 00000002 c0300ef0 0001e019 00010046 c038e59b 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 03040800 c0444000 (XEN) 00000000 00000000 00000000 c038e5a5 c038e5ad c038e5b5 c01032e1 c0103361 (XEN) c01033db c0103696 c01036fd c010390b c0104656 c02fe2e4 c02fe2f5 c02fe304 (XEN) c02fe30e c0104ae5 c0104c77 c0104fa1 c0105024 c01054f8 c01065d9 c01077d8 (XEN) c01078b1 c01078ba c0107c4e c0107c57 c0107c9c c0107ca8 c0107cba c0107eb3 (XEN) c0107ebc c0107ecd c0107eea c0107f39 c0107f51 c0107f5a c0108125 c0108147 (XEN) c0108ab2 c0108aea c0108b38 c0108f79 c01098d9 c0109dc2 c010a14e c010a251 (XEN) c010a372 c010a3b3 c010a4bd c010a53d c0395770 c010c5d6 c010c5de c010c6c3 (XEN) c010c6cb c039631d c0396325 c010cfed c010d607 c010d61a c010d620 c010d633 (XEN) c010d646 c010d79b c010d7f4 c010d888 c010d99a c03967cd c0396867 c039689c (XEN) c03968b5 c0396a11 c0396a95 c0396ace c0396ad4 c0396b07 c0396dc3 c0396dd8 (XEN) c0396de2 c0396fe6 c039706f c0397312 c039739c c03973a1 c03973b2 c0397475 (XEN) c039749e c0397524 c010e212 c010e2a6 c010e2b8 c010e2ce c010e2e8 c010ea59 (XEN) c010ea79 c010eadb c010eb43 c03978eb c010f833 c010f8ed c010f9de c010fa08 (XEN) c010fd93 c010fdea c01114c6 c01116e6 c03982fe c0398310 c0111827 c039849a (XEN) c0398667 c0111941 c0111963 c0111b73 c0111e81 c01124ad c011252c c01125ff (XEN) c0112650 c0112658 c01126b6 c0112e08 c0113503 c011352b c0113c43 c0113c7e (XEN) c011407e c0114fa2 c0115da7 c0115fd5 c0399609 c01197e9 c011ab66 c011ac67 (XEN) c011aca2 c011b49e c011b5fc c011b767 c011b786 c011b890 c011bc61 c011c043 p-dom0:/etc/xen# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 2894 4 r----- 604.7 p-file 322 384 1 --p--- 0.0 I can''t shutdown the domain in the ''nice'' manner: it keeps showing up, as if it''s in some loop. So far xm destroy seems to work. I recompiled the xenU kernel, without any success. Any idea what can be causing this? System Info: - Server: ASUS RS120-E4/PA4 - Distro: Debian etch - Architecture: 32bit / 686 - Memory: 4 GB - CPU: Intel Q6600 (Quad) - Disk Controller: 3ware 8006-2LP (Driver Version = 1.26.03.000-2.6.18, Firmware Version = FE8S 1.05.00.068, Bios Version = BE7X 1.08.00.048) - Disks: 2x Hitachi HDT725050VLA360 Xen Info: host : p-dom0 release : 2.6.18.8-xen0-bserved-20080314 version : #11 SMP Tue Apr 22 16:39:53 CEST 2008 machine : i686 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2400 hw_caps : bfebfbff:20100000:00000000:00000140:0000e3bd:00000000:00000001 total_memory : 4095 free_memory : 772 node_to_cpu : node0:0-3 xen_major : 3 xen_minor : 2 xen_extra : .0 xen_caps : xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xf5800000 xen_changeset : unavailable cc_compiler : gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21) cc_compile_by : root cc_compile_domain : bserved.nl cc_compile_date : Fri Mar 14 20:06:00 CET 2008 xend_config_format : 4 Config: # # Configuration file for the Xen instance p-file, created # by xen-tools 3.9 on Sun Mar 16 14:08:47 2008. # # # Kernel + memory size # kernel = ''/boot/vmlinuz-2.6.18.8-xenU'' memory = ''384'' # # Disk device(s). # disk = [''phy:p-dom0/File-Root,sda2,w'', ''phy:p-dom0/File-Swap,sda1,w'' ] root = "/dev/sda2 ro" extra = "xencons=tty" # # Hostname # name = ''p-file'' # # Networking # #vif = [ ''ip=10.0.1.10,mac=00:16:3E:51:1A:91'' ] vif = [ ''bridge=xenbr0'', ''bridge=xenbr1'' ] # # Behaviour # on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' Cheers, Bas Verhoeven _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users