Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi

[Harry G McGavran Jr]

Intel Micorocde 3.20191115.1ubuntu0.16.04.2 STILL hangs on warm reboot
with Dell T5820 and Intel(R) Xeon(R) W-2125 CPU

Reverting to 3.20151106.1 fixes the problem.

Running Ubuntu 16.04 LTS.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Seth Arnold (seth-arnold)]

Hello Harry,

Just to double-check, did you perform a *cold* reboot at least once after installing the 3.20191115.1ubuntu0.16.04.2?

Can you please provide the output of:

iucode-tool -S

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.)

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

[Harry G McGavran Jr (w5pny)]

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?
>
> 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
>

[Harry G McGavran Jr (w5pny)]

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
>>

[Harry G McGavran Jr (w5pny)]

I finally got a little time to try to search for which package exactly
causes this problem.

I downloaded:

intel-microcode_3.20151106.1_amd64.deb
intel-microcode_3.20190618.0ubuntu0.16.04.1_amd64.deb
intel-microcode_3.20191112-0ubuntu0.16.04.2_amd64.deb
intel-microcode_3.20191115.1ubuntu0.16.04.1_amd64.deb
intel-microcode_3.20191115.1ubuntu0.16.04.2_amd64.deb

I had downgraded to 3.20151106.1, which is working.

So, I tried intel-microcode_3.20190618.0ubuntu0.16.04.1_amd64.deb,
and it worked ok.

So, next I tried intel-microcode_3.20191112-0ubuntu0.16.04.2_amd64.deb,
and it worked ok.

So, Next I tried intel-microcode_3.20191115.1ubuntu0.16.04.1_amd64.deb
and it hangs on warm reboot.

So, next I tried intel-microcode_3.20191112-0ubuntu0.16.04.2_amd64.deb,
and NOW IT hangs on warm reboot.

So, next I tried intel-microcode_3.20190618.0ubuntu0.16.04.1_amd64.deb,
and now IT TOO hangs on warm reboot.

So, Next I tried intel-microcode_3.20151106.1_amd64.deb,
and it works ok --

Unfortunately, I just don't have time to go back one by one through
all the releases between 3.20151106.1 and 3.20190618.0 to
see how far back I need to go before finding where it really would
start working ok again.

I find it very puzzling that the packages all worked until I got
to 3.20191115.1ubuntu0.16.04.1, and then none of them worked
until I backed off all the way to 3.20151106.1. There must be a clue in
that somewhere.

Good luck, I hope you find it -- I'm staying locked on 3.20151106.1
until this gets fixed...

   Harry

On 12/17/19 12:51 PM, Harry G McGavran Jr wrote:
>
>
> 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
>>>

[Henrique de Moraes Holschuh (hmh)]

This has been reported to be fixed on very similar processors (with the same microcode signature as yours) in the 20200609 microcode updates, could you test them?

[Harry G McGavran Jr (w5pny)]

On 6/10/20 5:48 PM, Henrique de Moraes Holschuh wrote:
> This has been reported to be fixed on very similar processors (with the
> same microcode signature as yours) in the 20200609 microcode updates,
> could you test them?
>

I see four versions on your webpage:

two versions of 3.20200609.0ubuntu0.16.04.1
and two versions of 3.20200609.0ubuntu0.16.04.0.

I downloaded all four and both versions of 3.20200609.0ubuntu0.16.04.1
compared without any differences AND both versions of
3.20200609.0ubuntu0.16.04.0 compared without any differences. So in
spite of the statement on the web page that each of those versions had a
different publishing time, the two versions of .1 seem to be the same
and the two versions of .0 seem to be the same.

So I tried BOTH versions and warm reboots DID work with either .0 or .1.

I left my machine with 3.20200609.0ubuntu0.16.04.1

Let me know if I missed any version you wished me to test...

    Harry McGavran

[Henrique de Moraes Holschuh (hmh)]

That's enough, it confirms that the bug is *fixed*.

Thank you

[Henrique de Moraes Holschuh (hmh)]

Fixed by upstream 20200609 release.