netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

Syncopated · 2015-04-25 05:08:14

A few hours ago, I upgraded from wpa_supplicant-2.3-1 to wpa_supplicant-2.4-1. Subsequently netctl-auto@wlp3s0.service stopped working. After I started it, it would be reported as "active (running)" but fail to connect to any WIFI network (I wouldn't get assigned a DHCP IP address):

Apr 25 12:44:47 sauron wpa_actiond[6952]: Interface 'wlp3s0' connected to network 'Edward'
Apr 25 12:44:47 sauron dhcpcd[6974]: DUID xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
Apr 25 12:44:47 sauron dhcpcd[6974]: wlp3s0: IAID xx:xx:xx:xx
Apr 25 12:44:47 sauron dhcpcd[6974]: wlp3s0: rebinding lease of 192.168.1.20
Apr 25 12:44:51 sauron dhcpcd[6974]: wlp3s0: leased 192.168.1.20 for 43200 seconds
Apr 25 12:44:51 sauron dhcpcd[6974]: wlp3s0: adding route to 192.168.1.0/24
Apr 25 12:44:51 sauron dhcpcd[6974]: wlp3s0: adding default route via 192.168.1.1
12:55 ~$ journalctl -xe -u netctl-auto@wlp3s0.service                  
Apr 25 12:36:28 sauron netctl-auto[5505]: Included profile 'wlp3s0-cz'                                                                                                               
Apr 25 12:36:28 sauron netctl-auto[5505]: Successfully initialized wpa_supplicant
Apr 25 12:36:28 sauron netctl-auto[5505]: Could not read interface p2p-dev-wlp3s0 flags: No such device
Apr 25 12:36:28 sauron systemd[1]: Started Automatic wireless network connection using netctl profiles.
-- Subject: Unit netctl-auto@wlp3s0.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl-auto@wlp3s0.service has finished starting up.

Notice the "Could not read interface...". I downgraded back to 2.3-1 and the problem went away. Could this be a wpa_supplicant bug (new bug in 2.4-1) or netctl bug (incompatibility with the new wpa_supplicant)?

There's nothing special about the profile files in /etc/netctl. In addition to the ones for wired network, I have a few files named like "wlp3s0-XXX" and they look like this (password crossed out):

Connection=wireless
Description='Edward'
Interface=wlp3s0
Security=wpa
ESSID='Edward'
Key='????'
Hidden=yes
IP=dhcp

60lpsdf250 · 2015-04-25 05:52:39

Syncopated, I have the same problem with the same solution (downgrading). I am interested in any response, thus my reply.

Smetterleen · 2015-04-25 09:22:58

I'm having exactly the same problem.

# wpa_supplicant -D wext -i wlp2s0 -c /tmp/wpap                                                                                                                                                                                                                                                            
Successfully initialized wpa_supplicant
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWSCAN]: Device or resource busy
wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
ioctl[SIOCSIWSCAN]: Device or resource busy
wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
ioctl[SIOCSIWSCAN]: Device or resource busy
wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
ioctl[SIOCSIWSCAN]: Device or resource busy
wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
wlp2s0: Trying to associate with 00:1e:e5:6d:83:6f (SSID='Driesen-Peeters' freq=2437 MHz)
ioctl[SIOCSIWFREQ]: Device or resource busy
wlp2s0: Association request to the driver failed
wlp2s0: Authentication with 00:1e:e5:6d:83:6f timed out.
ioctl[SIOCSIWMLME]: Transport endpoint is not connected
ioctl[SIOCSIWAP]: Device or resource busy
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=00:1e:e5:6d:83:6f reason=3 locally_generated=1
ioctl[SIOCSIWSCAN]: Device or resource busy
wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
ioctl[SIOCSIWSCAN]: Device or resource busy
wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
^Cwlp2s0: CTRL-EVENT-TERMINATING 

# wpa_supplicant -D wext -i wlp2s0 -c /tmp/wpap
Successfully initialized wpa_supplicant
Could not read interface p2p-dev-wlp2s0 flags: No such device
wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
wlp2s0: SME: Trying to authenticate with 00:1e:e5:6d:83:6f (SSID='My-Network' freq=2437 MHz)
wlp2s0: SME: Authentication request to the driver failed
.
.
.
^C
nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
p2p-dev-wlp2s0: CTRL-EVENT-TERMINATING 
nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
wlp2s0: CTRL-EVENT-TERMINATING

