[Bug 1200584] New: Alien:Isolation crashes to desktop after upgrade to 5.17.9
http://bugzilla.opensuse.org/show_bug.cgi?id=1200584 Bug ID: 1200584 Summary: Alien:Isolation crashes to desktop after upgrade to 5.17.9 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: Michael.Zapf@mizapf.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 859634 --> http://bugzilla.opensuse.org/attachment.cgi?id=859634&action=edit snapper status Alien:Isolation (game ported by Feral, run in Steam) crashes to desktop after some seconds in the game. Console output says segmentation fault, but no other helpful information. The crash occurs since the upgrade to 5.17.9 on 2022-05-24. The previous release that still works (verified by booting as a snapshot) is 5.17.7 of 2022-05-16. Later releases (5.18.x) are also affected. I attach a snapper status output between the last working and the first non-working release as available on my computer. My apologies if this bug tracker is not appropriate for this issue. As always, issues of this kind are difficult to report; you don't even know where to report first: distributor, video drivers, game, ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200584 http://bugzilla.opensuse.org/show_bug.cgi?id=1200584#c2 --- Comment #2 from Michael Zapf <Michael.Zapf@mizapf.de> --- In order to boot an older kernel, I will have to roll back. There is no older kernel left in my current system (only vmlinuz-5.17.9-1-default in /boot). When I do that, and then trigger an update, I will do a long jump to 5.18.4; I doubt that the libs will then run with the old kernel. I can roll back and then try to do updates to Mesa etc. first, without doing a dist upgrade. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200584 http://bugzilla.opensuse.org/show_bug.cgi?id=1200584#c3 --- Comment #3 from Takashi Iwai <tiwai@suse.com> --- Hmm, too bad that the old kernel doesn't exist. Unfortunately, 5.17.7 is no longer found in TW history repo, either. Another possible check would be to roll back to the old system, then upgrade only the kernel to the newer one. But, as the issue still happens with 5.18 kernel and the latest update, it's very likely a bug in the game program (or the underlying system) itself -- unless you see any relevant messages in the kernel log. You can try to catch the crash core and check with gdb, too. Or you can get strace output to see what triggers the crash. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200584 http://bugzilla.opensuse.org/show_bug.cgi?id=1200584#c4 --- Comment #4 from Michael Zapf <Michael.Zapf@mizapf.de> --- The problem is that Alien:Isolation is one of those Feral games that seem to be very brittle when things change around them. I remember that some years ago I could not play it for months, then it suddenly worked again until now. Catching the dump and using the debugger is a small hope, but I don't really believe it will help, because I know from own works that unless you do a debug build or have all the symbols, the debugger output is almost useless. I could decide to keep that snapshot and finish the game (I think I am not far from the end), but every such reproducible crash may indicate some problem that could appear elsewhere. I'll probably try a rollback and a step-by-step upgrade. Reporting later. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200584 http://bugzilla.opensuse.org/show_bug.cgi?id=1200584#c5 --- Comment #5 from Michael Zapf <Michael.Zapf@mizapf.de> --- OK, did a rollback to 5.17.7 where Alien:Isolation still works. The segfault occurs reproducibly when I upgrade Mesa and its libs from 22.0.3-309.2 to 22.1.1-315.1 I locked Mesa to the current state and tried a zypper dup. This meant to exclude KDE5/Plasma from the update as well (i.e. stay on 5.24). However, with the rest of the system updated, I cannot start anymore; before X starts, the screen is cleared, leaving a lonely underscore cursor in the top left corner, and a dead keyboard. Had to use the Reset button, then rolled back again. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200584 http://bugzilla.opensuse.org/show_bug.cgi?id=1200584#c6 --- Comment #6 from Takashi Iwai <tiwai@suse.com> --- Unfortunately it's almost impossible to debug or fix from our side without any logs or more detailed information about the crash. Of course, we can't fix the game binary itself, either :) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200584 http://bugzilla.opensuse.org/show_bug.cgi?id=1200584#c7 --- Comment #7 from Michael Zapf <Michael.Zapf@mizapf.de> --- Isn't that a Mesa issue anyway, i.e. somewhere upstream? Should I report there? And is there a reason why the Plasma desktop locks up when I lock it at 5.24 and run with the new kernel? If Plasma depended on the 5.17.x kernel, it should not have allowed me to update the kernel. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200584 http://bugzilla.opensuse.org/show_bug.cgi?id=1200584#c8 --- Comment #8 from Takashi Iwai <tiwai@suse.com> --- (In reply to Michael Zapf from comment #7)
Isn't that a Mesa issue anyway, i.e. somewhere upstream? Should I report there?
Well, even if you report it, the same problem: it won't help unless you can give some logs and details...
And is there a reason why the Plasma desktop locks up when I lock it at 5.24 and run with the new kernel? If Plasma depended on the 5.17.x kernel, it should not have allowed me to update the kernel.
That sounds weird, but I can't answer unless I get the crash log or whatever indicating the problem. It depends on the type of "lock up". If it's a GPU freeze or such a kernel driver problem, it explains. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200584 http://bugzilla.opensuse.org/show_bug.cgi?id=1200584#c9 --- Comment #9 from Michael Zapf <Michael.Zapf@mizapf.de> --- That's all I got from the core dump: (gdb) backtrace #0 0x00007f10b89263d9 in ?? () from /usr/lib64/dri/radeonsi_dri.so #1 0x00007f10b8926581 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x00007f10b8683fa2 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x00007f10b86859c1 in ?? () from /usr/lib64/dri/radeonsi_dri.so #4 0x00007f10b81a4d94 in ?? () from /usr/lib64/dri/radeonsi_dri.so #5 0x00007f10b819eea7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #6 0x00007f10d484c777 in start_thread () from /lib64/libc.so.6 #7 0x00007f10d48d6c70 in clone3 () from /lib64/libc.so.6 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200584 http://bugzilla.opensuse.org/show_bug.cgi?id=1200584#c11 --- Comment #11 from Michael Zapf <Michael.Zapf@mizapf.de> --- The problem seems to have disappeared with one of the recent updates. I will give it some more tries, then we may close that ticket. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200584 http://bugzilla.opensuse.org/show_bug.cgi?id=1200584#c12 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(Michael.Zapf@miza | |pf.de) | --- Comment #12 from Takashi Iwai <tiwai@suse.com> --- OK, thanks for the update. Let's close now. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com