Created attachment 143242 [details] dmesg with backtrace Currently https://cgit.freedesktop.org/~agd5f/linux/tree/?h=drm-next-5.1-wip is totally broken at least for raven 2400g apu. 4.20.5 works pretty well on this machine. Dmesg with backtrace attached. Dear AMD developers: it would be bad if drm-next-5.1-wip code in its current state went into mainline, please review and fix.
Created attachment 143243 [details] another dmesg with warning backtrace before GPF Previous dmesg was from a build containing a patch to make shut up the warning which hasn't been fixed for months ...
Does reverting this commit help? https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-5.1-wip&id=12c51ee226c12933d0188b8f04804166a69f6f6e
No, sadly it doesn't help. Additional observations: If amdgpu is built as module the system boots without graphics, but networking and ssh are working, however it's impossible to reboot the system, it just hangs after issuing "reboot". If amdgpu is built-in (with embedded raven* firmware blobs) the system just hangs with black screen, no network.
Reverting this patch should fix it: https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-5.1-wip&id=10117450735c7a7c0858095fb46a860e7037cb9a
Reverting just the -msse2 commit on top of drm-next works fine for me.
Yes, indeed reverting https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-5.1-wip&id=10117450735c7a7c0858095fb46a860e7037cb9a seems to fix the issue.
-- 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/drm/amd/issues/686.
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.