t;> 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.
>>>
>>> Try
>>>
>>> https://us-east.manta.joyent.com/jbk/public/OS-7079/platform
>&g
: Youzhong Yang
Reply: Youzhong Yang
Date: August 13, 2018 at 9:29:07 AM
To: Jason King
Cc: smartos-discuss@lists.smartos.org
Subject: Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common
races itself
Hi Jason,
The image that had the issue was a full build, but last night I
> bug in OS-7079, so I’ll see if I can get it to hang (though it’ll take a
> bit to do a full build).
>
>
> From: Youzhong Yang
> Reply: Youzhong Yang
> Date: August 13, 2018 at 12:27:52 AM
>
> To: Jason King
> Cc: smartos-discuss@lists.smartos.org
>
> Subject:
it to hang (though it’ll take a bit to do
a full build).
From: Youzhong Yang
Reply: Youzhong Yang
Date: August 13, 2018 at 12:27:52 AM
To: Jason King
Cc: smartos-discuss@lists.smartos.org
Subject: Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common
races itself
So your image
ll want to boot -k) — you can grab it at
>> https://us-east.manta.joyent.com/jbk/OS-7079/platform-201807
>> 19T001516Z.{iso,tgz,usb.bz2}
>>
>> If you do, it’d be interesting to see ::cpustack on each core looks like.
>>
>>
>> From: Youzhong Yang
>> Reply
@lists.smartos.org
Subject: Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common
races itself
I got this:
{"code":"ResourceNotFound","message":"/jbk/OS-7079/platform-20180719T001516Z.iso
does not exist"}
In our /etc/system, I ha
Subject: Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common
races itself
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
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
10 matches
Mail list logo
