Leap 15.5 in VMware - GUI fails to start after updates
I've got a test system in VMware Workstation 17.5 that, after applying the updates released since 2023-11-12, hangs upon reaching the start of the Locale service. It's not a "hard hang" - I can't toggle VTs in the VM, but I can connect via SSH. I've been able to reproduce this with a fresh installation as well from the most recent Net install ISO (also in VMware). Adding 'nomodeset' to the kernel line in grub gets me to a text login on tty1, but Xorg still fails to start. Looks like a segfault. The /var/log/Xorg.0.log is at https://paste.opensuse.org/pastes/ e8722dd3b81a I've added locks for xorg-x11-server, xorg-x11-server-extra, and xorg-x11- server-Xvfb (the three Xorg packages that show up for updates), but the system still fails to get to a GUI target. What other information would be useful to diagnose this issue? -- Jim Henderson Please keep on-topic replies on the list so everyone benefits
On 04.01.2024 07:13, Jim Henderson wrote:
I've got a test system in VMware Workstation 17.5 that, after applying the updates released since 2023-11-12, hangs upon reaching the start of the Locale service. It's not a "hard hang" - I can't toggle VTs in the VM, but I can connect via SSH.
I've been able to reproduce this with a fresh installation as well from the most recent Net install ISO (also in VMware).
Adding 'nomodeset' to the kernel line in grub gets me to a text login on tty1, but Xorg still fails to start. Looks like a segfault.
The /var/log/Xorg.0.log is at https://paste.opensuse.org/pastes/ e8722dd3b81a
[ 6.877] (EE) vmware(0): Unable to map frame buffer BAR. Invalid argument (22) It sounds like something changed in the kernel. Try rollback and applying each update one by one to find which package triggers this problem. Educated guess - it should be kernel update.
I've added locks for xorg-x11-server, xorg-x11-server-extra, and xorg-x11- server-Xvfb (the three Xorg packages that show up for updates), but the system still fails to get to a GUI target.
What other information would be useful to diagnose this issue?
On Thu, 4 Jan 2024 09:45:03 +0300, Andrei Borzenkov wrote:
[ 6.877] (EE) vmware(0): Unable to map frame buffer BAR. Invalid argument (22)
It sounds like something changed in the kernel. Try rollback and applying each update one by one to find which package triggers this problem. Educated guess - it should be kernel update.
Thanks - I'll give the kernel update a try and see if that resolves it. I had thought the xorg updates would (hence why I locked them), but that wasn't it. Will report back today if it was the kernel or not. The full list of updates is quite long (279 as I recall), so one-by-one would take a bit of time (suppose I could narrow it more quickly by going by halves instead of one by one, though). -- Jim Henderson Please keep on-topic replies on the list so everyone benefits
On Thu, 4 Jan 2024 18:02:05 -0000 (UTC), Jim Henderson wrote:
On Thu, 4 Jan 2024 09:45:03 +0300, Andrei Borzenkov wrote:
[ 6.877] (EE) vmware(0): Unable to map frame buffer BAR. Invalid argument (22)
It sounds like something changed in the kernel. Try rollback and applying each update one by one to find which package triggers this problem. Educated guess - it should be kernel update.
Thanks - I'll give the kernel update a try and see if that resolves it. I had thought the xorg updates would (hence why I locked them), but that wasn't it.
Will report back today if it was the kernel or not. The full list of updates is quite long (279 as I recall), so one-by-one would take a bit of time (suppose I could narrow it more quickly by going by halves instead of one by one, though).
This was a good guess - I started by locking anything starting with kernel-default, and the system booted successfully. I then updated just the kernel-default package, and the boot failed the same way. It seems that the update that causes this is the update from 5.14.21-150500.55.36 (which is what is working) to the latest 5.14.21-150500.55.39 version. Will get a bugzilla bug entered for it. Thanks for the pointer in the right direction. -- Jim Henderson Please keep on-topic replies on the list so everyone benefits
participants (2)
-
Andrei Borzenkov -
Jim Henderson