FS#68987 - iwlwifi - Authentication with <AP MAC> timed out
Attached to Project:
Arch Linux
Opened by Jeremy DeJournett (ijustlovemath) - Tuesday, 15 December 2020, 14:51 GMT
Last edited by Toolybird (Toolybird) - Thursday, 02 March 2023, 06:17 GMT
Opened by Jeremy DeJournett (ijustlovemath) - Tuesday, 15 December 2020, 14:51 GMT
Last edited by Toolybird (Toolybird) - Thursday, 02 March 2023, 06:17 GMT
|
Details
Description:
This seems to be related to https://bugs.archlinux.org/task/39815 , which was apparently fixed almost 6 years ago. This laptop has worked fine with my DDWRT router/AP (Archer C7) for many years, and it's only after cold booting it after a month or so of no usage that it no longer wants to associate with my AP anymore. This is not a hardware issue, as it connects to a mobile hotspot just fine (that's how I'm posting this bug) Additional info: * package version(s) (see packages.txt, attached) * config and/or log files etc. The timeout lines in question are in journalctl2.log, but I'll copy the most important ones here: ``` Dec 15 09:00:45 x220 kernel: wlp3s0: authenticate with 04:1b:6d:fa:3c:3a Dec 15 09:00:45 x220 kernel: wlp3s0: send auth to 04:1b:6d:fa:3c:3a (try 1/3) Dec 15 09:00:45 x220 kernel: wlp3s0: send auth to 04:1b:6d:fa:3c:3a (try 2/3) Dec 15 09:00:45 x220 kernel: wlp3s0: send auth to 04:1b:6d:fa:3c:3a (try 3/3) Dec 15 09:00:45 x220 kernel: wlp3s0: authentication with 04:1b:6d:fa:3c:3a timed out ``` ``` % cat /etc/systemd/network/00-default.link [Match] MACAddress=74:e5:0b:e7:7b:50 [Link] MACAddressPolicy=random NamePolicy=kernel database onboard slot path 8:56 @x220 /home/ % cat /etc/systemd/network/25-wireless.network [Match] Name=wl* [Network] DHCP=yes #DHCPServer=yes LinkLocalAddressing=ipv4 ``` * link to upstream bug report, if any `dmesg | grep iwlwifi` ``` [ 3.252511] iwlwifi 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control [ 3.254760] iwlwifi 0000:03:00.0: loaded firmware version 39.31.5.1 build 35138 op_mode iwldvm [ 3.858396] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG enabled [ 3.858398] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS enabled [ 3.858400] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled [ 3.858402] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Wireless-N 1000 BGN, REV=0x6C [ 3.900684] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0 [ 3.979814] iwlwifi 0000:03:00.0: Radio type=0x0-0x0-0x3 [ 4.058169] iwlwifi 0000:03:00.0: Radio type=0x0-0x0-0x3 [ 30.376504] iwlwifi 0000:03:00.0: Radio type=0x0-0x0-0x3 [ 30.449649] iwlwifi 0000:03:00.0: Radio type=0x0-0x0-0x3 ``` Here's my `systemd-analyze blame` ``` 1min 16.724s systemd-networkd-wait-online.service > 2.748s systemd-random-seed.service > 2.061s systemd-resolved.service > 625ms netctl-auto@wlp3s0.service > 602ms lvm2-monitor.service > 475ms tlp.service > 409ms dev-sda2.device > 257ms upower.service > 187ms systemd-journal-flush.service > 94ms systemd-logind.service > 92ms systemd-rfkill.service > 90ms user@1000.service > 89ms systemd-udev-trigger.service > 88ms systemd-journald.service > 88ms systemd-networkd.service > 84ms polkit.service > 83ms systemd-udevd.service > 71ms systemd-fsck@dev-disk-by\x2duuid-d8d30129\x2dec2c\x2d48d3\x2d8b19\x2d9f4ec3ccc876.s> 67ms systemd-fsck@dev-disk-by\x2duuid-c1bf01f1\x2d7127\x2d4408\x2da382\x2dd031fcf6f969.s> 65ms modprobe@drm.service > 54ms systemd-binfmt.service > 40ms dev-disk-by\x2duuid-0a3f47ab\x2dc109\x2d4a4b\x2d95ab\x2db623763d9f3f.swap > 39ms systemd-tmpfiles-setup-dev.service > 32ms sys-fs-fuse-connections.mount > 31ms sys-kernel-config.mount > 28ms boot.mount > 28ms systemd-tmpfiles-setup.service > 27ms lightdm.service > 25ms home.mount > 25ms ntpd.service > 23ms dev-hugepages.mount > 22ms dev-mqueue.mount > 21ms sys-kernel-debug.mount > 21ms sys-kernel-tracing.mount > 20ms kmod-static-nodes.service > 19ms modprobe@fuse.service > 19ms systemd-modules-load.service > 18ms bluetooth.service > 18ms modprobe@configfs.service > 18ms systemd-remount-fs.service > 13ms proc-sys-fs-binfmt_misc.mount > 12ms systemd-backlight@backlight:acpi_video0.service > 10ms user-runtime-dir@1000.service > 10ms systemd-sysctl.service > 9ms tmp.mount ``` Steps to reproduce: 1. Restart netctl-auto@wlp3s0.service 2. Watch the timeouts roll in |
This task depends upon
Closed by Toolybird (Toolybird)
Thursday, 02 March 2023, 06:17 GMT
Reason for closing: None
Additional comments about closing: Very old/stale bug. Please request reopen if still reproducible on current kernels.
Thursday, 02 March 2023, 06:17 GMT
Reason for closing: None
Additional comments about closing: Very old/stale bug. Please request reopen if still reproducible on current kernels.