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: [Xen-devel] xen.git branch reorg / crash with 2.6.30-rc3 pv_ops dom0

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] xen.git branch reorg / crash with 2.6.30-rc3 pv_ops dom0
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Mon, 27 Apr 2009 22:38:35 +0300
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Delivery-date: Mon, 27 Apr 2009 12:39:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49F6086D.1020602@xxxxxxxx>
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: <49F0A797.1050402@xxxxxxxx> <20090423182451.GV24960@xxxxxxxxxxxxxxx> <49F0B42E.2040904@xxxxxxxx> <20090425115404.GZ24960@xxxxxxxxxxxxxxx> <49F6086D.1020602@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
On Mon, Apr 27, 2009 at 12:33:01PM -0700, Jeremy Fitzhardinge wrote:
> Pasi Kärkkäinen wrote:
> >On Thu, Apr 23, 2009 at 11:32:14AM -0700, Jeremy Fitzhardinge wrote:
> >  
> >>Pasi Kärkkäinen wrote:
> >>    
> >>>I'll try upgrading from dom0/hackery to xen-tip/next and see how it works
> >>>for me. 
> >>> 
> >>>      
> >>Thanks.
> >>
> >>    
> >
> >
> >[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. 
> >  
> "x/i 0xc088adae" would be more useful, as that will show the faulting 
> instruction.
> I just booted a current xen-tip/next kernel as dom0 on my 32-bit machine 
> with no problems, so I'm not sure what's going wrong on your machine.

This is from xen-tip/master:

(XEN) d0:v0: unhandled page fault (ec=0003)
(XEN) Pagetable walk from c1266000:
(XEN)  L3[0x003] = 000000003c8ee001 000008ee
(XEN)  L2[0x009] = 000000003d274067 00001274 
(XEN)  L1[0x066] = 000000003d266061 00001266
(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=n  Not tainted ]----
(XEN) CPU:    0
(XEN) EIP:    e019:[<c0888d74>]
(XEN) EFLAGS: 00000206   EM: 1   CONTEXT: pv guest
(XEN) eax: 00000000   ebx: 00800000   ecx: 00200000   edx: c1266000
(XEN) esi: 01266000   edi: c1266000   ebp: c086be5c   esp: c086be1c
(XEN) cr0: 8005003b   cr4: 000006f0   cr3: 3c85a000   cr2: c1266000
(XEN) ds: e021   es: e021   fs: e021   gs: e021   ss: e021   cs: e019
(XEN) Guest stack trace from esp=c086be1c:

[root@dom0test linux-2.6-xen]# gdb vmlinux
(gdb) x/i 0xc0888d74
0xc0888d74 <__constant_c_memset+21>:    rep stos %eax,%es:(%edi)

-- Pasi

Xen-devel mailing list

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