If I read this correctly you reverted the commit which enables UVD PG on Tonga? I can't see how that impacts Polaris at all.
If I had to guess it's a dGPU state issue. I've had on occasion to resort to cold reboots to bisect the kernel because the GPU firmware can get into states that aren't 100% resolved by a warm reboot. There is a known bad commit which was reverted by Christian which I guess isn't out on fdo yet. https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-4.7&id=6691270952b6909218c520dcc71a342070c96874 that commit seems to break dGPU support. Cheers, Tom ________________________________ From: amd-gfx <amd-gfx-boun...@lists.freedesktop.org> on behalf of Jeremy Newton <alexjn...@gmail.com> Sent: Wednesday, October 5, 2016 22:54 To: amd-gfx@lists.freedesktop.org Subject: Issue with amd-staging-4.7 on rx480 Hello, I'm currently regularly building and using the amd-staging-4.7 linux branch, which can be found here: https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-4.7 It seems that one of the commits pushed on 2016-10-03 broke something, and I just wanted to give the devs a heads up in case no one noticed. I'm guessing it was caused by one of the commits in the range of e3bb40f all the way up to 78d1842. I'm using an RX480, polaris10. The issue seems to have two symptoms: - Plymouth (the boot splash screen) seems to get visually corrupted or just blacked out. - After login, the screen just remains black until I hard reset. Reverting back to 8f877a8 seems to fix it. I'm using Fedora 24 with GNOME. As well, I haven't had time to bisect, but I can do so if desired. Thanks!
_______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
