Please test EARLY_AP_STARTUP
Sepherosa Ziehau
sepherosa at gmail.com
Mon Nov 28 06:35:10 UTC 2016
Hi John,
fdc seems to cause panic on Hyper-V:
https://people.freebsd.org/~sephe/fdc_panic.png
I then commented out device fdc, and I fixed one panic on Hyper-V here:
https://reviews.freebsd.org/D8656
After fdc is disabled and hyperv/storvsc is fixed, it seems to boot
fine, except a long delay (28~30seconds) here:
....
Timecounters tick every 1.000 msec
-----
28 ~ 30 seconds delay
-----
vlan: initialized, using hash tables with chaining
....
I have the bootverbose dmesg here:
https://people.freebsd.org/~sephe/dmesg_earlyap.txt
I booted 10 times, only one boot does not suffer this 30 seconds
delay. It sounds like some races to me. Any hints?
Thanks,
sephe
On Sat, Nov 26, 2016 at 2:20 AM, John Baldwin <jhb at freebsd.org> wrote:
> I plan to enable EARLY_AP_STARTUP on x86 in a week on HEAD. Some folks
> have been testing it for the last week or so which has exposed some
> additional things to fix. I think I've resolved most of those in one
> way or another, but it will make things smoother if other folks can
> start testing this over the next few days before it is enabled by default.
>
> (To enable, add 'options EARLY_AP_STARTUP' to your kernel config.)
>
> Note that non-x86 platforms should eventually adopt this, but I don't
> think any of them are ready yet.
>
> --
> John Baldwin
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
--
Tomorrow Will Never Die
More information about the freebsd-current
mailing list