>From WuFan: HI Manoj,
Sorry for the delay. I haven't got chance to test your patch but I do find a (much) simple way to verify it. In a working system you have: /home/ubuntu>ls /sys/bus/pci/devices/0002\:01\:00.0/resource* /sys/bus/pci/devices/0002:01:00.0/resource /sys/bus/pci/devices/0002:01:00.0/resource0 /sys/bus/pci/devices/0002:01:00.0/resource1 /sys/bus/pci/devices/0002:01:00.0/resource2 While a failing system has this: ubuntu@controller:~$ ls /sys/bus/pci/devices/0002\:01\:00.0/resource* /sys/bus/pci/devices/0002:01:00.0/resource Here the PCI device could be any PCIe NIC. Thanks, Fan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1712580 Title: [SRU][Zesty]PCI: Add pci_mmap_resource_range() and use it for ARM64 Status in linux package in Ubuntu: Incomplete Bug description: [Impact] uio device binding inside VM would fail with errors EAL: Detected 3 lcore(s) EAL: Probing VFIO support... EAL: PCI device 0000:00:01.0 on NUMA socket -1 EAL: probe driver: 1af4:1000 net_virtio EAL: Cannot open /sys/bus/pci/devices/0000:00:01.0/resource1: No such file or directory EAL: Cannot open /sys/bus/pci/devices/0000:00:01.0/resource0: No such file or directory EAL: Error - exiting with code: 1 Cause: Requested device 0000:00:01.0 cannot be used [Fix] Fixed in linus kernel by patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm64/include/asm/pci.h?h=v4.13-rc4&id=f719582435afe9c7985206e42d804ea6aa315d33 [Test] [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
