glmark2 [desktop] effect=shadow:windows=4 failure on mx3
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glmark2 |
Opinion
|
Undecided
|
Unassigned |
Bug Description
./glmark2-es2-mir --reuse-context --fullscreen
running against mir_demo_
once glmark2 gets to the test:
[desktop] effect=
on the mx3, the driver starts complaining, and the server/client locks up.
The device's driver kicks out some cryptic messages:
E/IMGSRV ( 3519): :0: FlushRenderSurface: ScheduleTA did not work properly on the current surface
E/IMGSRV ( 3519): :0: SGXKickSubmit: failed acquire CCB space!
E/IMGSRV ( 3519): :0: DoKickTA: SGXKickTA() failed with error 9
E/IMGSRV ( 3519): :0: FlushRenderSurface: ScheduleTA did not work properly on the attachment
E/IMGSRV ( 3519): :0: KEGL_SGXDestroy
E/IMGSRV ( 3519): :0: FreePDSFragBuffers: PDS fragment buffer for render surface still in use
E/IMGSRV ( 3519): :0: Failed to flush HW render context (24)
E/IMGSRV ( 3519): :0: KEGLDestroyRend
E/IMGSRV ( 3519): :0: FBOAttachableHa
E/IMGSRV ( 3519): :0: SGXKickSubmit: failed acquire CCB space!
E/IMGSRV ( 3519): :0: DoKickTA: SGXKickTA() failed with error 9
E/IMGSRV ( 3519): :0: FreeListOfVerte
E/IMGSRV ( 3519):
E/IMGSRV ( 3497): :0: DeferFlushOpWorker: Timed out waiting for ops to flush
seems like something is triggering a page fault:
(dmesg)
[11482.742] c0@A15 kworker/0:1 PVR_K: Found MMU context for page fault 0x00000000
[11482.750] c2@A15 migration/2 IRQ154 no longer affine to CPU2
[11482.752] c0@A15 kworker/0:1 PVR_K: GPU memory context is for PID=5371 (glmark2-es2-mir)