On Sat, Nov 24, 2018 at 02:44:37PM -0500, Bryan Steele wrote: > On Sat, Nov 24, 2018 at 07:38:32PM +0000, Leighton Sheppard wrote: > > Hi, > > > > > > > > I just wanted to point this bug out in case this hasn't been reported yet. > > Upgrading to latest -current (GENERIC.MP#466 amd64), the upgrade completed > > ok, however, after the first reboot the kernel panics. > > > > The same panic can be repeated by simply rebooting the VM. The host is a > > Windows 10 x64 (1809 - 17763.134). > > > > I managed to catch some of this crash below and can provide screenshots, > > if this is preferred: > > > > pvbus0 at mainbus0: Hyper-V 10.0 > > pvclock0 at pvbus0panic: pvclock0: unstable result on stable clock > > Stoped at db_enter+0x12: popq %rll > > TID PID UID PRFLAGS PFLAGS CPU COMMAND > > * 0 0 0 0x10000 0x200 0K swapper > > db_enter(32812156fefcc1ab,100,10,ffffffff81f6daa8,202,8) at db_enter+0x12 > > panic(0,ffffffff81c7b330,ffffffff81c7b310,ffff800000068780,ffff8000000687a > > 4,ffffffff81ce24e9) at panic+0x120 > > pvclock_get_timecount(e27619fa46d73893,ffffffff81c8bd28,ffffffff810eww48, > > ffffffff81f6db60,0,fffffffff81c7b330) at pvclock_get_timecount+0xa8 > > > > I can boot into an older kernel to grab a dmesg if this is required? > > > > Kind Regards, > > Leighton > > This should be fixed by the latest commit by phessler@ > > https://marc.info/?l=openbsd-cvs&m=154307429728533&w=2 >
Thank you Bryan, I appreciate the quick response. I will update to a newer snapshot on this VM shortly. Kind regards, Leighton
