From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 204975] AMD-Vi: Command buffer timeout
Date: Mon, 23 Sep 2019 23:20:24 +0000 [thread overview]
Message-ID: <bug-204975-28872-KNWvhyPhAa@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204975-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204975
Alex Williamson (alex.williamson@redhat.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alex.williamson@redhat.com
--- Comment #7 from Alex Williamson (alex.williamson@redhat.com) ---
When we get the "stuck in D3" message, it usually means that we're getting back
-1 on config space reads rather than the device is actually stuck in D3. The
-1 return probably means the downstream bus never recovered when we issued a
secondary bus reset to perform a reset on the GPU. This seems to be common
with AGESA updates and AFAICT indicates a hardware/firmware issue, not a kernel
issue. As you indicate, it worked previously and started failing after BIOS
update. This is the common story, AMD needs to fix secondary bus reset support
on their root ports. I believe some users have had success rolling back their
BIOS to a previous release.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-09-23 23:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 23:06 [Bug 204975] New: AMD-Vi: Command buffer timeout bugzilla-daemon
2019-09-23 23:07 ` [Bug 204975] " bugzilla-daemon
2019-09-23 23:07 ` bugzilla-daemon
2019-09-23 23:08 ` bugzilla-daemon
2019-09-23 23:08 ` bugzilla-daemon
2019-09-23 23:09 ` bugzilla-daemon
2019-09-23 23:09 ` bugzilla-daemon
2019-09-23 23:20 ` bugzilla-daemon [this message]
2019-09-23 23:32 ` bugzilla-daemon
2019-09-25 13:38 ` bugzilla-daemon
2019-09-26 14:59 ` bugzilla-daemon
2020-04-02 11:29 ` 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-204975-28872-KNWvhyPhAa@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).