On Mon, Apr 30, 2018 at 07:31:28AM -0600, Jan Beulich wrote:
> >>> On 25.04.18 at 16:42, <bou...@antioche.eu.org> wrote:
> > On Wed, Apr 25, 2018 at 12:42:42PM +0200, Manuel Bouyer wrote:
> >> > Without line numbers associated with at least the top stack trace entry
> >> > I can only guess what it might be - could you give the patch below a try?
> >> > (This may not be the final patch, as I'm afraid there may be some race
> >> > here, but I'd have to work this out later.)
> >>
> >> Yes, this works. thanks !
> >> I'll now put this version on the NetBSD testbed I'm running.
> >> This should put some pressure on it.
> >
> > Running NetBSD tests in several guests I got:
> > (XEN)
> > (XEN) ****************************************
> > (XEN) Panic on CPU 1:
> > (XEN) Assertion 'oc > 0' failed at mm.c:628
> > (XEN) ****************************************
> > (see attached file for complete report).
>
> So in combination with your later reply I'm confused: Are you observing
> this with 64-bit guests as well (your later reply appears to hint towards
> 64-bit-ness), or (as the stack trace suggests) only 32-bit ones? Knowing
> this may already narrow areas where to look.
I've seen it a server where, I think, only 32bits domUs are running.
But the dom0 is a 64bits NetBSD anyway.
--
Manuel Bouyer <bou...@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
