[Openchrome-users] *ERROR* via_cmdbuf_wait timed out

[Benno Schulenberg]

Hi,

Only today I looked at the kernel log of a crash that happend here last week:

Feb 12 14:30:28 ordesa kernel: [drm:via_cmdbuf_wait] *ERROR* via_cmdbuf_wait timed out hw 1787e0 cur_addr f8708 next_addr 178908
Feb 12 14:30:29 ordesa kernel: [drm:via_cmdbuf_wait] *ERROR* via_cmdbuf_wait timed out hw 1787e0 cur_addr f8800 next_addr 178902
Feb 12 14:30:29 ordesa kernel: [drm:via_cmdbuf_wait] *ERROR* via_cmdbuf_wait timed out hw 1787e0 cur_addr f8800 next_addr 178930
Feb 12 14:30:29 ordesa kernel: [drm:via_cmdbuf_wait] *ERROR* via_cmdbuf_wait timed out hw 1787e0 cur_addr f8800 next_addr 178960
Feb 12 14:30:29 ordesa kernel: [drm:via_cmdbuf_wait] *ERROR* via_cmdbuf_wait timed out hw 1787e0 cur_addr f8800 next_addr 178990
[...]
Feb 12 14:31:32 ordesa kernel: [drm:via_cmdbuf_wait] *ERROR* via_cmdbuf_wait timed out hw 1787e0 cur_addr f8800 next_addr 17c7a0
Feb 12 14:31:32 ordesa kernel: [drm:via_cmdbuf_wait] *ERROR* via_cmdbuf_wait timed out hw 1787e0 cur_addr f8800 next_addr 17c7e0
Feb 12 14:31:33 ordesa kernel: [drm:via_cmdbuf_wait] *ERROR* via_cmdbuf_wait timed out hw 1787e0 cur_addr f8800 next_addr 17c7f0
Feb 12 14:31:33 ordesa kernel: [drm:via_cmdbuf_wait] *ERROR* via_cmdbuf_wait timed out hw 1787e0 cur_addr f8800 next_addr 17c800

This happened upon running morph3d, in Mesa/progs/demos/, after haphazardly 
running a whole series of those demos.  When running morph3d the box started 
freezing: it still responded to Alt+Tab a few times, but misdrew the contents 
of the windows, and then froze entirely.

I haven't tried running morph3d again: after the crash the box took an awful 
long time to come back up, replaying journal entries.  And if it weren't so 
unlikely, I would swear that the hardware is somehow damaged: desktop switches 
are noticeably slower now.

Benno