Bug 109487 - drm-next-5.1-wip broken as of 672c6238
Summary: drm-next-5.1-wip broken as of 672c6238
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
Depends on:
Reported: 2019-01-28 19:42 UTC by asavah
Modified: 2019-01-29 17:15 UTC (History)
5 users (show)

See Also:
i915 platform:
i915 features:

dmesg with backtrace (65.50 KB, text/plain)
2019-01-28 19:42 UTC, asavah
no flags Details
another dmesg with warning backtrace before GPF (70.46 KB, text/plain)
2019-01-28 19:54 UTC, asavah
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description asavah 2019-01-28 19:42:28 UTC
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.
Comment 1 asavah 2019-01-28 19:54:27 UTC
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 ...
Comment 3 asavah 2019-01-28 21:39:56 UTC
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.
Comment 5 Tom St Denis 2019-01-29 15:35:32 UTC
Reverting just the -msse2 commit on top of drm-next works fine for me.

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.