Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common races itself

2018-08-14 Thread Youzhong Yang
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

Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common races itself

2018-08-13 Thread Jason King
: 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

Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common races itself

2018-08-13 Thread Youzhong Yang
ouzhong Yang >> Reply: Youzhong Yang >> Date: August 13, 2018 at 12:12:52 AM >> >> To: Jason King >> Cc: smartos-discuss@lists.smartos.org >> >> Subject: Re: [smartos-discuss] still hang at boot - OS-7079 >> mp_startup_common

Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common races itself

2018-08-13 Thread Jason King
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

Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common races itself

2018-08-12 Thread Youzhong Yang
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

Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common races itself

2018-08-12 Thread Jason King
@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

Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common races itself

2018-08-12 Thread Jason King
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

Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common races itself

2018-08-12 Thread Youzhong Yang
> Date: August 12, 2018 at 10:46:05 PM > To: 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. I

Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common races itself

2018-08-12 Thread Youzhong Yang
sy to > trigger until recent CPUs. > > > From: Youzhong Yang > Reply: smartos-discuss@lists.smartos.org smartos.org> > Date: August 12, 2018 at 10:46:05 PM > To: smartos-discuss@lists.smartos.org > > Subject: [smartos-discuss] still hang at boot - OS-7079 >

Re: [smartos-discuss] still hang at boot - OS-7079 mp_startup_common races itself

2018-08-12 Thread Jason King
until recent CPUs. From: Youzhong Yang Reply: smartos-discuss@lists.smartos.org Date: August 12, 2018 at 10:46:05 PM To: 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

[smartos-discuss] still hang at boot - OS-7079 mp_startup_common races itself

2018-08-12 Thread Youzhong Yang
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