Zhaoming Luo, le mar. 29 avril 2025 17:21:05 +0800, a ecrit: > On Tue, Apr 29, 2025 at 09:51:25AM +0200, Samuel Thibault wrote: > > > > What is more concerning is: > > > > piixide0:0:0: lost interrupt > > > > So the user-level interrupt mechanism should be checked. > > > > But overall it seems it only sees cd0, the CD drive, plugged on piixide, > > so not AHCI. Did you check that your AHCI controller is actually > > supported by rumpdisk (e.g. running lspci in Linux and check that the > > PCI vendor/product showing up there do show up in the rumpdisk code)? > > > Here is the output of lspci, not sure how to check the PCI in the > rumpdisk code. > > https://paste.debian.net/1372213/
To get vendor/product id, you can pass -n to lspci Or finding 82801GBM/GHM in pci.ids, which shows it's 8086:27c5 (also showing up in the rumpdisk log) It is there in ./buildrump.sh/src/sys/dev/pci/pcidevs.h:#define PCI_PRODUCT_INTEL_82801GBM_AHCI 0x27c5 /* 82801GBM AHCI SATA Controller */ ./buildrump.sh/src/sys/dev/pci/pcidevs:product INTEL 82801GBM_AHCI 0x27c5 82801GBM AHCI SATA Controller The rump boot talks a bit about it: ahcisata0 at pci0 dev 31 function 2 vendor 8086 product 27c5 (rev. 0x02) ahcisata0: AHCI revision 0g.0, 1 port, 1 slot, but then doesn't seem to be trying to probe devices from it You probably want to put prints in the ahci sata code to see why it's not probing there. Samuel
