Re: radeon 0000:1d:00.0: GPU lockup (current fence id 0x00000000010da43f last fence id 0x00000000010da52d on ring 0)

2018-06-07 Thread Borislav Petkov
On Wed, Jun 06, 2018 at 10:26:15AM +0200, Christian König wrote: > Well what did you do to trigger the lockup? Looks like an application send > something to the hardware to crash the GFX block. So what I observed was (in that order): machine was building a kernel so was busy, X didn't respond for

Re: radeon 0000:1d:00.0: GPU lockup (current fence id 0x00000000010da43f last fence id 0x00000000010da52d on ring 0)

2018-06-06 Thread Christian König
Am 05.06.2018 um 16:44 schrieb Borislav Petkov: Hi guys, X just froze here ontop of 4.17-rc7+ tip/master (kernel is from last week) with the splat at the end. Box is a x470 chipset with Ryzen 2700X. GPU gets detected as [7.440971] [drm] radeon kernel modesetting enabled. [7.441220]

Re: radeon 0000:1d:00.0: GPU lockup (current fence id 0x00000000010da43f last fence id 0x00000000010da52d on ring 0)

2018-06-06 Thread Huang Rui
On Tue, Jun 05, 2018 at 04:44:04PM +0200, Borislav Petkov wrote: > Hi guys, > > X just froze here ontop of 4.17-rc7+ tip/master (kernel is from last > week) with the splat at the end. > > Box is a x470 chipset with Ryzen 2700X. > > GPU gets detected as > > [7.440971] [drm] radeon kernel