Created attachment 96295 [details]
dmesg after the lockup with Ubuntu kernel 3.11.0-18.32 (based on 188.8.131.52)
I am using kernel 3.11.0-18.32 (default Ubuntu 13.10 kernel) with mesa from git on a RV530. The system is usually very stable, however when running sauerbreaten with wake6 map (sauerbraten-wake6 package on Debian/Ubuntu) this way:
after some minutes I get the following lockup:
[ 8425.176130] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[ 8425.176144] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000002845 last fence id 0x0000000000002844)
[ 8425.349835] radeon: wait for empty RBBM fifo failed ! Bad things might happen.
[ 8425.523469] Failed to wait GUI idle while programming pipes. Bad things might happen.
[ 8425.524520] radeon 0000:01:00.0: Saved 59 dwords of commands on ring 0.
[ 8425.530923] radeon 0000:01:00.0: (rs600_asic_reset:401) RBBM_STATUS=0x9401C100
[ 8426.029068] radeon 0000:01:00.0: (rs600_asic_reset:421) RBBM_STATUS=0x9401C100
[ 8426.526183] radeon 0000:01:00.0: (rs600_asic_reset:429) RBBM_STATUS=0x9400C100
[ 8427.023299] radeon 0000:01:00.0: (rs600_asic_reset:437) RBBM_STATUS=0x9400C100
[ 8427.023370] radeon 0000:01:00.0: failed to reset GPU
[ 8427.024701] radeon 0000:01:00.0: GPU reset failed
[ 8427.028124] radeon 0000:01:00.0: couldn't schedule ib
[ 8427.028133] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
[ 8427.057855] radeon 0000:01:00.0: couldn't schedule ib
Full dmesg is attached. After the lockup I can switch to/from console, but I have to reboot because the screen is corrupted/flashing.
After upgrading to Ubuntu 14.04 I cannot reproduce this issue. Note that I was using current git of mesa/ati/libdrm with both 13.10 and 14.04. What changed was the kernel and sauerbraten get updated. I also tried with the 13.10 kernel, but the issue is no more reproducible.
It could be that the updated sauerbraten has a different path that doesn't trigger this issue. Closing since I cannot reproduce it anymore anyway.
This is still happening with updated sauerbraten. However I cannot find an easy way to reproduce it.
I suggest using the old sauerbraten to reproduce it.
Created attachment 99497 [details]
dmesg after the lockup with Ubuntu kernel 3.13.0-24.47 (based on 3.13.9)
Here is an updated dmesg with kernel 3.13.9 (ubuntu 3.13.0-24.47), only relevant difference is "on ring 0" is added to this line:
[11757.716140] radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000003dd41 last fence id 0x000000000003dd40 on ring 0)
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/480.