So your image booted up. Interesting ... Maybe something else messed up
your fix?
Anyway I am now building my image and see what I can get from ::cpustack.
On Mon, Aug 13, 2018 at 1:14 AM, Jason King
wrote:
> Doh.. the problems of it being late :) .. there should be a ‘public’ in
> there.
>
>
Doh.. the problems of it being late :) .. there should be a ‘public’ in there.
Try
https://us-east.manta.joyent.com/jbk/public/OS-7079/platform-20180719T001516Z.iso
From: Youzhong Yang
Reply: Youzhong Yang
Date: August 13, 2018 at 12:12:52 AM
To: Jason King
Cc:
There’s a couple of ways — you can boot -kd and set a breakpoint to set it.
You can also set it in etc/system in the proto area when building an image.
If you want, I do have an image of 20180719 w/ OS-7079 applied and kmdb on NMI
already set (you’d still want to boot -k) — you can grab it at
I sent NMI, but it printed out a stack trace plus a message "no dump
device" or something then rebooted. I tried -v on my old supermicro system,
on the console I saw message about sd## devices, then it hung. The console
still responded to keyboard, but just stayed that way forever.
What change is
So I tried on our new Supermicro X11DPU system ( Intel(R) Xeon(R) Gold 6140
CPU @ 2.30GHz ), same issue, hung at boot, but with OS-7079 reverted, it
booted up successfully.
I can try NMI tomorrow and update.
On Mon, Aug 13, 2018 at 12:06 AM, Jason King
wrote:
> Was that with boot -v? Are you
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
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