This also break wifi-menu by the way, so the only option now is trying a manual wpa_supplicant connect. I should mention that this morning (after troubleshooting all night with no result) I managed to connect to my AP once (while begin connected via ethernet as well). After disconnecting the ethernet cable and trying again it failed again. I have not been able to reproduce this.

Other possibly interesting information:

# dmesg
[  734.004304] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
[  734.004343] iwlwifi 0000:02:00.0: No available PHY context
[  734.004378] iwlwifi 0000:02:00.0: No available PHY context
[  737.496406] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
[  737.496431] iwlwifi 0000:02:00.0: No available PHY context
[  741.388469] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
[  741.388493] iwlwifi 0000:02:00.0: No available PHY context
[  963.953904] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
[  963.956708] wlp2s0: send auth to 00:1e:e5:6d:83:6f (try 1/3)
[  963.958860] wlp2s0: authenticated
[  963.961363] wlp2s0: associate with 00:1e:e5:6d:83:6f (try 1/3)
[  963.964229] wlp2s0: RX AssocResp from 00:1e:e5:6d:83:6f (capab=0x411 status=0 aid=1)
[  963.965539] wlp2s0: associated
[  966.651095] wlp2s0: deauthenticating from 00:1e:e5:6d:83:6f by local choice (Reason: 3=DEAUTH_LEAVING)
[  966.655984] cfg80211: Calling CRDA to update world regulatory domain
[  966.659308] cfg80211: World regulatory domain updated:
[  966.659312] cfg80211:  DFS Master region: unset
[  966.659313] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[  966.659315] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[  966.659317] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[  966.659319] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[  966.659321] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[  966.659323] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[  966.659324] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[  966.659326] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[  966.659327] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[ 1033.789418] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 1043.308740] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 1046.718632] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
[ 1046.718644] iwlwifi 0000:02:00.0: No available PHY context
[ 1046.718654] iwlwifi 0000:02:00.0: No available PHY context
[ 1050.109123] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
[ 1050.109147] iwlwifi 0000:02:00.0: No available PHY context
[ 1072.258284] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 1075.694370] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
[ 1075.697180] wlp2s0: send auth to 00:1e:e5:6d:83:6f (try 1/3)
[ 1076.003982] iwlwifi 0000:02:00.0: No association and the time event is over already...
[ 1076.004017] wlp2s0: Connection to AP 00:1e:e5:6d:83:6f lost
[ 1080.255382] wlp2s0: authenticated

# pacman -Q wpa_supplicant
wpa_supplicant 2.4-1
# uname -r
3.19.3-3-ARCH
# lspci -v | grep Wireless -A 15
02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
        Subsystem: Intel Corporation Dual Band Wireless-AC 7265
        Flags: bus master, fast devsel, latency 0, IRQ 50
        Memory at f7000000 (64-bit, non-prefetchable) [size=8K]
        Capabilities: [c8] Power Management version 3
        Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [40] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number 60-57-18-ff-ff-4a-6a-8c
        Capabilities: [14c] Latency Tolerance Reporting
        Capabilities: [154] L1 PM Substates
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi

I'm on a Zenbook UX305, what are you guys on and could you post the output of those last three commands I posted?

Cheers!

mdi · 2015-04-25 11:44:20

Same problem here.

PaterSiul · 2015-04-25 12:21:17

Same here. Except: I don't get repeated authentication. netctl-auto starts and just sits there.

netctl start Profile

is successfull, however. The same goes for manually connecting. In both those cases I got the line:

Could not read interface p2p-dev-wlan0 flags: No such device

So, the cause does not lie with wpa_supplicant alone.

The following output was generated before I shut down netctl-auto@wlan0 and after it had been running for about two minutes:

# dmesg|egrep "(iwlwifi|cfg80211|wlan)"
[    2.686013] cfg80211: Calling CRDA to update world regulatory domain
[    2.719543] iwlwifi 0000:03:00.0: loaded firmware version 25.15.12.0 op_mode iwlmvm
[    2.750633] iwlwifi 0000:03:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144
[    2.750974] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[    2.751786] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[    4.443850] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[    4.444628] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[    4.463766] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  250.775737] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[  250.776482] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
[  250.797594] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

