FS#55456 - [netctl] 1.13-2 won't connect to wireless network

Attached to Project: Arch Linux
Opened by Alin Porcic (onixion) - Friday, 01 September 2017, 14:18 GMT
Last edited by Jouke Witteveen (jouke) - Sunday, 08 October 2017, 07:53 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Jouke Witteveen (jouke)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After upgrading the system the wireless netctl scripts stopped working.
I first thought that the issue only affected the iwlwifi driver, but
rt5370 (rt2800usb) (usb wireless adapter) also didn't work.

After downgrading the netctl package to netctl 1.12-2 my scripts
worked again. So something is up with the package netctl 1.13-2 (at least on
my machine).


Additional info:

netctl 1.13-2
linux-firmware 20170622.7d2c913-1
Linux archlinux 4.9.46-1-lts #1 SMP Wed Aug 30 17:49:09 CEST 2017 x86_64 GNU/Linux


Attached files:

home.conf - Netctl config file for home
hotspot.conf - Netctl config file for hotspot

home.txt - Is the dmesg output after trying to connect with 'home.conf' (using iwlwifi driver)
hotspot.txt - Is the journal output after trying to connect with 'hotspot.conf' (using rt2800usb driver)


Steps to reproduce:

(remove '.conf' ending and place config files in /etc/netctl/ folder)

netctl start home
netctl start hotspot

   home.conf (0.1 KiB)
   home.txt (5.4 KiB)
   hotspot.conf (0.2 KiB)
   hotspot.txt (0.7 KiB)
This task depends upon

Closed by  Jouke Witteveen (jouke)
Sunday, 08 October 2017, 07:53 GMT
Reason for closing:  Not a bug
Comment by Alin Porcic (onixion) - Friday, 01 September 2017, 14:32 GMT
lsmod
   lsmod.txt (5.1 KiB)
Comment by Alin Porcic (onixion) - Friday, 01 September 2017, 14:33 GMT
dmesg
   dmesg.txt (63.6 KiB)
Comment by Jouke Witteveen (jouke) - Saturday, 16 September 2017, 10:16 GMT
This really puzzles me. Your files only show a driver problem that should be entirely independent of netctl. The only change in netctl 1.13 that should be noticeable is faster start-up because it now correctly implements network.target logic. Basically, the old behavior can be restored by adding 'WaitOnline=yes' to your profile files. However, I completely fail to see how that would make a difference in your case. Is this problem even still present?
Comment by Alin Porcic (onixion) - Sunday, 17 September 2017, 13:49 GMT
Problem still present. Currently I am using 1.12 without any problems. When executing "netctl start home" with 1.13 I got this (see error.txt). Then I tried 'WaitOnline=Yes', but with 1.13 I get a timeout error (see timeout.txt) instead of the usual error (see error.txt).

edit.: I also tried disabling IPv6 support with linux cmd, still not working.
   error.txt (10.3 KiB)
   timeout.txt (1.2 KiB)
Comment by Jouke Witteveen (jouke) - Sunday, 17 September 2017, 13:55 GMT
Are you sure netctl is the only thing you down-/upgrade and not some other kernel/firmware packages as well? These errors appear unrelated to netctl. Did you make any custom edits to the netctl services? Maybe re-enabling (`netctl reenable`) them helps. If not, please post the journal output with 'NETCTL_DEBUG=yes' added to your profile.
Comment by Alin Porcic (onixion) - Sunday, 17 September 2017, 14:07 GMT
I upgraded to 1.13 with this:

netctl stop-all
pacman -U /var/cache/pacman/pkg/netctl-1.13-2-any.pkg.tar.xz
systemctl daemon-reload

(edited the config; see new_config.txt)

netctl reenable home
netctl start home

The I got this (see new.txt). No other packages where upgraded or downgraded.
When switching back to 1.12, I have to "ip link set wlp3s0 down" because 1.13 leaves the network interface "up".



   new_config.txt (0.2 KiB)
   new.txt (1.1 KiB)
Comment by Jouke Witteveen (jouke) - Sunday, 17 September 2017, 14:18 GMT
So systemd says the netctl service has timed out after 1 second?! I am out of ideas... I'll report back when I have one again, but I am pretty sure netctl is not the root cause and there is some other problem with your setup. Just to be sure, there are no dropins for your netctl service either, right?
Comment by Alin Porcic (onixion) - Sunday, 17 September 2017, 14:26 GMT
No drop-in files for nectl@home.service. The folder /etc/systemd/system/netctl@home.d/ does not exist.
Thanks for the great support :)
Comment by Jouke Witteveen (jouke) - Monday, 18 September 2017, 19:44 GMT
Here is another idea. What is the output for the following profile under 1.13?

----
Description=test
Interface=test
Connection=dummy
IP=no
ExecUpPost='sleep 3'
WaitOnline=yes
NETCTL_DEBUG=yes
----

This should not really 'do' anything, other than waiting 3 seconds. If it also gets a timeout, than somehow systemd is configured with a very short TimeoutStartSec. If it does not crash, then probably the driver problems somehow convince systemd to trigger a timeout.
Comment by Alin Porcic (onixion) - Monday, 18 September 2017, 21:17 GMT
Yes got a timeout with 1.13 (see 1_13.txt).
1.12 seems to work (see 1_12.txt) (note: I renamed the interface to 'test2').
   1_12.txt (0.9 KiB)
   1_13.txt (1.3 KiB)
Comment by Alin Porcic (onixion) - Monday, 18 September 2017, 21:26 GMT
Last year systemd started to waste 30 seconds on every shutdown ("stop job running for ..."). So I googled and modified this in my '/etc/systemd/system.conf':

DefaultTimeoutStartSec=1s
DefaultTimeoutStopSec=1s

When I uncomment this and make a 'daemon-reload', 1.13 works again ...
I just change it to 5 seconds or something.

Thanks Jouke for wasting your time helping me. You can close this bug. :D
Comment by Jouke Witteveen (jouke) - Tuesday, 19 September 2017, 10:22 GMT
Ouch, that's quite a terrible workaround if I may say so ;-).

Thanks for getting back with the root cause of the problem and your input in debugging this issue!

Loading...