Radeon 9650 (rv350): gpu reset/lockup (dri3, ppc)

Submitted by ernsteiswuerfel @ernsteiswuerfel

Assigned to xf86-video-ati maintainers

Link to original bug (#101038)

Description

Created attachment 131346
dmesg output

Did a git-build yesterday to try out the now enabled dri3 on my ppc hardware. Xorg succesfully starts with dri3 enabled, but after some desktop usage I get gpu resets or total freezes (machine unaccessable via sshd).

[ 295.760807] radeon 0000:f0:10.0: ring 0 stalled for more than 10133msec
[ 295.760818] radeon 0000:f0:10.0: GPU lockup (current fence id 0x00000000000016d5 last fence id 0x00000000000016df on ring 0)
[ 295.912956] Failed to wait GUI idle while programming pipes. Bad things might happen.
[ 295.914021] radeon 0000:f0:10.0: Saved 347 dwords of commands on ring 0.
[ 295.914035] radeon 0000:f0:10.0: (r300_asic_reset:425) RBBM_STATUS=0x80010140
[ 296.414026] radeon 0000:f0:10.0: (r300_asic_reset:444) RBBM_STATUS=0x80010140
[ 296.910023] radeon 0000:f0:10.0: (r300_asic_reset:456) RBBM_STATUS=0x00000140
[ 296.910054] radeon 0000:f0:10.0: GPU reset succeed
[ 296.910058] radeon 0000:f0:10.0: GPU reset succeeded, trying to resume
[ 296.910098] [drm] radeon: 1 quad pipes, 1 Z pipes initialized.
[ 296.910105] radeon 0000:f0:10.0: WB disabled
[ 296.910111] radeon 0000:f0:10.0: fence driver on ring 0 use gpu addr 0x0000000000000000 and cpu addr 0xd0000000018e9000
[ 296.910203] [drm] radeon: ring at 0x0000000000001000
[ 296.910274] [drm] ring test succeeded in 0 usecs
[ 296.963794] [drm] ib test succeeded in 0 usecs

Very similar to #94877 but as the card is different (r300 instead of r100), dri3 instead of dri2, current kernel & mesa-git I decided to file a new bug.

Attachment 131346, "dmesg output":
log_dmesg02.txt