Created attachment 128760 [details] Photo Using Fedora 25 with Mesa 13 and LLVM 3.8 on: 04:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Venus XTX [Radeon HD 8890M / R9 M275X/M375X] [1002:6820] (rev 81) identified as "AMD CAPE VERDE" by Mesa. Photo is attached. This is a dual GPU laptop (Lenovo Z51-70), main GPU being 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09) While corruption happens, dmesg | grep radeon does not show anything suspicious, just: [21253.931482] radeon 0000:04:00.0: WB enabled [21253.931484] radeon 0000:04:00.0: fence driver on ring 0 use gpu addr 0x0000000100000c00 and cpu addr 0xffff99e2d0bb1c00 [21253.931485] radeon 0000:04:00.0: fence driver on ring 1 use gpu addr 0x0000000100000c04 and cpu addr 0xffff99e2d0bb1c04 [21253.931486] radeon 0000:04:00.0: fence driver on ring 2 use gpu addr 0x0000000100000c08 and cpu addr 0xffff99e2d0bb1c08 [21253.931486] radeon 0000:04:00.0: fence driver on ring 3 use gpu addr 0x0000000100000c0c and cpu addr 0xffff99e2d0bb1c0c [21253.931487] radeon 0000:04:00.0: fence driver on ring 4 use gpu addr 0x0000000100000c10 and cpu addr 0xffff99e2d0bb1c10 [21253.932296] radeon 0000:04:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffbefe01235a18 [21253.952686] radeon 0000:04:00.0: fence driver on ring 6 use gpu addr 0x0000000100000c18 and cpu addr 0xffff99e2d0bb1c18 [21253.952687] radeon 0000:04:00.0: fence driver on ring 7 use gpu addr 0x0000000100000c1c and cpu addr 0xffff99e2d0bb1c1c Should I test LLVM 3.9/4.0-git? Any other info that could be useful?
Are you still having this issue with recent Mesa / LLVM ?
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1245.
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.