Re: [Xen-devel] What is the current state of Dom0 kernel support? / crash

[Pasi Kärkkäinen <pasik@xxxxxx>]

On Wed, Jul 15, 2009 at 11:22:42AM +0300, Pasi Kärkkäinen wrote:
> On Fri, Jul 10, 2009 at 01:24:14AM +0300, Pasi Kärkkäinen wrote:
> > On Wed, Jul 08, 2009 at 05:23:36PM -0700, Jeremy Fitzhardinge wrote:
> > > On 07/08/09 15:14, Pasi Kärkkäinen wrote:
> > > > On Fri, Jun 26, 2009 at 11:29:30AM -0700, Jeremy Fitzhardinge wrote:
> > > >   
> > > >> On 06/26/09 11:21, Tim Post wrote:
> > > >>     
> > > >>> Is it possible for you to set up a blog just for this? I think many
> > > >>> people are just going to pull your tree, it would be really, really 
> > > >>> nice
> > > >>> to have a feed to pull so we know when to pull and update .. 
> > > >>> especially
> > > >>> when the next merge window closes.
> > > >>>
> > > >>> As if you didn't have your hands full already :) Perhaps something on
> > > >>> xen.org just for kernel development?
> > > >>>
> > > >>> Sorry if something like this already exists.
> > > >>>   
> > > >>>       
> > > >> No, its a good idea.  I'll sort something out (and poke me if I don't
> > > >> appear to do anything in the next few days).
> > > >>
> > > >>     
> > > >
> > > > Btw what's the current tree people should be testing? xen-tip/next or
> > > > rebase/master? 
> > > 
> > > rebase/master is what I'm currently working on.  It's work-in-progress,
> > > but it works for me at the moment.  I'd appreciate any test results you
> > > have.  (I don't yet have a fix in there for your PAE issue however.)
> > > 
> > 
> > I just tried latest rebase/master (2.6.31-rc1) on Xen 3.4.0.
> > 
> > Seems to crash during dom0 kernel startup:
> > http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-log-09-rebase-master-with-highpte.txt
> > 
> > Checking if this processor honours the WP bit even in supervisor mode...
> > BUG: unable to handle kernel NULL pointer dereference at (null)
> > IP: [<c058d0e7>] xen_evtchn_do_upcall+0xcc/0x13f
> > *pdpt = 000000003d272001 
> > Thread overran stack, or stack corrupted
> > Oops: 0000 [#1] SMP 
> > 
> > It's 32bit PAE like usual..
> > 
> > My previous xen-tip/next 2.6.30-rc6-tip booted ok.
> > 
> 
> Is there something to test to debug this further? 
> 

I just tried the latest 32b PAE rebase/master tree (2.6.31-rc3).

http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-log-10-rebase-master-with-highpte.txt

Checking if this processor honours the WP bit even in supervisor mode...
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: [<c058cdcb>] xen_evtchn_do_upcall+0xcc/0x13f
*pdpt = 000000003d275001 
Thread overran stack, or stack corrupted
Oops: 0000 [#1] SMP 
last sysfs file: 
Modules linked in:

Pid: 0, comm: swapper Not tainted (2.6.31-rc3 #20) P8SC8
EIP: 0061:[<c058cdcb>] EFLAGS: 00010046 CPU: 0
EIP is at xen_evtchn_do_upcall+0xcc/0x13f
EAX: 00000000 EBX: ffffffff ECX: 00000000 EDX: 00000000
ESI: 00000000 EDI: c08ec558 EBP: c087eedc ESP: c087eea0
 DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: e021
Process swapper (pid: 0, ti=c087e000 task=c083b1a0 task.ti=c087e000)
Stack:
 00001a6e 00000220 00000200 00000000 00000000 00000000 e3201014 c08ec558
<0> c087eee4 f5681000 e3201010 00000000 00000000 c09017f8 f54ff000 c087ef20
<0> c0409927 00000000 c09017f8 f54ff000 c09017f8 f54ff000 c087ef20 c0843f70
Call Trace:
 [<c0409927>] ? xen_do_upcall+0x7/0xc
 [<c0404581>] ? xen_pte_clear+0x9/0x12
 [<c0427a94>] ? set_pte_vaddr+0xb4/0xc4
 [<c0426c8c>] ? __native_set_fixmap+0x25/0x30
 [<c040471a>] ? xen_set_fixmap+0xc7/0xcc
 [<c0897d86>] ? mem_init+0x24a/0x298
 [<c088367e>] ? start_kernel+0x14b/0x2cd
 [<c088336f>] ? unknown_bootoption+0x0/0x18e
 [<c0883082>] ? i386_start_kernel+0x71/0x79
 [<c0886188>] ? xen_start_kernel+0x52a/0x533
Code: d0 89 45 cc 89 55 c8 eb 16 0f bc c8 03 4d d4 8b 04 8a 83 f8 ff 74 f8
8b 55 e4 e8 36 de e7 ff 8b 55 f0 8b 45 d0 03 
05 1c 0c 97 c0 <8b> 0c 10 8b 55 e8 8b 45 cc 23 0c 82 8b 45 c8 8b 04 82 8b 15
18 
EIP: [<c058cdcb>] xen_evtchn_do_upcall+0xcc/0x13f SS:ESP e021:c087eea0
CR2: 0000000000000000
---[ end trace 4eaa2a86a8e2da22 ]---
Kernel panic - not syncing: Fatal exception in interrupt


-- Pasi

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel