Re: radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec

Antti Palosaari
2013-01-02T01:43:09Z

On 12/25/2012 06:50 AM, Shuah Khan wrote:
> On Sun, Dec 23, 2012 at 6:31 AM, Borislav Petkov <bp@alien8.de> wrote:
>> On Sun, Dec 23, 2012 at 01:22:12PM +0100, Borislav Petkov wrote:
>>> Right, let me try that and report back.
>>
>> Yep, looks like reverting the above commit fixes it - the boston.com
>> website loads just fine.
>>
>> Thanks.
>>
>> --
>> Regards/Gruss,
>> Boris.
>
> Saw the same error and after reading this thread, reverted the
>
> Commit 2d6cc7296d4ee128ab0fa3b715f0afde511f49c2.
>
> drm/radeon: use async dma for ttm buffer moves on 6xx-SI
>
> and the problem is gone. In my case, it is a solid hang right after
> system switches to vga. I was able to login on console once or twice.
> But dmesg showed the same message reported in this thread:
>
> [ 35.812085] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
> [ 35.812091] radeon 0000:01:00.0: GPU lockup (waiting for
> 0x0000000000000002 last fence id 0x0000000000000001)
>
>
> My system has:
> 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee
> ATI RV620 [Mobility Radeon HD 3400 Series]

I ended up also that same commit after bisecting from current 3.8 master.

01:05.0 VGA compatible controller: ATI Technologies Inc 760G [Radeon 3000]
It is ASUS M5A78L-M/USB3 with integrated GPU.

I cannot even boot unless graphical boot is removed from Fedora 17 boot
options (rhgb quiet). Random GPU crashes still.

regards
Antti

--