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

On Fri, May 01, 2009 at 11:35:19AM -0700, Jeremy Fitzhardinge wrote:
> Pasi Kärkkäinen wrote:
> >On Wed, Apr 29, 2009 at 09:25:24AM -0700, Jeremy Fitzhardinge wrote:
> >  
> >>>There was some unification work in this area around the
> >>>beginning of March although I'm pretty such I've had it work much more
> >>>recently. (I guess it might not have been merged into a visible branch
> >>>until more recently, it's a bit hard to tell with git but I don't think
> >>>that's what happened).
> >>>      
> >>Yeah, I think it has been working properly for some since then, though I 
> >>think Pasi has been reporting problems since 32-bit dom0 first booted.
> >>
> >>    
> >
> >Yep, I've had problems from the beginning.. 
> >
> >dom0/hackery was working pretty OK for me before it was removed.. 
> >I could run and install new PV guests etc.
> >  
> Sorry, perhaps I was too hasty in removing the branches.  Though you 
> still have references in your own git tree?
> You still had problems with HIGHPTE in hackery?  My suspicion is that 
> we're seeing the same bug manifesting in a much more obvious way, since 
> I'm seeing somewhat similar symptoms, even without HIGHPTE.

Actually I didn't try with CONFIG_HIGHPTE=y for some time, since I didn't see 
any notes about it being fixed/changed..

> >>I also realized that my Xen doesn't have debug=y set, so I'm probably 
> >>missing some information.
> >>
> >>    
> >
> >Hmm, good point. I don't have debug=y either.. 
> >  
> That would be useful.  It would be interesting to see if Xen complains 
> about any stray pte writes.

And here we go:

(XEN) d0:v0: unhandled page fault (ec=0003)
(XEN) Pagetable walk from c1268000:
(XEN)  L3[0x003] = 000000003c8ee001 000008ee
(XEN)  L2[0x009] = 000000003d276067 00001276 
(XEN)  L1[0x068] = 000000003d268061 00001268
(XEN) domain_crash_sync called from entry.S (ff1a5c72)
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.3.1-12.0customdebug1.fc11  x86_32p  debug=y  Not tainted ]----
(XEN) CPU:    0
(XEN) EIP:    e019:[<c0888d87>]

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

-- Pasi

Xen-devel mailing list