Port-xen archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: amd64 panics w/XEN_DOM0, not GENERIC



On Wed, Aug 20, 2008 at 04:43:29PM -0400, Todd Kover wrote:
> 
>  > > I slowly paired things down so I was not running any xen daemons and
>  > > consequently, no domUs, and had eventually dedicated all of the 4gb
>  > > of memory to dom0.
>  > 
>  > Which is probably the cause of your problem.
> 
> I left out some detail on what I slowly paired down: I started running
> xen daemons and domUs.  I got the kern_physio.c panic.  A few days
> later after it was clear it was systemic, I tried just the xen daemons
> with no domUs, got the kern_physio.c panic, after a few more days
> of repititions, I killed the xen daemons and continue to get the
> kern_physio.c panic.  I ran generic for a few days, didn't get any
> panics, went back to xen kernel, didn't bother going back to starting
> xen daemons and got a new panic.  I tried GENERIC kernels interpersed in
> there and it was always fine.
> 
> Whether or not xen daemons running seems to have no impact.
> 
> However, in any case, it seems like a panic is never the right
> behavior...

Could you try a GENERIC+DEBUG+DIAGNOSTIC kernel ? XEN3_DOM0 has
options DEBUG
options DIAGNOSTIC
while GENERIC doesn't.

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


Home | Main Index | Thread Index | Old Index