[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] (XEN) Xen BUG at page_alloc.c:385


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx>
  • Date: Tue, 19 Oct 2010 14:16:43 +0200
  • Delivery-date: Tue, 19 Oct 2010 05:19:43 -0700
  • Domainkey-signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:From:To:Subject:Date:User-Agent: X-KMail-Markup:MIME-Version:Content-Type: Content-Transfer-Encoding:Message-Id; b=ChtqUnn/6RXs4yJPRK/uiieDdRPjDGoTKH60azkbUtPgxBlFFVb07cNd wczX6FTmE1uOACR4SJPObi3QhEzpUGo200O1ldF1Pt3wzzgwoLStk/0CH yVxNymc1ShfhOt4YP6ZePkEXJjqpchM0GvrfiHIAxUFhH4zdNCWAyXcvt iGHSkuLV+2cgmTjYfwIm2olrym4f3GlDgtTapat6UJ9m9SNvObWLK/vAP QBex5nSeFuPKqGmKa/H+3nHHaSgNE;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi list,

I had a hypervisor crash and would need some assistance.

This is a SLES11 SP1 system with some patches from Novell.

I got a vmcore but reading it with crash in xen-mode failed. So I tried

# strings vmcore | grep '(XEN)'

and got the following output (among others):

(XEN) page_alloc.c:1111:d9 Over-allocation for domain 9: 263169 > 263168

(XEN) memory.c:132:d9 Could not allocate order=0 extent: id=9 memflags=0 (79 of 512)

(XEN) memory.c:171:d9 Domain 9 page number 11fe4f invalid

(XEN) page_alloc.c:1111:d9 Over-allocation for domain 9: 263169 > 263168

(XEN) memory.c:132:d9 Could not allocate order=0 extent: id=9 memflags=0 (79 of 512)

(XEN) memory.c:171:d9 Domain 9 page number 11fe4f invalid

These messages are surely caused by failures of our balloon stuff in

our domU.

(XEN) sh error: sh_remove_all_mappings(): can't find all mappings of mfn 3f3daac: c=00000005 t=7400000000000000

Because I'am not familiar with the shadow code, what type of mappings can

lead to such a warning, in which direction should I look?

(XEN) Xen BUG at page_alloc.c:385

The code line is:

BUG_ON(pg[i].count_info != PGC_state_free);

Is it possible in any way that a free page is in use? Or is it always a

failure somewhere in the code like a multiple use of the same page?

Any help would be very welcome.

Thanks.

Dietmar.

(XEN) ----[ Xen-4.0.0_21091_04-0.2.6.1590.1.PTF.624285 x86_64 debug=n Tainted: C ]----

(XEN) CPU: 15

(XEN) RIP: e008:[<ffff82c480117491>] alloc_heap_pages+0x451/0x460

(XEN) RFLAGS: 0000000000010a02 CONTEXT: hypervisor

(XEN) rax: 0180000000000000 rbx: ffff82f65ac3afc0 rcx: 0000000000000000

(XEN) rdx: 0000000000000019 rsi: 0000000000000000 rdi: ffff833fcfbff9e8

(XEN) rbp: 0000000000000000 rsp: ffff833fcfbff998 r8: 0000000000000001

(XEN) r9: 00000000000001db r10: 0000000000000000 r11: ffff82c48047fc80

(XEN) r12: ffff82c480267324 r13: ffff833fcfbff9e8 r14: 0000000000000020

(XEN) r15: ffff833fcfbff9c8 cr0: 0000000080050033 cr4: 00000000000026f0

(XEN) cr3: 0000003012034000 cr2: 00000000beff6fec

