This is all great and good, but I’m surprised that this patch was made only for 1164, I have similar devices, but on an asm1166 chip, and they have exactly the same problem. I think that this problem applies to the entire 116* line and requires a general patch in the kernel. Tell me, how can I report this so that I can check and make changes to the update?
Code:
01:00.0 SATA controller: ASMedia Technology Inc. ASM1166 Serial ATA Controller (rev 02) (prog-if 01 [AHCI 1.0])
Subsystem: ZyDAS Technology Corp. Device 2116
!!! Unknown header type 7f
Memory at 80b82000 (32-bit, non-prefetchable) [size=8K]
Memory at 80b80000 (32-bit, non-prefetchable) [size=8K]
Expansion ROM at 80b00000 [disabled] [size=512K]
Kernel driver in use: vfio-pci
Kernel modules: ahci
02:00.0 SATA controller: ASMedia Technology Inc. ASM1166 Serial ATA Controller (rev 02) (prog-if 01 [AHCI 1.0])
Subsystem: ZyDAS Technology Corp. Device 2116
!!! Unknown header type 7f
Memory at 80a82000 (32-bit, non-prefetchable) [size=8K]
Memory at 80a80000 (32-bit, non-prefetchable) [size=8K]
Expansion ROM at 80a00000 [disabled] [size=512K]
Kernel driver in use: vfio-pci
Kernel modules: ahci
Code:
-[0000:00]-+-00.0 Intel Corporation Device a72a
+-02.0 Intel Corporation Raptor Lake-S UHD Graphics
+-08.0 Intel Corporation GNA Scoring Accelerator module
+-0a.0 Intel Corporation Raptor Lake Crashlog and Telemetry
+-14.0 Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 Gb/s) XHCI Host Controller
+-14.2 Intel Corporation Raptor Lake-S PCH Shared SRAM
+-15.0 Intel Corporation Raptor Lake Serial IO I2C Host Controller #0
+-15.1 Intel Corporation Raptor Lake Serial IO I2C Host Controller #1
+-15.2 Intel Corporation Raptor Lake Serial IO I2C Host Controller #2
+-15.3 Intel Corporation Device 7a4f
+-16.0 Intel Corporation Raptor Lake CSME HECI #1
+-17.0 Intel Corporation Device 7a63
+-19.0 Intel Corporation Device 7a7c
+-19.1 Intel Corporation Device 7a7d
+-1a.0-[01]----00.0 ASMedia Technology Inc. ASM1166 Serial ATA Controller
+-1c.0-[02]----00.0 ASMedia Technology Inc. ASM1166 Serial ATA Controller
+-1c.6-[03]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller
+-1d.0-[04]----00.0 Shenzhen Techwinsemi Technology Co., Ltd. TWSC TE3420 series
+-1e.0 Intel Corporation Device 7a28
+-1e.3 Intel Corporation Device 7a2b
+-1f.0 Intel Corporation Device 7a0c
+-1f.4 Intel Corporation Raptor Lake-S PCH SMBus Controller
\-1f.5 Intel Corporation Raptor Lake SPI (flash) Controller
Code:
[ 637.979764] tap124i0: left allmulticast mode
[ 637.979780] vmbr0: port 2(tap124i0) entered disabled state
[ 639.025928] pcieport 0000:00:1a.0: Data Link Layer Link Active not set in 100 msec
[ 639.089975] vfio-pci 0000:01:00.0: resetting
[ 640.114800] pcieport 0000:00:1a.0: Data Link Layer Link Active not set in 100 msec
[ 640.117598] vfio-pci 0000:01:00.0: reset done
[ 640.120238] vfio-pci 0000:01:00.0: Unable to change power state from D0 to D3hot, device inaccessible
[ 681.663247] sd 41:0:0:0: [sdg] Stopping disk
[ 682.670715] vfio-pci 0000:02:00.0: resetting
[ 682.695282] vfio-pci 0000:02:00.0: reset done
[ 683.229014] tap124i0: entered promiscuous mode
[ 683.256715] vmbr0: port 2(tap124i0) entered blocking state
[ 683.256721] vmbr0: port 2(tap124i0) entered disabled state
[ 683.256735] tap124i0: entered allmulticast mode
[ 683.256832] vmbr0: port 2(tap124i0) entered blocking state
[ 683.256835] vmbr0: port 2(tap124i0) entered forwarding state
[ 683.963469] vfio-pci 0000:02:00.0: resetting
[ 683.987949] vfio-pci 0000:02:00.0: reset done
[ 684.023421] vfio-pci 0000:02:00.0: resetting
[ 685.047464] pcieport 0000:00:1c.0: broken device, retraining non-functional downstream link at 2.5GT/s
[ 686.047402] pcieport 0000:00:1c.0: retraining failed
[ 686.047458] pcieport 0000:00:1c.0: Data Link Layer Link Active not set in 100 msec
[ 686.111916] vfio-pci 0000:02:00.0: reset done
[ 686.111938] vfio-pci 0000:02:00.0: resetting
[ 687.138302] pcieport 0000:00:1c.0: Data Link Layer Link Active not set in 100 msec
[ 687.140027] vfio-pci 0000:02:00.0: reset done
[ 689.212311] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 689.239639] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 689.261429] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 689.277068] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 689.277568] vfio-pci 0000:02:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff
[ 689.277762] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 689.294186] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 689.294415] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 689.294491] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 689.295270] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 689.314185] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 689.335482] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 689.335907] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 689.365674] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 689.379039] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 689.862226] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 689.863155] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 689.864028] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 689.867786] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 689.868655] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 689.869557] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 704.516915] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 704.517031] vfio-pci 0000:02:00.0: vfio_bar_restore: reset recovery - restoring BARs
[ 935.843187] sdc: sdc1 sdc2 sdc3
[ 935.867056] sdd: sdd1 sdd2 sdd3
[ 1236.589531] sdc: sdc1 sdc2 sdc3
[ 1236.604253] sdd: sdd1 sdd2 sdd3
[ 1538.921800] sdc: sdc1 sdc2 sdc3
[ 1538.951991] sdd: sdd1 sdd2 sdd3
[ 1739.352740] zd560: p1 p2 p3
[ 1739.484348] tap124i0: left allmulticast mode
[ 1739.484364] vmbr0: port 2(tap124i0) entered disabled state
[ 1740.540365] pcieport 0000:00:1c.0: Data Link Layer Link Active not set in 100 msec
[ 1740.604098] vfio-pci 0000:02:00.0: resetting
[ 1741.630318] pcieport 0000:00:1c.0: Data Link Layer Link Active not set in 100 msec
[ 1741.633262] vfio-pci 0000:02:00.0: reset done
[ 1741.636165] vfio-pci 0000:02:00.0: Unable to change power state from D0 to D3hot, device inaccessible
[ 1754.795052] vfio-pci 0000:01:00.0: Unable to change power state from D3cold to D0, device inaccessible
[ 1754.798244] vfio-pci 0000:01:00.0: Unable to change power state from D3cold to D0, device inaccessible
[ 1754.809963] vfio-pci 0000:02:00.0: Unable to change power state from D3cold to D0, device inaccessible
[ 1754.813225] vfio-pci 0000:02:00.0: Unable to change power state from D3cold to D0, device inaccessible
The problem is still the same, the proxmox OS starts, both ASM 116rabhf cards open and display the connected disks, but when adding them to a virtual machine with standard settings, the virtual machine starts, but the disks and controllers are no longer in the guest OS =) the errors provided above are in the message log. After stopping, restarting the guest OS will no longer start with the error:
error writing '1' to '/sys/bus/pci/devices/0000:02:00.0/reset': Inappropriate ioctl for device
failed to reset PCI device '0000:02:00.0', but trying to continue as not all devices need a reset
kvm: ../hw/pci/pci.c:1815: pci_irq_handler: Assertion `0 <= irq_num && irq_num < PCI_NUM_PINS' failed.
TASK ERROR: start failed: QEMU exited with code 1
Well, actually, the disks are not displayed on the host, only rebooting the Proxmox host helps
I tried adding this for the kernel in Proxmox, and it worked for onboard asm1166 controller (had "unknown header type 7f, ignoring device" on WTR MAX Intel version).
The only difference is the model:
Yes, I supplemented the message with additional information. It worked.
I'm asking patchrick84 personally about contacts or how to add this fix to the kernel.
Because I'm not experienced in such matters, I "tortured" Gemini for a long time in order to get a result.
I am really fscinated by all this AI craze. You do not need to ask patchrick84, or the AI for that matter. The required information is all in this thread. Reading and understanding is all that is required. The official Linux maintainer for the PCI subsystem is even mentioned by name in here.
I am really fscinated by all this AI craze. You do not need to ask patchrick84, or the AI for that matter. The required information is all in this thread. Reading and understanding is all that is required. The official Linux maintainer for the PCI subsystem is even mentioned by name in here.
I used gemini to compile the kernel on the linux subsystem on win11 (so as not to compile it for hours on the proxmox host) and send it for installation on my proxmox host. Maybe the solution was somewhere here (how to do it), but it seems to me that Ai saved me time.
