https://bugs.freedesktop.org/show_bug.cgi?id=102414
Bug ID: 102414 Summary: Hawaii gpu (R9 290) and the troubles with the amd-staging-drm-next branch Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel@lists.freedesktop.org Reporter: ptpzz@yandex.ru QA Contact: dri-devel@lists.freedesktop.org
Created attachment 133782 --> https://bugs.freedesktop.org/attachment.cgi?id=133782&action=edit dmesg
Current amd-staging-drm-next branch has some issues with hawaii/CI R9 290 gpu, there is a lot of backtrace noise in the dmesg (see attachment) and some related messages during the boot. I'll add a dmesg right after the boot as well.
There are also some issues with suspend/resume which are possibly related, though not sure.
The problem appeared since the beginning of the August, IIRC. Everything was more stable previously, but it's hard to double-check older versions as long as the branch is usually force-pushed.
https://bugs.freedesktop.org/show_bug.cgi?id=102414
--- Comment #1 from Vadim Girlin ptpzz@yandex.ru --- Created attachment 133783 --> https://bugs.freedesktop.org/attachment.cgi?id=133783&action=edit lspci
https://bugs.freedesktop.org/show_bug.cgi?id=102414
--- Comment #2 from Vadim Girlin ptpzz@yandex.ru --- Created attachment 133784 --> https://bugs.freedesktop.org/attachment.cgi?id=133784&action=edit Xorg.0.log
https://bugs.freedesktop.org/show_bug.cgi?id=102414
--- Comment #3 from Vadim Girlin ptpzz@yandex.ru --- Created attachment 133785 --> https://bugs.freedesktop.org/attachment.cgi?id=133785&action=edit dmesg right after boot
There is a lot of noise, so initial stuff is missing anyway. Please let me know if you need it, I can probably adjust kernel options to save the entire log.
https://bugs.freedesktop.org/show_bug.cgi?id=102414
--- Comment #4 from Harry Wentland harry.wentland@amd.com --- Created attachment 133786 --> https://bugs.freedesktop.org/attachment.cgi?id=133786&action=edit Patch for suspend/resume issues
Hopefully this helps with the suspend/resume issues.
https://bugs.freedesktop.org/show_bug.cgi?id=102414
--- Comment #5 from Vadim Girlin ptpzz@yandex.ru --- (In reply to Harry Wentland from comment #4)
Created attachment 133786 [details] [review] Patch for suspend/resume issues
Hopefully this helps with the suspend/resume issues.
Unfortunately the problem with suspend is still there, basically the system fails to suspend and then any attempt to suspend/reboot/shutdown results in "There's already a shutdown or sleep operation in progress" message, so I have to use magic sysrq keys to reboot.
I'm still not sure if it's directly related to the amdgpu driver issues, but IIRC the problem has appeared at the same time as the backtraces noise in the logs, and I didn't hit it with other kernels, only with the amd-staging-drm-next branch.
It was reproducible for me on Fedora 26 and currently it's the same with the clean installation of Fedora 27 (pre-release).
https://bugs.freedesktop.org/show_bug.cgi?id=102414
--- Comment #6 from Vadim Girlin ptpzz@yandex.ru --- Created attachment 134152 --> https://bugs.freedesktop.org/attachment.cgi?id=134152&action=edit dmesg after failed resume
The latest amd-staging-drm-next branch fails to resume from suspend properly for me. It worked previously (when it was possible to perform a suspend).
After resume the screen is mostly blue now with some dynamic random noise - horizontal black lines etc. Though I hear the sound via the display port audio from the video that was playing at the moment of suspend, so at least that part seems to work.
There are some amdgpu backtraces in the attached dmesg before and after the suspend/resume, but I didn't notice any real issues before suspend so far, the only problem is that the display is unusable after resume.
https://bugs.freedesktop.org/show_bug.cgi?id=102414
--- Comment #7 from Timothy Arceri t_arceri@yahoo.com.au --- Is this still a problem?
https://bugs.freedesktop.org/show_bug.cgi?id=102414
GitLab Migration User gitlab-migration@fdo.invalid changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED
--- Comment #8 from GitLab Migration User gitlab-migration@fdo.invalid --- -- 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/1277.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org