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

Alex Deucher
2013-01-10T16:21:24Z

On Thu, Jan 10, 2013 at 4:38 AM, Borislav Petkov <bp@alien8.de> wrote:
> [ deliberately breaking the thread because it got too long]
>
> On Sat, Dec 22, 2012 at 09:35:47PM +0100, Borislav Petkov wrote:
>> Hi Alex,
>>
>> got the sickest bug on 3.8-rc1, see below. The GPU locks up somewhere
>> down radeon_fence_wait_seq, judging by the error messages.
>>
>> And this doesn't happen with 3.7, of course.
>>
>> Let me know if you need any more info, thanks.
>>
>> [16273.668350] radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec
>> [16273.668361] radeon 0000:02:00.0: GPU lockup (waiting for 0x000000000000002b last fence id 0x000000000000002a)
>> [16273.882550] plugin-containe[11435]: segfault at 7f1f0a66cc08 ip 00007f1f13289bdb sp 00007f1f0a2fe9e0 error 4 in libflashplayer.so[7f1f130c5000+117b000]
>> [16274.502807] ------------[ cut here ]------------
>> [16274.502845] WARNING: at lib/list_debug.c:53 __list_del_entry+0x63/0xd0()
>
> Ok, this got fixed by 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb which is
> upstream now. And I'm testing -rc2+ which contains this patch already
> + tip/master + another fix from Alan which reworks fb console locking
> (should be unrelated) and the machine gets unresponsive for a couple of
> seconds and then it is fine again.
>
> See dmesg below, the GPU gets the same lockup CP stall without the list
> corruption so it recovers fine. But I didn't have those stalls before so
> it has to be something which came up with 3.8 merge window.

I'm assuming you didn't also update your userspace gfx stack? Does
disabling the new DMA ring for ttm bo moves avoid the issue?

Alex