On 1/8/2020 12:33 PM, Jung-uk Kim wrote:
> On 20. 1. 8., mike tancsa wrote:
>> On 1/8/2020 10:15 AM, mike tancsa wrote:
>>> Going from a kernel from Dec 21st to today, my bhyve image no longer
>>> starts up. Is this possibly related to the mfc 356471 ?
>>>
>>>
>> OK, confirmed. Doing a svnlite
On 20. 1. 8., mike tancsa wrote:
> On 1/8/2020 10:15 AM, mike tancsa wrote:
>> Going from a kernel from Dec 21st to today, my bhyve image no longer
>> starts up. Is this possibly related to the mfc 356471 ?
>>
>>
> OK, confirmed. Doing a svnlite update -r356469, to just before the ACPI
> MFC
On 1/8/2020 10:15 AM, mike tancsa wrote:
> Going from a kernel from Dec 21st to today, my bhyve image no longer
> starts up. Is this possibly related to the mfc 356471 ?
>
>
OK, confirmed. Doing a svnlite update -r356469, to just before the ACPI
MFC allows be to start up my bhyve image.
Going from a kernel from Dec 21st to today, my bhyve image no longer
starts up. Is this possibly related to the mfc 356471 ?
/boot/kernel/kernel text=0x948ee3 data=0x13d9b8+0x463b10
syms=[0x8+0xef220+0x8+0x10ec23]
/boot/entropy size=0x1000
Booting...
/tmp/bhyve.e6GT9mY 61: [0001]