• Login
  • Register
  • Dolphin Forums
  • Home
  • FAQ
  • Download
  • Wiki
  • Code

Dolphin, the GameCube and Wii emulator - Forums › Dolphin Emulator Discussion and Support › Support v
« Previous 1 … 18 19 20 21 22 … 1226 Next »

Save/Load kills Dolphin on Raspberry Pi 5
View New Posts | View Today's Posts

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Threaded Mode
Save/Load kills Dolphin on Raspberry Pi 5
01-07-2024, 07:49 AM
#1
sAdamingo Offline
Junior Member
**
Posts: 5
Threads: 1
Joined: Jan 2024
Hi All,
I'm new to forum but have been an user of Dolphin for some time, mainly on Linux (Ubuntu, Debian etc).

I'm trying to make my Raspberry pi 5 running Dolphin. I've installed latest version from git repo with all required dependencies etc.
Games are not running as smoothly as I would expect, but this is not the case.
When I try to save/load state from file/slot, dolphin is basically crashing leaving this message in logs:
Code:
46:48:332 Core/PowerPC/JitArm64/Jit.cpp:104 E[JIT]: Exception handler - Not on CPU thread
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:31 E[JIT]: R0: 0x0000000000002000    R1: 0x0000000000000000
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:31 E[JIT]: R2: 0x0000000000000008    R3: 0x0000000000000000
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:31 E[JIT]: R4: 0x0000000000000000    R5: 0x000000000000000b
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:31 E[JIT]: R6: 0x0000aaaab81606d8    R7: 0x0000aaaab81606d8
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:31 E[JIT]: R8: 0x0000ffff3efdcd10    R9: 0x0000ffeb4fffcf70
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:31 E[JIT]: R10: 0x000000000000002e    R11: 0x00000000ffffffd0
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:31 E[JIT]: R12: 0x0000ffff3efdcbac    R13: 0x000000000000004d
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:31 E[JIT]: R14: 0x000000000000004a    R15: 0x0000000000003800
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:31 E[JIT]: R16: 0x0000ffff1deda230    R17: 0x0000ffff8cbb0600
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:31 E[JIT]: R18: 0x0000000000004a00    R19: 0x0000ffff3efdcd10
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:31 E[JIT]: R20: 0x0000aaaab8368c90    R21: 0x0000ffff3453acc0
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:31 E[JIT]: R22: 0x0000000000000000    R23: 0x0000000000000010
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:31 E[JIT]: R24: 0x0000aaaab805c148    R25: 0x0000005ab5070ffb
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:31 E[JIT]: R26: 0x0000000000000001    R27: 0x0000000000461680
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:31 E[JIT]: R28: 0x0000ffff83627690    R29: 0x0000ffff3efdd280
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:35 E[JIT]: R30: 0x0000aaaab73523d8    SP: 0x0000ffff3efdccd0
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:37 E[JIT]: Access Address: 0x0000000000000000
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:38 E[JIT]: PC: 0x0000000000000000
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:40 E[JIT]: Memory Around PC
46:48:332 Core/PowerPC/JitArm64/JitArm64_BackPatch.cpp:53 E[JIT]: Full block:
Segmentation fault (core dumped)
I have tried to run on Raspbian OS and Ubuntu, but same problem ocured on both.


I haven't found any info nor have any clue what this could mean...
I'm happy to hear any suggestions on where to search for solution.
Thank you in advance!
Find
Reply
01-07-2024, 07:55 AM
#2
JosJuice Offline
Developer
**********
Developers (Some Administrators and Super Moderators)
Posts: 9,381
Threads: 7
Joined: Oct 2014
That's an interesting crash! I don't think I've seen something quite like that before.

To try and troubleshoot this, could you go to Config > Advanced and switch the CPU emulation engine to Cached Interpreter? This will make emulation much slower, but it should give a crash message that makes more sense.
Find
Reply
01-07-2024, 05:26 PM (This post was last modified: 01-07-2024, 06:01 PM by sAdamingo. Edit Reason: Additional info to describe problem )
#3
sAdamingo Offline
Junior Member
**
Posts: 5
Threads: 1
Joined: Jan 2024
(01-07-2024, 07:55 AM)JosJuice Wrote: That's an interesting crash! I don't think I've seen something quite like that before.

To try and troubleshoot this, could you go to Config > Advanced and switch the CPU emulation engine to Cached Interpreter? This will make emulation much slower, but it should give a crash message that makes more sense.

Hey JosJuice! Thanks for heads up.
I Think it;s worth mentioning that I've compiled it to deb package with this options recommended for slower devices:
-DCMAKE_BUILD_TYPE=Release -DCMAKE_CXX_FLAGS=-march=native -DCMAKE_C_FLAGS=-march=native


After switching to cached interpreter I only get :
Code:
Segmentation fault (core dumped)


Second problem arose meanwhile. On Ubuntu I've needed to run dolphin-emu with QT_QPA_PLATFORM=xcb or I would get the below errors. Now it wont start either run with this env set or without.
It smells like something related to compilation stage.


Code:
setenv:   QT_QPA_PLATFORM=xcb
executing: dolphin-emu
   arg[0]= ‘dolphin-emu’
qt.core.qobject.connect: QObject::connect: signal not found in QTimer
qt.core.qobject.connect: QObject::connect: signal not found in QSocketNotifier
qt.core.qobject.connect: QObject::connect: signal not found in QSocketNotifier
qt.core.qobject.connect: QObject::connect: signal not found in QDBusServiceWatcher
QIBusPlatformInputContext: invalid bus.
Segmentation fault (core dumped)


Thanks for your interest in this thread.
Find
Reply
01-07-2024, 08:00 PM
#4
JosJuice Offline
Developer
**********
Developers (Some Administrators and Super Moderators)
Posts: 9,381
Threads: 7
Joined: Oct 2014
(01-07-2024, 05:26 PM)sAdamingo Wrote: After switching to cached interpreter I only get :
Code:
Segmentation fault (core dumped)


Second problem arose meanwhile.

Could you use gdb to get a backtrace of where it crashes?
Find
Reply
01-07-2024, 09:37 PM
#5
sAdamingo Offline
Junior Member
**
Posts: 5
Threads: 1
Joined: Jan 2024
I was unable to start emulation with gda, got following output:

Code:
24:24:747 Core/HW/Memmap.cpp:158 I[MI]: Memory system initialized. RAM at 0xffff6e000000
[New Thread 0xffff69e7cb00 (LWP 7213)]
24:24:776 Core/PowerPC/JitArm64/JitAsm.cpp:76 W[JIT]: Dispatcher is 0xfffbe266f000
24:24:790 VideoBackends/OGL/OGLConfig.cpp:740 I[Video]: Video Info: Broadcom, V3D 7.1, 3.1 Mesa 23.2.1-1ubuntu3.1
24:24:790 VideoBackends/OGL/OGLConfig.cpp:762 W[Video]: Missing OGL Extensions: DualSourceBlend EarlyZ PinnedMemory SSAA GSInstancing ClipControl DepthClamp
24:24:793 VideoBackends/OGL/OGLConfig.cpp:740 I[Video]: Video Info: Broadcom, V3D 7.1, 3.1 Mesa 23.2.1-1ubuntu3.1
24:24:793 VideoBackends/OGL/OGLConfig.cpp:762 W[Video]: Missing OGL Extensions: DualSourceBlend EarlyZ PinnedMemory SSAA GSInstancing ClipControl DepthClamp
[New Thread 0xffebdc165b00 (LWP 7214)]
[New Thread 0xffebdb955b00 (LWP 7215)]
[New Thread 0xffebda744b00 (LWP 7216)]
24:25:575 VideoCommon/ShaderCache.cpp:322 I[Video]: Loaded 302 cached pipelines from /home/adam/.cache/dolphin-emu/Shaders/OpenGL-specialized-pipeline-GMSE01-4628840.cache
24:26:220 VideoCommon/ShaderCache.cpp:322 I[Video]: Loaded 27 cached pipelines from /home/adam/.cache/dolphin-emu/Shaders/OpenGL-uber-pipeline-4628840.cache
24:26:220 VideoCommon/ShaderCache.cpp:993 I[Video]: Read 476 pipeline UIDs from /home/adam/.cache/dolphin-emu/GMSE01.uidcache
24:26:221 Core/HW/DSPHLE/UCodes/UCodes.cpp:254 I[DSPHLE]: Switching to ROM ucode
24:26:221 Core/HW/DSPHLE/UCodes/ROM.cpp:28 I[DSPHLE]: UCode_Rom - initialized
24:26:221 Core/Boot/Boot.cpp:537 N[BOOT]: Booting from disc: /media/adam/Games/Super Mario Sunshine/Super Mario Sunshine (USA).nkit.iso
[Thread 0xffff69e7cb00 (LWP 7213) exited]
[New Thread 0xffff69e7cb00 (LWP 7217)]
24:26:222 Core/Boot/Boot_BS2Emu.cpp:270 I[BOOT]: Faking GC BS2...
24:26:302 Core/HW/DVD/DVDInterface.cpp:1234 I[DVD]: DTK disabled
24:26:305 Core/HLE/HLE_OS.cpp:95 N[OSREPORT_HLE]: 81200308->81300000|
24:26:305 Core/HLE/HLE_OS.cpp:95 N[OSREPORT_HLE]: 81200324->81300000| This Apploader built Apr 10 2002 02:35:29
24:26:305 Core/Boot/Boot_BS2Emu.cpp:201 I[BOOT]: DVDRead: offset: 00000420   memOffset: 81201480   length: 32
24:26:306 Core/Boot/Boot_BS2Emu.cpp:201 I[BOOT]: DVDRead: offset: 00000440   memOffset: 812015c0   length: 32
24:26:306 Core/Boot/Boot_BS2Emu.cpp:201 I[BOOT]: DVDRead: offset: 00000440   memOffset: 817fcec0   length: 8192
24:26:306 Core/Boot/Boot_BS2Emu.cpp:201 I[BOOT]: DVDRead: offset: 0001e000   memOffset: 812014a0   length: 256
24:26:316 Core/Boot/Boot_BS2Emu.cpp:201 I[BOOT]: DVDRead: offset: 0001e100   memOffset: 80003100   length: 9280
24:26:349 Core/Boot/Boot_BS2Emu.cpp:201 I[BOOT]: DVDRead: offset: 00020540   memOffset: 80005600   length: 3594944
24:26:356 Core/Boot/Boot_BS2Emu.cpp:201 I[BOOT]: DVDRead: offset: 0038e000   memOffset: 80005540   length: 96
24:26:356 Core/Boot/Boot_BS2Emu.cpp:201 I[BOOT]: DVDRead: offset: 0038e060   memOffset: 800055a0   length: 96
24:26:356 Core/Boot/Boot_BS2Emu.cpp:201 I[BOOT]: DVDRead: offset: 0038e0c0   memOffset: 803730c0   length: 960
24:26:356 Core/Boot/Boot_BS2Emu.cpp:201 I[BOOT]: DVDRead: offset: 0038e480   memOffset: 80373480   length: 32
24:26:358 Core/Boot/Boot_BS2Emu.cpp:201 I[BOOT]: DVDRead: offset: 0038e4a0   memOffset: 803734a0   length: 229824
24:26:361 Core/Boot/Boot_BS2Emu.cpp:201 I[BOOT]: DVDRead: offset: 003c6660   memOffset: 803ab660   length: 254112
24:26:361 Core/Boot/Boot_BS2Emu.cpp:201 I[BOOT]: DVDRead: offset: 00404700   memOffset: 8040c1c0   length: 3392
24:26:361 Core/Boot/Boot_BS2Emu.cpp:201 I[BOOT]: DVDRead: offset: 00405440   memOffset: 8040eba0   length: 35936
24:26:362 Core/Boot/Boot_BS2Emu.cpp:201 I[BOOT]: DVDRead: offset: 0040e100   memOffset: 817feec0   length: 4416
[New Thread 0xffebd9f34b00 (LWP 7218)]
24:26:368 Core/PowerPC/Interpreter/Interpreter_SystemRegisters.cpp:358 I[PowerPC]: Flush Instruction Cache! ICE=1
24:26:383 Common/ArmFPURoundMode.cpp:57 W[PowerPC]: Non-IEEE mode was requested, but host CPU is not known to support FEAT_AFP

Thread 38 "CPU thread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xffebd9f34b00 (LWP 7218)]
0x0000fffbe26752dc in ?? ()


I have made couple of checks and this are my findings:

Save/load is crashing only when I use Open GL as renderer. For Vulcan I can only use llvmpipe but it's very slow, unplayable.
I think I would need to create another thread for V3D 7.1.7 vulcan driver not working with dolphin, correct me if I'm wrong.
I have to run dolphin using "env QT_QPA_PLATFORM=xcb dolphin-emu" otherwise none of renderers are able to startup.
Maybe this is why gdb run dolphin is crashing when trying to launch game? Because I;m using command "gdb --args env QT_QPA_PLATFORM=xcb dolphin-emu" ?
Find
Reply
01-07-2024, 10:40 PM
#6
JosJuice Offline
Developer
**********
Developers (Some Administrators and Super Moderators)
Posts: 9,381
Threads: 7
Joined: Oct 2014
(01-07-2024, 09:37 PM)sAdamingo Wrote: I think I would need to create another thread for V3D 7.1.7 vulcan driver not working with dolphin, correct me if I'm wrong.

Either way is fine. It's in some sense related, and you're not hijacking someone else's thread.
Find
Reply
01-08-2024, 07:06 AM
#7
sAdamingo Offline
Junior Member
**
Posts: 5
Threads: 1
Joined: Jan 2024
I'm adding GDA outputs for OpenGL and Vulkan on V3D driver as well as cmake and make outputs.
Find
Reply
« Next Oldest | Next Newest »


  • View a Printable Version
Forum Jump:


Users browsing this thread: 1 Guest(s)


Powered By MyBB | Theme by Fragma