Bug 107876

Summary: GPU lockup with Radeon HD 7850 in 18.1.6 driver
Product: Mesa Reporter: Lukasz Krotowski <lukasz.krotowski>
Component: Drivers/Gallium/radeonsiAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED DUPLICATE QA Contact: Default DRI bug account <dri-devel>
Severity: normal    
Priority: medium    
Version: 18.1   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Relevant part of kernel log
lspci
xrandr
Xorg.0.log

Description Lukasz Krotowski 2018-09-09 20:47:08 UTC
Created attachment 141494 [details]
Relevant part of kernel log

When using dual monitors (I'm not sure is correlated but first error shows on turning second monitor with xrandr) GPU locks up with:

[  451.840071] radeon 0000:01:00.0: ring 0 stalled for more than 32210msec
[  451.840077] radeon 0000:01:00.0: ring 3 stalled for more than 32210msec
[  451.840084] radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000003d501 last fence id 0x000000000003d768 on ring 3)
[  451.840088] radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000001e67a last fence id 0x000000000001e74a on ring 0)

When turning on second monitor this shows up:
[drm:radeon_cs_parser_relocs [radeon]] *ERROR* gem object lookup failed 0xa
[drm:radeon_cs_ioctl [radeon]] *ERROR* Failed to parse relocation -2!

Old driver 17.2.0-0.20170513 (some git snapshot from 2017-05-13, don't know exact commit) works fine even when used with Mesa-18.1.6 package (I've reverted Radeon SI driver only).
Comment 1 Lukasz Krotowski 2018-09-09 20:47:33 UTC
Created attachment 141495 [details]
lspci
Comment 2 Lukasz Krotowski 2018-09-09 20:47:53 UTC
Created attachment 141496 [details]
xrandr
Comment 3 Lukasz Krotowski 2018-09-09 20:48:10 UTC
Created attachment 141497 [details]
Xorg.0.log
Comment 4 Lukasz Krotowski 2018-09-09 20:50:32 UTC
I'm pretty sure that this bug exists also in 18.2 (I've build git snapshot and had similar issues but attached logs are from 18.1).
Comment 5 Michel Dänzer 2018-09-10 09:46:32 UTC

*** This bug has been marked as a duplicate of bug 105381 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.