| Summary: | AMDGPU Crash from previous AMDGPU Crash running Marvel Rivals on Steam. | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | adros |
| Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | kdedev |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 6.3.2 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
adros
2025-03-09 07:33:37 UTC
Created attachment 179243 [details]
New crash information added by DrKonqi
DrKonqi auto-attaching complete backtrace.
Searchable backtrace Thread 1 (Thread 0x7f0fc95ff6c0 (LWP 31135)): [KCrash Handler] #5 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #6 0x00007f0ff5c80183 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:78 #7 0x00007f0ff5c26f9e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x00007f0ff5c0e942 in __GI_abort () at abort.c:79 #9 0x00007f0fd1bbbad0 in amdgpu_ctx_set_sw_reset_status(radeon_winsys_ctx*, pipe_reset_status, char const*, ...) () at /usr/lib64/dri-freeworld/libgallium-25.0.0.so #10 0x00007f0fd1bbfa44 in void amdgpu_cs_submit_ib<(queue_type)0>(void*, void*, int) () at /usr/lib64/dri-freeworld/libgallium-25.0.0.so #11 0x00007f0fd16b1ca1 in util_queue_thread_func () at /usr/lib64/dri-freeworld/libgallium-25.0.0.so #12 0x00007f0fd16e719c in impl_thrd_routine () at /usr/lib64/dri-freeworld/libgallium-25.0.0.so #13 0x00007f0ff5c7e168 in start_thread (arg=<optimized out>) at pthread_create.c:448 #14 0x00007f0ff5d0214c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 This is a duplicate of 493679. The fix requires Qt changes which are in progress with https://codereview.qt-project.org/c/qt/qtbase/+/606100 and https://codereview.qt-project.org/c/qt/qtwayland/+/606101 *** This bug has been marked as a duplicate of bug 493679 *** > This is a duplicate of 493679. The fix requires Qt changes which are in
> progress with https://codereview.qt-project.org/c/qt/qtbase/+/606100 and
> https://codereview.qt-project.org/c/qt/qtwayland/+/606101
Gotcha!
But, does this fix "fix" the underlying crash event in Marvel Rivals?
Correct me if I'm wrong (I'm not a developer), but it looks like this fix helps with plasma-shell recovery during and after the crash. However, the main crash in Marvel Rivals, that led with all of this, will still be present.
Should I file a separate bug report (with back traces and all) for the main crash event in Marvel Rivals?
Can KDE even deal with such a bug report?
If not, what channels and forums do I need to contact to report this crash event?
(In reply to adros from comment #4) > But, does this fix "fix" the underlying crash event in Marvel Rivals? QT bug 606100 makes information available to applications that their developers need to do something with. QT 606101 provides support for GPU resets, which should fix crashes caused by that. > However, the > main crash in Marvel Rivals, that led with all of this, will still be > present. > > Should I file a separate bug report (with back traces and all) for the main > crash event in Marvel Rivals? If you have a crash from Marvel Rivals and the backtrace is different than the one in this report, we can take a look. Please open a new bug report for it. If it needs to be reported somewhere else, we'll let you know. We're happy to help determine what the right course of action is. |