Re: Bootup fix for _brk_end being != _end

[Daniel Kiper]

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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/