From: James Prestwood <prestwoj at gmail.com>
To: iwd at lists.01.org
Subject: Re: iwd fails to create device
Date: Tue, 31 May 2022 09:06:01 -0700 [thread overview]
Message-ID: <fcf4e3fa19e68156e95e379fafe59a0929c32a76.camel@gmail.com> (raw)
In-Reply-To: 20220528192423.2134.31838@ml01.vlan13.01.org
[-- Attachment #1: Type: text/plain, Size: 11367 bytes --]
Hi,
On Sat, 2022-05-28 at 19:24 +0000,
1148d778-20a8-4ab0-96b7-24572ddab965(a)simplelogin.co wrote:
> Hi,
>
> A few times I've already seen a strange behaviour right after
> rebooting. All of the sudden the wifi card is no longer available. To
> me it looks like iwd fails to detect and rename the device. Hopefully
> it happens very seldom.
>
> $ journalctl -b -1 | grep -i wifi
> may 27 12:02:52 kernel: Intel(R) Wireless WiFi driver for Linux
> may 27 12:02:52 kernel: iwlwifi 0000:03:00.0: enabling device (0000 ->
> 0002)
> may 27 12:02:52 kernel: iwlwifi 0000:03:00.0: Direct firmware load for
> iwlwifi-cc-a0-69.ucode failed with error -2
> may 27 12:02:52 kernel: iwlwifi 0000:03:00.0: api flags index 2 larger
> than supported by driver
> may 27 12:02:52 kernel: iwlwifi 0000:03:00.0: TLV_FW_FSEQ_VERSION: FSEQ
> Version: 89.3.35.37
> may 27 12:02:52 kernel: iwlwifi 0000:03:00.0: loaded firmware version
> 68.01d30b0c.0 cc-a0-68.ucode op_mode iwlmvm
> may 27 12:02:52 kernel: iwlwifi 0000:03:00.0: Detected Intel(R) Wi-Fi 6
> AX200 160MHz, REV=0x340
> may 27 12:02:53 kernel: iwlwifi 0000:03:00.0: Detected RF HR B3,
> rfid=0x10a100
> may 27 12:02:53 kernel: iwlwifi 0000:03:00.0: base HW address:
> xx:xx:xx:xx:xx:xx
>
>
> $ journalctl -b -1 | grep -i iwd
> may 27 12:02:53 iwd[863]: Wireless daemon version 1.27
> may 27 12:02:53 iwd[863]: Loaded configuration from /etc/iwd/main.conf
> may 27 12:02:53 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
> ses=4294967295 msg='unit=iwd comm="systemd"
> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
> res=success'
> may 27 12:02:53 iwd[863]: Wiphy: 0, Name: phy0
> may 27 12:02:53 iwd[863]: Permanent Address: xx:xx:xx:xx:xx:xx
> may 27 12:02:53 iwd[863]: 2.4Ghz Band:
> may 27 12:02:53 iwd[863]: Bitrates (non-HT):
> may 27 12:02:53 iwd[863]: 1.0 Mbps
> may 27 12:02:53 iwd[863]: 2.0 Mbps
> may 27 12:02:53 iwd[863]: 5.5 Mbps
> may 27 12:02:53 iwd[863]: 11.0 Mbps
> may 27 12:02:53 iwd[863]: 6.0 Mbps
> may 27 12:02:53 iwd[863]: 9.0 Mbps
> may 27 12:02:53 iwd[863]: 12.0 Mbps
> may 27 12:02:53 iwd[863]: 18.0 Mbps
> may 27 12:02:53 iwd[863]: 24.0 Mbps
> may 27 12:02:53 iwd[863]: 36.0 Mbps
> may 27 12:02:53 iwd[863]: 48.0 Mbps
> may 27 12:02:53 iwd[863]: 54.0 Mbps
> may 27 12:02:53 iwd[863]: HT Capabilities:
> may 27 12:02:53 iwd[863]: HT40
> may 27 12:02:53 iwd[863]: Short GI for 20Mhz
> may 27 12:02:53 iwd[863]: Short GI for 40Mhz
> may 27 12:02:53 iwd[863]: HT RX MCS indexes:
> may 27 12:02:53 iwd[863]: 0-15
> may 27 12:02:53 iwd[863]: 5Ghz Band:
> may 27 12:02:53 iwd[863]: Bitrates (non-HT):
> may 27 12:02:53 iwd[863]: 6.0 Mbps
> may 27 12:02:53 iwd[863]: 9.0 Mbps
> may 27 12:02:53 iwd[863]: 12.0 Mbps
> may 27 12:02:53 iwd[863]: 18.0 Mbps
> may 27 12:02:53 iwd[863]: 24.0 Mbps
> may 27 12:02:53 iwd[863]: 36.0 Mbps
> may 27 12:02:53 iwd[863]: 48.0 Mbps
> may 27 12:02:53 iwd[863]: 54.0 Mbps
> may 27 12:02:53 iwd[863]: HT Capabilities:
> may 27 12:02:53 iwd[863]: HT40
> may 27 12:02:53 iwd[863]: Short GI for 20Mhz
> may 27 12:02:53 iwd[863]: Short GI for 40Mhz
> may 27 12:02:53 iwd[863]: HT RX MCS indexes:
> may 27 12:02:53 iwd[863]: 0-15
> may 27 12:02:53 iwd[863]: VHT Capabilities:
> may 27 12:02:53 iwd[863]: 160 Mhz operation
> may 27 12:02:53 iwd[863]: Short GI for 80Mhz
> may 27 12:02:53 iwd[863]: Short GI for 160 and
> 80 + 80 Mhz
> may 27 12:02:53 iwd[863]: Max RX MCS: 0-9 for
> NSS: 2
> may 27 12:02:53 iwd[863]: Max TX MCS: 0-9 for
> NSS: 2
> may 27 12:02:53 iwd[863]: Ciphers: CCMP TKIP BIP
> may 27 12:02:53 iwd[863]: Supported iftypes: ad-hoc station ap
> p2p-client p2p-go p2p-device
> may 27 12:02:53 iwd[863]: Unable to add the net.connman.iwd.Adapter
> interface to /net/connman/iwd/0
> may 27 12:02:53 iwd[863]: Unable to add the
> org.freedesktop.DBus.Properties interface to /net/connman/iwd/0
> may 27 12:02:53 iwd[863]: Wiphy: 0, Name: phy0
> may 27 12:02:53 iwd[863]: Permanent Address: xx:xx:xx:xx:xx:xx
> may 27 12:02:53 iwd[863]: 2.4Ghz Band:
> may 27 12:02:53 iwd[863]: Bitrates (non-HT):
> may 27 12:02:53 iwd[863]: 1.0 Mbps
> may 27 12:02:53 iwd[863]: 2.0 Mbps
> may 27 12:02:53 iwd[863]: 5.5 Mbps
> may 27 12:02:53 iwd[863]: 11.0 Mbps
> may 27 12:02:53 iwd[863]: 6.0 Mbps
> may 27 12:02:53 iwd[863]: 9.0 Mbps
> may 27 12:02:53 iwd[863]: 12.0 Mbps
> may 27 12:02:53 iwd[863]: 18.0 Mbps
> may 27 12:02:53 iwd[863]: 24.0 Mbps
> may 27 12:02:53 iwd[863]: 36.0 Mbps
> may 27 12:02:53 iwd[863]: 48.0 Mbps
> may 27 12:02:53 iwd[863]: 54.0 Mbps
> may 27 12:02:53 iwd[863]: HT Capabilities:
> may 27 12:02:53 iwd[863]: HT40
> may 27 12:02:53 iwd[863]: Short GI for 20Mhz
> may 27 12:02:53 iwd[863]: Short GI for 40Mhz
> may 27 12:02:53 iwd[863]: HT RX MCS indexes:
> may 27 12:02:53 iwd[863]: 0-15
> may 27 12:02:53 iwd[863]: 5Ghz Band:
> may 27 12:02:53 iwd[863]: Bitrates (non-HT):
> may 27 12:02:53 iwd[863]: 6.0 Mbps
> may 27 12:02:53 iwd[863]: 9.0 Mbps
> may 27 12:02:53 iwd[863]: 12.0 Mbps
> may 27 12:02:53 iwd[863]: 18.0 Mbps
> may 27 12:02:53 iwd[863]: 24.0 Mbps
> may 27 12:02:53 iwd[863]: 36.0 Mbps
> may 27 12:02:53 iwd[863]: 48.0 Mbps
> may 27 12:02:53 iwd[863]: 54.0 Mbps
> may 27 12:02:53 iwd[863]: HT Capabilities:
> may 27 12:02:53 iwd[863]: HT40
> may 27 12:02:53 iwd[863]: Short GI for 20Mhz
> may 27 12:02:53 iwd[863]: Short GI for 40Mhz
> may 27 12:02:53 iwd[863]: HT RX MCS indexes:
> may 27 12:02:53 iwd[863]: 0-15
> may 27 12:02:53 iwd[863]: VHT Capabilities:
> may 27 12:02:53 iwd[863]: 160 Mhz operation
> may 27 12:02:53 iwd[863]: Short GI for 80Mhz
> may 27 12:02:53 iwd[863]: Short GI for 160 and
> 80 + 80 Mhz
> may 27 12:02:53 iwd[863]: Max RX MCS: 0-9 for
> NSS: 2
> may 27 12:02:53 iwd[863]: Max TX MCS: 0-9 for
> NSS: 2
> may 27 12:02:53 iwd[863]: Ciphers: CCMP TKIP BIP
> may 27 12:02:53 iwd[863]: Supported iftypes: ad-hoc station ap
> p2p-client p2p-go p2p-device
> may 27 12:02:53 iwd[863]: DEL_INTERFACE failed: No such device
> may 27 12:02:53 iwd[863]: Could not register frame watch type 00d0: -19
> may 27 12:02:53 iwd[863]: RTM_GETLINK error -19: No such device
> may 27 12:02:53 iwd[863]: Could not register frame watch type 00d0: -19
> may 27 12:02:53 iwd[863]: Could not register frame watch type 00d0: -19
> may 27 12:02:53 iwd[863]: Could not register frame watch type 00d0: -19
> may 27 12:02:53 iwd[863]: Could not register frame watch type 00d0: -19
> may 27 12:03:31 iwd[863]: D-Bus disconnected, quitting...
> may 27 12:03:32 iwd[863]: Terminate
> may 27 12:03:32 iwd[863]: Removing scan context for wdev 2
> may 27 12:03:33 systemd[1]: iwd.service: Deactivated successfully.
This looks very familiar to an issue we fixed with dual-phy cards, but
this isn't the case for you. Its as if your phy is being detected
twice.
It would be great if you could get some iwmon logs when this happens.
Hopefully it happens frequent enough you can get a capture. More info
about how to do that can be found here:
https://iwd.wiki.kernel.org/debugging
>
> Arch Linux wiki on iwd troubleshooting mentions two issues that look
> possible causes to me:
> - Low entropy pool
> - Wireless device not renamed by udev
>
> You can check it here:
> https://wiki.archlinux.org/title/Iwd#Troubleshooting
>
> Any help to fix this issue would be appreciated.
>
> Thanks!
> _______________________________________________
> iwd mailing list -- iwd(a)lists.01.org
> To unsubscribe send an email to iwd-leave(a)lists.01.org
next reply other threads:[~2022-05-31 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 16:06 James Prestwood [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-31 20:17 iwd fails to create device James Prestwood
2023-01-15 15:53 ` Kevin Boulain
2023-01-17 18:30 ` James Prestwood
2023-01-17 20:23 ` Kevin Boulain
2022-05-31 18:39 1148d778-20a8-4ab0-96b7-24572ddab965
2022-05-28 19:24 1148d778-20a8-4ab0-96b7-24572ddab965
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fcf4e3fa19e68156e95e379fafe59a0929c32a76.camel@gmail.com \
--to=unknown@example.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.