Hi,
I have a old (core i7 ) system running on all previous version of LEAP 15 and all kernels and never had a problem with any.
Yesterday I ran my usual update and among others the new kernel was installed.
Today I was booting the machine for the first time and it simply does not boot. I can not even know what is happening since there are no logs on disk … the system hangs/freezes before I even have the option to insert the luks filesystem pass … I even thought I had a hardware failure such was the early freeze on the kernel.
I could only detect that there was no issue with hardware since I booted from an old dvd and all drives mounted with no problem and fsck was ok.
Booting from the previous kernel vmlinuz-5.14.21-150400.24.46-default is what allowed me to be writing in here.
Does anyone have any idea what is happening ?
Also is there a good idea to revert/delete the last update?
Regards
A long time to release a Kernel patch when the solution was already found.
But you did read the bugreport? The issue was caused by an upstream commit for intel i915 driver. So no fault on openSUSE side. openSUSE kernel maintainer has done what was possible and retracted the affected kernel with the applied upstream commit less than 22 hours after the bug was opened… 
The solution must be found by the upstream intel team…
it’s easy to bash when there is a lack of understanding… 
What exact problem do you have with the working kernel that so desperately needs patching?
The issue was caused by upstream commit which was already reverted upstream before it was backported to SUSE kernel, but this revert was overlooked. So if we start to point fingers, it was most certainly fault on SUSE side.
I’m not bashing, I’m not pointing fingers.
I’m not or was not pointing fingers , I quite literally do not care who or what happened. that’s truly not important.
The info on the new kernel (49) was several security patches. I want those …
I have this same issue on a Lenovo Ideapad 305 that has had Win 10 and OpenSuSE happily co-existing since the day I bought the machine from new and until I upgraded it from Leap 15.3 to 15.4 just 5 days ago.
The only way out was to hold the power button for 6 seconds until it powered off, then restart with the previous kernel 5.14.21-150400.24.46-default by using the 3rd option in the recovery menu of Grub’s boot menu. That kernel seemed to work OK. I say seemed because as it started to load prior to the actual boot sequences getting underway, I felt that had I caught a brief glimpse of the same error message that had frozen on screen for the 24.49 version but it successfully continued with the rest of the boot sequence to a working desktop.
Sure enough I found this message early on in the boot.msg file in /var/log/just after line 230 :
<3>[ 0.101398] DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000009d800000-0x000000009fffffff], contact BIOS vendor for fixes
<4>[ 0.101406] DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR [0x000000009d800000-0x000000009fffffff]
I tried flashing the firmware with latest version from Lenovo support which worked fine, but it made no difference to this issue at all.
I searched Bugzilla and found this: Bug 1165939 - Bios firmware memory errors in boot.msg
However it is from 2020 and appears to have gone to a back burner with no resolution so it didn’t really help me and I had trouble logging in to Bugzilla to try to escalate it again.
Has anyone else seen this and found a decent workaround?? The worry I have is that the warnings are there even n the earlier kernel even though it manages to boot.