This bug was fixed in the package nplan - 0.32~16.04.4

nplan (0.32~16.04.4) xenial; urgency=medium

  [ Oliver Grawert ]
  * Prevent unbinding ath6kl_sdio, driver does not support it correctly.
    (LP: #1741910)

  [ Mathieu Trudel-Lapierre ]
  * Re-add snap support patch. (LP: #1747714)
  * Fix syntax for IPv6 addresses in doc. (LP: #1735317)
  * doc: routes are not top-level but per-interface. (LP: #1726695)
  * Implement bridge port-priority parameter. (LP: #1735821)
  * Implement "optional: true" to correctly write systemd network definitions
    with "RequiredForOnline=false", such that these networks do not block boot.
    (LP: #1664844)
  * Various documentation fixes. (LP: #1751814)

 -- Mathieu Trudel-Lapierre <>  Fri, 02 Mar 2018
17:02:03 -0500

** Changed in: nplan (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs

  ath6kl_sdio does not support unbinding

Status in netplan:
  Fix Committed
Status in nplan package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Released

Bug description:
  Atheros users -- some of our users with wireless devices driven by the 
ath6kl_sdio driver; when running 'netplan apply' may wedge the wireless driver 
in an unrecoverable state.

  [Test case]
  -- requires ath6kl_sdio hardware --
  1) Run 'sudo netplan apply'
  2) Ensure the wireless interface still responds and can connect to wireless.

  [Regression potential]
  Renaming the interface is already broken since the interface cannot respond 
correctly after it has been "replugged", because the driver is not supporting 
the replug operation. The same applies to configuring an MTU for the interface.

  If existing installations depend on current netplan behavior to rename
  / set the device MTU, and then follow up with manual configuring of
  the device, they will regress in that the MTU setting or renaming may
  not take place. This is an unavoidable side-effect of this hardware's
  driver not supporting the required operation.


  like the brcmfmac*, ath9k_htc and mwifiex_pcie modules, the
  ath6kl_sdio module does not support unbind/bind operations.
  works around this issue

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to