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/
Home Products Support Community News


Re: [XenPPC] domU bad page state

To: Amos Waterland <apw@xxxxxxxxxx>
Subject: Re: [XenPPC] domU bad page state
From: Hollis Blanchard <hollisb@xxxxxxxxxx>
Date: Mon, 28 Aug 2006 21:23:17 -0500
Cc: xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 28 Aug 2006 19:24:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060829021351.GA2875@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: IBM Linux Technology Center
References: <20060829021351.GA2875@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, 2006-08-28 at 22:13 -0400, Amos Waterland wrote:
> Using tip of tree xen.hg and linux.hg, I get this when launching a domU:
> Freeing initrd memory: 3141k freed
> Bad page state in process 'swapper'
> page:c00000000075d000 flags:0x0000100000080000 mapping:0000000000000000 
> mapcount
> :0 count:0
> Trying to fix it up, but a reboot is needed
> Backtrace:
> Call Trace:
> [C00000000081BBA0] [C00000000000F844] .show_stack+0x54/0x1f0 (unreliable)
> [C00000000081BC50] [C000000000094B60] .bad_page+0x70/0xd0
> [C00000000081BCD0] [C00000000009574C] .free_hot_cold_page+0x1fc/0x210
> [C00000000081BD70] [C0000000000332BC] .free_initrd_mem+0x10c/0x150
> [C00000000081BE10] [C0000000004F08F0] .free_initrd+0x70/0x130
> [C00000000081BEB0] [C0000000000092D8] .init+0x168/0x430
> [C00000000081BF90] [C000000000028F54] .kernel_thread+0x4c/0x68
> The domU completes its boot fine and I am able to run programs etc.
> I'm using the dom1 config that Jimi published earlier.

Hmm, I'm not sure what could cause this.

How reproducible is it? Does it only happen once per domU boot? Always
the same address/backtrace? Generally speaking, how old were the builds
you were using before (one day old? one week old?)?

Hollis Blanchard
IBM Linux Technology Center

Xen-ppc-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>