dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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	[thread overview]
Message-ID: <bug-109135-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2196 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=109135

            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=142874&action=edit
Example of failed amdgpu boot with R9 390.

I'm running the latest Manjaro and have a Sapphire Nitro R9 390. Kernels before
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=1 and/or amdgpu.dc=1 with the bad
kernels. If you leave those options out amdgpu works, but things like resuming
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="quiet
resume=UUID=b4f71480-8fe3-43c2-99c9-fc3f5687545b libata.atapi_passthru16=0
rd.modules-load=vfio-pci amd_iommu=on iommu=pt amdgpu.modeset=1
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1
amdgpu.cik_support=1 amdgpu.dpm=1 amdgpu.dc=1"

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3702 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-12-22 19:20 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-22 19:20 bugzilla-daemon [this message]
2018-12-22 19:21 ` [Bug 109135] R9 390 hangs at boot with DPM/DC enabled for kernels 4.19.x and above, says KMS not supported bugzilla-daemon
2018-12-23 19:52 ` bugzilla-daemon
2018-12-24 21:43 ` bugzilla-daemon
2018-12-27 16:10 ` bugzilla-daemon
2018-12-27 16:10 ` bugzilla-daemon
2018-12-27 16:10 ` bugzilla-daemon
2018-12-27 16:15 ` bugzilla-daemon
2019-01-10 23:47 ` bugzilla-daemon
2019-01-11  0:54 ` bugzilla-daemon
2019-01-11  1:09 ` bugzilla-daemon
2019-01-11  1:25 ` bugzilla-daemon
2019-01-11 15:30 ` bugzilla-daemon
2019-01-11 16:29 ` bugzilla-daemon
2019-01-11 20:10 ` bugzilla-daemon
2019-01-11 20:38 ` bugzilla-daemon
2019-01-11 20:44 ` bugzilla-daemon
2019-01-11 20:49   ` Alex Deucher
2019-01-11 20:49 ` bugzilla-daemon
2019-01-12 21:46 ` bugzilla-daemon
2019-01-14 15:45 ` bugzilla-daemon
2019-01-14 17:53 ` bugzilla-daemon
2019-01-14 19:19 ` bugzilla-daemon
2019-01-14 20:04 ` bugzilla-daemon
2019-01-16 14:27 ` bugzilla-daemon
2019-01-16 16:45 ` bugzilla-daemon
2019-01-16 17:57 ` bugzilla-daemon
2019-01-16 18:58 ` bugzilla-daemon
2019-11-19  9:08 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-109135-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox