Re: Panic on reboot in very -current XEN3_DOM0 (both amd64 and i386)

[Sarton O'Brien <bsd-xen%roguewrt.org@localhost>]

On Fri, 18 Jul 2008 07:53:27 am Johan Ihren wrote:
> I've been living with these since 4.99.68 or .69 (I think .67 was
> fine, at least for amd64 which was the only thing I ran then) and the
> panic is still there in 4.99.70 with source from an hour ago.
> 
> On reboot:
> 
> Stopped in pid 201.1 (mount_mfs) at ...
> breakpoint() ...
> panic() ...
> kmem_poison_check()
> kmem_backend_free()
> amap_free()
> uvm_unmap_detach()
> uvmspace_free()
> exit1()
> sigexit()
> postsig()
> lwp_userret()
> syscall()
> ...
> 
> Note #1: an i386 XEN3_DOM0 kernel produced exactly the same panic
> trace as the amd64 one.
> 
> Note #2: "halt" produces the same panic on amd64 but works ok on i386
> (it hangs after unmounting /, though, but that's another issue).
> 
> Note #3: GENERIC kernels (both amd64 and i386) from the same sources
> and running on the same userland works just fine.
> 
> Anyone else rebooting their DOM0s recently?

From memory there was another problem where I think using a debug or lockdebug 
kernel broke mfs. Due to this problem, a few of us are avoiding mfs use.

Seeing as you say GENERIC works fine, maybe this is related in some way.

Sarton