Activity log for bug #1969434

Date Who What changed Old value New value Message
2022-04-19 08:32:57 You-Sheng Yang bug added bug
2022-04-19 15:26:22 You-Sheng Yang summary dkms.conf doesn't respect --kernelsourcedir passed to dkms build build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
2022-04-19 15:26:49 You-Sheng Yang description Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has: MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver" [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has:   MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver"
2022-04-19 15:27:02 You-Sheng Yang bug task added linux (Ubuntu)
2022-04-19 15:27:17 You-Sheng Yang bug task added linux-oem-5.17 (Ubuntu)
2022-04-19 15:27:31 You-Sheng Yang bug task added linux-oem-5.14 (Ubuntu)
2022-04-19 15:27:40 You-Sheng Yang nominated for series Ubuntu Jammy
2022-04-19 15:27:40 You-Sheng Yang bug task added linux (Ubuntu Jammy)
2022-04-19 15:27:40 You-Sheng Yang bug task added backport-iwlwifi-dkms (Ubuntu Jammy)
2022-04-19 15:27:40 You-Sheng Yang bug task added linux-oem-5.14 (Ubuntu Jammy)
2022-04-19 15:27:40 You-Sheng Yang bug task added linux-oem-5.17 (Ubuntu Jammy)
2022-04-19 15:27:40 You-Sheng Yang nominated for series Ubuntu Focal
2022-04-19 15:27:40 You-Sheng Yang bug task added linux (Ubuntu Focal)
2022-04-19 15:27:40 You-Sheng Yang bug task added backport-iwlwifi-dkms (Ubuntu Focal)
2022-04-19 15:27:40 You-Sheng Yang bug task added linux-oem-5.14 (Ubuntu Focal)
2022-04-19 15:27:40 You-Sheng Yang bug task added linux-oem-5.17 (Ubuntu Focal)
2022-04-19 15:27:56 You-Sheng Yang linux (Ubuntu Focal): status New Invalid
2022-04-19 15:28:07 You-Sheng Yang linux-oem-5.14 (Ubuntu Jammy): status New Invalid
2022-04-19 15:28:23 You-Sheng Yang linux-oem-5.17 (Ubuntu Focal): status New Invalid
2022-04-19 15:30:05 Ubuntu Kernel Bot linux (Ubuntu): status New Incomplete
2022-04-19 16:08:11 You-Sheng Yang attachment added backport-iwlwifi-dkms_9858-0ubuntu3.debdiff https://bugs.launchpad.net/ubuntu/focal/+source/linux-oem-5.17/+bug/1969434/+attachment/5581484/+files/backport-iwlwifi-dkms_9858-0ubuntu3.debdiff
2022-04-19 16:12:18 You-Sheng Yang merge proposal linked https://code.launchpad.net/~vicamo/ubuntu/+source/backport-iwlwifi-dkms/+git/backport-iwlwifi-dkms/+merge/419698
2022-04-19 16:20:36 Ubuntu Foundations Team Bug Bot tags patch
2022-04-19 16:20:43 Ubuntu Foundations Team Bug Bot bug added subscriber Ubuntu Sponsors Team
2022-04-19 17:25:11 You-Sheng Yang description [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has:   MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver" [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed. However, while we need secureboot to be enabled on these platforms, backport-iwlwifi-dkms must also be signed somehow. There are two possible method to achieve this, too. One, to prebuild this dkms as zfs and v4l2loopback does. However, while backport-iwlwifi-dkms generates kernel modules with exactly the same name as the in-tree ones, when prebuilt, they'll be available directly from the linux-modules package and therefore overrides the in-tree ones always, turning the in-tree driver completely useless and risk the stability of all other generic installations. The second one is to build backport-iwlwifi-dkms as nvidia graphic drivers in the linux-restricted-modules source package. In this way, affected platforms may install the corresponding packages when needed without interfering others. However, l-r-m is for restricted modules that needs special care of redistribution of its binaries, and backport-iwlwifi-dkms is GPL licensed. Here a similar but simpler process in the main kernel tree is re-implemented. Two additional packages, linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package linux-modules-MODULE-FLAVOUR will be created. [Test Case] Test builds: ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb [Where problems could occur] The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails to build under this proposed process. Debdiff attached to the same bug. Different from nvidia packages built from l-r-m, the generated package names do not carry an additional short version string, e.g. nvidia-410, as there is no such necessity to build multiple versions of iwlwifi. The modules are installed to /lib/modules/<kver>/kernel/iwlwifi, not iwlwifi-9858/. ========== original bug report ========== [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has:   MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver"
2022-04-20 07:16:11 Stefan Bader linux (Ubuntu Jammy): importance Undecided Medium
2022-04-20 07:16:11 Stefan Bader linux (Ubuntu Jammy): status Incomplete In Progress
2022-04-20 11:08:32 Dimitri John Ledkov description [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed. However, while we need secureboot to be enabled on these platforms, backport-iwlwifi-dkms must also be signed somehow. There are two possible method to achieve this, too. One, to prebuild this dkms as zfs and v4l2loopback does. However, while backport-iwlwifi-dkms generates kernel modules with exactly the same name as the in-tree ones, when prebuilt, they'll be available directly from the linux-modules package and therefore overrides the in-tree ones always, turning the in-tree driver completely useless and risk the stability of all other generic installations. The second one is to build backport-iwlwifi-dkms as nvidia graphic drivers in the linux-restricted-modules source package. In this way, affected platforms may install the corresponding packages when needed without interfering others. However, l-r-m is for restricted modules that needs special care of redistribution of its binaries, and backport-iwlwifi-dkms is GPL licensed. Here a similar but simpler process in the main kernel tree is re-implemented. Two additional packages, linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package linux-modules-MODULE-FLAVOUR will be created. [Test Case] Test builds: ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb [Where problems could occur] The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails to build under this proposed process. Debdiff attached to the same bug. Different from nvidia packages built from l-r-m, the generated package names do not carry an additional short version string, e.g. nvidia-410, as there is no such necessity to build multiple versions of iwlwifi. The modules are installed to /lib/modules/<kver>/kernel/iwlwifi, not iwlwifi-9858/. ========== original bug report ========== [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has:   MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver" [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed. However, while we need secureboot to be enabled on these platforms, backport-iwlwifi-dkms must also be signed somehow. There are two possible method to achieve this, too. One, to prebuild this dkms as zfs and v4l2loopback does. However, while backport-iwlwifi-dkms generates kernel modules with exactly the same name as the in-tree ones, when prebuilt, they'll be available directly from the linux-modules package and therefore overrides the in-tree ones always, turning the in-tree driver completely useless and risk the stability of all other generic installations. The second one is to build backport-iwlwifi-dkms as nvidia graphic drivers in the linux-restricted-modules source package. In this way, affected platforms may install the corresponding packages when needed without interfering others. However, l-r-m is for restricted modules that needs special care of redistribution of its binaries, and backport-iwlwifi-dkms is GPL licensed. Here a similar but simpler process in the main kernel tree is re-implemented. Two additional packages, linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package linux-modules-MODULE-FLAVOUR will be created. [Test Case] Test builds: ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb [Where problems could occur] The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails to build under this proposed process. Debdiff attached to the same bug. Different from nvidia packages built from l-r-m, the generated package names do not carry an additional short version string, e.g. nvidia-410, as there is no such necessity to build multiple versions of iwlwifi. The modules are installed to /lib/modules/<kver>/kernel/iwlwifi, not iwlwifi-9858/. ========== backport-iwlwifi-dkms SRU ========== Fix FTBFS with non-standard build directory layout, as executed by dkms build with a sourcedir setting, as will be done by the above kernel built-in dkms packages. [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has:   MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver"
2022-04-20 11:12:13 Dimitri John Ledkov description [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed. However, while we need secureboot to be enabled on these platforms, backport-iwlwifi-dkms must also be signed somehow. There are two possible method to achieve this, too. One, to prebuild this dkms as zfs and v4l2loopback does. However, while backport-iwlwifi-dkms generates kernel modules with exactly the same name as the in-tree ones, when prebuilt, they'll be available directly from the linux-modules package and therefore overrides the in-tree ones always, turning the in-tree driver completely useless and risk the stability of all other generic installations. The second one is to build backport-iwlwifi-dkms as nvidia graphic drivers in the linux-restricted-modules source package. In this way, affected platforms may install the corresponding packages when needed without interfering others. However, l-r-m is for restricted modules that needs special care of redistribution of its binaries, and backport-iwlwifi-dkms is GPL licensed. Here a similar but simpler process in the main kernel tree is re-implemented. Two additional packages, linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package linux-modules-MODULE-FLAVOUR will be created. [Test Case] Test builds: ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb [Where problems could occur] The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails to build under this proposed process. Debdiff attached to the same bug. Different from nvidia packages built from l-r-m, the generated package names do not carry an additional short version string, e.g. nvidia-410, as there is no such necessity to build multiple versions of iwlwifi. The modules are installed to /lib/modules/<kver>/kernel/iwlwifi, not iwlwifi-9858/. ========== backport-iwlwifi-dkms SRU ========== Fix FTBFS with non-standard build directory layout, as executed by dkms build with a sourcedir setting, as will be done by the above kernel built-in dkms packages. [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has:   MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver" [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed. However, while we need secureboot to be enabled on these platforms, backport-iwlwifi-dkms must also be signed somehow. There are two possible method to achieve this, too. One, to prebuild this dkms as zfs and v4l2loopback does. However, while backport-iwlwifi-dkms generates kernel modules with exactly the same name as the in-tree ones, when prebuilt, they'll be available directly from the linux-modules package and therefore overrides the in-tree ones always, turning the in-tree driver completely useless and risk the stability of all other generic installations. The second one is to build backport-iwlwifi-dkms as nvidia graphic drivers in the linux-restricted-modules source package. In this way, affected platforms may install the corresponding packages when needed without interfering others. However, l-r-m is for restricted modules that needs special care of redistribution of its binaries, and backport-iwlwifi-dkms is GPL licensed. Here a similar but simpler process in the main kernel tree is re-implemented. Two additional packages, linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package linux-modules-MODULE-FLAVOUR will be created. [Test Case] Test builds: ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb [Where problems could occur] The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails to build under this proposed process. Debdiff attached to the same bug. Different from nvidia packages built from l-r-m, the generated package names do not carry an additional short version string, e.g. nvidia-410, as there is no such necessity to build multiple versions of iwlwifi. The modules are installed to /lib/modules/<kver>/kernel/iwlwifi, not iwlwifi-9858/. ========== backport-iwlwifi-dkms SRU ========== In order to be compiled with dkms-build in kernel source package, the kernel header dir will not be /lib/modules/<version>/build but a temporary directory. This change specifies KLIB_BUILD from dkms variable ${kernel_source_dir}. [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has:   MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver"
2022-04-20 11:12:20 Dimitri John Ledkov backport-iwlwifi-dkms (Ubuntu Jammy): status New Fix Committed
2022-04-20 16:24:55 Launchpad Janitor backport-iwlwifi-dkms (Ubuntu Jammy): status Fix Committed Fix Released
2022-05-05 21:55:36 You-Sheng Yang linux-oem-5.14 (Ubuntu Focal): importance Undecided High
2022-05-05 21:55:36 You-Sheng Yang linux-oem-5.14 (Ubuntu Focal): status New In Progress
2022-05-05 21:55:36 You-Sheng Yang linux-oem-5.14 (Ubuntu Focal): assignee You-Sheng Yang (vicamo)
2022-05-05 21:56:22 You-Sheng Yang linux-oem-5.17 (Ubuntu): status New Invalid
2022-05-05 21:56:40 You-Sheng Yang linux-oem-5.17 (Ubuntu Jammy): importance Undecided High
2022-05-05 21:56:40 You-Sheng Yang linux-oem-5.17 (Ubuntu Jammy): status New In Progress
2022-05-05 21:56:40 You-Sheng Yang linux-oem-5.17 (Ubuntu Jammy): assignee You-Sheng Yang (vicamo)
2022-05-05 21:57:32 You-Sheng Yang bug task added linux-meta (Ubuntu)
2022-05-05 22:00:03 You-Sheng Yang bug task added linux-meta-oem (Ubuntu)
2022-05-05 22:00:53 You-Sheng Yang linux-meta (Ubuntu): importance Undecided High
2022-05-05 22:00:53 You-Sheng Yang linux-meta (Ubuntu): status New In Progress
2022-05-05 22:00:53 You-Sheng Yang linux-meta (Ubuntu): assignee You-Sheng Yang (vicamo)
2022-05-05 22:01:05 You-Sheng Yang linux-meta (Ubuntu Focal): status New Invalid
2022-05-05 22:01:26 You-Sheng Yang linux-meta (Ubuntu Jammy): importance Undecided High
2022-05-05 22:01:26 You-Sheng Yang linux-meta (Ubuntu Jammy): status New In Progress
2022-05-05 22:01:26 You-Sheng Yang linux-meta (Ubuntu Jammy): assignee You-Sheng Yang (vicamo)
2022-05-05 22:01:59 You-Sheng Yang linux-meta-oem (Ubuntu): status New Invalid
2022-05-05 22:02:23 You-Sheng Yang linux-meta-oem (Ubuntu Focal): importance Undecided High
2022-05-05 22:02:23 You-Sheng Yang linux-meta-oem (Ubuntu Focal): status New In Progress
2022-05-05 22:02:23 You-Sheng Yang linux-meta-oem (Ubuntu Focal): assignee You-Sheng Yang (vicamo)
2022-05-05 22:02:47 You-Sheng Yang linux-meta-oem (Ubuntu Jammy): importance Undecided High
2022-05-05 22:02:47 You-Sheng Yang linux-meta-oem (Ubuntu Jammy): status New In Progress
2022-05-05 22:02:47 You-Sheng Yang linux-meta-oem (Ubuntu Jammy): assignee You-Sheng Yang (vicamo)
2022-05-05 22:03:26 You-Sheng Yang linux (Ubuntu): importance Medium High
2022-05-05 22:03:26 You-Sheng Yang linux (Ubuntu): assignee You-Sheng Yang (vicamo)
2022-05-05 22:03:44 You-Sheng Yang linux (Ubuntu Jammy): importance Medium High
2022-05-05 22:03:44 You-Sheng Yang linux (Ubuntu Jammy): assignee You-Sheng Yang (vicamo)
2022-05-13 14:19:39 Timo Aaltonen linux-oem-5.14 (Ubuntu Focal): status In Progress Fix Committed
2022-05-16 14:12:48 Ubuntu Kernel Bot tags patch patch verification-needed-focal
2022-05-18 05:55:30 Kai-Chuan Hsieh attachment added iwlwifi-rt-ucode-timeout.log https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1969434/+attachment/5590613/+files/iwlwifi-rt-ucode-timeout.log
2022-05-18 05:56:07 Kai-Chuan Hsieh tags patch verification-needed-focal patch verification-done-focal
2022-05-18 09:06:37 Kai-Chuan Hsieh tags patch verification-done-focal patch verification-needed-focal
2022-05-19 01:23:40 Kai-Chuan Hsieh attachment added kern.log https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1969434/+attachment/5591044/+files/kern.log
2022-05-19 01:26:01 Kai-Chuan Hsieh tags patch verification-needed-focal patch verification-done-focal
2022-05-20 09:49:56 Ubuntu Kernel Bot tags patch verification-done-focal patch verification-done-focal verification-needed-jammy
2022-05-23 13:48:35 Launchpad Janitor linux-oem-5.14 (Ubuntu Focal): status Fix Committed Fix Released
2022-05-23 13:48:35 Launchpad Janitor cve linked 2022-29581
2022-05-26 16:24:31 Kleber Sacilotto de Souza linux-meta (Ubuntu Jammy): status In Progress Fix Committed
2022-05-26 16:26:22 Kleber Sacilotto de Souza linux (Ubuntu Jammy): status In Progress Fix Committed
2022-06-07 07:34:14 You-Sheng Yang tags patch verification-done-focal verification-needed-jammy patch verification-done-focal verification-done-jammy
2022-06-07 07:47:42 Timo Aaltonen linux-oem-5.17 (Ubuntu Jammy): status In Progress Fix Committed
2022-06-07 19:12:17 Launchpad Janitor linux-oem-5.17 (Ubuntu Jammy): status Fix Committed Fix Released
2022-06-07 19:12:17 Launchpad Janitor cve linked 2022-1966
2022-06-07 19:12:17 Launchpad Janitor cve linked 2022-1972
2022-06-22 15:04:51 Launchpad Janitor linux (Ubuntu Jammy): status Fix Committed Fix Released
2022-06-22 15:05:02 Launchpad Janitor linux-meta (Ubuntu Jammy): status Fix Committed Fix Released
2022-09-02 17:48:08 Launchpad Janitor linux-meta (Ubuntu): status In Progress Fix Released
2022-09-02 17:48:00 Launchpad Janitor linux (Ubuntu): status In Progress Fix Released
2022-09-28 12:24:29 Kleber Sacilotto de Souza bug task added linux-meta-hwe-5.15 (Ubuntu)
2022-09-28 12:24:40 Kleber Sacilotto de Souza linux-meta-hwe-5.15 (Ubuntu): status New Invalid
2022-09-28 12:24:53 Kleber Sacilotto de Souza linux-meta-hwe-5.15 (Ubuntu Focal): status New In Progress
2022-09-28 12:25:02 Kleber Sacilotto de Souza linux-meta-hwe-5.15 (Ubuntu Jammy): status New Invalid
2022-10-11 08:15:58 You-Sheng Yang description [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed. However, while we need secureboot to be enabled on these platforms, backport-iwlwifi-dkms must also be signed somehow. There are two possible method to achieve this, too. One, to prebuild this dkms as zfs and v4l2loopback does. However, while backport-iwlwifi-dkms generates kernel modules with exactly the same name as the in-tree ones, when prebuilt, they'll be available directly from the linux-modules package and therefore overrides the in-tree ones always, turning the in-tree driver completely useless and risk the stability of all other generic installations. The second one is to build backport-iwlwifi-dkms as nvidia graphic drivers in the linux-restricted-modules source package. In this way, affected platforms may install the corresponding packages when needed without interfering others. However, l-r-m is for restricted modules that needs special care of redistribution of its binaries, and backport-iwlwifi-dkms is GPL licensed. Here a similar but simpler process in the main kernel tree is re-implemented. Two additional packages, linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package linux-modules-MODULE-FLAVOUR will be created. [Test Case] Test builds: ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb [Where problems could occur] The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails to build under this proposed process. Debdiff attached to the same bug. Different from nvidia packages built from l-r-m, the generated package names do not carry an additional short version string, e.g. nvidia-410, as there is no such necessity to build multiple versions of iwlwifi. The modules are installed to /lib/modules/<kver>/kernel/iwlwifi, not iwlwifi-9858/. ========== backport-iwlwifi-dkms SRU ========== In order to be compiled with dkms-build in kernel source package, the kernel header dir will not be /lib/modules/<version>/build but a temporary directory. This change specifies KLIB_BUILD from dkms variable ${kernel_source_dir}. [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has:   MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver" [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed. However, while we need secureboot to be enabled on these platforms, backport-iwlwifi-dkms must also be signed somehow. There are two possible method to achieve this, too. One, to prebuild this dkms as zfs and v4l2loopback does. However, while backport-iwlwifi-dkms generates kernel modules with exactly the same name as the in-tree ones, when prebuilt, they'll be available directly from the linux-modules package and therefore overrides the in-tree ones always, turning the in-tree driver completely useless and risk the stability of all other generic installations. The second one is to build backport-iwlwifi-dkms as nvidia graphic drivers in the linux-restricted-modules source package. In this way, affected platforms may install the corresponding packages when needed without interfering others. However, l-r-m is for restricted modules that needs special care of redistribution of its binaries, and backport-iwlwifi-dkms is GPL licensed. Here a similar but simpler process in the main kernel tree is re-implemented. Two additional packages, linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package linux-modules-MODULE-FLAVOUR will be created. [Test Case] Test builds: ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb [Where problems could occur] The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails to build under this proposed process. Debdiff attached to the same bug. Different from nvidia packages built from l-r-m, the generated package names do not carry an additional short version string, e.g. nvidia-410, as there is no such necessity to build multiple versions of iwlwifi. The modules are installed to /lib/modules/<kver>/kernel/iwlwifi, not iwlwifi-9858/. ========== linux-meta-hwe-5.15 SRU ========== [Impact] To bring standalone dkms module builds to hwe-5.15 as well. [Fix] Same fix that has been applied to Unstable/Kinetic/Jammy/OEM-6.0/OEM-5.14/HWE-5.19. [Test Case] This should generate meta packages: * linux-modules-iwlwifi-generic-hwe-20.04 * linux-modules-iwlwifi-generic-hwe-20.04-edge * linux-modules-iwlwifi-oem-20.04 * linux-modules-iwlwifi-oem-20.04d [Where problems could occur] This creates only the meta packages that are currently missing. No function changes. [Other Info] While this has been ported to all other series in concern, only hwe-5.15 is nominated for fix here. The patch titled "UBUNTU: [Packaging] skip standalone dkms modules for virtual flavour" was not tagged with a BugLink line, but we'd need that to skip generating linux-modules-foo meta packages for virtual flavour. ========== backport-iwlwifi-dkms SRU ========== In order to be compiled with dkms-build in kernel source package, the kernel header dir will not be /lib/modules/<version>/build but a temporary directory. This change specifies KLIB_BUILD from dkms variable ${kernel_source_dir}. [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has:   MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver"
2022-10-11 08:17:00 You-Sheng Yang linux-meta-hwe-5.15 (Ubuntu Focal): importance Undecided High
2022-10-11 08:17:00 You-Sheng Yang linux-meta-hwe-5.15 (Ubuntu Focal): assignee You-Sheng Yang (vicamo)
2022-10-11 08:25:52 You-Sheng Yang bug task deleted linux-meta-oem (Ubuntu)
2022-10-11 08:26:02 You-Sheng Yang bug task deleted linux-meta-oem (Ubuntu Focal)
2022-10-11 09:02:15 You-Sheng Yang bug task deleted linux-meta-oem (Ubuntu Jammy)
2022-11-15 10:50:42 Launchpad Janitor linux-meta-hwe-5.15 (Ubuntu Focal): status In Progress Fix Released
2023-06-05 10:23:50 Julian Andres Klode backport-iwlwifi-dkms (Ubuntu Focal): status New Incomplete
2023-06-05 10:23:57 Julian Andres Klode removed subscriber Ubuntu Sponsors