[Mesa-dev] r600g: status of my work on the shader optimization

[Stefan Seifert]

On Friday 15 February 2013 02:21:56 Vadim Girlin wrote:

> I pushed the fix for one problem that I noticed with FlightGear to that
> branch, please test if it helps with your lockups as well.

I have a commit d6327a397ed54b3b2e40d521a762a380c25cba48 but the lockups still 
occur:

[  125.082988] radeon 0000:01:00.0: GPU lockup CP stall for more than 
10000msec
[  125.082993] radeon 0000:01:00.0: GPU lockup (waiting for 0x00000000000021e8 
last fence id 0x00000000000021e1)
[  125.084038] radeon 0000:01:00.0: Saved 215 dwords of commands on ring 0.
[  125.084042] radeon 0000:01:00.0: GPU softreset: 0x00000003
[  125.099151] radeon 0000:01:00.0:   GRBM_STATUS               = 0xE7730828
[  125.099153] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0xFC000001
[  125.099154] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000007
[  125.099155] radeon 0000:01:00.0:   SRBM_STATUS               = 0x200000C0
[  125.099156] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
[  125.099157] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00010800
[  125.099158] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00028006
[  125.099159] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x80038647
[  125.099160] radeon 0000:01:00.0:   GRBM_SOFT_RESET=0x00007F6B
[  125.099211] radeon 0000:01:00.0:   GRBM_STATUS               = 0x00003828
[  125.099212] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0x00000007
[  125.099213] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000007
[  125.099214] radeon 0000:01:00.0:   SRBM_STATUS               = 0x200000C0
[  125.099215] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
[  125.099216] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
[  125.099217] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000000
[  125.099219] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x00000000
[  125.116712] radeon 0000:01:00.0: GPU reset succeeded, trying to resume

> If that fix doesn't help, you might want to test with the debug build of
> mesa (configure with "--enable-debug" option) if you haven't tried it
> yet - many issues then may be detected by the asserts in the code.

Unfortunately no change. I do not see any messages or abort()s. Just the 
lockups.

Regards,
Stefan