GNOME Bugzilla – Bug 770456
NetworkManager 1.4.0-1 breaks wifi
Last modified: 2016-09-23 20:13:07 UTC
networkmanager 1.4.0-1(1.2.5dev+5+g99e34d7-1) testing this package disables my wifi on a macbook. error msg on startup is: [ 21.950639] ERROR @wlcfg80211scan : WLC_SCAN error (-22) installing previous package from pacman cache fixes this. Note that the new libnm-glib does NOT break the wifi just the new networkmanager package. Running Apricity stable on macbook
this line is not printed by NetworkManager. Please attach full logfiles with debug logging enabled. You do that by configuring level=TRACE in NetworkManager.conf and restart NM. thank you.
What's the name of the log files after enabling trace & restarting?
NetworkManager logs to syslog, so it depends on your configuration. With systemd-journal, it is `journalctl -u NetworkManager`. Otherwise, probably somewhere in /var/log.
Created attachment 334255 [details] log file with trace on Here it is...as Homer Simpson once said "Nothin's easy!"
..for the record the log file was created with "journalctl -u NetworkManager > networkmanager.log"
...I was trying to get the Hotspot feature to work but it was acting badly. Is this the package responsible for this feature?
(In reply to Phil Reilly from comment #6) > ...I was trying to get the Hotspot feature to work but it was acting badly. > Is this the package responsible for this feature? yes, please open a separate BZ for that and provide logfiles. Thanks Be aware, that you need dnsmasq package installed (for which NetworkManager's package usually doesn't have a dependency, because it's optional).
Does this issue need more information from me?
Seems you didn't actually enable TRACE level for logging. Please edit /etc/NetworkManager/NetworkManager.conf to have: [logging] level=TRACE then restart NM. Actually, there attached logfile is full of the error: do-change-link[3]: failure changing link: failure 23 (Too many open files in system) that is certainly unusual. could you provide a logfile with debug-logging enabled? That would be helpful. Thanks!
Created attachment 334288 [details] Second Log file with trace really on Please confirm the usefulness of this log.
it's good. Thanks!
You wanna see a trace of the version that works?
Reports here[0] suggest that this is only a problem with broadcom wl driver. [0] https://aur.archlinux.org/packages/broadcom-wl-dkms
seems, NetworkManager receives a failure from kernel to reset the MAC address (although actually, the address does change). With 1.4.0, during Wi-Fi scanning NM tries to set the MAC address to a random address. That yields an error message from kernel, but actually the address changed. Afterwards, when NM activates the connection, it is configured to reset the permanent MAC address. That command fails again, which causes NM to abort the activation. You may work around that by disabling resetting the MAC address during scanning. Configure /etc/NetworkManager/NetworkManager.conf to have [device] wifi.scan-rand-mac-address=no and issue `killall -SIGHUP NetworkManager`. Afterwards, the first activation attempt may still fail (because it bails out on the error to change the randomized MAC address to the permanent one). Then the second attempt should succeed. It is a driver issue, but NM should try to workaround it.
Patch for review: https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/?h=th/platform-set-address-enfile-bgo770456
Dell xps 15 9550 (2016) Archlinux This bug afflict me as well. And I confirm workaround [device] wifi.scan-rand-mac-address=no worked for me too... In my case, I do not use broadcom-wl restricted driver (I tested trying them as solution to this problem, but after installed things went worse, I didn't see wifi device ! so disinstalled), I'm using brcmfmac driver and apart some dmesg warning, they work until use NetworkManager 1.2.4 and 1.2.5.dev but if I upgrade 1.4 I fall in this bug. Luckly, workaround is ok !
[device] wifi.scan-rand-mac-address=no Works foe me.....
I rebuilt networkmanager with the patch and (even without the workaround) can confirm that this works for me.
The patch looks sensible to me (but I would change the yoda condition to the usual form).
(In reply to Alessio Tomelleri from comment #16) > Dell xps 15 9550 (2016) > Archlinux > > This bug afflict me as well. And I confirm workaround > > [device] > wifi.scan-rand-mac-address=no > > worked for me too... > > In my case, I do not use broadcom-wl restricted driver (I tested trying them > as solution to this problem, but after installed things went worse, I didn't > see wifi device ! so disinstalled), > I'm using brcmfmac driver and apart some dmesg warning, they work until use > NetworkManager 1.2.4 and 1.2.5.dev but if I upgrade 1.4 I fall in this bug. Looking at brcmfmac driver code it doesn't seem evident that the same error (-ENFILE) of logs in comment 10 can be returned from set_mac(). Can you please attach trace logs or if you prefer only the error (if any) that you see when NM tries to change the MAC? See comment 9 for how to capture trace logs. Thanks!
patches merged upstream: master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=091620e76592349ae3efee08faed881ce1a2495b nm-1-4: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=a3fd48545cf186a7e33aa9df8c3dd2bc016b350d Closing BZ for now. The logfiles from comment 10 for brcmfmac are still interesting to see!!
Created attachment 334358 [details] output dmesg + journalctl Hi Bruno, (Comment #20) I follow your hint, here the attachment... dmesg + juorunalctl -u NetworkManager Alessio
(In reply to Alessio Tomelleri from comment #22) > Created attachment 334358 [details] > output dmesg + journalctl > > Hi Bruno, > > (Comment #20) > > I follow your hint, here the attachment... dmesg + juorunalctl -u > NetworkManager > > Alessio NetworkManager's logfile doesn't show contain the relevant part. Please more context.
Created attachment 334376 [details] journalctl networkmanager Hi Hans, Sorry... to much quick before, I hope this attachment could be more useful Alessio
This is a different issue. fix for review: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=th%2Fplatform-set-address-enfile-bgo770456-v2
*** Bug 770505 has been marked as a duplicate of this bug. ***
The workaround in this issue works for the problem I reported in #770504 with the ath9k driver (not broadcom). Possible duplicate: https://bugzilla.gnome.org/show_bug.cgi?id=770504
(In reply to Thomas Haller from comment #25) > This is a different issue. > > fix for review: > > https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/ > ?id=th%2Fplatform-set-address-enfile-bgo770456-v2 LGTM
second set of patches also merge upstream. master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=e109f870670e7503047309358cf97287ebd18d56 nm-1-4: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=3a2e3aa70bf948ab5e9f193ebc642ac21c22a651
*** Bug 770577 has been marked as a duplicate of this bug. ***
Turns out, the fixes up to know are not sufficient. https://bugzilla.redhat.com/show_bug.cgi?id=1374023 This fix is also required: master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=1a85103765d4eaa0acab6b03658a4f9cfe684a64 nm-1-4: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8d575403685208aad75f918484ae7adbc1a46085
Turns out, another fix is needed: master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=32f7c1d4b9aba597a99128631f07c2985149f303 nm-1-4: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=cd8f2ecc617a896d8007e6fe825c676a626a3b8d See also: https://bugzilla.gnome.org/show_bug.cgi?id=770504#c20