Displaying 3 results from an estimated 3 matches for "pcie004".
Did you mean:
pcie04
2020 Oct 05
2
PCI Passthrough and Surprise Hotplug
...'/>
</hostdev>
This all works fine during normal operation, but I noticed when we
remove the NVMe drive (surprise hotplug event), the PCIe EP then seems
"stuck"... here we see the link-down event on the host (when the drive
is removed):
[67720.177959] pciehp 0000:40:01.2:pcie004: Slot(238-1): Link Down
[67720.178027] vfio-pci 0000:42:00.0: Relaying device request to user (#0)
And naturally, inside of the Linux VM, we see the NVMe controller drop:
[ 1203.491536] nvme nvme1: controller is down; will reset:
CSTS=0xffffffff, PCI_STATUS=0xffff
[ 1203.522759] blk_update_request...
2020 Oct 07
0
Re: PCI Passthrough and Surprise Hotplug
...;
>
> This all works fine during normal operation, but I noticed when we
> remove the NVMe drive (surprise hotplug event), the PCIe EP then seems
> "stuck"... here we see the link-down event on the host (when the drive
> is removed):
> [67720.177959] pciehp 0000:40:01.2:pcie004: Slot(238-1): Link Down
> [67720.178027] vfio-pci 0000:42:00.0: Relaying device request to user (#0)
>
> And naturally, inside of the Linux VM, we see the NVMe controller drop:
> [ 1203.491536] nvme nvme1: controller is down; will reset:
> CSTS=0xffffffff, PCI_STATUS=0xffff
> [ 1...
2017 Jan 06
0
nouveau: display freezing
...] start plist test
[ 2.491948] end plist test
[ 2.493405] pcieport 0000:00:1c.0: enabling device (0000 -> 0003)
[ 2.495433] pcieport 0000:07:03.0: enabling device (0000 -> 0003)
[ 2.496113] pcieport 0000:07:05.0: enabling device (0000 -> 0003)
[ 2.496880] pciehp 0000:00:1c.0:pcie004: Slot #0 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ LLActRep+
[ 2.497060] pciehp 0000:07:00.0:pcie204: Slot #0 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ LLActRep+
[ 2.497189] pciehp 0000:07:03.0:pcie204: Slot #3 AttnBtn-...