> I'm wondering if the recent Intel microcode updates and related kernel patches could be responsible? Can you tell us what CPU the system has?
And BINGO!
This was my suspicion too, I found a way to disable microcode updates to verify this:
WORKAROUND: disable intel microcode updates
From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920
1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub
2/ update-grub
Results:
- linux-generic (4.15.0.50):
- proceeds to boot (I see some dmesg output, modules loading; gets stuck on some err on loading i915 module, probably due to the lack of microcode and new HW?)
- linux-generic-hwe (4.18):
- not tested yet
- linux-generic-hwe-edge (5.0):
- boots without an error! OK :)
I'll be attaching the apport report for the ubuntu kernel I'm now able to boot.
@Simon, can you please test this workaround and verify this hits ASUS and confirms it blames intel-microcode?
> I'm wondering if the recent Intel microcode updates and related kernel patches could be responsible? Can you tell us what CPU the system has?
And BINGO! /bugs.launchpad .net/ubuntu/ +source/ intel-microcode /+bug/1759920
This was my suspicion too, I found a way to disable microcode updates to verify this:
WORKAROUND: disable intel microcode updates
From this bug: https:/
1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub
2/ update-grub
Results:
- linux-generic (4.15.0.50):
- proceeds to boot (I see some dmesg output, modules loading; gets stuck on some err on loading i915 module, probably due to the lack of microcode and new HW?)
- linux-generic-hwe (4.18):
- not tested yet
- linux-generic- hwe-edge (5.0):
- boots without an error! OK :)
I'll be attaching the apport report for the ubuntu kernel I'm now able to boot.
@Simon, can you please test this workaround and verify this hits ASUS and confirms it blames intel-microcode?