Dell Latitude 7300, i7-8665U, sig=0x806ec/20200609: hangs on Whiskey Lake
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OEM Priority Project |
New
|
Undecided
|
Unassigned | ||
intel-microcode (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Basically the same symptoms as #1882809, but with 20.04 and on an i7-8665U (Dell Latitude 7300).
Affected version is 3.20200609.
CPU:
Vendor ID: GenuineIntel
CPU family: 6
Model: 142
Model name: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz
Stepping: 12
microcode: sig=0x806ec, pf=0x80, revision=0xca
The first sign of a problem was a hard lockup while processing the new microcode package as part of a larger update; after fixing the resulting mess and completing the update (which regenerated the initramfs) I started having random lockups early in the boot process, with just "Loading initramfs" printed on the console.
Downgrading intel-microcode to 3.20191115.1ubuntu3 and regenerating the initramfs fixes the problem.
Changed in intel-microcode (Ubuntu): | |
status: | Fix Released → Incomplete |
Changed in intel-microcode (Ubuntu): | |
status: | Fix Released → Incomplete |
Changed in intel-microcode (Ubuntu): | |
status: | Fix Released → Confirmed |
summary: |
- intel-ucode 20200609: hangs on Whiskey Lake + Dell Latitude 7300, i7-8665U, sig=0x806ec/20200609: hangs on Whiskey + Lake |
tags: | added: merion oem-priority somerville |
On Wed, 10 Jun 2020, Andrea C wrote:
> CPU family: 6
> Model: 142
> Model name: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz
> Stepping: 12
>
> microcode: sig=0x806ec, pf=0x80, revision=0xca
>
> The first sign of a problem was a hard lockup while processing the new
> microcode package as part of a larger update; after fixing the resulting
At that moment in time, the microcode *is not changed*. Only a *reboot*
(or shutdown + powerup) would load the new microcode update.
That means the update run hang with whatever older microcode and kernel
you already had at the time -- so, it was not caused by the
intel-microcode update, *unless* you already had intel-microcode
installed and had already rebooted for some reason.
> Downgrading intel-microcode to 3.20191115.1ubuntu3 and regenerating the
> initramfs fixes the problem.
If it is not asking too much, with the computer fully stable and
intel-microcode 3.20191115.1ubuntu3 installed (*and* rebooted so that it
got applied to the processor), could you please do another install
cycle, *just* with the intel-microcode security update that supposedly
caused issues?
It must complete the update safely, it will not attempt to update the
processor. Only when you reboot, will it attempt to install the updated
microcode into the processor.
Please ensure you have enough free space in /boot: if it fills up, *bad
things can (and likely will) happen* the next time you reboot.
If the reboot to activate the microcode update does hang, does it also
hang when powering up the computer with the new microcode package
installed (instead of rebooting)?
--
Henrique Holschuh