FS#43605 - [wpa_actiond] terminates on startup when RFKILL enabled
Attached to Project:
Arch Linux
Opened by Olivier Mehani (shtrom) - Wednesday, 28 January 2015, 02:24 GMT
Last edited by freswa (frederik) - Monday, 07 September 2020, 20:22 GMT
Opened by Olivier Mehani (shtrom) - Wednesday, 28 January 2015, 02:24 GMT
Last edited by freswa (frederik) - Monday, 07 September 2020, 20:22 GMT
|
Details
Description:
I'm using netctl-auto to manage a wireless card (Intel(R) Dual Band Wireless AC 7260, REV=0x144; firmware version 23.10.10.0 op_mode iwlmvm) on a Dell Latitude E7440 (0JNYGR, BIOS A11 08/28/2014). When the RFKILL switch is initially on, then disabled the card never gets an IP address. When it is off when netct-auto is started, everything works as expected. This appears to be due to wpa_actiond terminating (Terminating wpa_actiond session for interface 'wlp2s0') when it is first started (by netctl-auto) on an interface with the RKFILL bit on. Additional info: * wpa_actiond 1.4-2 * wpa_supplicant 2.3-1 * netctl 1.10-1 * dhcpcd 6.6.7-1 Steps to reproduce: [working.log] * sudo systemctl stop netctl-auto@wlp2s0.service * Switch RFKILL off * sudo systemctl start netctl-auto@wlp2s0.service -> wpa_supplicant and wpa_actiond start -> interface authenticates to network -> dhcpcd starts -> interface gets an IPv4 address * Switch RFKILL on -> interface disconnects from network -> eventually, IPv4 is removed * Switch RFKILL off -> wpa_supplicant and wpa_actiond start -> interface authenticates to network -> dhcpcd starts -> interface gets an IPv4 address [failure.log] * sudo systemctl stop netctl-auto@wlp2s0.service * Switch RFKILL on * sudo systemctl start netctl-auto@wlp2s0.service -> wpa_supplicant and wpa_actiond start -> wpa_actiond terminates with "Terminating wpa_actiond session for interface 'wlp2s0'" * Switch RFKILL off -> interface authenticates to network -> dhcpd is not started -> no IPv4 is configured on interface * Switch RFKILL on -> interface disconnects from network * Switch RFKILL off -> interface authenticates to network -> dhcpd is not started -> no IPv4 is configured on interface |
This task depends upon
Closed by freswa (frederik)
Monday, 07 September 2020, 20:22 GMT
Reason for closing: Won't fix
Additional comments about closing: Package has been dropped from repositories
Monday, 07 September 2020, 20:22 GMT
Reason for closing: Won't fix
Additional comments about closing: Package has been dropped from repositories
Comment by Olivier Mehani (shtrom) -
Wednesday, 28 January 2015, 03:46 GMT
Comment by Olivier Mehani (shtrom) -
Wednesday, 28 January 2015, 03:51 GMT
The problem seems to be with the initial select. See the following
straces.
The first select timeouts, leading to termination.