Skip to content

[Regression] Unable to boot games on Linux #14409

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
cipherxof opened this issue Aug 1, 2023 · 27 comments
Closed

[Regression] Unable to boot games on Linux #14409

cipherxof opened this issue Aug 1, 2023 · 27 comments

Comments

@cipherxof
Copy link
Contributor

Quick summary

After the update to qt6 I am no longer able to boot any games on Arch Linux.

#12471

Details

image

Build with regression

v0.0.29-15420-ef12da77

Attach two log files

RPCS3.log

Attach capture files for visual issues

No response

System configuration

RPCS3 v0.0.29-15420-ef12da77 Alpha | master
12th Gen Intel(R) Core(TM) i7-12700KF | 16 Threads | 31.16 GiB RAM | TSC: 3.610GHz | AVX-512+ | FMA3
Operating system: POSIX, Name: Linux, Release: 6.2.6-273-tkg-cfs, Version: #1 SMP PREEMPT_DYNAMIC TKG Wed, 15 Mar 2023 23:53:12 +0000
Qt version: Compiled against Qt 6.5.0 | Run-time uses Qt 6.5.0

Other details

No response

@AniLeo
Copy link
Member

AniLeo commented Aug 2, 2023

Cannot reproduce

image

Linux 6.4.7
Manjaro 23.0.0
X11
GNOME 44.3
Mutter

@MastaG
Copy link

MastaG commented Aug 2, 2023

Are you running on Wayland and using a dedicated GPU?
(E.g. not the primary one)

@justunscored
Copy link

justunscored commented Aug 2, 2023

CPU AMD Ryzen 9 7900X GPU: Nvidia RTX 3070
OS: Arch Linux Kernel: 6.4.7-arch1-3
X11
KDE plasma 5.27.7

I am experiencing similar issues on Arch Linux as well, build 15417-9b3a878c is fine but builds 15419-6cd5a7ea and after cause Call Of Duty: Ghosts to crash on launch, firmware cache causes rpcs3 to crash, also when exiting any game rpcs3 crashes.
My other games seem to be fine.

@MastaG
Copy link

MastaG commented Aug 3, 2023

Try running rpcs3 with: QT_QPA_PLATFORM=xcb

@Yahfz
Copy link
Contributor

Yahfz commented Aug 4, 2023

I can reproduce here too. You don't even have to boot any game, it crashes when creating the firmware cache.

@BigTreezZ
Copy link

I am getting this exact error on Arch Linux as well, except it's when I close any game. I can boot and run games with no issue, but this error will always pop up when closing a game, crashing RPCS3 entirely.

  • SYS: RPCS3 v0.0.29-15443-dea24c90 Alpha | master
  • SYS: Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz | 12 Threads | 15.49 GiB RAM | TSC: 3.192GHz | AVX+ | FMA3 | TSX
  • SYS: Operating system: POSIX, Name: Linux, Release: 6.4.8-lqx1-1-lqx, Version: Wip #1 ZEN SMP PREEMPT Thu, 03 Aug 2023 20:20:21 +0000
  • SYS: Current Time: 2023-08-05T13:52:14
  • RSX: Found Vulkan-compatible GPU: 'NVIDIA GeForce GTX 1650' running on driver 535.86.5.0
  • SYS: Firmware version: 4.89

I uploaded a log below (it's a manually compressed RPCS3.log file. The .log.gz file wasn't working, and the .log file was 32mb, surpassing the 25mb upload limit.)

RPCS3.zip

@Techbane
Copy link

Same issue on Mint 21.1. It triggers either on attempting to run a game or install a firmware, seemingly triggered by the "compiling PPU modules" process. I can't get it to produce a log, but it keeps spamming this over and over in the terminal until crashing with a segfault:

RPCS3: Pad Thread: SIG: Thread terminated due to fatal error: futex_waitv is not supported (Linux kernel is too old)
(in file /tmp/cirrus-ci-build/rpcs3/util/atomic.cpp:883, in function wait) (errno=38=Function not implemented)
RPCS3: RSX [0x0000000]: SIG: Thread terminated due to fatal error: futex_waitv is not supported (Linux kernel is too old)
(in file /tmp/cirrus-ci-build/rpcs3/util/atomic.cpp:883, in function wait) (errno=38=Function not implemented)

It actually had been a while since I updated my kernel so I went and did that, to no avail. As mentioned by @justunscored reverting to 15417-9b3a878c fixes it.

@AniLeo
Copy link
Member

AniLeo commented Aug 10, 2023

Not the same issue. What you're having is #14422. We will bump our minimal kernel requirement if no other solution is found.

@AniLeo
Copy link
Member

AniLeo commented Aug 11, 2023

Needs retest on latest build for the issue specifically reported in this issue, not the outdated kernel one.

@justunscored
Copy link

justunscored commented Aug 11, 2023

The latest build seems to have fixed it for me, my game is able to boot now and can now create firmware cache.

@AniLeo AniLeo closed this as completed Aug 11, 2023
@BigTreezZ
Copy link

The issue I had before (error message after closing a game) still persists for me as well.

Arch Linux 6.4.10-lqx1-1-lqx
KDE Plasma 5.27.7
X11

@AniLeo
Copy link
Member

AniLeo commented Aug 12, 2023

The problem persists for me, I can't install the firmware nor start MGS4. Issues that don't exist in the pre-update to Qt6 (v0.0.28-15417-9b3a878c_linux64).
I have the kernel and Ubuntu updated.

Need log file to update the issue so it can be reopened

@justunscored
Copy link

justunscored commented Aug 12, 2023

Okay so I realized why mine was working...

I only really use X11 but In a attempt to see if it was just X11 not launching games when both were broken, i had switched to wayland but it didn't fix the issue and both were crashing upon launching the same game and creating firmware cache and I forgot to switch back to X11 after trying to see if wayland would fix the issue

and that's why it was fixed for me at that time. Issue still persists on X11 but not wayland.
Sorry for double posting i accidentally deleted my first comment

@AniLeo AniLeo reopened this Aug 12, 2023
@therealbungus
Copy link

This is also happening to me, preventing the system menu from booting. Error happens at the very end of compiling modules, or when closing out of a game. Same exact error popup in the original issue post.

Arch 6.4.10-zen2-1-zen
KDE Plasma 5.27.7, X11
Nvidia GTX 1080Ti
Intel i5-10600k

@Parotaku

This comment was marked as off-topic.

@ghost
Copy link

ghost commented Aug 16, 2023

Should be fixed now.

@BigTreezZ
Copy link

If the latest version (RPCS3 v0.0.29-15487-384c807d Alpha) was supposed to fix it, it didn't, at least for me. I still get the message saying "Segfault executing location 00007f604c022fd0 at 00007f604c022fd0. Thread: Main Thread." as soon as I close any game I'm playing.

In addition, Red Dead Redemption GOTY (BLES01294) has completely stopped booting for me, and instantly gives me the error "Segfault executing location 00007f539c1b1fd0 at 00007f539c1b1fd0. Thread: Main Thread." (slightly different error). It is the only game where I encounter the behavior others have experienced, whereas I normally only get an error message when I close a game I'm currently running. Keep in mind this could have already been happening since I first commented on this issue, but only now did I try booting that game specifically.

I attached a log for the RDR GOTY crash below.

RPCS3.log

@AniLeo
Copy link
Member

AniLeo commented Aug 16, 2023

This is not related to the futex_waitv regression (that has been fixed) as I already said above, do not mix issues as it confuses developers

@therealbungus
Copy link

Issue is still persisting after latest update. After updating, I cleared my spu and ppu caches, then tried creating them again, crashes with the same segfault error as in OP. Only game I have in RPCS3 is Skate 3 (BLUS30464). Log attached below.

RPCS3.log

@cipherxof
Copy link
Contributor Author

I'm no longer having trouble booting as of the latest master build 🤷‍♂️

@BigTreezZ
Copy link

Fully working for me now as well (RPCS3 v0.0.29-15497-454cb697 Alpha). Red Dead Redemption boots up again, and no more error messages after closing any game. Thank you!

@justunscored
Copy link

The issue is fixed for real this time. This time I am actually on X11 rather then Wayland.

@therealbungus
Copy link

Issue already closed, but I can confirm that this issue has been fixed. Thank you so much to everyone who has worked on this project ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

11 participants