From: Daniel Kiper <dkiper@net-space.pl>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Daniel Kiper <dkiper@net-space.pl>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Ian Campbell <Ian.Campbell@eu.citrix.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"andi.kleen@intel.com" <andi.kleen@intel.com>,
"haicheng.li@linux.intel.com" <haicheng.li@linux.intel.com>,
"fengguang.wu@intel.com" <fengguang.wu@intel.com>,
"jeremy@goop.org" <jeremy@goop.org>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
"v.tolstov@selfip.ru" <v.tolstov@selfip.ru>,
"pasik@iki.fi" <pasik@iki.fi>,
"dave@linux.vnet.ibm.com" <dave@linux.vnet.ibm.com>,
"wdauchy@gmail.com" <wdauchy@gmail.com>,
"rientjes@google.com" <rientjes@google.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Bootup fix for _brk_end being != _end
Date: Tue, 15 Mar 2011 16:40:24 +0100 [thread overview]
Message-ID: <20110315154024.GA14100@router-fw-old.local.net-space.pl> (raw)
In-Reply-To: <alpine.DEB.2.00.1103151530290.3382@kaball-desktop>
On Tue, Mar 15, 2011 at 03:31:47PM +0000, Stefano Stabellini wrote:
> On Tue, 15 Mar 2011, Daniel Kiper wrote:
> > On Tue, Mar 15, 2011 at 10:48:21AM -0400, Konrad Rzeszutek Wilk wrote:
> > > > > > Additionally, I suggest to apply patch prepared by Steffano Stabellini
> > > > > > (https://lkml.org/lkml/2011/1/31/232) which fixes memory management
> > > > > > issue in Xen guest. I was not able boot guest machine without
> > > > > > above mentioned patch.
> > > > >
> > > > > after some discussions we came up with a different approach to fix the
> > > > > issue; I sent a couple of patches a little while ago:
> > > > >
> > > > > https://lkml.org/lkml/2011/2/28/410
> > > >
> > > > I tested git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git 2.6.38-tip-fixes
> > > > and it works on x86_64, however, it does not work on i386. Tested as
> > > > unprivileged guest on Xen Ver. 4.1.0-rc2-pre. On i386 domain crashes
> > > > silently at early boot stage :-(((.
> > >
> > > 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
Daniel
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-03-15 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 21:44 [PATCH R4 0/7] xen/balloon: Memory hotplug support for Xen balloon driver Daniel Kiper
2011-03-09 14:01 ` Stefano Stabellini
2011-03-15 14:29 ` Daniel Kiper
2011-03-15 14:48 ` Bootup fix for _brk_end being != _end Konrad Rzeszutek Wilk
2011-03-15 15:30 ` Daniel Kiper
2011-03-15 15:31 ` Stefano Stabellini
2011-03-15 15:40 ` Daniel Kiper [this message]
2011-03-17 8:51 ` Daniel Kiper
2011-03-17 15:07 ` Stefano Stabellini
2011-03-17 20:27 ` Pasi Kärkkäinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110315154024.GA14100@router-fw-old.local.net-space.pl \
--to=dkiper@net-space.pl \
--cc=Ian.Campbell@eu.citrix.com \
--cc=akpm@linux-foundation.org \
--cc=andi.kleen@intel.com \
--cc=dan.magenheimer@oracle.com \
--cc=dave@linux.vnet.ibm.com \
--cc=fengguang.wu@intel.com \
--cc=haicheng.li@linux.intel.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasik@iki.fi \
--cc=rientjes@google.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=v.tolstov@selfip.ru \
--cc=wdauchy@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox