Hi. Recently we meet with Adreno-GSL error with one of our application on Nexus 6 (Android Version 5.0).
This is the error message:
W/Adreno-GSL(10510): <gsl_ldd_control:427>: ioctl fd 27 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 71 Protocol error
W/Adreno-GSL(10510): <log_gpu_snapshot:337>: panel.gpuSnapshotPath is not set.not generating user snapshot
Then some time later, a new error will pop up:
W/Adreno-GSL(10510): <gsl_ldd_control:427>: ioctl fd 27 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 35 Resource deadlock would occur
W/Adreno-GSL(10510): <log_gpu_snapshot:337>: panel.gpuSnapshotPath is not set.not generating user snapshot
There will be plenty of such error, and then the app crash.
Could you please gave us some information about such error? If you need, we can provide you an apk about this problem. (Can I post a link to the apk here?)
I have shared the apk here:
Sorry. This link is invalid. Please try this one:
https://app.box.com/s/t3im9w0dl309ltwja56xbojpo090gi3d
Please try the "2D: Kiev". You will see the adreno error in logcat.
Pierre - Can you provide the exact Nexus 6 build information (version/date/#)? Are you able to update the OS to a later version (e.g. 5.1)?
I was able to reproduce the app crash on a Snapdragon 805 (Android Version 5.1.1) and also a Nexus 6 (Android Version 5.1).
However I was unable to reproduce your Adreno warning from your logcat: "W/Adreno-GSL(10510)".
The app crash appears to be an application error so here are the logs I captured from both devices:
Snapdragon 805:
Snapdragon 805 5.1.1 crash log:
Nexus 6:
Nexus 6 5.1 crash log:
Here is the image that appears on the devices when the crash happens:
Snapdragon device:
http://imgur.com/BB75lHi
Nexus 6 device:
http://imgur.com/XDnvoN9
Perhaps a tool such as "addr2line" can help you find the cause of the crash, using the above information.
This is the link to the APK
https://drive.google.com/file/d/0BxT5Kv3pTStLVWJHMG9BcHh3ZFU/view
In order to reproduce you need to select delightex.test.ManAnimationTest
I have also same problem on Xperia Z5. it seems that this problem happens when gl_FragDepth is written.
Is there anone who are investigating this issue in Qualcomm?
logcat
W/Adreno-GSL(14689): : ioctl fd 44 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 71 Protocol error
W/Adreno-GSL(14689): : panel.gpuSnapshotPath is not set.not generating user snapshot
I/yabause (14689): prg = 3
I/yabause (14689): prg = 3
W/Adreno-GSL(14689): : ioctl fd 44 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 71 Protocol error
W/Adreno-GSL(14689): : panel.gpuSnapshotPath is not set.not generating user snapshot
I/yabause (14689): prg = 3
I/yabause (14689): prg = 3
W/Adreno-GSL(14689): : ioctl fd 44 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 71 Protocol error
W/Adreno-GSL(14689): : panel.gpuSnapshotPath is not set.not generating user snapshot
I/yabause (14689): prg = 3
I/yabause (14689): prg = 3
W/Adreno-GSL(14689): : ioctl fd 44 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 35 Resource deadlock would occur
W/Adreno-GSL(14689): : panel.gpuSnapshotPath is not set.not generating user snapshot
W/Adreno-GSL(14689): : ioctl fd 44 code 0xc0140933 (IOCTL_KGSL_TIMESTAMP_EVENT) failed: errno 22 Invalid argument
W/Adreno-GSL(14689): : (2d, 17, 1814) fail 22 Invalid argument
W/Adreno-GSL(14689): : ioctl fd 44 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 35 Resource deadlock would occur
W/Adreno-GSL(14689): : panel.gpuSnapshotPath is not set.not generating user snapshot
W/Adreno-GSL(14689): : ioctl fd 44 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 35 Resource deadlock would occur
W/Adreno-GSL(14689): : panel.gpuSnapshotPath is not set.not generating user snapshot
I/WindowState( 1469): WIN DEATH: Window{1fd7e2ae u0 SurfaceView}
Shader source
" gl_FragDepth = (depth+1.0)/2.0;\n"
Hello,
We have problem that seems to be related to the Adreno error on Nexus 6 / Android 5.0.1 with the Deezer app. Some time the phone reboot, sometime we can see this in the logcat:
Then:
According to the Qualcomm guidelines: https://developer.qualcomm.com/community-guidelines
"Forums are not the correct place to report software bugs or post suggestions on products, tools and services. To suggest changes, report software bugs, or submit feedback about Qualcomm products, tools and services, please utilize the Contact Us areas of the QDN site."
We used the "Contact Us" to report this problem but we got this response by email: