Freeze with newest kernel - probably Intel-Graphics related

Discussion:

(too old to reply)

Don Spam's Reckless Son

2023-03-18 08:00:16 UTC

kernel-default-5.14.21-150400.24.49.3.x86_64 came out a day or so ago
[leap 15.4] and I have been installing it on various machines. The AMD
machines with Radeon Graphics are perfectly happy with it but my
10-year-old Acer Laptop [intel graphics] freezes 3.6 seconds into the
boot process.

The last message before it stops is
fb0: switching to i915 from EFI VGA

The obvious workaround is to boot the previous kernel and that works
just fine.

I see others have had the problem over the last year, but theirs appear
to be with brand new Intel Graphics systems and that does not describe
my laptop.
https://superuser.com/questions/1761864/leap-15-4-boot-hangs-on-fbo-switching-to-i915-from-efi-vga
is an example.

Don Spam's Reckless Son

2023-03-18 10:12:01 UTC

Permalink

Post by Don Spam's Reckless Son
kernel-default-5.14.21-150400.24.49.3.x86_64 came out a day or so ago
[leap 15.4] and I have been installing it on various machines. The AMD
machines with Radeon Graphics are perfectly happy with it but my
10-year-old Acer Laptop [intel graphics] freezes 3.6 seconds into the
boot process.
The last message before it stops is
fb0: switching to i915 from EFI VGA
The obvious workaround is to boot the previous kernel and that works
just fine.
I see others have had the problem over the last year, but theirs appear
to be with brand new Intel Graphics systems and that does not describe
my laptop.
https://superuser.com/questions/1761864/leap-15-4-boot-hangs-on-fbo-switching-to-i915-from-efi-vga
is an example.

*Workaround*

It boots ok if I specify "nomodeset".

The messages which followed
fb0: switching to i915 from EFI VGA

with the *previous* kernel (and without nomodeset) were:
Console: switching to colour dummy device 80x25
i915 0000:00:02.0: vgaarb: deactivate vga console

grinch

2023-03-18 16:31:19 UTC

Permalink

Post by Don Spam's Reckless Son
kernel-default-5.14.21-150400.24.49.3.x86_64 came out a day or so ago
[leap 15.4] and I have been installing it on various machines. The
AMD machines with Radeon Graphics are perfectly happy with it but my
10-year-old Acer Laptop [intel graphics] freezes 3.6 seconds into the
boot process.
The last message before it stops is
fb0: switching to i915 from EFI VGA
The obvious workaround is to boot the previous kernel and that works
just fine.
I see others have had the problem over the last year, but theirs
appear to be with brand new Intel Graphics systems and that does not
describe my laptop.
https://superuser.com/questions/1761864/leap-15-4-boot-hangs-on-fbo-switching-to-i915-from-efi-vga is an example.

I have the same issue with my 3 year old i9 machine. I have taken the
lazy way out and boot from the previous kernel ,so its not just your old
laptop that is the issue.

Carlos E.R.

2023-03-18 21:06:42 UTC

Permalink

Has been commented on the mail list, there is a bugzilla, and they are
working on it.

https://bugzilla.opensuse.org/show_bug.cgi?id=1209436

--
Cheers, Carlos.

grinch

2023-03-20 09:29:03 UTC

Permalink

Post by Carlos E.R.

Post by Don Spam's Reckless Son
kernel-default-5.14.21-150400.24.49.3.x86_64 came out a day or so ago
[leap 15.4] and I have been installing it on various machines. The
AMD machines with Radeon Graphics are perfectly happy with it but my
10-year-old Acer Laptop [intel graphics] freezes 3.6 seconds into the
boot process.
The last message before it stops is
fb0: switching to i915 from EFI VGA
The obvious workaround is to boot the previous kernel and that works
just fine.
I see others have had the problem over the last year, but theirs
appear to be with brand new Intel Graphics systems and that does not
describe my laptop.
https://superuser.com/questions/1761864/leap-15-4-boot-hangs-on-fbo-switching-to-i915-from-efi-vga is an example.

Has been commented on the mail list, there is a bugzilla, and they are
working on it.
https://bugzilla.opensuse.org/show_bug.cgi?id=1209436

The offending kernel was in Yasts redacted list so I uninstalled it via
yast and all working properly now.

I have only added this post in case anybody else is looking for a simple
fix ,google will hopefully find this.

Carlos E.R.

2023-03-20 09:43:35 UTC

Permalink

Post by grinch

Post by Carlos E.R.

Post by Don Spam's Reckless Son
kernel-default-5.14.21-150400.24.49.3.x86_64 came out a day or so ago
[leap 15.4] and I have been installing it on various machines. The
AMD machines with Radeon Graphics are perfectly happy with it but my
10-year-old Acer Laptop [intel graphics] freezes 3.6 seconds into the
boot process.
The last message before it stops is
fb0: switching to i915 from EFI VGA
The obvious workaround is to boot the previous kernel and that works
just fine.
I see others have had the problem over the last year, but theirs
appear to be with brand new Intel Graphics systems and that does not
describe my laptop.
https://superuser.com/questions/1761864/leap-15-4-boot-hangs-on-fbo-switching-to-i915-from-efi-vga is an example.

Has been commented on the mail list, there is a bugzilla, and they are
working on it.
https://bugzilla.opensuse.org/show_bug.cgi?id=1209436