# journalctl -b -u netctl-auto@wlan0
Apr 25 13:34:42 mymachine systemd[1]: Starting Automatic wireless network connection using netctl profiles...
Apr 25 13:34:42 mymachine netctl-auto[358]: Included profile 'Profile'
<removed all profile name output for privacy reasons, but there were all of them>
Apr 25 13:34:42 mymachine netctl-auto[358]: Successfully initialized wpa_supplicant
Apr 25 13:34:42 mymachine netctl-auto[358]: Could not read interface p2p-dev-wlan0 flags: No such device
Apr 25 13:34:42 mymachine systemd[1]: Started Automatic wireless network connection using netctl profiles.

# lspci -v
03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83)
	Subsystem: Intel Corporation Dual Band Wireless-AC 7260
	Flags: bus master, fast devsel, latency 0, IRQ 45
	Memory at f0400000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: [c8] Power Management version 3
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [40] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number <removed by author>
	Capabilities: [14c] Latency Tolerance Reporting
	Capabilities: [154] Vendor Specific Information: ID=cafe Rev=1 Len=014 <?>
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

joe_silver · 2015-04-25 14:47:46

Same problem here this morning. But since I use Gnome with Network-Manager, it is sufficient to restart the daemon

systemctl restart NetworkManager.service

Nevertheless it is a bit annoying.

Looking at the latest diff:

https://projects.archlinux.org/svntogit … 0d495c9d86

there seems to be a change related to this p2p device... but I don't really know how to solve it.

falcon9 · 2015-04-25 15:46:39

Same problem here. wifi-menu broke for me after the update. (Warning, I am an Arch n00b.)

Downgrading worked as mentioned by OP, but another solution is to keep the upgrade and do

 netctl start Profile

as mentioned by PaterSiul. However, I do not get the "No such device' output.

I also do not get the repeated authentication that was spotted by Smetterleen.

Curiously enough, even AFTER executing the above (and successfully connecting to the internet), WPA supplicant appears inactive (I'm connected to a WPA2 network... is the below expected behavior?)

$ systemctl status wpa_supplicant.service
● wpa_supplicant.service - WPA supplicant
   Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled; vendor preset: disabled)
   Active: inactive (dead)

There is similar output for netctl-auto@wlp3s0.service:

$ systemctl status netctl-auto@wlp3s0.service
● netctl-auto@wlp3s0.service - Automatic wireless network connection using netctl profiles
   Loaded: loaded (/usr/lib/systemd/system/netctl-auto@.service; disabled; vendor preset: disabled)
   Active: inactive (dead)
     Docs: man:netctl.special(7)

Here's my HW:

03:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
        Subsystem: AzureWave AW-NB037H 802.11bgn Wireless Half-size Mini PCIe Card [AR9002WB-1NGCD]
        Flags: bus master, fast devsel, latency 0, IRQ 17
        Memory at f5600000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
        Capabilities: [60] Express Legacy Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel
        Capabilities: [160] Device Serial Number 00-15-17-ff-ff-24-14-12
        Capabilities: [170] Power Budgeting <?>
        Kernel driver in use: ath9k
        Kernel modules: ath9k

Last edited by falcon9 (2015-04-25 15:51:38)

xanb · 2015-04-25 16:07:05

I have the same problem with the openrc installed. I confirmed that with downgraded package (2.3) all is ok, but with 2.4 I receive the error "No networks found" with netctl. Can anyone see if this is a reported bug?

Head_on_a_Stick · 2015-04-25 16:11:19

http://w1.fi/security/2015-1/wpa_suppli … erflow.txt

I think P2P doesn't work on the new version of wpa_supplicant (for now).

Syncopated · 2015-04-25 16:39:30

I couldn't find a bug for this, so I filed a netctl bug: https://bugs.archlinux.org/task/44731

xanb · 2015-04-26 11:25:18

Thanks, Syncopated, but I think that the bug is against wpa_supplicant

foutrelis · 2015-04-26 12:10:26

wifi-menu should be fixed in netctl 1.10-2 (currently in [testing]).

I was unable to reproduce the netctl-auto bug; hopefully someone will figure that one out soon.

