[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18
Our vendor told us that this is a generic problem with the following supermicro board/system and many nvme ssd devices: Board: H12SSW-NT Servertype: Supermicro AS -1114S-WTRT https://www.supermicro.com/Aplus/system/1U/1114/AS-1114S-WTRT.cfm so it seems this is not kernel related, afaik. -- 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/1998224 Title: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18 Status in linux package in Ubuntu: Confirmed Bug description: situation: ubuntu 18.04 server install on a supermicro x64 host. hot plug NVME ssd into NVME U.2 HotSwap Slot. problem: hot plug does not work/ nvme is not recognised. how to test: echo 1 > /sys/bus/pci/rescan dmesg output: [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io 0x1000-0x0fff] to [bus 41] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io 0x1000-0x0fff] to [bus 42] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] Kernel Version: 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux hardware information: tried with micron and intel NVME, e.g: INTEL SSDPE2KE016T8 after a reboot, the NVME is recognized, so there is no hardware problem. if you need additional debug information, feel free to ask. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998224/+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
[Kernel-packages] [Bug 1898909] Re: Installing hwe linux-tools does not provide /usr/bin wrappers
any update on this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1898909 Title: Installing hwe linux-tools does not provide /usr/bin wrappers Status in linux-hwe-5.4 package in Ubuntu: Invalid Status in linux-hwe-5.8 package in Ubuntu: Invalid Status in linux-hwe-5.4 source package in Bionic: In Progress Status in linux-hwe-5.8 source package in Bionic: Invalid Status in linux-hwe-5.4 source package in Focal: Invalid Status in linux-hwe-5.8 source package in Focal: Confirmed Bug description: I have a test script that requires /usr/bin/cpupower. Before calling it, I 'apt install linux-tools-$(uname -r)' to make sure it is available. For GA kernels, this works fine as there is a dependency chain on linux-tools-common which provides them. For HWE (tested on bionic), this does not work because linux-tools-5.4.0-48-generic doesn't depend on linux-tools-common. There is a linux-hwe-5.4-tools- common package, but it is empty, and also not a dependency of linux- tools-5.4.0-48-generic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1898909/+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
[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
> I am not sure I would still call it a regression and it is certainly an annoying, but it can be workarounded. it worked before, now it doesn't without manual intervention, that's the basic definition of a regression, no? after all, there are _always_ workarounds for regressions, so I would not consider it appropriate to call a regression not-a-regression because there is some workaround available. we are currently affected by this and need to figure out if the workaround is even an acceptable solution, because in a cloud environment you can't/don't want to manually patch libvirt xml for dozens of machines. -- 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/1887490 Title: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in qemu source package in Focal: Fix Released Bug description: [Impact] * CPU definitions are added to libvirt as these CPUs are known and added to qemu for execution. And due to that over time some are considered missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports three upstream fixes that just add definitions (no control flow changes) [Test Case] * Check if it has an EPYC-Rome entry in /usr/share/libvirt/cpu_map/index.xml and the file included there exists. * Define a guest like: EPYC-Rome You can only "really" start this on a system with the matching HW. But even on others it will change from: error: internal error: Unknown CPU model EPYC-Rome to being unable to start for some features missing. * libvirt probes a system if a named cpu can be used, after the fix this should include EPYC-Rome $ virsh domcapabilities | grep EPYC EPYC-IBPB EPYC [Regression Potential] * Usually these type additions are safe unless they add control flow changes (e.g. to handle yet unknown types of registers or such) but that isn't the case here. A regression if any is to be expected on systems that are close to the newly added type(s). Those will after the update be detected as such if e.g. host-model is used. If then running on a mixed cluster of updated/non-updated systems migrations will only work if the target is updated as well. [Other Info] * This is the first build since glibc 2.32 arrived in groovy, hence we need to be careful of the fix done for bug 1892826. It has to be checked if the linking is fine after the rebuild. The workload still works in groovy despite 2.32 being present (I'd ahve expected it doesn't), so we will keep the revert as-is for now. To be sure that adds two tests that shall be done: - check the linking to point to libtirpc instead of glibc $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL Was pointing to glibc, does it still and if so does it work (see below)? - run the autopkgtest cases as the LXC tests would trigger an issue if there is one ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor (with IBPB) Focal with fix also adds: x86 EPYC-Rome (alias configured by machine type) x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-v3 AMD EPYC Processor * Given such HW is available start a KVM guest using those new types Since we don't have libvirt support (yet) do so directly in qemu commandline like (bootloader is enough) $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm -nographic $ qemu-system-x86_64 -cpu EPYC-v3 -machine pc-q35-
[Kernel-packages] [Bug 1914774] Re: HWE kernels do not ship linux-tools packages
so, this is very weird. We used to install binary "cpupower" from linux-tools via this package for the hwe kernel: linux-tools-generic-hwe-18.04 but this seems to have changed somewhere in between, the file list on packages.ubuntu.com only lists: /usr/share/doc/linux-tools-generic-hwe-18.04/changelog.gz /usr/share/doc/linux-tools-generic-hwe-18.04/copyright see, e.g.: https://packages.ubuntu.com/bionic-updates/amd64/linux-tools-generic-hwe-18.04/filelist linked from: https://packages.ubuntu.com/bionic-updates/linux-tools-generic-hwe-18.04 I believe this is, because it's a meta/virtual package? nevertheless I found how to install "cpupower" it seems it moved to the following package (adjust kernel subversion as needed): https://packages.ubuntu.com/bionic-updates/linux-hwe-5.4-tools-5.4.0-80 but this is also strange for several reasons: first, afaik you need to install the version for your specific installed kernel, but the package name leads to bad sed-magic in install scripts like: apt install linux-hwe-5.4-tools-$(uname -r | sed 's#-generic$##') this is obviously bad, but I could live with that. what is really really weird though, is the installation path of the cpupower binary: root@server:~# /usr/lib/linux-hwe-5.4-tools-5.4.0-104/cpupower --help Usage: cpupower [-d|--debug] [-c|--cpu cpulist ] [] Supported commands are: frequency-info frequency-set idle-info idle-set set info monitor help Not all commands can make use of the -c cpulist option. Use 'cpupower help ' for getting help for above commands. root@server:~# type cpupower -su: type: cpupower: not found it is not installed in $PATH at all, which is really contracdicting the upstream makefile, imho? see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/power/cpupower/Makefile am I holding it wrong? is there another package which installs cpupower in the correct path? why was the packaging changed, mid release? This breaks every workflow around the provided tools. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1914774 Title: HWE kernels do not ship linux-tools packages Status in linux-meta-hwe-5.4 package in Ubuntu: Confirmed Bug description: While running kernel 5.4.0-64 today on bionic I noticed that Canonical kernel team does not provide a linux-hwe-5.4-tools package. Is that a deliberate choice? If so, would you please share the reason? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1914774/+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
[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18
** Attachment added: "Kernel Version" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998224/+attachment/5633193/+files/version.log -- 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/1998224 Title: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18 Status in linux package in Ubuntu: Incomplete Bug description: situation: ubuntu 18.04 server install on a supermicro x64 host. hot plug NVME ssd into NVME U.2 HotSwap Slot. problem: hot plug does not work/ nvme is not recognised. how to test: echo 1 > /sys/bus/pci/rescan dmesg output: [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io 0x1000-0x0fff] to [bus 41] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io 0x1000-0x0fff] to [bus 42] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] Kernel Version: 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux hardware information: tried with micron and intel NVME, e.g: INTEL SSDPE2KE016T8 after a reboot, the NVME is recognized, so there is no hardware problem. if you need additional debug information, feel free to ask. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998224/+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
[Kernel-packages] [Bug 1998224] [NEW] pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18
Public bug reported: situation: ubuntu 18.04 server install on a supermicro x64 host. hot plug NVME ssd into NVME U.2 HotSwap Slot. problem: hot plug does not work/ nvme is not recognised. how to test: echo 1 > /sys/bus/pci/rescan dmesg output: [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io 0x1000-0x0fff] to [bus 41] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io 0x1000-0x0fff] to [bus 42] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] Kernel Version: 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux hardware information: tried with micron and intel NVME, e.g: INTEL SSDPE2KE016T8 after a reboot, the NVME is recognized, so there is no hardware problem. if you need additional debug information, feel free to ask. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "lspci Output" https://bugs.launchpad.net/bugs/1998224/+attachment/5633192/+files/lspci-vnvn.log -- 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/1998224 Title: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18 Status in linux package in Ubuntu: Incomplete Bug description: situation: ubuntu 18.04 server install on a supermicro x64 host. hot plug NVME ssd into NVME U.2 HotSwap Slot. problem: hot plug does not work/ nvme is not recognised. how to test: echo 1 > /sys/bus/pci/rescan dmesg output: [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io 0x1000-0x0fff] to [bus 41] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io 0x1000-0x0fff] to [bus 42] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] Kernel Version: 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux hardware information: tried with micron and intel NVME, e.g: INTEL SSDPE2KE016T8 after a reboot, the NVME is recognized, so there is no hardware problem. if you need additional debug information, feel free to ask. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998224/+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
[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18
apport-collect is not installed on this system. I added some manually collected logs. If you need further debug data, please specify what exactly you need and I will try to provide it. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1998224 Title: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18 Status in linux package in Ubuntu: Confirmed Bug description: situation: ubuntu 18.04 server install on a supermicro x64 host. hot plug NVME ssd into NVME U.2 HotSwap Slot. problem: hot plug does not work/ nvme is not recognised. how to test: echo 1 > /sys/bus/pci/rescan dmesg output: [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io 0x1000-0x0fff] to [bus 41] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io 0x1000-0x0fff] to [bus 42] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] Kernel Version: 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux hardware information: tried with micron and intel NVME, e.g: INTEL SSDPE2KE016T8 after a reboot, the NVME is recognized, so there is no hardware problem. if you need additional debug information, feel free to ask. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998224/+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
[Kernel-packages] [Bug 1914774] Re: HWE kernels do not ship linux-tools packages
I'm sorry, but can you show me your $PATH? According to: https://packages.ubuntu.com/bionic-updates/amd64/linux- tools-5.4.0-132-generic/filelist cpupower get's installed into the following path: /usr/lib/linux-tools/5.4.0-132-generic/cpupower which seems to be a symlink, according to my system, to: ls -lashin /usr/lib/linux-tools/5.4.0-132-generic/cpupower 2546080 0 lrwxrwxrwx 1 0 0 44 Oct 24 15:52 /usr/lib/linux-tools/5.4.0-132-generic/cpupower -> ../../linux-hwe-5.4-tools-5.4.0-132/cpupower ls -lashin /usr/lib/linux-hwe-5.4-tools-5.4.0-132/cpupower 2546021 292K -rwxr-xr-x 1 0 0 290K Oct 24 15:52 /usr/lib/linux-hwe-5.4-tools-5.4.0-132/cpupower but if I'm not terribly mistaken /usr/lib/ is on no default $PATH, see this system: echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin or also these answers, neither contain /usr/lib/ in $PATH? https://askubuntu.com/questions/386629/what-are-the-default-path-values -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1914774 Title: HWE kernels do not ship linux-tools packages Status in linux-meta-hwe-5.4 package in Ubuntu: Confirmed Bug description: While running kernel 5.4.0-64 today on bionic I noticed that Canonical kernel team does not provide a linux-hwe-5.4-tools package. Is that a deliberate choice? If so, would you please share the reason? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1914774/+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
[Kernel-packages] [Bug 1914774] Re: HWE kernels do not ship linux-tools packages
also: cpupower --help bash: cpupower: command not found type cpupower -su: type: cpupower: not found command cpupower -su: cpupower: command not found /usr/lib/linux-hwe-5.4-tools-5.4.0-132/cpupower Usage: cpupower [-d|--debug] [-c|--cpu cpulist ] [] Supported commands are: frequency-info frequency-set idle-info idle-set set info monitor help Not all commands can make use of the -c cpulist option. Use 'cpupower help ' for getting help for above commands. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1914774 Title: HWE kernels do not ship linux-tools packages Status in linux-meta-hwe-5.4 package in Ubuntu: Confirmed Bug description: While running kernel 5.4.0-64 today on bionic I noticed that Canonical kernel team does not provide a linux-hwe-5.4-tools package. Is that a deliberate choice? If so, would you please share the reason? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1914774/+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
[Kernel-packages] [Bug 1914774] Re: HWE kernels do not ship linux-tools packages
** Changed in: linux-meta-hwe-5.4 (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1914774 Title: HWE kernels do not ship linux-tools packages Status in linux-meta-hwe-5.4 package in Ubuntu: Invalid Bug description: While running kernel 5.4.0-64 today on bionic I noticed that Canonical kernel team does not provide a linux-hwe-5.4-tools package. Is that a deliberate choice? If so, would you please share the reason? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1914774/+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
[Kernel-packages] [Bug 1914774] Re: HWE kernels do not ship linux-tools packages
so, we seem to have a dependency problem here, no? for reference, this is fixed by: apt install linux-tools-common but why was "linux-tools-common" not installed as a part of "linux- tools-generic-hwe-18.04"? this is the dependency chain: root@ceph-osd03:~# apt-cache depends linux-tools-generic-hwe-18.04 linux-tools-generic-hwe-18.04 Depends: linux-tools-5.4.0-132-generic root@ceph-osd03:~# apt-cache depends linux-tools-5.4.0-132-generic linux-tools-5.4.0-132-generic Depends: linux-hwe-5.4-tools-5.4.0-132 root@ceph-osd03:~# apt-cache depends linux-hwe-5.4-tools-5.4.0-132 linux-hwe-5.4-tools-5.4.0-132 Depends: libc6 Depends: libcap2 Depends: libdw1 Depends: libelf1 Depends: liblzma5 Depends: libnuma1 Depends: libpci3 Depends: libslang2 Depends: libssl1.1 Depends: libudev1 Depends: libunwind8 Depends: zlib1g Depends: linux-hwe-5.4-tools-common root@ceph-osd03:~# apt-cache depends linux-hwe-5.4-tools-common linux-hwe-5.4-tools-common Depends: lsb-release root@ceph-osd03:~# dpkg -S linux-hwe-5.4-tools-common linux-hwe-5.4-tools-common: /usr/share/doc/linux-hwe-5.4-tools-common linux-hwe-5.4-tools-common: /usr/share/doc/linux-hwe-5.4-tools-common/copyright linux-hwe-5.4-tools-common: /usr/share/doc/linux-hwe-5.4-tools-common/changelog.Debian.gz nothing installs /usr/bin/cpupower (that is, "linux-tools-common"). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1914774 Title: HWE kernels do not ship linux-tools packages Status in linux-meta-hwe-5.4 package in Ubuntu: Invalid Bug description: While running kernel 5.4.0-64 today on bionic I noticed that Canonical kernel team does not provide a linux-hwe-5.4-tools package. Is that a deliberate choice? If so, would you please share the reason? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1914774/+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
[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18
I wasn't able to test this just yet as I have limited time for debugging this and it is a production system, so I need to prepare maintenance etc. so it might take some time. Do you have any information if this is supposed to work on this kernel? I saw some patches afaik from 2017~2019 which addressed problems in this area, but I don't know yet if they made it to the ubuntu kernel. I will report back if a newer kernel fixes this. We are only using offical HWE Kernels from Ubuntu LTS releases at the moment though. -- 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/1998224 Title: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18 Status in linux package in Ubuntu: Confirmed Bug description: situation: ubuntu 18.04 server install on a supermicro x64 host. hot plug NVME ssd into NVME U.2 HotSwap Slot. problem: hot plug does not work/ nvme is not recognised. how to test: echo 1 > /sys/bus/pci/rescan dmesg output: [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io 0x1000-0x0fff] to [bus 41] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io 0x1000-0x0fff] to [bus 42] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] Kernel Version: 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux hardware information: tried with micron and intel NVME, e.g: INTEL SSDPE2KE016T8 after a reboot, the NVME is recognized, so there is no hardware problem. if you need additional debug information, feel free to ask. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998224/+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
[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18
my vendor told me this should work with updated bios and firmware, which it does not. in fact, I can't even find the pci hotplug kernel module, neither loaded, nor present under /lib/modules/*. so could you please reopen, so we can double check I'm not missing anything from the ubuntu side? currently I have upgraded to the official 18.04 HWE Kernel 5.4.0-135-generic #152 when I e.g. grep for hotplug on a fedora test laptop I get: grep -i hotplug /lib/modules/6.1.8-100.fc36.x86_64/modules.builtin kernel/drivers/pci/hotplug/shpchp.ko kernel/drivers/pci/hotplug/acpiphp.ko but the ubuntu system returns: root@ceph-osd01:~# grep -i hotplug /lib/modules/5.4.0-135-generic/modules.builtin root@ceph-osd01:~# ** Changed in: linux (Ubuntu) Status: Invalid => New -- 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/1998224 Title: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18 Status in linux package in Ubuntu: New Bug description: situation: ubuntu 18.04 server install on a supermicro x64 host. hot plug NVME ssd into NVME U.2 HotSwap Slot. problem: hot plug does not work/ nvme is not recognised. how to test: echo 1 > /sys/bus/pci/rescan dmesg output: [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io 0x1000-0x0fff] to [bus 41] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io 0x1000-0x0fff] to [bus 42] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] Kernel Version: 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux hardware information: tried with micron and intel NVME, e.g: INTEL SSDPE2KE016T8 after a reboot, the NVME is recognized, so there is no hardware problem. if you need additional debug information, feel free to ask. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998224/+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
[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18
as already stated above I did provide log files manually, as apport- collect is not installed on this system. I'm happy to provide further logfiles to debug this issue. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1998224 Title: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18 Status in linux package in Ubuntu: Confirmed Bug description: situation: ubuntu 18.04 server install on a supermicro x64 host. hot plug NVME ssd into NVME U.2 HotSwap Slot. problem: hot plug does not work/ nvme is not recognised. how to test: echo 1 > /sys/bus/pci/rescan dmesg output: [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io 0x1000-0x0fff] to [bus 41] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io 0x1000-0x0fff] to [bus 42] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] Kernel Version: 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux hardware information: tried with micron and intel NVME, e.g: INTEL SSDPE2KE016T8 after a reboot, the NVME is recognized, so there is no hardware problem. if you need additional debug information, feel free to ask. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998224/+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
[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18
okay, it seems that both acpi_pci_hotplug and pci_hotplug are enabled for this kernel: grep "CONFIG_HOTPLUG_PCI_ACPI=" /boot/config-`uname -r` CONFIG_HOTPLUG_PCI_ACPI=y grep "CONFIG_HOTPLUG_PCI=" /boot/config-`uname -r` CONFIG_HOTPLUG_PCI=y but still, hotplug is not working. the current situation is: I unplugged a correctly recognized Intel NVME and switched it for a Micron NVME, there is also a second intel nvme still installed. nvme list shows the intel nvme which remained in the system: nvme list Node SN Model Namespace Usage Format FW Rev - -- /dev/nvme0n1 PHLN130100QJ1P6AGN INTEL SSDPE2KE016T8 1 1.60 TB / 1.60 TB512 B + 0 B VDV10184 but when I look into /sys/, I still find shadows of the other intel nvme, which just got plugged out: find /sys/devices | egrep "nvme[0-9][0-9]?$" /sys/devices/pci:40/:40:01.1/:41:00.0/nvme/nvme0 /sys/devices/virtual/nvme-subsystem/nvme-subsys1/nvme1 /sys/devices/virtual/nvme-subsystem/nvme-subsys0/nvme0 also, nvme list-subsys, throws an error. I suppose because that old subsystem nvme-subsys1 does no longer exist, but is still referenced: nvme list-subsys free(): double free detected in tcache 2 Aborted googling the above error leads me to this bug report: https://github.com/linux-nvme/nvme-cli/issues/1707 when rescanning the pci bus via: echo 1 > /sys/bus/pci/rescan I get the following messages in dmesg: [Wed Feb 8 10:20:49 2023] pci :c3:00.0: PCI bridge to [bus c4] [Wed Feb 8 10:20:49 2023] pci :c3:00.0: bridge window [io 0xf000-0x] [Wed Feb 8 10:20:49 2023] pci :c3:00.0: bridge window [mem 0xb800-0xb90f] [Wed Feb 8 10:20:49 2023] pcieport :40:01.1: bridge window [io 0x1000-0x0fff] to [bus 41] add_size 1000 [Wed Feb 8 10:20:49 2023] pcieport :40:01.2: bridge window [io 0x1000-0x0fff] to [bus 42] add_size 1000 [Wed Feb 8 10:20:49 2023] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Wed Feb 8 10:20:49 2023] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] [Wed Feb 8 10:20:49 2023] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Wed Feb 8 10:20:49 2023] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Wed Feb 8 10:20:49 2023] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Wed Feb 8 10:20:49 2023] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Wed Feb 8 10:20:49 2023] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Wed Feb 8 10:20:49 2023] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] as already stated in the original bug report. how can I get rid of the now defunct nvme subsystem? anything else I could try? ** Bug watch added: github.com/linux-nvme/nvme-cli/issues #1707 https://github.com/linux-nvme/nvme-cli/issues/1707 ** Summary changed: - pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18 + pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.135.152~18 -- 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/1998224 Title: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.135.152~18 Status in linux package in Ubuntu: Confirmed Bug description: situation: ubuntu 18.04 server install on a supermicro x64 host. hot plug NVME ssd into NVME U.2 HotSwap Slot. problem: hot plug does not work/ nvme is not recognised. how to test: echo 1 > /sys/bus/pci/rescan dmesg output: [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io 0x1000-0x0fff] to [bus 41] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io 0x1000-0x0fff] to [bus 42] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] Kernel Version: 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux hardware information: tried with micron and intel NVME,
[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.135.152~18
I was finally able to test this with the mainline kernel: 6.1.10-060110-generic #202302060840 taken from: https://kernel.ubuntu.com/~kernel- ppa/mainline/v6.1.10/amd64/linux-image- unsigned-6.1.10-060110-generic_6.1.10-060110.202302060840_amd64.deb and it works! this is specific about hot swap. i suspect the following commits are missing from the HWE kernel in 18.04. to make this work: 2baa85d6927d11b8d946da2e4ad00dddca5b8da2 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2baa85d6927d11b8d946da2e4ad00dddca5b8da2) and 85ae3970a0e393cbb07ec30ac99d82cfd6c3f922 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=85ae3970a0e393cbb07ec30ac99d82cfd6c3f922) -- 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/1998224 Title: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.135.152~18 Status in linux package in Ubuntu: Confirmed Bug description: situation: ubuntu 18.04 server install on a supermicro x64 host. hot plug NVME ssd into NVME U.2 HotSwap Slot. problem: hot plug does not work/ nvme is not recognised. how to test: echo 1 > /sys/bus/pci/rescan dmesg output: [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io 0x1000-0x0fff] to [bus 41] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io 0x1000-0x0fff] to [bus 42] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] Kernel Version: 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux hardware information: tried with micron and intel NVME, e.g: INTEL SSDPE2KE016T8 after a reboot, the NVME is recognized, so there is no hardware problem. if you need additional debug information, feel free to ask. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998224/+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
[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.135.152~18
The above comment might not be correct, because it turned out one of the micron nvme devices had a defect and was not recognized by any hardware at all, even when not hot swapping. There is a chance that this is related to the bios/firmware combination on this supermicro model. I will test this again with a known working micron nvme and the following scenarios: - hotswap intel -> micron - hotswap micron -> micron both will first be tested on the linux-generic-hwe-18.04 5.4.0.135.152~18 kernel. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1998224 Title: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.135.152~18 Status in linux package in Ubuntu: Incomplete Bug description: situation: ubuntu 18.04 server install on a supermicro x64 host. hot plug NVME ssd into NVME U.2 HotSwap Slot. problem: hot plug does not work/ nvme is not recognised. how to test: echo 1 > /sys/bus/pci/rescan dmesg output: [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io 0x1000-0x0fff] to [bus 41] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io 0x1000-0x0fff] to [bus 42] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] Kernel Version: 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux hardware information: tried with micron and intel NVME, e.g: INTEL SSDPE2KE016T8 after a reboot, the NVME is recognized, so there is no hardware problem. if you need additional debug information, feel free to ask. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998224/+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
