On Tue, Jan 08, 2019 at 03:40:23PM +0100, Christoph Badura wrote: > On Mon, Jan 07, 2019 at 03:08:38PM +0100, Manuel Bouyer wrote: > > it looks like this broke Xen domU: > > http://www-soc.lip6.fr/~bouyer/NetBSD-tests/xen/HEAD/ > > > > [ 1.0800662] boot device: xbd0 > > [ 1.0800662] xenbus: can't get state for device/suspend/event-channel (2) > > [ 1.0800662] unknown device major 0xffffffffffffffff > > [ 1.0800662] root device (default xbd0a): > > > > and it waits for the user to press enter > > do you have an idea ? > > Really? Are you sure that change makes a difference?
No, but it happended at about the same time. But a run with a 2019-01-06 13:20 UTC build installs and completes the tests successfully, so I guess something after this commit fixed it. > > I spent Wednesday/Thursday instrumenting that code and figuring out the > same symptom (unknown device major) for dom0. And the cause there is > not changed by Michael's change. I'm not sure that the "unknown device major" message is a problem, it may have been this way before. -- Manuel Bouyer <bou...@antioche.eu.org> NetBSD: 26 ans d'experience feront toujours la difference --