Feynman · 2015-04-26 16:12:55

I think the problem may be intermittent, unfortunately. I upgraded wpa_supplicant 2 days ago and didn't have issues until this morning. Today I resume from suspend and was having the exact same issues described above. I rebooted into windows (sorry) to search for the problem, found the fix, and by the time I got back into linux netctl-auto was working perfectly again.

joe_silver · 2015-04-27 09:27:59

No, the problem has not been solved and I think that it is not due to a bug in netctl.

I still have the same issue with NetworkManager. Here netctl is disabled

Apr 27 10:03:56 Albion wpa_supplicant[780]: Could not read interface p2p-dev-wlp1s0 flags: No such device
Apr 27 10:03:56 Albion wpa_supplicant[780]: process 780: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_path (*string_p)" failed in file dbus-message.c line 2681.
Apr 27 10:03:56 Albion wpa_supplicant[780]: This is normally a bug in some application using the D-Bus library.
Apr 27 10:03:56 Albion wpa_supplicant[780]: D-Bus not built with -rdynamic so unable to print a backtrace
Apr 27 10:03:56 Albion wpa_supplicant[829]: Successfully initialized wpa_supplicant
Apr 27 10:03:56 Albion wpa_supplicant[829]: Could not read interface p2p-dev-wlp1s0 flags: No such device
Apr 27 10:03:56 Albion wpa_supplicant[829]: process 829: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_path (*string_p)" failed in file dbus-message.c line 2681.
Apr 27 10:03:56 Albion wpa_supplicant[829]: This is normally a bug in some application using the D-Bus library.
Apr 27 10:03:56 Albion wpa_supplicant[829]: D-Bus not built with -rdynamic so unable to print a backtrace

Again, restarting NetworkManager make things work but the problem persists after reboot.

Syncopated · 2015-04-29 17:05:04

I just did a pacman -Syu and the problem I posted about seems to be gone. I now have:
linux: 4.0.1-1
wpa_supplicant: 1:2.3-1
netctl: 1.10-2

Additionally, the bug has also been closed.

Last edited by Syncopated (2015-04-29 17:06:08)

PhilThompson · 2015-04-29 17:45:22

It looks like they've reverted to the previous version of wpa_supplicant

letni69 · 2015-12-07 23:08:59

It seems like the bug is back. After upgrading to wpa_supplicant 2.5-1 the bug came back, so downgrading to 2.3-1 solved this.

adrolter · 2015-12-08 02:23:25

I'm getting this now too, since this morning.

[2015-12-07 15:46] [ALPM] upgraded wpa_supplicant (1:2.3-1 -> 1:2.5-1)

klemmster · 2015-12-08 09:08:04

I' too affected by the issue(wifi broken after upgrading wpa_supplicant), albeit my error seems a little different.

Dec 08 09:54:27 lazzle wpa_actiond[910]: Error (wlp2s0): Could not attach to wpa_supplicant

Manually setting the profile as suggested works around that.

brandon099 · 2015-12-09 06:09:57

I'm also experiencing this issue after upgrading to wpa_supplicant 2.5-1. Downgraded to 2.3-1 for now.

LaserEyess · 2015-12-09 16:30:47

Yeah I am getting the same issue, downgrading wpa_supplicant to 2.3-1 works. I got the same error as klenmaster before. It was complaining that p2p-dev-wlp4s0 did not exist. And ip link gave this:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
    link/ether 60:57:18:e6:ae:79 brd ff:ff:ff:ff:ff:ff
3: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether 54:ee:75:47:78:7f brd ff:ff:ff:ff:ff:ff

after downgrading I get this:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
    link/ether 60:57:18:e6:ae:79 brd ff:ff:ff:ff:ff:ff
3: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether 54:ee:75:47:78:7f brd ff:ff:ff:ff:ff:ff

If it helps I'm using the following wireless card:

04:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
	Subsystem: Intel Corporation Dual Band Wireless-AC 7265
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

No errors with iwlwifi afaik.

tholmes · 2015-12-10 20:45:13

Just wanted to chime in that I am also seeing this same issue when trying to connect to my corporate 802.1X network. Downgrading to 2.3 resolved my issue as well.

I have the same device as LaserEyess, an Intel 7265 Rev 59.

