Date: Fri, 22 May 2026 18:43:50 -0400 From: Mark Johnston <markj@freebsd.org> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: virtualization@freebsd.org Subject: Re: pci_passthru: unmap_pptdev_mmio failed: No such file or directory Message-ID: <ahDcJmJ1x5AmEz9D@nuc> In-Reply-To: <516r368n-8574-2rp9-ross-p2575qo62oq@mnoonqbm.arg> References: <s2q01p9s-9qr4-5s25-7p18-366s837611p5@mnoonqbm.arg> <516r368n-8574-2rp9-ross-p2575qo62oq@mnoonqbm.arg>
index | next in thread | previous in thread | raw e-mail
On Fri, May 22, 2026 at 10:02:12PM +0000, Bjoern A. Zeeb wrote: > On Fri, 22 May 2026, Bjoern A. Zeeb wrote: > > > Hi, > > > > after updating my current base system (unknown from what anymore) > > I was restarting one of my development bhyves which has two > > passthru (one wifi card and one full pci xhci). > > > > I am now getting: > > > > pci_passthru: unmap_pptdev_mmio failed: No such file or directory > > pci_passthru: unmap_pptdev_mmio failed: No such file or directory > > pci_passthru: unmap_pptdev_mmio failed: No such file or directory > > > > which is a fairly unhelpful message. Could at least tell the device > > if not more... > > > > Anyone any ideas where this is from (or how to fix it)? > > So this comes from ppt.c in the kernel ppt_find(). > > I am a bit buffled given: > > [1.001385] ppt0 mem 0xe1320000-0xe132ffff at device 20.0 on pci0 > [1.001386] ppt0: attached > [1.001445] ppt1 mem 0xe1000000-0xe10fffff,0xe1100000-0xe1107fff at device 0.0 on pci2 > [1.001446] ppt1: attached > > % pciconf -l | grep ppt > ppt0@pci0:0:20:0: class=0x0c0330 rev=0x21 hdr=0x00 vendor=0x8086 device=0x9d2f subvendor=0x17aa subdevice=0x5062 > ppt1@pci0:3:0:0: class=0x028000 rev=0x00 hdr=0x00 vendor=0x14c3 device=0x0616 subvendor=0x14c3 subdevice=0xe616 > > % sysctl hw.vmm.ppt > hw.vmm.ppt.devices: 2 > > > The config syas: > > pci.0.1.0.device=passthru > pci.0.1.0.bus=0 > pci.0.1.0.slot=20 > pci.0.1.0.func=0 > > pci.0.2.0.device=passthru > pci.0.2.0.bus=3 > pci.0.2.0.slot=0 > pci.0.2.0.func=0 > > pci.0.10.0.device=virtio-net > pci.0.10.0.backend=tap3 > > Funny enough not even the network interface is available to netboot upon start. > > I'll keep digging but if someone has a clue to save me some time that would be appreciated. As the immediate problem is fixed by commit b13335331092 but the problem is apparently still there: is this a regression? Can you at least approximate the revision you upgraded from?home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ahDcJmJ1x5AmEz9D>