https://bugs.freedesktop.org/show_bug.cgi?id=76558 Priority: high Bug ID: 76558 Assignee: dri-devel@lists.freedesktop.org Summary: GPU lockup: radeon: wait for empty RBBM fifo failed ! when playing sauerbraten Severity: critical Classification: Unclassified OS: Linux (All) Reporter: fabio.ped@libero.it Hardware: x86 (IA32) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 96295 --> https://bugs.freedesktop.org/attachment.cgi?id=96295&action=edit dmesg after the lockup, got switching to a VT 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: sauerbraten -lwake6 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. -- You are receiving this mail because: You are the assignee for the bug.