kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 218876] PCIE device crash when trying to pass through USB PCIe Card to virtual machine
Date: Tue, 28 May 2024 21:16:12 +0000	[thread overview]
Message-ID: <bug-218876-28872-pmN0dnGr2r@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218876-28872@https.bugzilla.kernel.org/>

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

Alex Williamson (alex.williamson@redhat.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alex.williamson@redhat.com

--- Comment #9 from Alex Williamson (alex.williamson@redhat.com) ---
(In reply to TJ from comment #2)
> This could be a power management issue:
> 
>   vfio-pci 0000:02:00.0: Unable to change power state from D3cold to D0,
> device inaccessible

I wouldn't rule out a power management issue, but I think the device has
already disappeared by the time we're seeing these error logs.  We're hitting
the timeouts waiting for the device after bus reset and we trigger quirks that
are trying to retrain the link at a reduced rate.  Unfortunately this device
only supports bus reset.

Is it possible to test assigning another single function device installed in
this slot?  We'd want to make sure that the reset_method is still "bus", which
can be selected via the same sysfs file if the other device supports more reset
mechanism.

If it is a power management issue, we can also restrict vfio-pci use of power
management by passing the disable_idle_d3=1 module option when loading the
vfio-pci driver.  If that works, we might want to quirk the ID for this old NEC
controller to avoid D3 states.

-- 
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:[~2024-05-28 21:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22 19:31 [Bug 218876] New: PCIE device crash when trying to pass through USB Device to virtual machine bugzilla-daemon
2024-05-22 19:32 ` [Bug 218876] " bugzilla-daemon
2024-05-22 19:34 ` [Bug 218876] PCIE device crash when trying to pass through USB PCIe Card " bugzilla-daemon
2024-05-22 20:38 ` bugzilla-daemon
2024-05-23 14:35 ` bugzilla-daemon
2024-05-23 15:28 ` bugzilla-daemon
2024-05-23 15:28 ` bugzilla-daemon
2024-05-24 11:19 ` bugzilla-daemon
2024-05-25 13:49 ` bugzilla-daemon
2024-05-25 14:16 ` bugzilla-daemon
2024-05-25 14:20 ` bugzilla-daemon
2024-05-28 21:16 ` bugzilla-daemon [this message]
2024-05-29 10:42 ` bugzilla-daemon
2024-05-29 11:35 ` 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-218876-28872-pmN0dnGr2r@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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).