August 24, 2025Aug 24 HiUnraid keeps spamming the following errors:Aug 24 11:31:26 blackbox kernel: pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible Aug 24 11:31:26 blackbox kernel: pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessibleThis happens exactly once every time I reload the "VMS" tab (with my VMs running) or continuously every couple of seconds when displaying the "DASHBOARD" tab.It's related to Thunderbolt (I have a Thunderbolt monitor with build-in KVM)root@blackbox:~# lspci | grep 1b 1b:00.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) 1b:01.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) 1b:02.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) 1b:03.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) 1b:04.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) root@blackbox:~#The device is authorized:root@blackbox:~# cat /sys/bus/thunderbolt/devices/0-1/device_name U2724DE root@blackbox:~# cat /sys/bus/thunderbolt/devices/0-1/authorized 1 root@blackbox:~# My iGPU is passed through to a Kubuntu-VM as well as one of the USB-Controllers that is part of Thunderbolt. The Thunderbolt Controller is managed by Unraid though. I tried to pass it through to the VM as well but I could not get a stable setup with this.Here my full lspci:root@blackbox:~# lspci -k 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Root Complex Subsystem: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge IOMMU Subsystem: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge GPP Bridge Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1453 Kernel driver in use: pcieport 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge GPP Bridge Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1453 Kernel driver in use: pcieport 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge 00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge GPP Bridge Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1453 Kernel driver in use: pcieport 00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge GPP Bridge Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1453 Kernel driver in use: pcieport 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Internal GPP Bridge to Bus [C:A] Subsystem: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Internal GPP Bridge to Bus [C:A] Kernel driver in use: pcieport 00:08.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Internal GPP Bridge to Bus [C:A] Subsystem: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Internal GPP Bridge to Bus [C:A] Kernel driver in use: pcieport 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 71) Subsystem: ASRock Incorporation Device 790b Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) Subsystem: ASRock Incorporation Device 790e 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 3 Kernel driver in use: k10temp Kernel modules: k10temp 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 7 01:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev 24) Subsystem: Tul Corporation / PowerColor Device 1478 Kernel driver in use: pcieport 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch (rev 24) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch Kernel driver in use: pcieport 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 48 [RX 9070/9070 XT] (rev c0) Subsystem: Tul Corporation / PowerColor Device 2435 Kernel driver in use: vfio-pci Kernel modules: amdgpu 03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device ab40 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device ab40 Kernel driver in use: vfio-pci 04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal] Subsystem: Samsung Electronics Co Ltd Device a801 Kernel driver in use: nvme Kernel modules: nvme 05:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Upstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 06:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 06:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 06:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 06:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 06:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 06:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 06:0c.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 06:0d.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 07:00.0 SATA controller: JMicron Technology Corp. JMB58x AHCI SATA controller Subsystem: JMicron Technology Corp. Device 0000 Kernel driver in use: ahci 0a:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8126 5GbE Controller (rev 01) Subsystem: ASRock Incorporation Device 8126 Kernel driver in use: r8169 Kernel modules: r8169 0b:00.0 Network controller: MEDIATEK Corp. Device 0717 Subsystem: MEDIATEK Corp. Device 0717 0c:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Upstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 0d:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 0d:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 0d:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 0d:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 0d:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 0d:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 0d:0c.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 0d:0d.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. Device 3328 Kernel driver in use: pcieport 13:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal] Subsystem: Samsung Electronics Co Ltd Device a801 Kernel driver in use: nvme Kernel modules: nvme 14:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 800 Series Chipset USB 3.x XHCI Controller (rev 01) Subsystem: ASMedia Technology Inc. Device 1142 Kernel driver in use: xhci_hcd 15:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset SATA Controller (rev 01) Subsystem: ASMedia Technology Inc. Device 1062 Kernel driver in use: ahci 16:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 800 Series Chipset USB 3.x XHCI Controller (rev 01) Subsystem: ASMedia Technology Inc. Device 1142 Kernel driver in use: vfio-pci 17:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset SATA Controller (rev 01) Subsystem: ASMedia Technology Inc. Device 1062 Kernel driver in use: ahci 18:00.0 PCI bridge: ASMedia Technology Inc. ASM4242 PCIe Switch Upstream Port (rev 01) Subsystem: ASMedia Technology Inc. ASM4242 PCIe Switch Upstream Port Kernel driver in use: pcieport 19:00.0 PCI bridge: ASMedia Technology Inc. ASM4242 PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. ASM4242 PCIe Switch Downstream Port Kernel driver in use: pcieport 19:01.0 PCI bridge: ASMedia Technology Inc. ASM4242 PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. ASM4242 PCIe Switch Downstream Port Kernel driver in use: pcieport 19:02.0 PCI bridge: ASMedia Technology Inc. ASM4242 PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. ASM4242 PCIe Switch Downstream Port Kernel driver in use: pcieport 19:03.0 PCI bridge: ASMedia Technology Inc. ASM4242 PCIe Switch Downstream Port (rev 01) Subsystem: ASMedia Technology Inc. ASM4242 PCIe Switch Downstream Port Kernel driver in use: pcieport 1a:00.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) Subsystem: Intel Corporation Device 0000 Kernel driver in use: pcieport 1b:00.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) Subsystem: Intel Corporation Device 0000 Kernel driver in use: pcieport 1b:01.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) Subsystem: Intel Corporation Device 0000 Kernel driver in use: pcieport 1b:02.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) Subsystem: Intel Corporation Device 0000 Kernel driver in use: pcieport 1b:03.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) Subsystem: Intel Corporation Device 0000 Kernel driver in use: pcieport 1b:04.0 PCI bridge: Intel Corporation Thunderbolt 4 Bridge [Goshen Ridge 2020] (rev 03) Subsystem: Intel Corporation Device 0000 Kernel driver in use: pcieport 7a:00.0 USB controller: ASMedia Technology Inc. ASM4242 USB 3.2 xHCI Controller (rev 01) Subsystem: ASMedia Technology Inc. ASM4242 USB 3.2 xHCI Controller Kernel driver in use: vfio-pci 7b:00.0 USB controller: ASMedia Technology Inc. ASM4242 USB 4 / Thunderbolt 3 Host Router (rev 01) Subsystem: ASMedia Technology Inc. ASM4242 USB 4 / Thunderbolt 3 Host Router Kernel driver in use: thunderbolt Kernel modules: thunderbolt 7c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Granite Ridge [Radeon Graphics] (rev c9) Subsystem: ASRock Incorporation Device 364e Kernel driver in use: vfio-pci Kernel modules: amdgpu 7c:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt Radeon High Definition Audio Controller Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt Radeon High Definition Audio Controller Kernel driver in use: vfio-pci 7c:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 19h PSP/CCP Subsystem: Advanced Micro Devices, Inc. [AMD] Family 19h PSP/CCP Kernel driver in use: ccp Kernel modules: ccp 7c:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge USB 3.1 xHCI Subsystem: ASRock Incorporation Device 15b6 Kernel driver in use: xhci_hcd 7c:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge USB 3.1 xHCI Subsystem: ASRock Incorporation Device 15b6 Kernel driver in use: xhci_hcd 7c:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h/1ah HD Audio Controller Subsystem: Advanced Micro Devices, Inc. [AMD] Device d601 7d:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge USB 2.0 xHCI Subsystem: ASRock Incorporation Device 15b6 Kernel driver in use: xhci_hcd root@blackbox:~# My system is working fine and stable though. I'm just wondering why this happens and if there is a way to "fix" this.Currently my best guess is that those two tabs somehow try to read device states but cannot access them due to the USB passthrough.Thank you very much!
August 24, 2025Aug 24 Community Expert did you edit unraid grub syslinux and reboot and checked again per post:
August 24, 2025Aug 24 Community Expert I would recommend binding and passing the IOMMU group that has the bolt port. as the kvm monitor device you have has connection and data states when off and when on.I would recommend editing the VM webui advance settings for IOMMUThis should add data to teh Main > Flash > syslinux grub.And I reccomend adding and running the grub options from the previous post. Didn't see you made another with similar issues.
August 24, 2025Aug 24 Author 6 hours ago, bmartino1 said:did you edit unraid grub syslinux and reboot and checked again per post:No I did not change syslinux yet
August 24, 2025Aug 24 Author 6 hours ago, bmartino1 said:I would recommend binding and passing the IOMMU group that has the bolt port. as the kvm monitor device you have has connection and data states when off and when on.Bolt and USB passthrough was my first attempt. I did not work reliably and I always had blackscreen issues. See here for more details.The power stat error messages I only get when I refresh the VMS tab in the Unraid GUI or ervery few seconds as long as I remain on the DASHBOARD tab. As soon as I navigate away e.g. to SETTINGS the errors immediately stop. This is why I think that in those two tabs, Unraid tries to read some stats and then sees some conflicts.It does not matter if the monitor is powered ON or OFF. As long as I have the DASHBOARD of the Unraid GUI open in a browser I get these messages:[1580441.237843] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580441.251374] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580443.238651] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580443.251005] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580444.522330] thunderbolt 0-1: device disconnected [1580445.237055] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580445.250417] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580447.239106] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580447.253058] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580449.239796] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580449.252973] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580451.241709] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580451.255736] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580453.243492] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580453.256542] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580455.242512] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580455.256439] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580457.259949] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580457.273274] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580459.259047] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible [1580459.273195] pcieport 0000:1b:04.0: Unable to change power state from D3cold to D0, device inaccessible [1580460.905226] thunderbolt 0-1: new device found, vendor=0xd4 device=0xc045 [1580460.905232] thunderbolt 0-1: DELL U2724DE [1580461.266454] pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessible Navigate away or close the Unraid WebUI and they stop.
August 26, 2025Aug 26 Community Expert Thank you for the clarity and information, this helps me better understand the issues at hand and whats going on.So, This tells me that the thunderbolt device in the off stat is being registered as a device requesting power and a edid display data and unraid full logging is capturing the power state of what it reads and sends to the kernel as it is inaccessible. The HID value changed and its not accepting inputs.pcieport 0000:1b:00.0: Unable to change power state from D3cold to D0, device inaccessiblewhen on it responds and tells Linux that xyz /dev/ path is accepting xyz and transporting a EDID for display when it's off the HID didn't change but the ability for it to accept and send and receive the otherwise functional packets has stopped.This is partly due to how KVMs work and what the kernel see what is being read can be read...(Similar to i plug a usb in and immediately unplug and plug it back in and unplug)Here more information on that:Thunderbolt docks/KVMs often cut power when the monitor is off → the PCIe root/downstream port (e.g. 0000:1b:00.0) runtime-suspends to D3cold power state...As this is a harmless but is a constant log spam due to Power and pcie ASMP and reports via AES you can ignore it by adding pci=noaer to the grub kernel params (disables PCIe AER messages) and that will suppress this harmless message.I personaly prefer to disable these poser states... due to VM and other hardware issues... and usb power state quirks... especialy when using them for a VM...To Prevent D3cold (preferred)"Disable PCIe port power management so the port never drops to D3in the Main > Flash > grub edit you should runpcie_port_pm=off pcie_aspm=offpcie_port_pm=off disables runtime PM(Power management) on PCIe ports (stops D3cold).pcie_aspm=off turns off link-level ASPM, further reducing power-down chances.* (Let the device handle it and not use software to report or control it...)OR Otherwise you would need to test it via terminal Per-device (no reboot, test first) -# See current statecat /sys/bus/pci/devices/0000:1b:00.0/power/control# Force always-onecho on > /sys/bus/pci/devices/0000:1b:00.0/power/controlAs that is essential what this udev rule does....you could add another udev rule affecting the port itself too...# /boot/config/udev/rules.d/90-pcie-port-always-on.rulesACTION=="add", SUBSYSTEM=="pci", KERNEL=="0000:1b:00.0", ATTR{power/control}="on"and let unraid control its dscold state (which may send a signal and turn on the monitor....)if you don't want to turn off aer or the power managment to the ports you can try tweaking the hotplug as its is a time syn issues of the kvm/screen being off and being reported as xyz device but unable to recvive and send as it is off. and need to be in that kind of state for when power returns to connect and be used...so a grub edit of:pciehp.pciehp_poll_mode=1*This disables PCI hotplug polling and can fix boot errors or hardware detection issues related to the PCI host bridge, like the "Notification initialization failed" or "Cannot get irq -1" errors.otherwise, you can disable ASPM in Bios or setup power controls with a user script at boot. Or a trigger to run when it detects the device is off in that state and runs something like:echo on > /sys/bus/pci/devices/0000:1b:00.0/power/controlto grant Linux the power control it needs/request when it goes into that power state.but essential what happened is the device is off and unraid was still sending something to it until the device didn't stop the tranmission(common KVM issue) and was forced into the power state of avbaible but not listening. then linux is reading it as (Similar to i plug a usb in and immediately unplug and plug it back in and unplug...) Edited August 26, 2025Aug 26 by bmartino1 data / spelling
August 26, 2025Aug 26 Community Expert Please post a unraid Diag file as I would liek to check some things form the libvirt log, the vm a config and other areas of the machines system login to better assist in a solution.if the goal is to pass this monitor and use the "igpu" in the VM Then I see n reason why the host shouldn't have this bound and accessible to the vm only no host access or control...
August 27, 2025Aug 27 Author @bmartino1 Thank you very much for your long answer and explanations. I'm not sure though if we have a misunderstanding. Just to clarify I do not need to power off the monitor. I do get the errors independent of the monitor's power state as long as I have the Dashboard tab of Unraid's Web UI open in a browser. Edited August 27, 2025Aug 27 by Tom082
August 27, 2025Aug 27 Community Expert Interesting bug then. My understanding is that this is happening when the monitor is off.in which i can only asume it has to do with console blank ...Settings > Console settings. as this has turned off hte screen but is requesing a diaplay but not getting it...its werid that it when your in the dashbaord. I would asume a plugin or other nginx isseus with ho the dispaly dashbaord is being requested.simalr to the nchan memory errors.again would need a diag file to look deeper into what may be happening.as thiws may be a triger form the impelmentaiton of the screen time out state and trying to use the monitor.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.