Toomas Soome wrote:
On 18 Sep 2019, at 18:01, Yuri Pankov <yur...@yuripv.net> wrote:
I have tested several snapshot ISOs available for download:
FreeBSD-13.0-CURRENT-amd64-20190822-r351363-disc1.iso - OK
FreeBSD-13.0-CURRENT-amd64-20190829-r351591-disc1.iso - OK
FreeBSD-13.0-CURRENT-amd64-20190906-r351901-disc1.iso - FAIL
FreeBSD-13.0-CURRENT-amd64-20190913-r352265-disc1.iso - FAIL
FAIL being VM shutdown after loading kernel/modules and displaying "EFI framebuffer
information". Relevant messages in the VM log are rather unhelpful:
2019-09-18T14:47:12.397Z| vcpu-0| I125: Guest: Firmware has transitioned to
runtime.
2019-09-18T14:47:12.434Z| vcpu-0| I125: Msg_Post: Error
2019-09-18T14:47:12.434Z| vcpu-0| I125: [msg.efi.exception] The firmware
encountered an unexpected exception. The virtual machine cannot boot.
Any hints on debugging this further?
Im not really sure about debugging; I can not tell about early kernel, but I’d
check if the kernel/module locations conflict with efi memory map items…
The same issue can be seen with vmware fusion, it is not 100% repeatable but
I’d say, 95%, starting grab_faults, perhaps ls or some other random command,
and boot -v may actually start the system up.
OK. It's 100% reproducible here, going from 20190829 (which works) to
20190906 (which doesn't), so I was wondering if anything in
r351591-r351901 range could be pointed at as a likely offender.
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
