I enabled early microcode update for my Intel Core i5 2540M and it was fine until I tried to resume from suspend (to RAM). Black screen, LED lights in unusual states, hard power off. Seems to work fine in 4.8.16 but I have only tried once so far. :) I wouldn't usually worry about reporting a bug on an old kernel version, but it's the latest stable version at the moment.
I wonder if this caused the problem I had (not resuming, system said it was resumed though (bios thought it was)). Will update if I have problems on 4.4.40/41
If anyone wants me to do further debugging, I'm happy to but you'll have to remind me how. :) (Still no problems on 4.8.16 btw.)
can you check with 4.4.44?
(In reply to Alice Ferrazzi from comment #3) > can you check with 4.4.44? Same problem.
Can you please attach dmesg from normal boot and "lspci -vvvv" output? Have you only set CONFIG_MICROCODE=y or are you actual using microcode updates? Than, how do you do your updates (using genkernel, own initramfs, embedded into kernel...)? If you found a working kernel it would be nice if you could bisect the kernel which would allow kernel upstream to backport the fix. See https://wiki.gentoo.org/wiki/Kernel_git-bisect for more details.
Created attachment 462342 [details] 4.8.17 dmesg, normal boot with suspends+resumes I wasn't sure which kernel version you wanted a dmesg from so I just started with the one that I'm using, which (unsurprisingly) is from the 4.8 series, that does not exhibit the bug. Do you want a dmesg from 4.4 too?
Created attachment 462344 [details] lspci -vvv output
Oh, I missed a 'v'; is it really -vvvv? The man page only documents up to -vvv.
I have enabled the early microcode update and loaded the microcode via CONFIG_EXTRA_FIRMWARE. So no initram or whatever that some how-tos describe.
4.8 is end of life and the upstream will no release bug-fixes for this kernel version. You should consider to upgrade to a more recent kernel and check if you still have problem
so it works in 4.8.17 ?
(In reply to Alice Ferrazzi from comment #11) > so it works in 4.8.17 ? Correct.
I haven't started the bisect yet, but I'm going to guess that the fix was introduced in 4.6.0: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=9cf8d6360c1589a97a98313729ed9e5db187f80b
Resolved upstream it seems, closing it. Reopen if occurring in newer kernels.