lozenges crash

| | Comments (0)
Lozenges crashed this morning after we went home from moving some of the other servers to market post tower. It looks like a bug in Xen 4.0.1:
 (XEN) Xen BUG at page_alloc.c:1204
(XEN) ----[ Xen-4.0.1  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    e008:[<ffff82c4801159f2>] free_domheap_pages+0x1f2/0x380
(XEN) RFLAGS: 0000000000010206   CONTEXT: hypervisor
(XEN) rax: 007fffffffffffff   rbx: ffff83007bfd0000   rcx: 0000000000000000
(XEN) rdx: ffff82f600a7f660   rsi: 0000000000000000   rdi: ffff83007bfd0014
(XEN) rbp: ffff830051d13000   rsp: ffff82c48035fa58   r8:  0000000000000000
(XEN) r9:  0000000000000000   r10: ffff83007bfd0018   r11: 0000000000000000
[Wed Jun 22 11:49:16 2011](XEN) r12: 0000000000000001   r13: ffff82f600a7f660   r14: 0000000000000000
(XEN) r15: ffff83007bfd0014   cr0: 000000008005003b   cr4: 00000000000006f0
(XEN) cr3: 000000031280c000   cr2: ffff8800369c0358
(XEN) ds: 0000   es: 0000   fs: 0063   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from rsp=ffff82c48035fa58:
(XEN)    000000017bfd0000 ffff830051d12f08 ffff830051d13000 ffff83007bfd0000
(XEN)    ffff83007bfd0000 0000000000000000 ffff830000000000 ffff82c48015ce25
(XEN)    0000000002150c70 000000003e2c7d38 0000000000000156 1400000000000001
(XEN)    ffff82f600a3a240 1400000000000001 ffff82c48035ff28 0000000000000000
(XEN)    ffff830000000000 ffff82c48015d179 0000000100000246 ffff82f600a3a240
[Wed Jun 22 11:49:16 2011](XEN)    000000000007ea58 ffff82f600fd4b00 ffff83007bfd0000 ffff83007ea58000
(XEN)    ffff82c48035ff28 ffff82c48015c951 0000000000000052 000000000007ea58
(XEN)    ffff82f600fd4b00 ffff83007bfd0000 ffff83007ea58000 ffff82c48015cbef
(XEN)    0000000100db89c0 0000000000000000 0000000000000156 2400000000000001
(XEN)    ffff82f600fd4b00 2400000000000001 ffff82c48035ff28 0000000000000001
(XEN)    ffff830000000000 ffff82c48015d179 0000000100000242 ffff82f600fd4b00
(XEN)    ffff83007ea59000 ffff82f600fd4b20 0000000000000000 000000000007ea59
(XEN)    ffff83007ea59000 ffff82c48015d987 0000000000000000 ffff83007ea59000
(XEN)    ffff82f600fd4b20 ffff82c48015cd79 0000000100000000 00000000000534b0
(XEN)    ffff83007bfd0000 3400000000000001 ffff82f600fd4b20 3400000000000001
[Wed Jun 22 11:49:16 2011](XEN)    ffff82c48035ff28 0000000000000001 ffff830000000000 ffff82c48015d179
(XEN)    ffff82f600a7bcc0 ffff82f600fd4b20 0000000000000000 ffff82f600fd4e80
(XEN)    000000000007ea74 ffff83007bfd0000 ffff83007ea74000 ffff82c48015d825
(XEN)    0000000000000001 0000000000000140 0000000000000000 ffff82c48015cb41
(XEN)    0000000100a7bcc0 00000000ffffffe0 0000000000000156 4400000000000001
(XEN) Xen call trace:
(XEN)    [<ffff82c4801159f2>] free_domheap_pages+0x1f2/0x380
(XEN)    [<ffff82c48015ce25>] free_page_type+0x4c5/0x670
(XEN)    [<ffff82c48015d179>] __put_page_type+0x1a9/0x290
(XEN)    [<ffff82c48015c951>] put_page_from_l2e+0xe1/0xf0
[Wed Jun 22 11:49:16 2011](XEN)    [<ffff82c48015cbef>] free_page_type+0x28f/0x670
(XEN)    [<ffff82c48015d179>] __put_page_type+0x1a9/0x290
(XEN)    [<ffff82c48015d987>] put_page_from_l3e+0x157/0x170
(XEN)    [<ffff82c48015cd79>] free_page_type+0x419/0x670
(XEN)    [<ffff82c48015d179>] __put_page_type+0x1a9/0x290
(XEN)    [<ffff82c48015d825>] put_page_from_l4e+0xd5/0xe0
(XEN)    [<ffff82c48015cb41>] free_page_type+0x1e1/0x670
(XEN)    [<ffff82c48015d179>] __put_page_type+0x1a9/0x290
(XEN)    [<ffff82c48014be85>] relinquish_memory+0x1e5/0x500
(XEN)    [<ffff82c48014c64d>] domain_relinquish_resources+0x1ad/0x280
[Wed Jun 22 11:49:16 2011](XEN)    [<ffff82c480106250>] domain_kill+0x80/0xf0
(XEN)    [<ffff82c48010430e>] do_domctl+0x1be/0xff0
(XEN)    [<ffff82c48011bc70>] get_cpu_idle_time+0x20/0x30
(XEN)    [<ffff82c4801e5169>] syscall_enter+0xa9/0xae
(XEN)   
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Xen BUG at page_alloc.c:1204
(XEN) ****************************************
[Wed Jun 22 11:49:16 2011](XEN)
(XEN) Reboot in five seconds...
So hopefully its fixed in 4.0.2 that just came out. Meanwhile, it looks like everybody is back up, but we will probably not put more new customers on lozenges for a while. Please email support@prgmr.com if you are still having trouble. Thanks.

Leave a comment

About this Entry

This page contains a single entry by nick published on June 22, 2011 4:31 PM.

network outage this morning was the previous entry in this blog.

server move tonight is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.