WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Xen unstable crash

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen unstable crash
From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
Date: Tue, 17 Mar 2009 11:12:30 +0000
Cc: "Li, Haicheng" <haicheng.li@xxxxxxxxx>, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 17 Mar 2009 04:13:05 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=5V832UmEiTlelFJmq76YOqhYEmmYEC/QsbxB2VAmyGM=; b=fspBPEoJTKQk2bhoi/ebRk6CLod39QRUOCzzy1PExd82XflCvhRolaAOEFGydzJJrZ YfGFIWHEVCKEQv1C1uLNFRjAOlfQwbf7boyKIKX5G7hO/AnkcnHVlMtvvygedCgr/1kH H+H5lic3zxTAoHhyBzTam3rOKAj2FdvdU2xug=
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=d9HkxnzM2CWp6S767DeWZTrQCu+MJMaAFaxtqhVQnSKT8/SM6qxm/RUIDVqR2FepTL Vi/szxMYAze842XC0OUCbRUWDRxp4bf7ij5VTPASW/nCpNah9URnNdjoSaO54J4sikPL jKLpwAIDbVmDFuSzuO2eKowFg0f+qtbtttlAA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <f4527be0903170337s5fb0570ayd9e733bc5f5430eb@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <f4527be0903170300qdb61f50mfea0354b6a69766c@xxxxxxxxxxxxxx> <C5E52785.55F4%keir.fraser@xxxxxxxxxxxxx> <f4527be0903170320k2a4ec170s3c074485050aeacd@xxxxxxxxxxxxxx> <f4527be0903170337s5fb0570ayd9e733bc5f5430eb@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, Mar 17, 2009 at 10:37 AM, Andrew Lyon <andrew.lyon@xxxxxxxxx> wrote:
> On Tue, Mar 17, 2009 at 10:20 AM, Andrew Lyon <andrew.lyon@xxxxxxxxx> wrote:
>> On Tue, Mar 17, 2009 at 10:10 AM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> 
>> wrote:
>>> On 17/03/2009 10:00, "Andrew Lyon" <andrew.lyon@xxxxxxxxx> wrote:
>>>
>>>> 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:
>>>
>>> Can you try reverting some suspicious changesets?
>>>  hg export 19317 | patch -Rp1
>>>  hg export 19285 | patch -Rp1
>>> Then re-build the hypervisor (no need to redo tools or kernel). To put the
>>> tree back in a clean state afterwards:
>>>  hg diff | patch -Rp1
>>>
>>>  Thanks,
>>>  Keir
>>>
>>>
>>>
>>
>> Building now... I noticed that both of those changesets touch multi.c,
>> and I happened to notice this message was displayed before one of the
>> crashes:
>>
>> (XEN) multi.c:3348:d12 write to pagetable during event injection:
>> cr2=0x80392d74, mfn=0xb58bb
>>
>> Perhaps related?
>>
>> Andy
>>
>
> Reverting those two changesets did not stop the problem, I didn't get
> the crash message this time because the scrollback buffer in my serial
> console had been overwritten before I got a change to copy it, but it
> looked the same as the others.
>
> Andy
>

here is a crash with the two changesets reverted:

(XEN) ** page_alloc.c:407 -- 279/512 ffffffffffffffff
(XEN) Xen BUG at page_alloc.c:409
(XEN) ----[ Xen-3.4-unstable  x86_64  debug=y  Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    e008:[<ffff828c8011206f>] alloc_heap_pages+0x35a/0x486
(XEN) RFLAGS: 0000000000010286   CONTEXT: hypervisor
(XEN) rax: 0000000000000000   rbx: ffff8284014422e0   rcx: 0000000000000001
(XEN) rdx: 000000000000000a   rsi: 000000000000000a   rdi: ffff828c801fec6c
(XEN) rbp: ffff828c8027fcb8   rsp: ffff828c8027fc58   r8:  0000000000000004
(XEN) r9:  0000000000000004   r10: 0000000000000010   r11: 0000000000000010
(XEN) r12: ffff828401440000   r13: 0000000000000117   r14: 0000000000000200
(XEN) r15: 0000000000000000   cr0: 0000000080050033   cr4: 00000000000026f0
(XEN) cr3: 000000011d9e6000   cr2: 000000000142f000
(XEN) ds: 0000   es: 0000   fs: 0063   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from rsp=ffff828c8027fc58:
(XEN)    0000000900000001 0000000000000098 0000000000000200 0000000100000001
(XEN)    ffff828c8027fcf8 ffff828c801a5c6d ffff828c8027fccc ffff828c8027ff28
(XEN)    0000000000000027 0000000000000000 ffff830102176000 0000000000000000
(XEN)    ffff828c8027fcf8 ffff828c8011383b 0100000400000009 ffff828c8027ff28
(XEN)    0000000000000006 0000000044803758 00000000448037c0 0000000000000000
(XEN)    ffff828c8027ff08 ffff828c80110591 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000200 0000000000000000 0000000000000000 ffff830127fcc000
(XEN)    0000000000800167 000000000004ee7f 800000004ee7f167 ffff8284009dcfe0
(XEN)    ffff828c8027fd88 ffff828c80151777 ffff828c8027fda8 ffff828c8013c559
(XEN)    0000000000000004 0000020000000001 ffff828c8027fdb8 ffff828c8013c5f6
(XEN)    ffff828c8027fde8 ffff828c80107247 ffff828c8027fde8 ffff828c8011d72e
(XEN)    0000000000000000 0000000000000000 ffff828c8027fe28 ffff830102176000
(XEN)    0000000000000282 0000000400000009 0000000044803750 ffff8300cfdfc030
(XEN)    ffff83004f6bc018 ffff83004f6bc010 0000000000000001 ffff828c80119cb7
(XEN)    0000000000000082 ffff828c80237180 0000000000000002 ffff828c8027fe68
(XEN)    ffff828c8011c0c8 ffff828c80237180 ffff828c8027fe78 ffff828c8014c173
(XEN)    ffff828c8027fe98 ffff828c801d166d ffff828c8027fe98 00000000000a2200
(XEN)    0000000000007c00 ffff828c801d2063 0000000044803750 0000000000000004
(XEN)    0000000000000009 0000000000000004 00002af8d03b0eb7 ffff830102176000
(XEN) Xen call trace:
(XEN)    [<ffff828c8011206f>] alloc_heap_pages+0x35a/0x486
(XEN)    [<ffff828c8011383b>] alloc_domheap_pages+0x128/0x17b
(XEN)    [<ffff828c80110591>] do_memory_op+0x988/0x17a7
(XEN)    [<ffff828c801cf1bf>] syscall_enter+0xef/0x149
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Xen BUG at page_alloc.c:409

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