Re: disappointing upgrade to NetBSD 5.0

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Wed, May 27, 2009 at 11:49:04PM -0700, Dan Engholm wrote:
> On Tue, 26 May 2009 17:55:56 -0700, Sarton O'Brien 
> <bsd-xen%roguewrt.org@localhost>  
> wrote:
> 
> >On 26/05/2009 3:46 PM, Dan Engholm wrote:
> >>To the experts,
> >
> >Sorry but I'm replying anyway :P
> >
> >>I can't be sure what I am doing to get the problem to occur, but it  
> >>seems
> >>to be network related.  Looking around Google, I found one thread in
> >>port-xen with a similar description but it dead ended with no  
> >>resolution.
> >>(see http://mail-index.netbsd.org/port-xen/2009/01/18/msg004686.html)  I
> >>thought that since I was still using Xen 2, I should look at this as an
> >>opportunity to upgrade to Xen 3.  It was a further learning experience  
> >>but
> >>I did manage to get Domain0 up and running and also got my user domain
> >>created and booting.  But, before it finished its rc script, it died:
> >
> >I'm running a CURRENT dom0 kernel on 5.0 userland with xen33. I had  
> >issues with earlier versions of Xen. I keep moving forward with Xen3 and  
> >it seems to keep me ahead of the main problems, with the exception of an  
> >off by 1 issue here and there ;)
> 
> So I took a cue from you and upgraded my domain0 to NetBSD 5.0 so I could  
> move to Xen 3.3.  Now xdm doesn't work.  Sheesh.  I also tried to boot up  
> with the Xen 3.3 kernel.  The XEN3_DOM0 NetBSD kernel that came with  
> NetBSD 5.0 does not boot with this Xen kernel.  Since it automatically  
> reboots after a few seconds of delay, I can only go by my memory.  There's  
> some message about signatures for the two kernels not matching.  I had  
> assumed that a NetBSD Xen 3 kernel would work with Xen kernel 3.3.  Am I  
> wrong about this?
> 
> FWIW, here's the backtrace from booting my DomU under Xen 3:
> 
> Building databases:panic: buf mem pool index 7
> fatal breakpoint trap in supervisor mode
> trap type 1 code 0 eip c0394d3c cs 9 eflags 246 cr2 bbbc9924 ilevel 0
> Stopped in pid 102.1 (sh) at    netbsd:breakpoint+0x4:  popl    %ebp
> db> bt
> breakpoint(c0443ae7,cac55958,c0459400,c02fda7c,0,2,cac5596c,c02d1bfd,c0a9fe30,0)
>   
> at netbsd:breakpoint+0x4
> panic(c043c22f,7,cac5598c,c0337b38,c04b7260,c0a9fe30,cac5598c,c0341787,cac27f20,
>   
> c9d49508) at netbsd:panic+0x1a6
> buf_mempoolidx(c04b7260,c0a9fe30,cac5598c,c0341787,cac27f20,c9d49508,0,c0a9fe30,0,0)
>   
> at netbsd:buf_mempoolidx+0x34
> allocbuf(c0a9fe30,10000,0,c02fd893,c9d495e0,cacc8ba8,0,200,cac27f20,0) at  
> netbsd:allocbuf+0x18
> getblk(cac27f20,200,0,10000,0,0,cac55a1c,200,c0b26d80,cac27f20) at  
> netbsd:getblk+0x144
> bio_doread(10000,ffffffff,0,c03f04cc,2,0,100,200,c0b26d80,ffffffff) at  
> netbsd:bio_doread+0x37
> bread(cac27f20,200,0,10000,ffffffff,0,cac55aa8,0,531d,40) at  
> netbsd:bread+0x32
> ffs_vget(ca16f2e0,2,0,cac55ae8,cac2350c,0,cac55c14,0,ca16f2e0,0) at  
> netbsd:ffs_vget+0x383
> ufs_root(ca16f2e0,cac55b38,cac55c28,20002,c9d5bc38,c9d55f54,cac55b2c,c0352c35,20,0)
>   
> at netbsd:ufs_root+0x28
> lookup(cac55c00,20002,400,cac55c1c,22,3,1,0,cac55c1c,0) at  
> netbsd:lookup+0x287
> namei(cac55c00,cac365e0,0,c030796c,4,1,cac55ccc,bb90fb74,0,0) at  
> netbsd:namei+0x144
> do_sys_stat(bb90fb74,40,cac55c70,6,cac33f20,1000,0,0,8,cab83590) at  
> netbsd:do_sys_stat+0x37
> sys___stat30(cac30d00,cac55d00,cac55d28,bbbc9000,c9d58ac4,c9d58ac4,2,bb90fb74,bfbfdd1c,bfbfdd98)
>   
> at netbsd:sys___stat30+0x2c
> syscall(cac55d48,bb90001f,1f,bfbf001f,bbbb001f,1,2,bfbfdd98,bb90fb74,bb90fb74)
>   
> at netbsd:syscall+0xc7
> db>
> 

How was your filesystem formatted ? xen3 domU only support 32k MAXPHYS,
so you can't use a ffs with 64k block size ...

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--