There are failed messages showing "BAR 13: failed to assign [io size 0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

[Jeff Lane ]

1. Power on SUT and boot into UEFI setup.
2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC NVMe RAID disk.
4. Boot into OS then check system logs to check if there are any unexpected failed or error messages. (=> failed, there are failed messages in dmesg, /var/log/syslog, and /var/log/kern.log, showing:
pci 10001:80:02.0: BAR 13: failed to assign [io size 0x1000]
pci 10001:80:03.0: BAR 13: failed to assign [io size 0x1000]
pci 10001:80:04.0: BAR 13: failed to assign [io size 0x1000]
pci 10001:80:05.0: BAR 13: failed to assign [io size 0x1000]
where
10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04)
10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04)
10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04)
10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04)
)

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1986907

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu Jammy) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]