The offending kernel was in Yasts redacted list so I uninstalled it via
yast and all working properly now.
I have only added this post in case anybody else is looking for a simple
fix ,google will hopefully find this.

Google should find the thread in the mail list where the maintainer
explains what is going on, not this thread ;-)

+++..................
As already mentioned in this thread, it's tracked in
https://bugzilla.suse.com/show_bug.cgi?id=1209436

The problematic i915 fix patch was dropped from SLE15-SP4 git branch,
and the 5.14.21-150400.24.49 update kernel was retracted now.
We're going to prepare a new update.

The upstream 5.15.y hit the same issue and reverted it afterwards, but
unfortunately the revert was overlooked while backporting the fixes to
SLE15-SP4 branch. And it seemed slipping from QA's fingers...
..................++-

--
Cheers, Carlos.

Don Spam's Reckless Son

2023-04-01 08:26:08 UTC

Permalink

A new kernel was provided yesterday evening.
My Intel-Graphics machine is happy with it.

Don Spam's Reckless Son

2023-04-04 15:55:45 UTC

Permalink

One last comment on this subject.
I have a system where /boot is only large enough for two kernels
(actually, 3 would fit easily but the update process refuses to try) so
I have to remove the older kernel once I can see that the newer one is
working fine. Normally I go there and remove it using yast -> software
-> software management -> versions.

Since the previous installed kernel had been retracted, I decided to ssh
into the machine and mark the retracted kernel with "-" to uninstall it.
Of course it uninstalled both the old broken-with-intel-graphics kernel
along with the new one. Luckily everything I needed was in memory and I
could simply install the three current "kernel-default*" packages again.

We live and learn.

Carlos E.R.

2023-04-04 22:25:01 UTC

Permalink

Post by Don Spam's Reckless Son
One last comment on this subject.
I have a system where /boot is only large enough for two kernels
(actually, 3 would fit easily but the update process refuses to try) so
I have to remove the older kernel once I can see that the newer one is
working fine. Normally I go there and remove it using yast -> software
-> software management -> versions.

You could try to remove "plymouth" package, it is big and goes into
initrd. However, boot will be in text mode.

It might be enough bytes to make the 3 kernels fit.

Post by Don Spam's Reckless Son
Since the previous installed kernel had been retracted, I decided to ssh
into the machine and mark the retracted kernel with "-" to uninstall it.
Of course it uninstalled both the old broken-with-intel-graphics kernel
along with the new one. Luckily everything I needed was in memory and I
could simply install the three current "kernel-default*" packages again.
We live and learn.

kernel is a multiversion package. If you tick the top one, it deletes
them all. You have to do it in the "version" tab in yast.

--
Cheers, Carlos.

Don Spam's Reckless Son

2023-04-05 11:05:25 UTC

Permalink

Post by Carlos E.R.

Post by Don Spam's Reckless Son
One last comment on this subject.
I have a system where /boot is only large enough for two kernels
(actually, 3 would fit easily but the update process refuses to try)
so I have to remove the older kernel once I can see that the newer one
is working fine. Normally I go there and remove it using yast ->
software -> software management -> versions.

You could try to remove "plymouth" package, it is big and goes into
initrd. However, boot will be in text mode.
It might be enough bytes to make the 3 kernels fit.

You made that suggestion several months ago and I tried it, it did not
help. There is easily enough room in /boot for three kernels, it is the
update process being anal. Two kernels take around 50% of /boot so four
kernels would probably not work.

Post by Carlos E.R.

Post by Don Spam's Reckless Son
Since the previous installed kernel had been retracted, I decided to
ssh into the machine and mark the retracted kernel with "-" to
uninstall it.
Of course it uninstalled both the old broken-with-intel-graphics
kernel along with the new one. Luckily everything I needed was in
memory and I could simply install the three current "kernel-default*"
packages again.
We live and learn.

kernel is a multiversion package. If you tick the top one, it deletes
them all. You have to do it in the "version" tab in yast.

Yes, I saw that. I had thought I was just removing the Retracted
Installed Packages but when it listed the six packages it had removed it
was obvious that I had no kernel left.
Using the Version tab is what I normally do.

Carlos E.R.

2023-04-05 11:43:32 UTC

Permalink

Post by Don Spam's Reckless Son

Post by Carlos E.R.

Post by Don Spam's Reckless Son
One last comment on this subject.
I have a system where /boot is only large enough for two kernels
(actually, 3 would fit easily but the update process refuses to try)
so I have to remove the older kernel once I can see that the newer
one is working fine. Normally I go there and remove it using yast ->
software -> software management -> versions.

You could try to remove "plymouth" package, it is big and goes into
initrd. However, boot will be in text mode.
It might be enough bytes to make the 3 kernels fit.

Maybe temporary files while initrd archives are created.

Post by Don Spam's Reckless Son

Post by Carlos E.R.

Post by Don Spam's Reckless Son
Since the previous installed kernel had been retracted, I decided to
ssh into the machine and mark the retracted kernel with "-" to
uninstall it.
Of course it uninstalled both the old broken-with-intel-graphics
kernel along with the new one. Luckily everything I needed was in
memory and I could simply install the three current "kernel-default*"
packages again.
We live and learn.

kernel is a multiversion package. If you tick the top one, it deletes
them all. You have to do it in the "version" tab in yast.

Lucky you noticed before rebooting ;-)

--
Cheers, Carlos.