On Thu, Jun 14, 2018 at 08:33:17AM -0600, Jan Beulich wrote:
> > So far I've not been able to make Xen panic with the new xen kernel.
> > Attached is a log of the serial console, in case you notice something.
> 
> None of the printk()s replacing ASSERT()s have triggered, so nothing
> interesting to lear from the log, unfortunately.
> 
> > I'll keep anita tests running in a loop overnight, in case it ends up
> > hitting an assert.

Hello,
the dom0 has been running for a week now, running the daily NetBSD tests.
Attached is the console log.
I didn't notice anything suspect, exept a few domU crashes (crashing in
Xen, the problem is not reported back to the domU). But as this is
running NetBSD-HEAD tests it can also be a bug in the domU, that has
been fixed since then.

It's possible that the printk changed timings in a way that prevents the
race condition from happening ...

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

Attachment: xen1.gz
Description: application/gunzip

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Reply via email to