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

[conie chang]

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)
)
---
ProblemType: Bug
AlsaDevices:
 total 0
 crw-rw----+ 1 root audio 116, 1 Aug 18 14:57 seq
 crw-rw----+ 1 root audio 116, 33 Aug 18 14:57 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-08-18 (0 days ago)
InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220816)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
 Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
 Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Lenovo ThinkEdge SE450
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-46-generic N/A
 linux-backports-modules-5.15.0-46-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags: jammy uec-images
Uname: Linux 5.15.0-46-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 08/08/2022
dmi.bios.release: 1.23
dmi.bios.vendor: Lenovo
dmi.bios.version: CME105F-1.23
dmi.board.asset.tag: none
dmi.board.name: 7D8TCTO1WW
dmi.board.vendor: Lenovo
dmi.board.version: 05
dmi.chassis.asset.tag: none
dmi.chassis.type: 23
dmi.chassis.vendor: Lenovo
dmi.chassis.version: none
dmi.ec.firmware.release: 1.40
dmi.modalias: dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
dmi.product.family: ThinkSystem
dmi.product.name: ThinkEdge SE450
dmi.product.sku: 7D8TCTO1WW
dmi.product.version: 05
dmi.sys.vendor: Lenovo

[conie chang (conie)]

If the vmd feature is enabled, the messsage will be showed in syslog.

[conie chang (conie)]

if intel vmd feature is disabled, it has "BAR 13: failed to assign" message in the syslog.

[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 1986792

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.

[Jeff Lane  (bladernr)]

Hi Conie,

can you please run `apport-collect 1986792` as requested in comment #3 for this bug?

Thanks
Jeff

[conie chang (conie)]

apport information

[conie chang (conie)]

apport information

[conie chang (conie)]

apport information

[conie chang (conie)]

apport information

[conie chang (conie)]

apport information

[conie chang (conie)]

apport information

[conie chang (conie)]

apport information

[conie chang (conie)]

apport information

[conie chang (conie)]

apport information

[conie chang (conie)]

apport information

[conie chang (conie)]

apport information

[conie chang (conie)]

apport information

[conie chang (conie)]

yes! I update the logs. Please review it.

[xiaochun Lee (xavier-lee)]

I had tried to submit a patch to kernel community, and maintainer recommend we'd better cover all platforms other than VMD. The latest discussion listed as below.
https://lore.kernel.org/all/20221116174205.GA1122329@bhelgaas/#t

On the other hand, I had opened a case to Intel, the case was closed now because they said it is an known issue and actually it has not any function impact. Here is the link for your reference.
https://premiersupport.intel.com/IPS/s/case-detail?recordId=5003b00001hkcGf