Ubuntu
network-manager package

rfkill autopkgtests broken with linux 4.8: fake-rfkill.ko: Unknown symbol in module

Bug #1626568 reported by Martin Pitt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Medium
Martin Pitt

Bug Description

The two rfkill tests now fail in yakkety since linux got upgraded to 4.8, like in in
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/i386/n/network-manager/20160922_091844@/log.gz .

It still builds fine:
$ sudo make -f debian/tests/Makefile fake-rfkill
make -C /lib/modules/4.8.0-15-generic/build KBUILD_SRC=/lib/modules/4.8.0-15-generic/build M=/tmp/autopkgtest.zD5lki/build.WwA/real-tree/debian/tests
make[1]: Entering directory '/usr/src/linux-headers-4.8.0-15-generic'
  Building modules, stage 2.
  MODPOST 1 modules

But it can't be loaded:
$ sudo insmod debian/tests/fake-rfkill.ko
insmod: ERROR: could not insert module debian/tests/fake-rfkill.ko: Unknown symbol in module
$ dmesg
[ 7779.796145] fake_rfkill: Unknown symbol rfkill_unregister (err 0)
[ 7779.796153] fake_rfkill: Unknown symbol rfkill_destroy (err 0)
[ 7779.796162] fake_rfkill: Unknown symbol rfkill_alloc (err 0)
[ 7779.796168] fake_rfkill: Unknown symbol rfkill_register (err 0)

Tags: kernel-4.8
Andy Whitcroft (apw)
tags: added: kernel-4.8
Revision history for this message
Martin Pitt (pitti) wrote :

"modprobe rfkill" fixes this -- the built .ko already declares that dependency properly, it just doesn't get loaded by "insmod".

Changed in network-manager (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
Martin Pitt (pitti) wrote :

Fixed: https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?id=5fbc4bdf5dd

Changed in network-manager (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package network-manager - 1.2.4-0ubuntu1

---------------
network-manager (1.2.4-0ubuntu1) yakkety; urgency=medium

  [ Aron Xu ]
  * Imported Upstream version 1.2.4
  * Update patches for new upstream release:
    - Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch: not needed
    - Order-IPv6-nameservers-before-IPv4-for-dns-plugins-d.patch: not needed
    - libnm-don-t-require-initialized-out_encrypted-argume.patch: merged upstream
    - cli-initialize-connection-list-in-do_device_connect.patch: merged upstream
    - rename due to gbp-pq:
      Don-t-block-network.target-on-NetworkManager-wait-on.patch =>
      systemd-Don-t-enable-NetworkManager-wait-online.serv.patch
    - post-release cherry-picks:
      - wifi-clear-WiFi-requested_scan-if-suppl-exits.patch
      - wifi-clear-WiFi-requested_scan-if-suppl-goes-INACTIV.patch
    - refreshed remaining ones

  [ Martin Pitt ]
  * debian/tests/wpa-dhclient: Don't assume that the IPv6 prefix length from
    the DHCP server is /64. (LP: #1609898)
  * debian/tests/*rfkill*: Load fake-rfkill.ko's dependencies before trying to
    insserv it. (LP: #1626568)
  * debian/tests/killswitches-no-urfkill: Make the script work with set -e, so
    that we don't try to run tests after compile errors.
  * Switch back to dns=dnsmasq for Ubuntu 16.10. We still don't have a DNS
    plugin for resolved, and don't want to break domain-specific DNS servers
    for the final release.

 -- Martin Pitt <email address hidden> Tue, 27 Sep 2016 08:16:12 +0200

Changed in network-manager (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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