Was that with boot -v? Are you able to send the system an NMI after it hangs (or get the boot -v output up to the hang)?
Prior to OS-7079, the system would start to startup the next CPU before it had completely finished initializing the ‘current’ CPU (which could deadlock depending on which CPU obtained a particular lock first), the change makes it wait until the current CPU is finished starting up before proceeding to the next CPU. It’s certainly possible it could have revealed another bug — OS-7079 itself was introduced almost 10 years ago, but didn’t seem to be easy to trigger until recent CPUs. From: Youzhong Yang <youzh...@gmail.com> Reply: smartos-discuss@lists.smartos.org <smartos-discuss@lists.smartos.org> Date: August 12, 2018 at 10:46:05 PM To: smartos-discuss@lists.smartos.org <smartos-discuss@lists.smartos.org> Subject: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common races itself Today I built a smartos image (with all git repos synced to master) and rebooted the host with that image. It hung after the banner message + one more line about power management or something. Then I reverted OS-7079, built an image, rebooted, it worked perfectly. So does it mean OS-7079 fixed one issue, but caused another? My host is an old Supermicro X8DAH, Intel(R) Xeon(R) CPU X5570 @ 2.93GHz. Tomorrow I will try on a new all NVMe system and see if it works. Thanks. smartos-discuss | Archives | Modify Your Subscription
signature.asc
Description: Message signed with OpenPGP using AMPGpg
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125 Powered by Listbox: https://www.listbox.com
