All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 204975] New: AMD-Vi: Command buffer timeout
Date: Mon, 23 Sep 2019 23:06:58 +0000	[thread overview]
Message-ID: <bug-204975-28872@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 204975
           Summary: AMD-Vi: Command buffer timeout
           Product: Virtualization
           Version: unspecified
    Kernel Version: 4.19.75
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: sss123next@list.ru
        Regression: No

Created attachment 285127
  --> https://bugzilla.kernel.org/attachment.cgi?id=285127&action=edit
dmesg fragment with error

i have "ASRock X470 Gaming K4" motherboard, and using pci-passthrough for
sometime already, working fine on bios version 1.90, had some troubles, but
working overall, unfortunately i decided to update bios to latest versions
(3.40, 3.50), and pci-passthrough stopped work at all, i guess problem rerlated
to new "AMD AGESA Combo-AM4 1.0.0.3", a little searching over internet confirms
what it's common problem across different boards, i do not know exactly is it
amd bug, kvm, bug, or kernel bug, i have already reported problem to board
manufacturer.

in console i get something like "vfio: cannot power on device, stuck in D3"
from qemu.

also a lot of warnings in dmesg (see attachments).

device still visible in lspci, but looks completely unresponsive.

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

             reply	other threads:[~2019-09-23 23:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-23 23:06 bugzilla-daemon [this message]
2019-09-23 23:07 ` [Bug 204975] AMD-Vi: Command buffer timeout 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
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@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 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.