From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: xen.git branch reorg / crash with 2.6.30-rc3 pv_ops
	dom0
Date: Mon, 27 Apr 2009 12:33:01 -0700
Message-ID: <49F6086D.1020602@goop.org>
References: <49F0A797.1050402@goop.org>
	<20090423182451.GV24960@edu.joroinen.fi>
	<49F0B42E.2040904@goop.org>
	<20090425115404.GZ24960@edu.joroinen.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20090425115404.GZ24960@edu.joroinen.fi>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= <pasik@iki.fi>
Cc: Xen-devel <xen-devel@lists.xensource.com>, Ian Campbell <Ian.Campbell@citrix.com>
List-Id: xen-devel@lists.xenproject.org

Pasi K=E4rkk=E4inen wrote:
> On Thu, Apr 23, 2009 at 11:32:14AM -0700, Jeremy Fitzhardinge wrote:
>  =20
>> Pasi K=E4rkk=E4inen wrote:
>>    =20
>>> I'll try upgrading from dom0/hackery to xen-tip/next and see how it w=
orks
>>> for me.=20
>>> =20
>>>      =20
>> Thanks.
>>
>>    =20
>
> It seems latest tree crashes for me (happened yesterday, and also today=
, just rebuilt the latest commits):
> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-26-x=
en331-linux-2.6.30-rc3-crash-no-highpte.txt
>
> Zone PFN ranges:
>   DMA      0x00000010 -> 0x00001000
>   Normal   0x00001000 -> 0x000229fe
>   HighMem  0x000229fe -> 0x00040000
> Movable zone start PFN for each node
> early_node_map[3] active PFN ranges
>     0: 0x00000010 -> 0x0000009f
>     0: 0x00000100 -> 0x00001167
>     0: 0x00001268 -> 0x00040000
> (XEN) d0:v0: unhandled page fault (ec=3D0003)
> (XEN) Pagetable walk from c1268000:
> (XEN)  L3[0x003] =3D 000000003c8f0001 000008f0
> (XEN)  L2[0x009] =3D 000000003d276067 00001276=20
> (XEN)  L1[0x068] =3D 000000003d268061 00001268
> (XEN) domain_crash_sync called from entry.S (ff19f70e)
> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
> (XEN) ----[ Xen-3.3.1-11.fc11  x86_32p  debug=3Dn  Not tainted ]----
> (XEN) CPU:    0
> (XEN) EIP:    e019:[<c088adae>]
> (XEN) EFLAGS: 00000206   EM: 1   CONTEXT: pv guest
> (XEN) eax: 00000000   ebx: 00800000   ecx: 00200000   edx: c1268000
> (XEN) esi: 01268000   edi: c1268000   ebp: c086de5c   esp: c086de1c
> (XEN) cr0: 8005003b   cr4: 000006f0   cr3: 3c85c000   cr2: c1268000
> (XEN) ds: e021   es: e021   fs: e021   gs: e021   ss: e021   cs: e019
> (XEN) Guest stack trace from esp=3Dc086de1c:
>
> [root@dom0test linux-2.6-xen]# gdb ./vmlinux
> (gdb) x/i 0xc086de1c
> 0xc086de1c <init_thread_union+3612>:    add    %al,(%eax)
>
> 32b PAE dom0, 32b PAE hypervisor.=20
>  =20
"x/i 0xc088adae" would be more useful, as that will show the faulting=20
instruction.

I just booted a current xen-tip/next kernel as dom0 on my 32-bit machine=20
with no problems, so I'm not sure what's going wrong on your machine.

Ian, have you tried 32-bit boots lately?

    J