on kernel >= 5.17, iwlmvm: disagrees about version of symbol iwl_mei_tx_copy_to_csme

Bug #1975573 reported by You-Sheng Yang
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
backport-iwlwifi-dkms (Ubuntu)
Fix Released
Undecided
You-Sheng Yang
Jammy
Won't Fix
Undecided
You-Sheng Yang
Kinetic
Fix Released
Undecided
You-Sheng Yang

Bug Description

Starting from backport-iwlwifi-dkms upstream revision 9674, commit 6dec03d0ad7b ("[NOUPSTREAM] iwlwifi: mei: align the code with upstream") specifically, in drivers/net/wireless/intel/iwlwifi/Kconfig:

  config IWLMEI
      ...
      depends on WLAN_VENDOR_INTEL_MEI || !KERNEL_5_17

The least version to enable iwlmei has been lowered to 5.17, and therefore it's currently built but not installed by dkms when compiled against linux-oem-5.17 or newer.

This causes a problem that:

  iwlmvm: disagrees about version of symbol iwl_mei_tx_copy_to_csme
  iwlmvm: Unknown symbol iwl_mei_tx_copy_to_csme (err -22)
  iwlmvm: disagrees about version of symbol iwl_mei_register
  iwlmvm: Unknown symbol iwl_mei_register (err -22)
  iwlmvm: disagrees about version of symbol iwl_mei_set_netdev
  iwlmvm: Unknown symbol iwl_mei_set_netdev (err -22)

Tags: patch
Revision history for this message
You-Sheng Yang (vicamo) wrote :
Revision history for this message
You-Sheng Yang (vicamo) wrote :

Built modules (along with patch for bug 1975593, compat renaming):

$ ls /lib/modules/5.1*/updates/dkms
/lib/modules/5.15.0-33-generic/updates/dkms:
cfg80211.ko iwlmvm.ko iwlwifi-compat.ko iwlwifi.ko iwlxvt.ko mac80211.ko

/lib/modules/5.17.0-1003-oem/updates/dkms:
cfg80211.ko iwlmei.ko iwlmvm.ko iwlwifi-compat.ko iwlwifi.ko iwlxvt.ko mac80211.ko

/lib/modules/5.18.0-3-generic/updates/dkms:
cfg80211.ko iwlmei.ko iwlmvm.ko iwlwifi-compat.ko iwlwifi.ko iwlxvt.ko mac80211.ko

Revision history for this message
You-Sheng Yang (vicamo) wrote :
Changed in backport-iwlwifi-dkms (Ubuntu Jammy):
status: New → In Progress
Changed in backport-iwlwifi-dkms (Ubuntu Kinetic):
status: New → In Progress
Changed in backport-iwlwifi-dkms (Ubuntu Jammy):
assignee: nobody → You-Sheng Yang (vicamo)
Changed in backport-iwlwifi-dkms (Ubuntu Kinetic):
assignee: nobody → You-Sheng Yang (vicamo)
Revision history for this message
You-Sheng Yang (vicamo) wrote :

debdiff for kinetic 22.10

Revision history for this message
You-Sheng Yang (vicamo) wrote :

debdiff for jammy 22.04

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "backport-iwlwifi-dkms_9858-0ubuntu5.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

tags: added: patch
Revision history for this message
You-Sheng Yang (vicamo) wrote :

update kinetic debdiff to rebase on 9858-0ubuntu5.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package backport-iwlwifi-dkms - 9858-0ubuntu6

---------------
backport-iwlwifi-dkms (9858-0ubuntu6) kinetic; urgency=medium

  [ You-Sheng Yang ]
  * install iwlmei when compiled against kernel >= 5.17. (LP: #1975573)

  * compat: rename built module to iwlwifi-compat.ko (LP: #1975593)

  [ Dimitri John Ledkov ]
  * dkms: bump obsoleted by to 5.20.0 kernel
  * backport: patch backport headers to support CFI (LP: #1980484)

 -- Dimitri John Ledkov <email address hidden> Mon, 11 Jul 2022 16:46:24 +0100

Changed in backport-iwlwifi-dkms (Ubuntu Kinetic):
status: In Progress → Fix Released
Revision history for this message
You-Sheng Yang (vicamo) wrote :

Turns out this becomes a problem as described in bug 1987312. Stop SRU back to jammy.

Changed in backport-iwlwifi-dkms (Ubuntu Jammy):
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.