Re: [Xen-devel] Xen 4.2.1, Linux 3.3.4 kernel crash

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

On Thu, May 03, 2012 at 08:37:16AM -0700, Sam Mulvey wrote:
> 
> Hey folks...
> 
> This is with the same packages and such that I've been work on with Arch, and 
> I encountered an odd crash.   If I need to move this thread to Xen-users or 
> whatnot, apologies and please let me know.
> 
> The packages that I've been working with functioned great in the desktop VM, 
> and worked wonderfully in PV and HVM on my test hardware (an HP server with 
> Intel Xeons), but crashes right out of the gate on my production server (Tyan 
> motherboard with Opteron 8356s).   When I move the kernel back to a 2.6.32.18 
> pvops kernel I had been using, I can boot and run VMs without trouble.
> 
> Incidentally, I can now boot as many VMs as I like as long as the memory 
> holds out, so the initial trouble that got all of this started looks like 
> it's been fixed.
> 
> 
> Everything looks normal until Xen hands off to the kernel, then I get this:

This looks like an E820 alignment issue. Can you provide the full serial output 
please.


> 
> [    0.000000] Cannot find 20480 bytes in node 1
> [    0.000000] BUG: unable to handle kernel NULL pointer dereference at       
>     (null)
> [    0.000000] IP: [<ffffffff818d5704>] __alloc_bootmem_node+0x72/0x99
> [    0.000000] PGD 0 
> [    0.000000] Oops: 0000 [#1] PREEMPT SMP 
> [    0.000000] CPU 0 
> [    0.000000] Modules linked in:
> [    0.000000] 
> [    0.000000] Pid: 0, comm: swapper Not tainted 3.3.4-1-ARCH #1 empty 
> empty/S3992
> [    0.000000] RIP: e030:[<ffffffff818d5704>]  [<ffffffff818d5704>] 
> __alloc_bootmem_node+0x72/0x99
> [    0.000000] RSP: e02b:ffffffff81801de8  EFLAGS: 00010046
> [    0.000000] RAX: 0000000000000000 RBX: 0000000000000378 RCX: 
> 0000000000000000
> [    0.000000] RDX: 0000000000000040 RSI: 0000000000000378 RDI: 
> 0000000000000000
> [    0.000000] RBP: ffffffff81801e08 R08: 0000000000000000 R09: 
> ffffffff81801d98
> [    0.000000] R10: ffffffff81801d88 R11: ffffffff81801d90 R12: 
> 0000000000000040
> [    0.000000] R13: 0000000000000000 R14: 0000000000000000 R15: 
> 0000000000000001
> [    0.000000] FS:  0000000000000000(0000) GS:ffffffff8189f000(0000) 
> knlGS:0000000000000000
> [    0.000000] CS:  e033 DS: 0000 ES: 0000 CR0: 0000000080050033
> [    0.000000] CR2: 0000000000000000 CR3: 0000000001805000 CR4: 
> 0000000000000660
> [    0.000000] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 
> 0000000000000000
> [    0.000000] DR3: 0000000000000000 DR6: 0000000000000000 DR7: 
> 0000000000000000
> [    0.000000] Process swapper (pid: 0, threadinfo ffffffff81800000, task 
> ffffffff8180d020)
> [    0.000000] Stack:
> [    0.000000]  0000000000080000 0000000000000378 000000000000003c 
> ffff88003fbfa000
> [    0.000000]  ffffffff81801e68 ffffffff818d63f0 ffffffff81801e48 
> 00000001818d53bc
> [    0.000000]  ffff88003fbf9fe0 0000000000000000 000000000282c000 
> ffff88003fbfa000
> [    0.000000] Call Trace:
> [    0.000000]  [<ffffffff818d63f0>] 
> sparse_early_usemaps_alloc_node+0x63/0x1c4
> [    0.000000]  [<ffffffff818d677b>] sparse_init+0xf8/0x2c8
> [    0.000000]  [<ffffffff818ca4d2>] paging_init+0x13/0x22
> [    0.000000]  [<ffffffff818b9dca>] setup_arch+0x9f2/0xac0
> [    0.000000]  [<ffffffff814562d2>] ? printk+0x41/0x43
> [    0.000000]  [<ffffffff818b491b>] start_kernel+0xd4/0x3d1
> [    0.000000]  [<ffffffff818b4346>] x86_64_start_reservations+0x131/0x135
> [    0.000000]  [<ffffffff818b69c9>] xen_start_kernel+0x598/0x59f
> [    0.000000] Code: 4c 89 e9 4c 89 e2 48 89 de bf 40 00 00 00 e8 0f fc ff ff 
> eb 34 41 8b 96 a0 40 00 00 be 00 80 00 00 48 89 d 
> [    0.000000] RIP  [<ffffffff818d5704>] __alloc_bootmem_node+0x72/0x99
> [    0.000000]  RSP <ffffffff81801de8>
> [    0.000000] CR2: 0000000000000000
> [    0.000000] ---[ end trace a7919e7f17c0a725 ]---
> [    0.000000] Kernel panic - not syncing: Attempted to kill the idle task!
> (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
> 
> ----
> 
> This is the same kernel I've been using in the two testing machines.    The 
> server is, incidentally, the same server that houses the mail server I'm on, 
> so I'm cc'ing a gmail address, if you could include it in your replies, I'd 
> appreciate it.
> 
> Thanks!
> 
> -- 
> Sam Mulvey
> Tacoma Telematics
> sam@xxxxxxxxxxxxxxxxxxxx
> (253) 883-3030 x110
> 
> 
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel