821480 - Graphic buffer errors on boot screen

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: General, defect, P1)

Description

[Diego Wilson [:diego]]

Attachment: Logcat log

During the boot screen I can see the error messages below repeated several times:

E/libgenlock(  125): perform_lock_unlock_operation: GENLOCK_IOC_DREADLOCK failed (lockType0x1, err=Connection timed out fd=15)
W/Adreno200-EGLSUB(  125): <GetBackBuffer:2125>: genlock_lock_buffer GENLOCK_WRITE_LOCK failed
W/Adreno200-EGL(  125): <qeglDrvAPI_eglSwapBuffers:3476>: EGL_BAD_ALLOC
E/libgenlock(  125): perform_lock_unlock_operation: GENLOCK_IOC_DREADLOCK failed (lockType0x1, err=Connection timed out fd=15)

See full log attached

Comment 1

[Michael Vines [:m1] [:evilmachines]]

(seems to be related to the new bootanimation.zip support that was added to Gecko recently)

Comment 2

[Lawrence Mandel [:lmandel] (use needinfo)]

If the errors are not visible on screen it doesn't seem that this issue is critical enough to block. Can you comment on why this issue is severe enough to block?

Comment 3

[Michael Vines [:m1] [:evilmachines]]

Genlock errors like this are typically very serious and imply something very broken about how EGL/GLES is being used.  This is a stability issue that needs to resolved to successfully commercialize the platform.

Comment 4

[Dietrich Ayala (:dietrich)]

Blocking per comment #3. If investigation shows it's not actually blocking we can flip the flag back.

Comment 5

[Michael Wu [:mwu]]

I don't remember seeing this on unagi.

m1, does the boot animation work on your device?

Comment 6

[Michael Vines [:m1] [:evilmachines]]

Yeah it works.  I've seen this a couple times on Otoro.  It's not 100% though

Comment 7

[Michael Wu [:mwu]]

Ok that helps, thanks for the info. I'll see if I can fix this.

Comment 8

[Dietrich Ayala (:dietrich)]

Any update on a fix for this, mwu?

Comment 9

[Michael Wu [:mwu]]

The boot animation code doesn't seem to work on otoro. I'll fix it and see if I can reproduce this bug.

Comment 10

[Michael Wu [:mwu]]

I posted a patch to fix the boot animation on otoro to bug 824090.

However, I still can't reproduce the genlock errors on otoro, unagi, or m4. If I reboot the phone 6-7 times, should I expect to see it?

I'm testing against trunk but the boot animation code on trunk and branch is identical AFAIK.

m1, do you have any other ideas? I don't think we can block if we can't reproduce..

Comment 11

[Michael Vines [:m1] [:evilmachines]]

I can no longer reproduce at the tip.  Maybe the fix for bug 824090 helped, or maybe a mystery fix.  Will reopen this bug if it comes back I guess.

Comment 12

[Aniruddha Adhikary [:tuxboy]]

I am getting this, from a new port of Firefox OS on my Qualcomm 8225Q based phone. (K-touch Kiss U86). I was trying to port Firefox OS on my device, but the screen remains blank and the logcat is:

....
W/Adreno200-EGL(  450): <qeglDrvAPI_eglSwapBuffers:3508>: EGL_BAD_ALLOC
E/libgenlock(  450): perform_lock_unlock_operation: handle is invalid
W/Adreno200-EGLSUB(  450): <GetBackBuffer:2180>: genlock_lock_buffer GENLOCK_WRITE_LOCK failed
W/Adreno200-EGL(  450): <qeglDrvAPI_eglSwapBuffers:3508>: EGL_BAD_ALLOC
E/libgenlock(  450): perform_lock_unlock_operation: handle is invalid
W/Adreno200-EGLSUB(  450): <GetBackBuffer:2180>: genlock_lock_buffer GENLOCK_WRITE_LOCK failed
W/Adreno200-EGL(  450): <qeglDrvAPI_eglSwapBuffers:3508>: EGL_BAD_ALLOC
E/libgenlock(  450): perform_lock_unlock_operation: handle is invalid
W/Adreno200-EGLSUB(  450): <GetBackBuffer:2180>: genlock_lock_buffer GENLOCK_WRITE_LOCK failed
W/Adreno200-EGL(  450): <qeglDrvAPI_eglSwapBuffers:3508>: EGL_BAD_ALLOC
E/libgenlock(  450): perform_lock_unlock_operation: handle is invalid
W/Adreno200-EGLSUB(  450): <GetBackBuffer:2180>: genlock_lock_buffer GENLOCK_WRITE_LOCK failed
....

Comment 13

[Sotaro Ikeda [:sotaro]]

(In reply to Aniruddha Adhikary from comment #12)
> I am getting this, from a new port of Firefox OS on my Qualcomm 8225Q based
> phone. (K-touch Kiss U86). I was trying to port Firefox OS on my device, but
> the screen remains blank and the logcat is:

It might be better to disable gralloc during porting. You can disable gralloc by changing the following code if you are using recent master gecko.
 http://mxr.mozilla.org/mozilla-central/source/gfx/layers/client/CompositableClient.cpp#204

If you are using older gecko, you can disable gralloc by changin the following code.
http://mxr.mozilla.org/mozilla-central/source/gfx/layers/ipc/ShadowLayerUtilsGralloc.cpp#436

Comment 14

[Sotaro Ikeda [:sotaro]]

FYI. The following link has some information about gralloc.
https://wiki.mozilla.org/Platform/GFX/Gralloc