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

Re: [Xen-devel] Xen unstable crash


  • To: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
  • From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
  • Date: Tue, 17 Mar 2009 10:00:56 +0000
  • Cc: "Li, Haicheng" <haicheng.li@xxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Delivery-date: Tue, 17 Mar 2009 03:01:26 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=r14l6yAz+IsFb2nog4G8ERzLQ9FIV8exlRWaDTN13bUWON5kigrTKREncJH+071r5H PUz38JCJBSDijBo6nw/xgXo0H1RiK1eDybJYvdbtg+Vy6AkGKvkJvRe37kIxxkAdMtvn /tVB1IBKkGxsUrQtEo69coXOAHuSDDVf98cMg=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Tue, Mar 17, 2009 at 9:50 AM, Andrew Lyon <andrew.lyon@xxxxxxxxx> wrote:
> On Tue, Mar 17, 2009 at 9:35 AM, Andrew Lyon <andrew.lyon@xxxxxxxxx> wrote:
>> 2009/3/17 Jiang, Yunhong <yunhong.jiang@xxxxxxxxx>:
>>> We tried our auto test suite (the detailed testing is followed, it is same 
>>> as the Bi-weekly VMX status report sent by Haicheng), but still can't 
>>> trigger the issue. Andrew Lyon, can you share more detailed info on how 
>>> this issue is produced?
>>
>> I will do some testing now.
>>
>> Andy
>>
>
> I booted Xen unstable with kernel 2.6.18.8 64 bit, started a 32 bit
> windows xp hvm, a 32 bit vista hvm, and finally a 64 bit windows vista
> hvm, as the 64 bit was booting up the system crashes with this
> message:
>
> (XEN) ** page_alloc.c:534 -- 0/1 ffffffffffffffff
> (XEN) Xen BUG at page_alloc.c:536
> (XEN) ----[ Xen-3.4-unstable  x86_64  debug=y  Not tainted ]----
> (XEN) CPU:    1
> (XEN) RIP:    e008:[<ffff828c80112d77>] free_heap_pages+0x12f/0x4b8
> (XEN) RFLAGS: 0000000000010206   CONTEXT: hypervisor
> (XEN) rax: 0000000000000000   rbx: ffff82840235bc00   rcx: 0000000000000001
> (XEN) rdx: ffffffffffffffff   rsi: 000000000000000a   rdi: ffff828c801fedec
> (XEN) rbp: ffff830127fdfea8   rsp: ffff830127fdfe58   r8:  0000000000000004
> (XEN) r9:  0000000000000004   r10: 0000000000000010   r11: 0000000000000010
> (XEN) r12: ffff82840235bc00   r13: 0000000000000000   r14: 0000000000000000
> (XEN) r15: 0080000000000000   cr0: 000000008005003b   cr4: 00000000000026f0
> (XEN) cr3: 000000011de97000   cr2: 0000000080d30000
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e008
> (XEN) Xen stack trace from rsp=ffff830127fdfe58:
> (XEN)    ffff828c8011c0c8 ffff82840235bc00 0000000127fdfe98 0000000000000001
> (XEN)    0000000000000000 0000000000000200 c2c2c2c2c2c2c2c2 0000000000000000
> (XEN)    0000000000000000 ffff830000000000 ffff830127fdfee8 ffff828c8011329a
> (XEN)    00000042e383c411 0000000000000001 ffff830127fdff28 ffff828c80297880
> (XEN)    0000000000619e40 0000000000619e90 ffff830127fdff18 ffff828c8011ba21
> (XEN)    ffff8300cef8a000 ffff8300cef8a000 0000000000619e40 000000000061a710
> (XEN)    00007cfed80200b7 ffff828c801cf296 0000000000619e90 0000000000619e40
> (XEN)    000000000061a710 0000000000619e40 00007fff0032bee0 0000000000000000
> (XEN)    0000000000000246 0000000000000000 0000000000000000 00002b65aaf1aae0
> (XEN)    000000000061a6c0 0000000000619e40 00000000e814ec72 000000000040df76
> (XEN)    0000000000000000 000000f900000000 0000000000407e68 000000000000e033
> (XEN)    0000000000000206 00007fff0032beb0 000000000000e02b 7f466d7b7f79beef
> (XEN)    fdb7dbb473b9beef 0084a8008022beef 0005020b1a03beef f5f5ff7b00000001
> (XEN)    ffff8300cef8a000
> (XEN) Xen call trace:
> (XEN)    [<ffff828c80112d77>] free_heap_pages+0x12f/0x4b8
> (XEN)    [<ffff828c8011329a>] page_scrub_softirq+0x19a/0x23c
> (XEN)    [<ffff828c8011ba21>] do_softirq+0x6a/0x77
> (XEN)
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 1:
> (XEN) Xen BUG at page_alloc.c:536
> (XEN) ****************************************
>
> The problem is not predictable, in one instance it happened when
> starting the first hvm, other times I've been able to start and
> shutdown several before it happened.
>
> Andy
>

This time I was able to start all 3 of the vm's I mentioned, they are
setup to automatically boot up, run a chkdsk , then shutdown, , the
two vista vm's completed the cycle and I was able to start them again
before the error happened, this time it triggered just as one of them
was shutting down:

(XEN) ** page_alloc.c:534 -- 0/1 ffffffffffffffff
(XEN) Xen BUG at page_alloc.c:536
(XEN) ----[ Xen-3.4-unstable  x86_64  debug=y  Not tainted ]----
(XEN) CPU:    1
(XEN) RIP:    e008:[<ffff828c80112d77>] free_heap_pages+0x12f/0x4b8
(XEN) RFLAGS: 0000000000010206   CONTEXT: hypervisor
(XEN) rax: 0000000000000000   rbx: ffff828400090dc0   rcx: 0000000000000001
(XEN) rdx: ffffffffffffffff   rsi: 000000000000000a   rdi: ffff828c801fedec
(XEN) rbp: ffff830127fdfea8   rsp: ffff830127fdfe58   r8:  0000000000000004
(XEN) r9:  0000000000000004   r10: 0000000000000010   r11: 0000000000000010
(XEN) r12: ffff828400090dc0   r13: 0000000000000000   r14: 0000000000000000
(XEN) r15: 0080000000000000   cr0: 000000008005003b   cr4: 00000000000026f0
(XEN) cr3: 000000011d884000   cr2: 0000000001076090
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e008
(XEN) Xen stack trace from rsp=ffff830127fdfe58:
(XEN)    c2c2c2c2c2c2c2c2 ffff828400090dc0 00000001000917c0 0000000000000001
(XEN)    0000000000000000 0000000000000200 c2c2c2c2c2c2c2c2 ffff828400090da0
(XEN)    ffff828400090cc0 ffff830000000000 ffff830127fdfee8 ffff828c8011329a
(XEN)    000000962fa5971f 0000000000000001 ffff830127fdff28 ffff828c80297880
(XEN)    0000000000000000 000000962c2d2bed ffff830127fdff18 ffff828c8011ba21
(XEN)    0000000000000000 ffff8300cfdfc000 0000000000000000 ffff88000513d620
(XEN)    00007cfed80200b7 ffff828c801cf296 000000962c2d2bed 0000000000000000
(XEN)    ffff88000513d620 0000000000000000 ffffffff8062be88 0000000000020800
(XEN)    0000000000000246 0000000000000000 ffff880037fe5c98 0000000000000000
(XEN)    0000000000000000 00000000000003e8 ffffffffff578000 ffffffff8054d3a0
(XEN)    ffff88000513d620 000000f900000000 ffffffff804b6d2f 000000000000e033
(XEN)    0000000000000286 ffffffff8062be88 000000000000e02b 7f466d7b7f79beef
(XEN)    fdb7dbb473b9beef 0084a8008022beef 0005020b1a03beef f5f5ff7b00000001
(XEN)    ffff8300cfdfc000
(XEN) Xen call trace:
(XEN)    [<ffff828c80112d77>] free_heap_pages+0x12f/0x4b8
(XEN)    [<ffff828c8011329a>] page_scrub_softirq+0x19a/0x23c
(XEN)    [<ffff828c8011ba21>] do_softirq+0x6a/0x77
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 1:
(XEN) Xen BUG at page_alloc.c:536
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...

_______________________________________________
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®.