(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008

(XEN) Xen stack trace from rsp=ffff833fcfbff998:

(XEN) ffff8330193e0000 0000000000000000 0000000100000027 ffff82f65ac3afc0

(XEN) 00000001ffb83cb0 0000000000000001 0000000000000000 0000000000000000

(XEN) 0000000000000000 0000000000000000 ffff833fcfbffa2c ffff833fcfbfff28

(XEN) ffff833fcfbfff28 ffff833fcfbffa1c 0000000400000001 0000000000000000

(XEN) 0000000000000027 0000000000000000 ffff8330193e0000 0000000000000000

(XEN) 0000000000000000 ffff82c4801177e8 0100000000000006 0000000000000000

(XEN) 0000000000000196 ffff9700ffb83cb0 0000000000000006 ffff833fcfbfff28

(XEN) ffff8330193e0000 ffff82c480114396 ffffffffffffffff ffff833fcfbffb2c

(XEN) ffff833fcfbfff28 ffff8330193e0000 0000000000000223 ffff830077c26000

(XEN) ffff9700ff02315b 0000000000000010 ffff833fcfbffc00 ffff82c4801a4ce2

(XEN) 00000000cfbffc58 ffff833fcfbfff28 ffff833fcfbfff28 ffff833fcfbffc80

(XEN) ffff833fcfbfff28 ffff833fcfbffb1c 00000004193e0218 0000000000000380

(XEN) 0000000100000004 000000000000a09b ffff82c480483280 0000000000000200

(XEN) ffff9700ffb83000 ffff830077c26000 ffff833fcfbfff28 0000000000000200

(XEN) 0000000000000001 ffff82c48019e419 ffff833fcfbffb78 ffff830077c26000

(XEN) ffff9700ff02315b ffff830077c26000 ffff833fcfbffbe8 ffff830077c26000

(XEN) ffff97600016bbd8 ffff82c4801a8cf2 ffff9700fe1a9f98 0000000000000000

(XEN) ffff833fcfbffc78 ffff82c4801a4db0 0000000133210188 ffff833fcfbfff28

(XEN) ffff833fcfbffc1c ffff833fcfbfff28 ffff833fcfbfff28 0000004000000040

(XEN) 0000000500000001 48c300000380b889 ff9700ffb81708b8 ffff9700ff02315b

(XEN) Xen call trace:

(XEN) [<ffff82c480117491>] alloc_heap_pages+0x451/0x460

(XEN) [<ffff82c4801177e8>] alloc_domheap_pages+0x178/0x1a0

(XEN) [<ffff82c480114396>] do_memory_op+0xb86/0x1d20

(XEN) [<ffff82c4801a4ce2>] __hvm_copy+0x1c2/0x4c0

(XEN) [<ffff82c48019e419>] hvm_emulate_one+0xc9/0x1b0

(XEN) [<ffff82c4801a8cf2>] handle_mmio+0x92/0x1b0

(XEN) [<ffff82c4801a4db0>] __hvm_copy+0x290/0x4c0

(XEN) [<ffff82c4801a51c0>] copy_to_user_hvm+0x60/0x100

(XEN) [<ffff82c4801a292e>] hvm_memory_op+0xe/0x40

(XEN) [<ffff82c4801a2c57>] hvm_do_hypercall+0x247/0x280

(XEN) [<ffff82c4801be86b>] vmx_vmexit_handler+0xaab/0x1dd0

(XEN) [<ffff82c4801b31be>] pt_restore_timer+0x5e/0xb0

(XEN) [<ffff82c4801a3d31>] hvm_do_resume+0x31/0x1b0

(XEN) [<ffff82c4801b8d43>] vmx_do_resume+0x123/0x1d0

(XEN) [<ffff82c48014d852>] context_switch+0x192/0xed0

(XEN) [<ffff82c48014c6bd>] vcpu_kick+0x1d/0x80

(XEN) [<ffff82c4801b3243>] pt_update_irq+0x33/0x230

(XEN) [<ffff82c4801aa184>] hvm_vcpu_has_pending_irq+0x54/0x70

(XEN) [<ffff82c4801b7e2c>] vmx_intr_assist+0x5c/0x240

(XEN) [<ffff82c4801bb1fb>] vmx_vmenter_helper+0x5b/0x150

(XEN) [<ffff82c4801b7be3>] vmx_asm_do_vmentry+0x0/0xdd

(XEN)

(XEN)

(XEN) ****************************************

(XEN) Panic on CPU 15:

(XEN) Xen BUG at page_alloc.c:385

(XEN) ****************************************

(XEN)

(XEN) Reboot in five seconds...

(XEN) do_IRQ: 15.225 No irq handler for vector (irq -1)

--

Company details: http://ts.fujitsu.com/imprint.html

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.