Here is the output of journalctl -xe

Dec 10 15:41:04 e4 network[13009]: Starting network profile 'wlp3s0-RSG'...
Dec 10 15:41:04 e4 kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
Dec 10 15:41:04 e4 kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
Dec 10 15:41:04 e4 kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
Dec 10 15:41:04 e4 kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
Dec 10 15:41:05 e4 kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
Dec 10 15:41:05 e4 network[13009]: Could not read interface p2p-dev-wlp3s0 flags: No such device
Dec 10 15:41:07 e4 kernel: wlp3s0: authenticate with 7c:0e:ce:70:39:a9
Dec 10 15:41:07 e4 kernel: wlp3s0: send auth to 7c:0e:ce:70:39:a9 (try 1/3)
Dec 10 15:41:08 e4 kernel: wlp3s0: authenticated
Dec 10 15:41:08 e4 kernel: wlp3s0: associate with 7c:0e:ce:70:39:a9 (try 1/3)
Dec 10 15:41:08 e4 kernel: wlp3s0: RX AssocResp from 7c:0e:ce:70:39:a9 (capab=0x1111 status=0 aid=13)
Dec 10 15:41:08 e4 kernel: wlp3s0: associated
Dec 10 15:41:08 e4 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
Dec 10 15:41:08 e4 kernel: wlp3s0: Limiting TX power to 17 dBm as advertised by 7c:0e:ce:70:39:a9
Dec 10 15:41:08 e4 kernel: wlp3s0: deauthenticating from 7c:0e:ce:70:39:a9 by local choice (Reason: 1=UNSPECIFIED)
Dec 10 15:41:08 e4 kernel: wlp3s0: authenticate with 7c:0e:ce:6b:ab:39
Dec 10 15:41:08 e4 kernel: wlp3s0: send auth to 7c:0e:ce:6b:ab:39 (try 1/3)
Dec 10 15:41:08 e4 kernel: wlp3s0: authenticated
Dec 10 15:41:08 e4 kernel: wlp3s0: associate with 7c:0e:ce:6b:ab:39 (try 1/3)
Dec 10 15:41:08 e4 kernel: wlp3s0: RX AssocResp from 7c:0e:ce:6b:ab:39 (capab=0x1101 status=17 aid=0)
Dec 10 15:41:08 e4 kernel: wlp3s0: 7c:0e:ce:6b:ab:39 denied association (code=17)
Dec 10 15:41:08 e4 kernel: wlp3s0: authenticate with 7c:0e:ce:4e:71:c9
Dec 10 15:41:08 e4 kernel: wlp3s0: send auth to 7c:0e:ce:4e:71:c9 (try 1/3)
Dec 10 15:41:08 e4 kernel: wlp3s0: authenticated
Dec 10 15:41:08 e4 kernel: wlp3s0: associate with 7c:0e:ce:4e:71:c9 (try 1/3)
Dec 10 15:41:08 e4 kernel: wlp3s0: RX AssocResp from 7c:0e:ce:4e:71:c9 (capab=0x1111 status=0 aid=28)
Dec 10 15:41:08 e4 kernel: wlp3s0: associated
Dec 10 15:41:08 e4 kernel: wlp3s0: Limiting TX power to 20 dBm as advertised by 7c:0e:ce:4e:71:c9
Dec 10 15:41:09 e4 kernel: wlp3s0: deauthenticating from 7c:0e:ce:4e:71:c9 by local choice (Reason: 1=UNSPECIFIED)
Dec 10 15:41:09 e4 kernel: wlp3s0: authenticate with 7c:0e:ce:dc:e9:29
Dec 10 15:41:09 e4 kernel: wlp3s0: send auth to 7c:0e:ce:dc:e9:29 (try 1/3)
Dec 10 15:41:09 e4 kernel: wlp3s0: authenticated
Dec 10 15:41:09 e4 kernel: wlp3s0: associate with 7c:0e:ce:dc:e9:29 (try 1/3)
Dec 10 15:41:09 e4 kernel: wlp3s0: RX AssocResp from 7c:0e:ce:dc:e9:29 (capab=0x1111 status=0 aid=111)
Dec 10 15:41:09 e4 kernel: wlp3s0: associated
Dec 10 15:41:09 e4 kernel: wlp3s0: Limiting TX power to 12 dBm as advertised by 7c:0e:ce:dc:e9:29
Dec 10 15:41:09 e4 kernel: wlp3s0: deauthenticating from 7c:0e:ce:dc:e9:29 by local choice (Reason: 1=UNSPECIFIED)
Dec 10 15:41:09 e4 kernel: wlp3s0: authenticate with 7c:0e:ce:ea:b6:59
Dec 10 15:41:09 e4 kernel: wlp3s0: send auth to 7c:0e:ce:ea:b6:59 (try 1/3)
Dec 10 15:41:09 e4 kernel: wlp3s0: authenticated
Dec 10 15:41:19 e4 kernel: wlp3s0: associate with 7c:0e:ce:dc:e9:29 (try 1/3)
Dec 10 15:41:19 e4 kernel: wlp3s0: RX AssocResp from 7c:0e:ce:dc:e9:29 (capab=0x1111 status=0 aid=111)
Dec 10 15:41:19 e4 kernel: wlp3s0: associated
Dec 10 15:41:19 e4 kernel: wlp3s0: Limiting TX power to 12 dBm as advertised by 7c:0e:ce:dc:e9:29
Dec 10 15:41:19 e4 kernel: wlp3s0: deauthenticating from 7c:0e:ce:dc:e9:29 by local choice (Reason: 1=UNSPECIFIED)
Dec 10 15:41:20 e4 kernel: wlp3s0: authenticate with 7c:0e:ce:ea:b6:59
Dec 10 15:41:20 e4 kernel: wlp3s0: send auth to 7c:0e:ce:ea:b6:59 (try 1/3)
Dec 10 15:41:20 e4 kernel: wlp3s0: authenticated
Dec 10 15:41:20 e4 kernel: wlp3s0: associate with 7c:0e:ce:ea:b6:59 (try 1/3)
Dec 10 15:41:20 e4 kernel: wlp3s0: RX AssocResp from 7c:0e:ce:ea:b6:59 (capab=0x1111 status=0 aid=91)
Dec 10 15:41:20 e4 kernel: wlp3s0: associated
Dec 10 15:41:20 e4 kernel: wlp3s0: Limiting TX power to 14 dBm as advertised by 7c:0e:ce:ea:b6:59
Dec 10 15:41:20 e4 kernel: wlp3s0: deauthenticating from 7c:0e:ce:ea:b6:59 by local choice (Reason: 1=UNSPECIFIED)
Dec 10 15:41:20 e4 network[13009]: WPA association/authentication failed for interface 'wlp3s0'
Dec 10 15:41:20 e4 dhcpcd[1791]: wlp3s0: carrier acquired
Dec 10 15:41:20 e4 dhcpcd[1791]: wlp3s0: adding address fe80::92a2:4976:1cd3:2e14
Dec 10 15:41:20 e4 dhcpcd[1791]: wlp3s0: IAID 88:b0:a9:9b
Dec 10 15:41:20 e4 dhcpcd[1791]: wlp3s0: carrier lost
Dec 10 15:41:20 e4 dhcpcd[1791]: wlp3s0: deleting address fe80::92a2:4976:1cd3:2e14
Dec 10 15:41:20 e4 network[13009]: Failed to bring the network up for profile 'wlp3s0-RSG'
Dec 10 15:41:20 e4 systemd[1]: netctl@wlp3s0\x2dRSG.service: Main process exited, code=exited, status=1/FAILURE
Dec 10 15:41:20 e4 systemd[1]: Failed to start Networking for netctl profile wlp3s0-RSG.
-- Subject: Unit netctl@wlp3s0\x2dRSG.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@wlp3s0\x2dRSG.service has failed.
-- 
-- The result is failed.
Dec 10 15:41:20 e4 systemd[1]: netctl@wlp3s0\x2dRSG.service: Unit entered failed state.
Dec 10 15:41:20 e4 systemd[1]: netctl@wlp3s0\x2dRSG.service: Failed with result 'exit-code'.
Dec 10 15:41:20 e4 polkitd[4511]: Unregistered Authentication Agent for unix-process:13003:146446 (system bus name :1.48, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale e
Dec 10 15:41:20 e4 sudo[12998]: pam_unix(sudo:session): session closed for user root
Dec 10 15:41:22 e4 sudo[13524]:  tholmes : TTY=pts/0 ; PWD=/etc/netctl ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Dec 10 15:41:22 e4 sudo[13524]: pam_unix(sudo:session): session opened for user root by (uid=0)

drrossum · 2015-12-11 03:53:13

Yep, same problem here. See also this thread and this bug report
https://bbs.archlinux.org/viewtopic.php?id=206044
https://bugs.archlinux.org/task/44731

Network controller: Intel Corporation Wireless 7260 (rev 83)

Last edited by drrossum (2015-12-11 15:34:53)

tutu · 2015-12-11 16:19:46

I'm having a similar issue. I disable all netctl profiles and netctl-auto. I can get a network connection by starting the profile manually with

netctl start [PROFILE]

or by using wifi-menu, which issues an unusual message before the dialog box pops up:

Scanning for networks... Could not read interface p2p-dev-wlp2s0 flags: No such device

If I tried to start netctl-auto instead of starting a netctl profile manually using the command

systemctl start netctl-auto@wlp2s0.interface

I takes some time but I get a failed for the process

A dependency job for netctl-auto@wlp2s0.interface.service failed. See 'journalctl -xe' for details.

and I notice that my journalctl -xe contains a failed in some other unit. Here is a snippet of it:

Dec 11 00:05:21 hydra systemd[1]: sys-subsystem-net-devices-wlp2s0.interface.device: Job sys-subsystem-net-devices-wlp2s0.interface.device/start timed out.
Dec 11 00:05:21 hydra systemd[1]: Timed out waiting for device sys-subsystem-net-devices-wlp2s0.interface.device.
-- Subject: Unit sys-subsystem-net-devices-wlp2s0.interface.device has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit sys-subsystem-net-devices-wlp2s0.interface.device has failed.
-- 
-- The result is timeout.
Dec 11 00:05:21 hydra systemd[1]: Dependency failed for Automatic wireless network connection using netctl profiles.
-- Subject: Unit netctl-auto@wlp2s0.interface.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl-auto@wlp2s0.interface.service has failed.
-- 
-- The result is dependency.
Dec 11 00:05:21 hydra systemd[1]: netctl-auto@wlp2s0.interface.service: Job netctl-auto@wlp2s0.interface.service/start failed with result 'dependency'.
Dec 11 00:05:21 hydra systemd[1]: sys-subsystem-net-devices-wlp2s0.interface.device: Job sys-subsystem-net-devices-wlp2s0.interface.device/start failed with result 'timeout'.
Dec 11 00:05:21 hydra polkitd[482]: Unregistered Authentication Agent for unix-process:28518:64817 (system bus name :1.12, object path /org/freedesktop/PolicyKit1/Authenticat

I'm very new to this kind of debugging and I apologize if this is something that I should know already. I will try to downgrade wpa_supplicant, but I would love a pointer in how to do that. I appreciate all the help.

Head_on_a_Stick · 2015-12-12 19:42:33

tutu wrote:

I will try to downgrade wpa_supplicant, but I would love a pointer in how to do that

https://wiki.archlinux.org/index.php/Do … g_packages

Arch Linux

#1 2015-04-25 05:08:14

netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#2 2015-04-25 05:52:39

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#3 2015-04-25 09:22:58

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#4 2015-04-25 11:44:20

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#5 2015-04-25 12:21:17

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#6 2015-04-25 14:47:46

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#7 2015-04-25 15:46:39

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#8 2015-04-25 16:07:05

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#9 2015-04-25 16:11:19

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#10 2015-04-25 16:39:30

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#11 2015-04-26 11:25:18

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#12 2015-04-26 12:10:26

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#13 2015-04-26 16:12:55

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#14 2015-04-27 09:27:59

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#15 2015-04-29 17:05:04

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#16 2015-04-29 17:45:22

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#17 2015-12-07 23:08:59

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#18 2015-12-08 02:23:25

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#19 2015-12-08 09:08:04

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#20 2015-12-09 06:09:57

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#21 2015-12-09 16:30:47

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#22 2015-12-10 20:45:13

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#23 2015-12-11 03:53:13

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#24 2015-12-11 16:19:46

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

#25 2015-12-12 19:42:33

Re: netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

Board footer