From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 109135] R9 390 hangs at boot with DPM/DC enabled for kernels
4.19.x and above, says KMS not supported
Date: Sat, 22 Dec 2018 19:20:23 +0000
Message-ID:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1918924375=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[IPv6:2610:10:20:722:a800:ff:fe98:4b55])
by gabe.freedesktop.org (Postfix) with ESMTP id F080C6E3EE
for ; Sat, 22 Dec 2018 19:20:25 +0000 (UTC)
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============1918924375==
Content-Type: multipart/alternative; boundary="15455064250.df7a4.4061"
Content-Transfer-Encoding: 7bit
--15455064250.df7a4.4061
Date: Sat, 22 Dec 2018 19:20:25 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D109135
Bug ID: 109135
Summary: R9 390 hangs at boot with DPM/DC enabled for kernels
4.19.x and above, says KMS not supported
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: rmuncrief@humanavance.com
Created attachment 142874
--> https://bugs.freedesktop.org/attachment.cgi?id=3D142874&action=3Dedit
Example of failed amdgpu boot with R9 390.
I'm running the latest Manjaro and have a Sapphire Nitro R9 390. Kernels be=
fore
4.19.x work great with amdgpu, but all kernels from 4.19.x on hang at boot,=
and
usually don't even generate a boot log, no matter how long you wait.
However after compiling and testing the latest linux-amd-wip-git I was able=
to
get a log so I can finally file a bug. By the way, I've gotten a few logs
before but lost them while debugging, however this time I had the sense to =
save
it.
In nay case, the error line is always the same:
AMDGPU(0): [KMS] drm report modesetting isn't supported.
This only happens if you set amdgpu.dpm=3D1 and/or amdgpu.dc=3D1 with the b=
ad
kernels. If you leave those options out amdgpu works, but things like resum=
ing
from suspend, etc. don't work.
I've attached Xorg.0.good.log to show a good boot with kernel 4.18.20, and a
Xorg.0.bad.log to show the failed boot with amd-wip-git. And by the way I've
tried numerous kernels over the last weeks and they all fail the same way, =
but
if you want me to test a specific kernel I'll be happy to do so.
Here's the grub line I use for all testing:
GRUB_CMDLINE_LINUX_DEFAULT=3D"quiet
resume=3DUUID=3Db4f71480-8fe3-43c2-99c9-fc3f5687545b libata.atapi_passthru1=
6=3D0
rd.modules-load=3Dvfio-pci amd_iommu=3Don iommu=3Dpt amdgpu.modeset=3D1
radeon.si_support=3D0 radeon.cik_support=3D0 amdgpu.si_support=3D1
amdgpu.cik_support=3D1 amdgpu.dpm=3D1 amdgpu.dc=3D1"
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15455064250.df7a4.4061
Date: Sat, 22 Dec 2018 19:20:25 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
| Bug ID |
109135
|
| Summary |
R9 390 hangs at boot with DPM/DC enabled for kernels 4.19.x a=
nd above, says KMS not supported
|
| Product |
DRI
|
| Version |
XOrg git
|
| Hardware |
x86-64 (AMD64)
|
| OS |
Linux (All)
|
| Status |
NEW
|
| Severity |
critical
|
| Priority |
medium
|
| Component |
DRM/AMDgpu
|
| Assignee |
dri-devel@lists.freedesktop.org
|
| Reporter |
rmuncrief@humanavance.com
|
Created attachment 142874 [details]=
Example of failed amdgpu boot with R9 390.
I'm running the latest Manjaro and have a Sapphire Nitro R9 390. Kernels be=
fore
4.19.x work great with amdgpu, but all kernels from 4.19.x on hang at boot,=
and
usually don't even generate a boot log, no matter how long you wait.
However after compiling and testing the latest linux-amd-wip-git I was able=
to
get a log so I can finally file a bug. By the way, I've gotten a few logs
before but lost them while debugging, however this time I had the sense to =
save
it.
In nay case, the error line is always the same:
AMDGPU(0): [KMS] drm report modesetting isn't supported.
This only happens if you set amdgpu.dpm=3D1 and/or amdgpu.dc=3D1 with the b=
ad
kernels. If you leave those options out amdgpu works, but things like resum=
ing
from suspend, etc. don't work.
I've attached Xorg.0.good.log to show a good boot with kernel 4.18.20, and a
Xorg.0.bad.log to show the failed boot with amd-wip-git. And by the way I've
tried numerous kernels over the last weeks and they all fail the same way, =
but
if you want me to test a specific kernel I'll be happy to do so.
Here's the grub line I use for all testing:
GRUB_CMDLINE_LINUX_DEFAULT=3D"quiet
resume=3DUUID=3Db4f71480-8fe3-43c2-99c9-fc3f5687545b libata.atapi_passthru1=
6=3D0
rd.modules-load=3Dvfio-pci amd_iommu=3Don iommu=3Dpt amdgpu.modeset=3D1
radeon.si_support=3D0 radeon.cik_support=3D0 amdgpu.si_support=3D1
amdgpu.cik_support=3D1 amdgpu.dpm=3D1 amdgpu.dc=3D1"
You are receiving this mail because:
- You are the assignee for the bug.
=
--15455064250.df7a4.4061--
--===============1918924375==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============1918924375==--