RPi5 context: How to report to EDK2 developer why FreeBSD gets 'nvme0: unable to allocate MSI-X' (and for MSI too)

Go to: [ bottom of page ] [ top of archives ] [ this month ]

From: Mark Millard <marklmi_at_yahoo.com>
Date: Fri, 20 Jun 2025 15:16:04 UTC

My EDK2 ACPI based RPi5 experiments got:

nvme0: System interrupt issues?

which lead to discovering both:

nvme0: unable to allocate MSI-X
nvme0: unable to allocate MSI

and:

pcib0: slot 0 INTA hardwired to IRQ 251
pcib1: slot 0 INTA is routed to irq 13


More boot verbose detail:

pcib1: <PCI-PCI bridge> at device 0.0 on pci0
pcib1:   domain            1
pcib1:   secondary bus     1
pcib1:   subordinate bus   1
pcib1:   memory decode     0xc0000000-0xc00fffff
pci1: <PCI bus> on pcib1
pcib1: allocated bus range (1-1) for rid 0 of pci1
pci1: domain=1, physical bus=1
found->	vendor=0x10ec, dev=0x5765, revid=0x01
	domain=1, bus=1, slot=0, func=0
	class=01-08-02, hdrtype=0x00, mfdev=0
	cmdreg=0x0006, statreg=0x0010, cachelnsz=0 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=a, irq=255
	powerspec 3  supports D0 D3  current D0
	MSI supports 8 messages, 64 bit
	MSI-X supports 9 messages in map 0x10
	map[10]: type Memory, range 64, base 0xc0000000, size 14, enabled
pcib1: allocated memory range (0xc0000000-0xc0003fff) for rid 10 of pci1:1:0:0
	map[24]: type Memory, range 32, base 0xc0004000, size 13, enabled
pcib1: allocated memory range (0xc0004000-0xc0005fff) for rid 24 of pci1:1:0:0
nvme0: <Generic NVMe Device> mem 0xc0000000-0xc0003fff,0xc0004000-0xc0005fff at device 0.0 on pci1
nvme0: attempting to allocate 5 MSI-X vectors (9 supported)
nvme0: unable to allocate MSI-X
nvme0: attempting to allocate 2 MSI vectors (8 supported)
nvme0: unable to allocate MSI
pcib0: matched entry for 0.0.INTA
pcib0: slot 0 INTA hardwired to IRQ 251
pcib1: slot 0 INTA is routed to irq 13
nvme0: CapLo: 0x280103ff: MQES 1023, CQR, TO 40
nvme0: CapHi: 0x00000020: DSTRD 0, CSS pcib0: slot 0 INTA hardwired to IRQ 251
pcib1: slot 0 INTA is routed to irq 13, CPS 0, MPSMIN 0, MPSMAX 0
nvme0: Version: 0x00010400: 1.4


Not being familiar with the area, I'm wondering
how to collect the information to report to the
EDK2 developer for why the 'unable to allocate
MSI-X' and 'unable to allocate MSI' happened
(from the FreeBSD's kernel point of view).


===
Mark Millard
marklmi at yahoo.com