On 12/17/19 12:13 PM, Harry G McGavran Jr wrote:
>
>
> On 12/17/19 11:52 AM, Seth Arnold wrote:
>> Hello Harry,
>>
>> Just to double-check, did you perform a *cold* reboot at least once
>> after installing the 3.20191115.1ubuntu0.16.04.2?
Meant to respond to this in my first reply...
The answer to this one is yes.
The only way I could get the system to come up was with a cold boot as
well. This was true for each of the last two microcode releases
in my update stream.
Harry
>>
>> Can you please provide the output of:
>>
>> iucode-tool -S
>
> iucode-tool: system has processor(s) with signature 0x00050654
>
>>
>> It might also be helpful to know where exactly the failure started;
>> previous releases can be found on
>> https://launchpad.net/ubuntu/xenial/+source/intel-microcode
>>
>> (I'm guessing it's probably fastest to just work backwards up the list
>> rather than bisecting, but that's a guess.)
>
> I believe it was a problem with the last two microcode releases for
> Ubuntu 16.04 LTS.
>
> That would be the 3.20191115 and 3.20191112 releases.
> The 3.20190618 releases and before were ok.
>
> Exactly which ones on 3.20191115 and 3.20191112, I don't
> know without trying them, but the ones in the update stream
> for Ubuntu 16.04 LTS are the ones where I had trouble.
>
> Harry
>
>>
>> Here's the previous bug report for a handy link for navigating among the
>> bugs:
>> https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1854764
>>
>> Thanks
>>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855784
Title:
Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot
with Intel(R) Xeon(R) W-2125 CPUi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1855784/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
