The following warnings occurred:
Warning [2] Undefined property: MyLanguage::$archive_pages - Line: 2 - File: printthread.php(287) : eval()'d code PHP 8.2.26 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/printthread.php(287) : eval()'d code 2 errorHandler->error_callback
/printthread.php 287 eval
/printthread.php 117 printthread_multipage



EmuNewz Network
Downstream Panic! - ULUS10322 - Printable Version

+- EmuNewz Network (https://www.emunewz.net/forum)
+-- Forum: PSP Emulation (https://www.emunewz.net/forum/forumdisplay.php?fid=191)
+--- Forum: JPCSP Official Forum (https://www.emunewz.net/forum/forumdisplay.php?fid=51)
+---- Forum: Commercial Game Discussion (https://www.emunewz.net/forum/forumdisplay.php?fid=54)
+----- Forum: JPCSP - Playable Games (https://www.emunewz.net/forum/forumdisplay.php?fid=65)
+----- Thread: Downstream Panic! - ULUS10322 (/showthread.php?tid=41262)

Pages: 1 2

RE: Downstream Panic! - ULUS10322 - gid15 - 03-25-2015

Code:
17:08:38 DEBUG hle.sceMp3 - thread mp3 play - sceMp3GetInfoToAddStreamData returning writeAddr=0x0892A760, writableBytes=0xFD20, readOffset=0x2F760
17:08:38 DEBUG hle.sceMp3 - thread mp3 play - sceMp3NotifyAddStreamData id=0x0, bytesToAdd=0x1FA40
Hmmm, 0x1FA40 are added to the stream data even though only 0xFD20 were reported as writable. I would like to know how a real PSP reacts on that.

Could someone generate a JpcspTrace with this config file:
Code:
sceMp3GetInfoToAddStreamData 0xA703FE0F 4 xppp
sceMp3NotifyAddStreamData 0x0DB149F4 2 xx

Thank you!

RE: Downstream Panic! - ULUS10322 - sum2012 - 03-26-2015

Only can use @unknownbrackets JPCSPtrace
(03-25-2015, 06:45 PM)gid15 Wrote:
Code:
17:08:38 DEBUG hle.sceMp3 - thread mp3 play - sceMp3GetInfoToAddStreamData returning writeAddr=0x0892A760, writableBytes=0xFD20, readOffset=0x2F760
17:08:38 DEBUG hle.sceMp3 - thread mp3 play - sceMp3NotifyAddStreamData id=0x0, bytesToAdd=0x1FA40
Hmmm, 0x1FA40 are added to the stream data even though only 0xFD20 were reported as writable. I would like to know how a real PSP reacts on that.

Could someone generate a JpcspTrace with this config file:
Code:
sceMp3GetInfoToAddStreamData 0xA703FE0F 4 xppp
sceMp3NotifyAddStreamData 0x0DB149F4 2 xx

Thank you!


RE: Downstream Panic! - ULUS10322 - gid15 - 03-27-2015

Code:
19:30:21.078518 thread mp3 play - <- sceMp3GetInfoToAddStreamData 0x0, 0x09EB8558(0x891AA40), 0x09EB855C(0xFD20), 0x09EB8560(0x0) = 0x0
19:30:21.105342 thread mp3 play - <- sceMp3GetInfoToAddStreamData 0x0, 0x09EB8514(0x892A760), 0x09EB8518(0xFD20), 0x09EB851C(0xFD20) = 0x0
19:30:24.973613 thread mp3 play - <- sceMp3GetInfoToAddStreamData 0x0, 0x09EB8514(0x891AA40), 0x09EB8518(0xFD20), 0x09EB851C(0x1FA40) = 0x0
19:30:28.928594 thread mp3 play - <- sceMp3GetInfoToAddStreamData 0x0, 0x09EB8514(0x892A760), 0x09EB8518(0xFD20), 0x09EB851C(0x2F760) = 0x0
19:30:33.095982 thread mp3 play - <- sceMp3GetInfoToAddStreamData 0x0, 0x09EB8514(0x891AA40), 0x09EB8518(0xFD20), 0x09EB851C(0x3F480) = 0x0
Interesting information: sceMp3GetInfoToAddStreamData never returns more writable bytes than the half-buffer size, even at the first call.
I will update Jpcsp accordingly.

RE: Downstream Panic! - ULUS10322 - sum2012 - 03-28-2015

Compile myself in this commit https://github.com/gid15/jpcsp/commit/3d32d0443816a38a002461d062508835bdd8e0d9

Fixed

RE: Downstream Panic! - ULUS10322 - sum2012 - 11-08-2020

last work
https://github.com/jpcsp/jpcsp/commit/0858ea2ccff8d79b430d3873e842f754a5b4cc75
first bad
https://github.com/jpcsp/jpcsp/commit/7136396995479b2c37761291e945f3f18c7a258a

It mean https://github.com/jpcsp/jpcsp/commit/7136396995479b2c37761291e945f3f18c7a258a has problem

Attach their and b1b7e7e log

RE: Downstream Panic! - ULUS10322 - gid15 - 11-09-2020

(11-08-2020, 02:13 PM)sum2012 Wrote: It mean https://github.com/jpcsp/jpcsp/commit/7136396995479b2c37761291e945f3f18c7a258a has problem
Excellent! Thank you for pointing out the exact commit introducing the issue!
It should now be fixed in 97124eb.

RE: Downstream Panic! - ULUS10322 - sum2012 - 11-10-2020

Yes, 97124eb version fixed