https://bugs.freedesktop.org/show_bug.cgi?id=109487
Bug ID: 109487 Summary: drm-next-5.1-wip broken as of 672c6238 Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: irherder@gmail.com
Created attachment 143242 --> https://bugs.freedesktop.org/attachment.cgi?id=143242&action=edit 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.
https://bugs.freedesktop.org/show_bug.cgi?id=109487
asavah irherder@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #143242|0 |1 is obsolete| |
--- Comment #1 from asavah irherder@gmail.com --- Created attachment 143243 --> https://bugs.freedesktop.org/attachment.cgi?id=143243&action=edit 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 ...
https://bugs.freedesktop.org/show_bug.cgi?id=109487
--- Comment #2 from Alex Deucher alexdeucher@gmail.com --- Does reverting this commit help? https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-5.1-wip&id=...
https://bugs.freedesktop.org/show_bug.cgi?id=109487
--- Comment #3 from asavah irherder@gmail.com --- 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.
https://bugs.freedesktop.org/show_bug.cgi?id=109487
--- Comment #4 from Alex Deucher alexdeucher@gmail.com --- Reverting this patch should fix it: https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-5.1-wip&id=...
https://bugs.freedesktop.org/show_bug.cgi?id=109487
--- Comment #5 from Tom St Denis tom.stdenis@amd.com --- Reverting just the -msse2 commit on top of drm-next works fine for me.
https://bugs.freedesktop.org/show_bug.cgi?id=109487
--- Comment #6 from asavah irherder@gmail.com --- Yes, indeed reverting https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-5.1-wip&id=... seems to fix the issue.
https://bugs.freedesktop.org/show_bug.cgi?id=109487
Martin Peres martin.peres@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED
--- Comment #7 from Martin Peres martin.peres@free.fr --- -- 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.
dri-devel@lists.freedesktop.org