dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 215892] 6500XT [drm:amdgpu_dm_init.isra.0.cold [amdgpu]] *ERROR* Failed to register vline0 irq 30!
Date: Wed, 27 Apr 2022 12:22:29 +0000	[thread overview]
Message-ID: <bug-215892-2300-AMPp22KfRz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215892-2300@https.bugzilla.kernel.org/>

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

--- Comment #6 from Mark Johnston (ulatec@gmail.com) ---
There is one potentially similar report here:
https://gitlab.freedesktop.org/drm/amd/-/issues/1933

Though both of the users report having working desktop environments and nothing
about amdgpu not being able to come out of D3cold. In my case above the gpus
are non-responsive, as they are stuck in the d3cold power state. So the
amdgpu_dm_init.isra may be the same, but the results and impacts differ.

Not really sure what to do here. Should I add my findings (hardware tests) to
that report?

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

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2022-04-27 12:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27  2:23 [Bug 215892] New: 6500XT [drm:amdgpu_dm_init.isra.0.cold [amdgpu]] *ERROR* Failed to register vline0 irq 30! bugzilla-daemon
2022-04-27  2:24 ` [Bug 215892] " bugzilla-daemon
2022-04-27  2:28 ` bugzilla-daemon
2022-04-27  2:33 ` bugzilla-daemon
2022-04-27  2:52 ` bugzilla-daemon
2022-04-27  8:59 ` bugzilla-daemon
2022-04-27 12:22 ` bugzilla-daemon [this message]

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-215892-2300-AMPp22KfRz@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox