Hi, We found latest PAE Pv_ops Dom0 will crash when booting. The crash does not exist when booting 64b Pv_ops Dom0. The crash log is as attachment. The issue is found with commit 9b258d14a9f01b6be210aeaf55e39c51c48ba58e, while commit 350822b22d6cf8c29be9fe32fa47a8453bc5fd5b has no such issue. Best Regards, Jiajun _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Sander Eikelenboom
2010-Mar-22 16:09 UTC
Re: [Xen-devel] Latest PAE Pv_ops Dom0 crash when booting
Hmm doesn''t seem to be only related to PAE i guess, got it on a xen-next 2.6.32 kernel with 64bits as well. It doesn''t boot anymore after I switched off some options under power management / acpi. Trying to find out which one it is .... (XEN) ENTRY ADDRESS: ffffffff818d9200 (XEN) Dom0 has maximum 4 VCPUs (XEN) Scrubbing Free RAM: ............done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: All (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen) (XEN) Freed 164kB init memory. mapping kernel into physical memory about to get started... [ 0.000000] Initializing cgroup subsys cpuset (XEN) d0:v0: unhandled page fault (ec=0000) (XEN) Pagetable walk from ffff87fffffffc08: (XEN) L4[0x10f] = 0000000000000000 ffffffffffffffff (XEN) domain_crash_sync called from entry.S (XEN) Domain 0 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-4.0.0-rc6 x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e033:[<ffffffff81267163>] (XEN) RFLAGS: 0000000000000287 EM: 1 CONTEXT: pv guest (XEN) rax: 0000000000048000 rbx: ffffffff81832380 rcx: 0000000000000013 (XEN) rdx: fffffffffffff000 rsi: ffffffffffffffff rdi: ffff87fffffff000 (XEN) rbp: ffffffff817dfce8 rsp: ffffffff817dfc70 r8: 0000000000000000 (XEN) r9: 0000000000000004 r10: 0000000000000004 r11: 000000008190cdd1 (XEN) r12: 0000000000000008 r13: ffffffff8174b86d r14: 0000000000000008 (XEN) r15: ffff880000000000 cr0: 000000008005003b cr4: 00000000000026f0 (XEN) cr3: 0000000075001000 cr2: ffff87fffffffc08 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 (XEN) Guest stack trace from rsp=ffffffff817dfc70: (XEN) 0000000000000013 000000008190cdd1 0000000000000000 ffffffff81267163 (XEN) 000000010000e030 0000000000010087 ffffffff817dfcb8 000000000000e02b (XEN) ffffffff81713f9f 0000000000000004 ffffffff81832380 0000000000000031 (XEN) ffffffff8197f7e3 ffffffff818b8b70 0000000000000000 ffffffff817dfd28 (XEN) ffffffff8126731c 0000003400000000 ffffffff81832380 0000000000000031 (XEN) 0000000000000003 ffffffff818b8b70 0000000000000000 ffffffff817dfd58 (XEN) ffffffff81074db9 0000000000000034 0000000000000326 0000000000000000 (XEN) 00000000fffffcda ffffffff817dfd78 ffffffff81074e26 ffffffff8154af15 (XEN) 0000000000000034 ffffffff817dfda8 ffffffff8107520b ffffffff81832380 (XEN) 0000000000000000 ffffffff8197f710 0000000000000000 ffffffff817dfde8 (XEN) ffffffff81075a96 0000000000002121 ffffffff8190cdce 0000000000000000 (XEN) ffffffff8190cdce ffffffff8190cdd2 0000000000000000 ffffffff817dfdf8 (XEN) ffffffff81055975 ffffffff817dfe18 ffffffff818e8ce8 ffffffff8192b360 (XEN) ffffffff8190cdc2 ffffffff817dfe48 ffffffff818d9e1f 000000000000000f (XEN) ffffffff8190cdc2 ffffffff8190cdce 00000000fffffffe ffffffff817dfea8 (XEN) ffffffff8108b817 ffffffff817dfe68 ffffffff818d9dc2 00000000817dfe98 (XEN) 0000000000000000 ffffffff8170e52c 0000000000000000 ffffffffffffffff (XEN) ffffffff817dff70 0000000000000000 0000000000000000 ffffffff817dfeb8 (XEN) ffffffff818d9997 ffffffff817dff58 ffffffff818df373 ffffffff817dff58 (XEN) ffffffff8171d512 ffffffff81039157 ffffffff81911500 000000000211da00 (XEN) Domain 0 crashed: rebooting machine in 5 seconds. complete serial console attached. -- Sander Monday, March 22, 2010, 2:24:45 PM, you wrote:> Hi, > We found latest PAE Pv_ops Dom0 will crash when booting. The crash does not exist when booting 64b Pv_ops Dom0. The crash log is as attachment. > The issue is found with commit 9b258d14a9f01b6be210aeaf55e39c51c48ba58e, while commit 350822b22d6cf8c29be9fe32fa47a8453bc5fd5b has no such issue.> Best Regards, > Jiajun-- Best regards, Sander mailto:linux@eikelenboom.it _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Sander Eikelenboom
2010-Mar-22 16:14 UTC
Re: [Xen-devel] Latest PAE Pv_ops Dom0 crash when booting
Hello Jiajun, I think i have found out what was wrong at my case. I switched off powermanagement in the kernel config, this disables ACPI as well, and that turns off dom0 support. That all happened silently by just disableing powermanagent. So perhaps you could verify is the kernel config you build still has dom0 support enabled ? -- Sander Monday, March 22, 2010, 2:24:45 PM, you wrote:> Hi, > We found latest PAE Pv_ops Dom0 will crash when booting. The crash does not exist when booting 64b Pv_ops Dom0. The crash log is as attachment. > The issue is found with commit 9b258d14a9f01b6be210aeaf55e39c51c48ba58e, while commit 350822b22d6cf8c29be9fe32fa47a8453bc5fd5b has no such issue.> Best Regards, > Jiajun-- Best regards, Sander mailto:linux@eikelenboom.it _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Sander Eikelenboom
2010-Mar-22 16:31 UTC
Re: [Xen-devel] Latest PAE Pv_ops Dom0 crash when booting
Switching acpi and dom0 support (duh) back on fixed my problem, sorry for the noise ...> Hello Jiajun,> I think i have found out what was wrong at my case. I switched off powermanagement in the kernel config, this disables ACPI as well, and that turns off dom0 support. > That all happened silently by just disableing powermanagent. > So perhaps you could verify is the kernel config you build still has dom0 support enabled ?> --> Sander> Monday, March 22, 2010, 2:24:45 PM, you wrote:>> Hi, >> We found latest PAE Pv_ops Dom0 will crash when booting. The crash does not exist when booting 64b Pv_ops Dom0. The crash log is as attachment. >> The issue is found with commit 9b258d14a9f01b6be210aeaf55e39c51c48ba58e, while commit 350822b22d6cf8c29be9fe32fa47a8453bc5fd5b has no such issue.>> Best Regards, >> Jiajun-- Best regards, Sander mailto:linux@eikelenboom.it _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel