On Mon, Nov 04, 2019 at 11:04:21AM -0600, Amit Kulkarni wrote: > On Sun, Nov 3, 2019 at 1:33 PM Mike Larkin <[email protected]> wrote: > > > > On Sun, Nov 03, 2019 at 11:01:08AM -0800, Mike Larkin wrote: > > > On Sun, Nov 03, 2019 at 03:52:00PM +0100, Martin Pieuchot wrote: > > > > When halting/rebooting a i386 VM on an amd64 host (dmesg attached), the > > > > following fault is triggered. > > > > > > > > The same happens with a self built -current kernel w/o any suspect UVM > > > > diff :o) > > > > > > > > > > Works here on an Oct 21 kernel, are you saying something went in since > > > then > > > that started breaking this? > > > > > > > > > OpenBSD/i386 (test-i386.vm-7520.int.azathoth.net) (tty00) > > > > > > login: root > > > Password: > > > OpenBSD 6.6-current (GENERIC) #312: Mon Oct 21 21:14:28 MDT 2019 > > > > > > Welcome to OpenBSD: The proactively secure Unix-like operating system. > > > > > > Please use the sendbug(1) utility to report bugs in the system. > > > Before reporting a bug, please try to reproduce it with the latest > > > version of the code. With bug reports, please try to ensure that > > > enough information to reproduce the problem is enclosed, and if a > > > known fix for it exists, include that as well. > > > > > > You have mail. > > > -test-i386- ~> halt > > > syncing disks... done > > > vmmci0: powerdown > > > > > > The operating system has halted. > > > Please press any key to reboot. > > > > > > > > > [EOT] > > > > > > > > > I'll sysupgrade it and see if I see the problem. > > > > > > -ml > > > > > > > Yep, something went in between 21 Oct and now that broke it. I tried a 02 > > Nov > > snapshot as well as a kernel made from -current which includes your recent > > uvm revert, both failed: > > > > OpenBSD/i386 (test-i386.vm-7520.int.azathoth.net) (tty00) > > > > login: root > > Password: > > Last login: Sun Nov 3 11:27:50 on tty00 > > OpenBSD 6.6-current (GENERIC) #0: Sun Nov 3 11:25:25 PST 2019 > > > > Welcome to OpenBSD: The proactively secure Unix-like operating system. > > > > Please use the sendbug(1) utility to report bugs in the system. > > Before reporting a bug, please try to reproduce it with the latest > > version of the code. With bug reports, please try to ensure that > > enough information to reproduce the problem is enclosed, and if a > > known fix for it exists, include that as well. > > > > You have mail. > > -test-i386- ~> halt > > kernel: protection fault trap, code=0 > > Stopped at pmap_apte_flush+0x6: movl %eax,%cr3 > > ddb> > > > > > > i386 pmap hasn't been changed in ages, so this likely came from elsewhere. I > > made a quick trip through source-changes but couldn't find any likely > > suspects. > > > > Please check if reverting the reaper changes by visa@ works fine?
I have now reverted the changes.
