All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 210921] New: amdgpu on Radeon R9 280X floods "[drm] Display Core has been requested via kernel parameter but isn't supported by ASIC, ignoring"
Date: Sun, 27 Dec 2020 17:36:00 +0000	[thread overview]
Message-ID: <bug-210921-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=210921

            Bug ID: 210921
           Summary: amdgpu on Radeon R9 280X floods "[drm] Display Core
                    has been requested via kernel parameter but isn't
                    supported by ASIC, ignoring"
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.9.14
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: low
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: alexandre.f.demers@gmail.com
        Regression: No

A small extract of what is spurted in logs when using an Radeon R9 280X with
amdgpu.

[...]
[47837.292590] [drm] Display Core has been requested via kernel parameter but
isn't supported by ASIC, ignoring
[47837.409321] [drm] Display Core has been requested via kernel parameter but
isn't supported by ASIC, ignoring
[47837.553302] [drm] Display Core has been requested via kernel parameter but
isn't supported by ASIC, ignoring
[47837.640563] [drm] Display Core has been requested via kernel parameter but
isn't supported by ASIC, ignoring
[...]

My R9 280X was put aside in the last year for a Vega FE. However, I'm back at
working on VCE 1 and this is one of the things I've found out since plugging
the card in. I don't see why we should continually print (and at that pace...)
that this is not supported. Report it once and move along.

I've narrowed down the issue to line 3037 in
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c. DRM_INFO should be replaced by
DRM_INFO_ONCE.

By the way, the card is still rock solid for any regular work and many games in
my library.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

                 reply	other threads:[~2020-12-27 17:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-210921-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.