From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.01.org
Subject: Re: DEL_INTERFACE and CMD_SET_CQM failed; Could not register frame watch type 00d0: -95
Date: Mon, 19 Apr 2021 09:07:04 -0700 [thread overview]
Message-ID: <8567bf1d8aec2230ad7b46a57ed0e8a320c28e22.camel@gmail.com> (raw)
In-Reply-To: <B8SRRQ.IJ5TG5C88S3O3@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5529 bytes --]
Hi Philip,
On Sun, 2021-04-18 at 18:21 +0100, Philip Stewart wrote:
> Hello,
>
> I've recently switched from NetworkManager and wpasupplicant to
> systemd-networkd and iwd. Whilst everything appears to be working
> fine,
> I'm curious about some failures reported by iwd:
>
> Apr 18 15:10:32 systemd[1]: Starting Wireless service...
> Apr 18 15:10:33 iwd[661]: Wireless daemon version 1.12
> Apr 18 15:10:33 systemd[1]: Started Wireless service.
> Apr 18 15:10:33 iwd[661]: station: Network configuration is disabled.
> Apr 18 15:10:33 iwd[661]: Wiphy: 0, Name: phy0
> Apr 18 15:10:33 iwd[661]: Permanent Address:
> 00:00:00:00:00:00
> Apr 18 15:10:33 iwd[661]: Bands: 2.4 GHz 5 GHz
> Apr 18 15:10:33 iwd[661]: Ciphers: CCMP TKIP BIP
> Apr 18 15:10:33 iwd[661]: Supported iftypes: ad-hoc station
> Apr 18 15:10:33 iwd[661]: DEL_INTERFACE failed: Operation not
> supported
> Apr 18 15:10:33 iwd[661]: Could not register frame watch type 00d0:
> -95
> Apr 18 15:10:33 iwd[661]: Could not register frame watch type 00d0:
> -95
> Apr 18 15:10:33 iwd[661]: Could not register frame watch type 00d0:
> -95
> Apr 18 15:10:33 iwd[661]: Could not register frame watch type 00d0:
> -95
> Apr 18 15:10:33 iwd[661]: CMD_SET_CQM failed: Operation not supported
> Apr 18 15:10:33 iwd[661]: Could not register frame watch type 00d0:
> -95
> Apr 18 15:10:33 iwd[661]: Could not register frame watch type 00d0:
> -95
>
> Further, I note that in the output of 'networkctl status wlan0', the
> WiFi access point MAC address is reported as 00:00:00:00:00:00 and
> I'm
> wondering if this is a consequence of these failures and if there is
> anything I can do about it?
I'm not familiar with the wl driver specifically but I'm guessing it
does not support DEL_INTERFACE/CQM.
This is fine though. In the DEL_INTERFACE case IWD will just use the
interface that already exists on the system. Effectively
[General].UseDefaultInterface=true.
CQM is also ok as the driver (presumably) manages low RSSI itself and
will roam on its own. At least this is what I would expect.
We pull the permanent address from
/sys/class/ieee80211/<phy>/macaddress. Is that reporting zero's?
Thanks,
James
>
> Kind regards,
> Phil
>
> # lspci -vv -d 14e4:
> 03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4322
> 802.11a/b/g/n Wireless LAN Controller (rev 01)
> Subsystem: Apple Inc. AirPort Extreme
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr-
> Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0, Cache Line Size: 256 bytes
> Interrupt: pin A routed to IRQ 20
> Region 0: Memory at d3200000 (64-bit, non-prefetchable)
> [size=16K]
> Capabilities: [40] Power Management version 3
> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
> PME(D0+,D1-,D2-,D3hot+,D3cold+)
> Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=2 PME-
> Capabilities: [58] Vendor Specific Information: Len=78 <?>
> Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+
> Address: 0000000000000000 Data: 0000
> Capabilities: [d0] Express (v1) Endpoint, MSI 00
> DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency
> L0s <4us, L1
> unlimited
> ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
> SlotPowerLimit 0.000W
> DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
> RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop-
> MaxPayload 128 bytes, MaxReadReq 128 bytes
> DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq-
> AuxPwr- TransPend-
> LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s
> L1, Exit Latency
> L0s <4us, L1 <64us
> ClockPM+ Surprise- LLActRep- BwNot-
> ASPMOptComp-
> LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes, Disabled-
> CommClk+
> ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
> LnkSta: Speed 2.5GT/s (ok), Width x1 (ok)
> TrErr- Train- SlotClk+ DLActive- BWMgmt-
> ABWMgmt-
> Capabilities: [100 v1] Advanced Error Reporting
> UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt-
> UnxCmplt- RxOF-
> MalfTLP- ECRC- UnsupReq- ACSViol-
> UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt-
> UnxCmplt- RxOF-
> MalfTLP- ECRC- UnsupReq- ACSViol-
> UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt-
> UnxCmplt- RxOF+
> MalfTLP+ ECRC- UnsupReq- ACSViol-
> CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout-
> AdvNonFatalErr-
> CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout-
> AdvNonFatalErr+
> AERCap: First Error Pointer: 00, ECRCGenCap+
> ECRCGenEn- ECRCChkCap+
> ECRCChkEn-
> MultHdrRecCap- MultHdrRecEn- TLPPfxPres-
> HdrLogCap-
> HeaderLog: 00000000 00000000 00000000 00000000
> Capabilities: [13c v1] Virtual Channel
> Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
> Arb: Fixed- WRR32- WRR64- WRR128-
> Ctrl: ArbSelect=Fixed
> Status: InProgress-
> VC0: Caps: PATOffset=00 MaxTimeSlots=1
> RejSnoopTrans-
> Arb: Fixed- WRR32- WRR64- WRR128- TWRR128-
> WRR256-
> Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
> Status: NegoPending- InProgress-
> Capabilities: [160 v1] Device Serial Number xx-xx-xx-xx-xx-xx-
> xx-xx
> Capabilities: [16c v1] Power Budgeting <?>
> Kernel driver in use: wl
> Kernel modules: ssb, wl
>
>
> _______________________________________________
> iwd mailing list -- iwd(a)lists.01.org
> To unsubscribe send an email to iwd-leave(a)lists.01.org
next prev parent reply other threads:[~2021-04-19 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 17:21 DEL_INTERFACE and CMD_SET_CQM failed; Could not register frame watch type 00d0: -95 Philip Stewart
2021-04-19 16:07 ` James Prestwood [this message]
2021-04-19 18:16 ` Philip Stewart
2021-04-19 19:06 ` James Prestwood
2021-04-19 19:58 ` Philip Stewart
2021-04-19 20:10 ` James Prestwood
2021-04-19 20:41 ` Philip Stewart
2021-04-19 20:55 ` Denis Kenzior
2021-04-19 21:25 ` Philip Stewart
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=8567bf1d8aec2230ad7b46a57ed0e8a320c28e22.camel@gmail.com \
--to=prestwoj@gmail.com \
--cc=iwd@lists.01.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox