Emulator Issues #8355
openGameCube Service Disc-Hardware Status / CPU Test
0%
Description
Game Name?
US GameCube Service Disc
Game ID?
301E01
What's the problem? Describe what went wrong in few words.
Hangs on Test 6: l2c.dol
What did you expect to happen instead?
Test to pass.
What steps will reproduce the problem?
- Select Individual Tests
- Select Hardware Tests
- Select CPU Test
- Wait for Test 006:l2c.dol
- Test seems to run forever (or at least longer than the ~5 minutes I waited for it).
Dolphin 3.5 and 3.5-367 are old versions of Dolphin that have
known issues and bugs, so don't report issues about them and test the
latest Dolphin version first.
Which versions of Dolphin did you test on?
4.0-5823
Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?
Unknown
What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
Windows 7, Intel Core i7-960, nVidia GeForce 580
Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
https://wiki.dolphin-emu.org/index.php?title=File:Service_Disc-CPU_Test_6.jpg
Updated by JMC4789 almost 10 years ago
Have you tried it on JITIL and Interpreter?
Updated by kolano almost 10 years ago
Same issue with JITIL, haven't been patient enough to try with Interpreter.
Updated by kolano almost 10 years ago
Appears to have the same issues /w Interpreter. It's a bit harder to tell if things have hung when in Interpreter mode, but the inner counter hasn't incremented a new second in over 10min of emulation, and we proceeded through the prior 5 tests in about a minute.
Updated by kolano almost 10 years ago
20min in still no progress. Presumed hung with Interpreter too.
Updated by skidau almost 10 years ago
l2c = Level 2 cache.
Does this work on older versions of Dolphin? (4.0, 3.5, 3.0?)
Updated by Stevoisiak over 9 years ago
According to Lioncash, this happens because we don't actually emulate caches in Dolphin.
I guess in this case, the proper behavior would be to have the test fail, rather than getting stuck in an endless loop.