|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] Re: Bootup fix for _brk_end being != _end
To: |
Daniel Kiper <dkiper@xxxxxxxxxxxx> |
Subject: |
[Xen-devel] Re: Bootup fix for _brk_end being != _end |
From: |
Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> |
Date: |
Thu, 17 Mar 2011 15:07:05 +0000 |
Cc: |
"jeremy@xxxxxxxx" <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "haicheng.li@xxxxxxxxxxxxxxx" <haicheng.li@xxxxxxxxxxxxxxx>, Wilk <konrad.wilk@xxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Dan, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>, Magenheimer <dan.magenheimer@xxxxxxxxxx>, "v.tolstov@xxxxxxxxx" <v.tolstov@xxxxxxxxx>, "dave@xxxxxxxxxxxxxxxxxx" <dave@xxxxxxxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, "linux-mm@xxxxxxxxx" <linux-mm@xxxxxxxxx>, Konrad, "rientjes@xxxxxxxxxx" <rientjes@xxxxxxxxxx>, "andi.kleen@xxxxxxxxx" <andi.kleen@xxxxxxxxx>, "akpm@xxxxxxxxxxxxxxxxxxxx" <akpm@xxxxxxxxxxxxxxxxxxxx>, "fengguang.wu@xxxxxxxxx" <fengguang.wu@xxxxxxxxx>, "wdauchy@xxxxxxxxx" <wdauchy@xxxxxxxxx> |
Delivery-date: |
Thu, 17 Mar 2011 08:22:29 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<20110317085118.GA11346@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
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: |
<20110308214429.GA27331@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <alpine.DEB.2.00.1103091359290.2968@kaball-desktop> <20110315142957.GB12730@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20110315144821.GA11586@xxxxxxxxxxxx> <20110315153001.GD12730@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <alpine.DEB.2.00.1103151530290.3382@kaball-desktop> <20110315154024.GA14100@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20110317085118.GA11346@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Alpine 2.00 (DEB 1167 2008-08-23) |
On Thu, 17 Mar 2011, Daniel Kiper wrote:
> > > > > Details? Can you provide the 'xenctx' output of where it crashed?
> > > >
> > > > As I wrote above domain is dying and I am not able to connect to it
> > > > using
> > > > xenctx after crash :-(((. I do not know how to do that in another way.
> > >
> > > try adding:
> > >
> > > extra = "loglevel=9 debug earlyprintk=xenboot"
> >
> > (XEN) d55:v0: unhandled page fault (ec=0002)
> > (XEN) Pagetable walk from 000000000000000c:
> > (XEN) L4[0x000] = 000000010bebc027 0000000000024d28
> > (XEN) L3[0x000] = 0000000000000000 ffffffffffffffff
> > (XEN) domain_crash_sync called from entry.S
> > (XEN) Domain 55 (vcpu#0) crashed on cpu#3:
> > (XEN) ----[ Xen-4.1.0-rc2-pre x86_64 debug=y Not tainted ]----
> > (XEN) CPU: 3
> > (XEN) RIP: e019:[<00000000c1001180>]
> > (XEN) RFLAGS: 0000000000000282 EM: 1 CONTEXT: pv guest
> > (XEN) rax: 000000000000000c rbx: 000000000000000c rcx: 00000000c1371fd0
> > (XEN) rdx: 00000000c1371fd0 rsi: 00000000c1742000 rdi: 00000000a5c03d70
> > (XEN) rbp: 00000000c1371fc8 rsp: 00000000c1371fa8 r8: 0000000000000000
> > (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000
> > (XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000
> > (XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000026f4
> > (XEN) cr3: 0000000129b6e000 cr2: 000000000000000c
> > (XEN) ds: e021 es: e021 fs: e021 gs: e021 ss: e021 cs: e019
> > (XEN) Guest stack trace from esp=c1371fa8:
> > (XEN) 00000002 c1001180 0001e019 00010082 c10037af deadbeef c1742000
> > a5c03d70
> > (XEN) c1371fdc c13a4aa8 00000000 00000000 00000000 c1371ffc c13a3ff2
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 deadbeef c1753000 013fe001
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 013fe001 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000
> > (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000
>
> Any progress ??? Can I help you in something ???
>
Unfortunately unless you are able to resolve the IP of the crash these
logs don't tell me much.
Alternatively you can try to get more infos using /usr/lib/xen/bin/xenctx
like Konrad suggested.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|