https://bugs.freedesktop.org/show_bug.cgi?id=108031
Bug ID: 108031 Summary: [Regression] amdgpu_device_ip_init failed on Bonaire XT Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: tasos@tasossah.com
Created attachment 141697 --> https://bugs.freedesktop.org/attachment.cgi?id=141697&action=edit 4.19 rc4 boot log (black screen)
AMDGPU fails to initialise the graphics card with mainline kernel 4.19, from rc1 to rc4, resulting in a black screen on boot.
4.18.8 boots to the desktop without any fatal errors, and functions as expected. The regression happened some time before 4.19 rc1 but after the 4.18 release.
Graphics card is: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon HD 7790/8770 / R7 360 / R9 260/360 OEM] [1002:665c]
I attempted to bisect it, but I kept hitting another (possibly unrelated) bug that would cause a panic on boot and thus was unable to. Attached are the kernel logs from both 4.18.8 and 4.19 rc4.
Running the latest available firmware for this card from the git repo.
https://bugs.freedesktop.org/show_bug.cgi?id=108031
--- Comment #1 from Tasos Sahanidis tasos@tasossah.com --- Created attachment 141698 --> https://bugs.freedesktop.org/attachment.cgi?id=141698&action=edit 4.18.8 boot log (working)
https://bugs.freedesktop.org/show_bug.cgi?id=108031
--- Comment #2 from Alexander Schlarb alexander-fd@xmine128.tk --- Created attachment 143205 --> https://bugs.freedesktop.org/attachment.cgi?id=143205&action=edit 4.19.0 Debian kernal boot log (external screen working)
I can reproduce this with
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo (rev c4) 03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon R9 M280X] (rev 80)
on a “Lenovo ideapad Y700-ACZ”.
When I boot into the released Linux 4.19.0 from Debian I get a blank screen, however today I discovered that if you have an external displayed plugged during boot-up that display will be successfully enabled and you can then log in as usual. The internal laptop display will not ever be enabled however and checking under *Systemsettings* → *Monitor Settings* (KDE) will not show it either. Also the entire system will feel very sluggish (not CPU or disk related, I checked) and is only usable with lots of patience. On shutdown the system will then hang (nothing about this in system logs unfortunately).
https://bugs.freedesktop.org/show_bug.cgi?id=108031
--- Comment #3 from Alex Deucher alexdeucher@gmail.com --- Remove amdgpu.dpm=1 from your kernel command line. The default dpm implementation changed in 4.19.
https://bugs.freedesktop.org/show_bug.cgi?id=108031
--- Comment #4 from Alex Deucher alexdeucher@gmail.com --- (In reply to Alex Deucher from comment #3)
Remove amdgpu.dpm=1 from your kernel command line. The default dpm implementation changed in 4.19.
and setting dpm=1 overrides that resulting in different behavior. power management is always enabled by default. the dpm option is only for debugging and switching between implementations for asics that contain multiple implementations.
https://bugs.freedesktop.org/show_bug.cgi?id=108031
--- Comment #5 from Alexander Schlarb alexander-fd@xmine128.tk --- Using the latest Debian kernel (4.19.0-2, which apparently corresponds to Linux version 4.19.16, with 4.19.0-1 having corresponded to 4.19.13) this issue does not affect me anymore.
I looked through the kernel commits between the versions but none looked very related, there was some stuff about DP MST which maybe somehow relevant since the display is connected using eDP. Dunno.
Anyways, works for me now.
https://bugs.freedesktop.org/show_bug.cgi?id=108031
Martin Peres martin.peres@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED
--- Comment #6 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/538.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org