From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 208893] Navi (RX 5700 XT) system appears to hang with more than one display connected
Date: Thu, 13 Aug 2020 06:02:32 +0000 [thread overview]
Message-ID: <bug-208893-2300-IAZzA2NRvn@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208893-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208893
--- Comment #3 from Gordon (gordon@gordonite.tech) ---
The Diff from the log file - clearly showing the problem:
[ 51.925494] amdgpu: Msg issuing pre-check failed and SMU may be not in the
right state!
[ 54.442825] amdgpu: Msg issuing pre-check failed and SMU may be not in the
right state!
[ 56.962050] amdgpu: Msg issuing pre-check failed and SMU may be not in the
right state!
[ 59.475881] amdgpu: Msg issuing pre-check failed and SMU may be not in the
right state!
[ 61.752557] amdgpu: Msg issuing pre-check failed and SMU may be not in the
right state!
[ 64.274971] amdgpu: Msg issuing pre-check failed and SMU may be not in the
right state!
[ 66.797358] amdgpu: Msg issuing pre-check failed and SMU may be not in the
right state!
[ 69.318513] amdgpu: Msg issuing pre-check failed and SMU may be not in the
right state!
[ 70.395781] rfkill: input handler disabled
[ 72.035479] amdgpu: Msg issuing pre-check failed and SMU may be not in the
right state!
[ 74.554161] amdgpu: Msg issuing pre-check failed and SMU may be not in the
right state!
[ 77.073499] amdgpu: Msg issuing pre-check failed and SMU may be not in the
right state!
[ 78.755571] snd_hda_intel 0000:0c:00.1: refused to change power state from
D0 to D3hot
[ 79.593997] amdgpu: Msg issuing pre-check failed and SMU may be not in the
right state!
[ 81.941379] amdgpu: Msg issuing pre-check failed and SMU may be not in the
right state!
[ 84.460616] amdgpu: Msg issuing pre-check failed and SMU may be not in the
right state!
[ 86.980582] amdgpu: Msg issuing pre-check failed and SMU may be not in the
right state!
[ 89.498263] amdgpu: Msg issuing pre-check failed and SMU may be not in the
right state!
[ 91.742602] rfkill: input handler enabled
--
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
next prev parent reply other threads:[~2020-08-13 6:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 5:33 [Bug 208893] New: Navi (RX 5700 XT) system appears to hang with more than one display connected bugzilla-daemon
2020-08-13 5:58 ` [Bug 208893] " bugzilla-daemon
2020-08-13 6:01 ` bugzilla-daemon
2020-08-13 6:02 ` bugzilla-daemon [this message]
2020-08-13 6:39 ` bugzilla-daemon
2020-08-13 6:39 ` bugzilla-daemon
2020-08-13 6:47 ` bugzilla-daemon
2020-08-13 6:47 ` bugzilla-daemon
2020-08-13 6:48 ` bugzilla-daemon
2020-08-13 6:51 ` bugzilla-daemon
2020-08-13 15:34 ` bugzilla-daemon
2020-08-13 17:30 ` bugzilla-daemon
2020-08-13 19:16 ` bugzilla-daemon
2020-08-20 13:45 ` bugzilla-daemon
2020-08-21 14:33 ` bugzilla-daemon
2020-09-01 1:13 ` bugzilla-daemon
2020-09-12 21:29 ` bugzilla-daemon
2020-09-13 12:50 ` bugzilla-daemon
2020-09-13 13:03 ` bugzilla-daemon
2020-09-13 13:17 ` 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-208893-2300-IAZzA2NRvn@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox