NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/57992: urtwn (and athn) driver lost network when WIFI router changes channel
The following reply was made to PR kern/57992; it has been noted by GNATS.
From: Ramiro Aceves <ea1abz%gmail.com@localhost>
To: "gnats-bugs%netbsd.org@localhost" <gnats-bugs%netbsd.org@localhost>
Cc: "kern-bug-people%netbsd.org@localhost" <kern-bug-people%netbsd.org@localhost>,
"gnats-admin%netbsd.org@localhost" <gnats-admin%netbsd.org@localhost>, "netbsd-bugs%netbsd.org@localhost" <netbsd-bugs%netbsd.org@localhost>,
netbsd-users <netbsd-users%netbsd.org@localhost>
Subject: Re: kern/57992: urtwn (and athn) driver lost network when WIFI router
changes channel
Date: Fri, 8 Mar 2024 08:45:55 +0100
--000000000000d5a70e06132161aa
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
El domingo, 3 de marzo de 2024, Michael van Elst <mlelstv%serpens.de@localhost>
escribi=C3=B3:
> The following reply was made to PR kern/57992; it has been noted by GNATS=
.
>
> From: mlelstv%serpens.de@localhost (Michael van Elst)
> To: gnats-bugs%netbsd.org@localhost
> Cc:
> Subject: Re: kern/57992: urtwn (and athn) driver lost network when WIFI
router changes channel
> Date: Sun, 3 Mar 2024 13:29:58 -0000 (UTC)
>
> ea1abz%gmail.com@localhost writes:
>
> >If I force a channel change in the router, the network is lost and I
cannot recover it. "service wpa_supplicant restart" does not recover
network. "ifconfig urtwn0 down" and up does not fix it.
>
> While I can confirm that a channel change isn't recognized with urtwn(4)=
,
> a restart of wpa_supplicant (or just a "scan" request from wpa_cli)
> causes a new scan and association with the network.
>
> An attempt to enable automatic scanning using the roaming options
> (e.g. bgscan) in wpa_supplicant.conf didn't help.
>
> N.B. The same experiment with iwm(4) causes a disconnect as soon as the
> access point switches channels and an immediate scan, but afterwards
> the scan results are always truncated and the network is never found.
> Only a reboot recovers iwm(4) from this state.
>
>
Thanks Michael for sharing your experience.
Yesterday I faced a new scenario. My raspberry pi zero w for unknown reason
lost the network.
My rebooting script detected it and rebooted the system but network did not
recover. I connected the TV and I see that the system rebooted several
times but network did no work. Each reboot spaced 15minutes cause my
rebooting script used 3 ping retries at 5min intervals:
netbsd-raspa# zcat /var/log/messages.0.gz|grep firm
Mar 7 18:44:40 netbsd-raspa /netbsd: [ 9.1275860] urtwn0:
autoconfiguration error: timeout waiting for firmware readinessMar 7
18:44:40 netbsd-raspa /netbsd: [ 10.0384860] urtwn0: autoconfiguration
error: timeout waiting for firmware readinessMar 7 19:00:04 netbsd-raspa
/netbsd: [ 1.0000000] /soc/firmware at simplebus1 not configured
Mar 7 19:00:04 netbsd-raspa /netbsd: [ 9.0872570]
urtwn0: autoconfiguration error: timeout waiting for firmware readinessMar
7 19:00:04 netbsd-raspa /netbsd: [ 9.9782020] urtwn0: autoconfiguration
error: timeout waiting for firmware readinessMar 7 19:15:28 netbsd-raspa
/netbsd: [ 1.0000000] /soc/firmware at simplebus1 not configured
Mar 7 19:15:28 netbsd-raspa /netbsd: [ 9.1372840]
urtwn0: autoconfiguration error: timeout waiting for firmware readinessMar
7 19:15:28 netbsd-raspa /netbsd: [ 9.9581270] urtwn0: autoconfiguration
error: timeout waiting for firmware readinessMar 7 19:30:52 netbsd-raspa
/netbsd: [ 1.0000000] /soc/firmware at simplebus1 not configured
Mar 7 19:30:52 netbsd-raspa /netbsd: [ 9.0873250]
urtwn0: autoconfiguration error: timeout waiting for firmware readinessMar
7 19:30:52 netbsd-raspa /netbsd: [ 9.9982810] urtwn0: autoconfiguration
error: timeout waiting for firmware readinessMar 7 19:46:16 netbsd-raspa
/netbsd: [ 1.0000000] /soc/firmware at simplebus1 not configured
Mar 7 19:46:16 netbsd-raspa /netbsd: [ 9.0172810]
urtwn0: autoconfiguration error: timeout waiting for firmware readinessMar
7 19:46:16 netbsd-raspa /netbsd: [ 9.8881610] urtwn0: autoconfiguration
error: timeout waiting for firmware readinessnetbsd-raspa#
Some errors including wpa_supplicant messages:
Mar 7 19:55:12 netbsd-raspa wpa_supplicant[294]: ioctl[SIOCS80211, op=3D23=
,
val=3D0, arg_len=3D0]: Invalid argument Mar 7 19:55:12
netbsd-raspa wpa_supplicant[294]: urtwn0: CTRL-EVENT-SCAN-FAILED ret=3D-1
retry=3D1 Mar 7 19:55:13 netbsd-raspa
wpa_supplicant[294]: ioctl[SIOCS80211, op=3D23, val=3D0, arg_len=3D0]: Inva=
lid
argument Mar 7 19:55:13 netbsd-raspa wpa_supplicant[294]:
urtwn0: CTRL-EVENT-SCAN-FAILED ret=3D-1 retry=3D1
Mar 7 19:55:14 netbsd-raspa wpa_supplicant[294]: ioctl[SIOCS80211, op=3D23=
,
val=3D0, arg_len=3D0]: Invalid argument Mar 7 19:55:14
netbsd-raspa wpa_supplicant[294]: urtwn0: CTRL-EVENT-SCAN-FAILED ret=3D-1
retry=3D1 Mar 7 19:55:15 netbsd-raspa
wpa_supplicant[294]: ioctl[SIOCS80211, op=3D23, val=3D0, arg_len=3D0]: Inva=
lid
argument Mar 7 19:55:15 netbsd-raspa wpa_supplicant[294]:
urtwn0: CTRL-EVENT-SCAN-FAILED ret=3D-1 retry=3D1
Mar 7 19:55:16 netbsd-raspa wpa_supplicant[294]: ioctl[SIOCS80211, op=3D23=
,
val
Finally, I removed the power supply and system rebooted once more, this
time with network ok.
What could it happen? WIFI dongle got crazy?What is the difference between
a #reboot and a full restart after removing the voltage supply?
Thanks so much
Ramiro
--000000000000d5a70e06132161aa
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<br><br>El domingo, 3 de marzo de 2024, Michael van Elst <<a href=3D"mai=
lto:mlelstv%serpens.de@localhost">mlelstv%serpens.de@localhost</a>> escribi=C3=B3:<br>> T=
he following reply was made to PR kern/57992; it has been noted by GNATS.<b=
r>><br>> From: <a href=3D"mailto:mlelstv%serpens.de@localhost";>mlelstv@serpens.=
de</a> (Michael van Elst)<br>> To: <a href=3D"mailto:gnats-bugs@netbsd.o=
rg">gnats-bugs%netbsd.org@localhost</a><br>> Cc:<br>> Subject: Re: kern/57992: =
urtwn (and athn) driver lost network when WIFI router changes channel<br>&g=
t; Date: Sun, 3 Mar 2024 13:29:58 -0000 (UTC)<br>><br>> =C2=A0<a href=
=3D"mailto:ea1abz%gmail.com@localhost";>ea1abz%gmail.com@localhost</a> writes:<br>><br>> =
=C2=A0>If I force a channel change in the router, the network is lost an=
d I cannot recover it. "service wpa_supplicant restart" does not =
recover network. "ifconfig urtwn0 down" and up does not fix it.<b=
r>><br>> =C2=A0While I can confirm that a channel change isn't re=
cognized with urtwn(4),<br>> =C2=A0a restart of wpa_supplicant (or just =
a "scan" request from wpa_cli)<br>> =C2=A0causes a new scan an=
d association with the network.<br>><br>> =C2=A0An attempt to enable =
automatic scanning using the roaming options<br>> =C2=A0(e.g. bgscan) in=
wpa_supplicant.conf didn't help.<br>><br>> =C2=A0N.B. The same e=
xperiment with iwm(4) causes a disconnect as soon as the<br>> =C2=A0acce=
ss point switches channels and an immediate scan, but afterwards<br>> =
=C2=A0the scan results are always truncated and the network is never found.=
<br><br>> =C2=A0Only a reboot recovers iwm(4) from this state.<br>><b=
r>><br>Thanks Michael for sharing your experience.<br><br>Yesterday I fa=
ced a new scenario. My raspberry pi zero w for unknown reason lost the netw=
ork. <br><br>My rebooting script detected it and rebooted the system but ne=
twork did not recover. I connected the TV and I see that the system reboote=
d several times but network did no work. Each reboot spaced 15minutes cause=
my rebooting script used 3 ping retries at 5min intervals:<br><br>netbsd-r=
aspa# zcat /var/log/messages.0.gz|grep firm<br><br>Mar =C2=A07 18:44:40 net=
bsd-raspa /netbsd: [ =C2=A0 9.1275860] urtwn0: autoconfiguration error: tim=
eout waiting for firmware readinessMar =C2=A07 18:44:40 netbsd-raspa /netbs=
d: [ =C2=A010.0384860] urtwn0: autoconfiguration error: timeout waiting for=
firmware readinessMar =C2=A07 19:00:04 netbsd-raspa /netbsd: [ =C2=A0 1.00=
00000] /soc/firmware at simplebus1 not configured =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 M=
ar =C2=A07 19:00:04 netbsd-raspa /netbsd: [ =C2=A0 9.0872570] urtwn0: autoc=
onfiguration error: timeout waiting for firmware readinessMar =C2=A07 19:00=
:04 netbsd-raspa /netbsd: [ =C2=A0 9.9782020] urtwn0: autoconfiguration err=
or: timeout waiting for firmware readinessMar =C2=A07 19:15:28 netbsd-raspa=
/netbsd: [ =C2=A0 1.0000000] /soc/firmware at simplebus1 not configured =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 Mar =C2=A07 19:15:28 netbsd-raspa /netbsd: [ =C2=
=A0 9.1372840] urtwn0: autoconfiguration error: timeout waiting for firmwar=
e readinessMar =C2=A07 19:15:28 netbsd-raspa /netbsd: [ =C2=A0 9.9581270] u=
rtwn0: autoconfiguration error: timeout waiting for firmware readinessMar =
=C2=A07 19:30:52 netbsd-raspa /netbsd: [ =C2=A0 1.0000000] /soc/firmware at=
simplebus1 not configured =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Mar =C2=A07 19:30:52 netb=
sd-raspa /netbsd: [ =C2=A0 9.0873250] urtwn0: autoconfiguration error: time=
out waiting for firmware readinessMar =C2=A07 19:30:52 netbsd-raspa /netbsd=
: [ =C2=A0 9.9982810] urtwn0: autoconfiguration error: timeout waiting for =
firmware readinessMar =C2=A07 19:46:16 netbsd-raspa /netbsd: [ =C2=A0 1.000=
0000] /soc/firmware at simplebus1 not configured =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 M=
ar =C2=A07 19:46:16 netbsd-raspa /netbsd: [ =C2=A0 9.0172810] urtwn0: autoc=
onfiguration error: timeout waiting for firmware readinessMar =C2=A07 19:46=
:16 netbsd-raspa /netbsd: [ =C2=A0 9.8881610] urtwn0: autoconfiguration err=
or: timeout waiting for firmware readinessnetbsd-raspa#<br><br>Some errors =
including wpa_supplicant messages:<br><br>Mar =C2=A07 19:55:12 netbsd-raspa=
wpa_supplicant[294]: ioctl[SIOCS80211, op=3D23, val=3D0, arg_len=3D0]: Inv=
alid argument =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Mar =C2=A07 1=
9:55:12 netbsd-raspa wpa_supplicant[294]: urtwn0: CTRL-EVENT-SCAN-FAILED re=
t=3D-1 retry=3D1 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Mar =C2=A07 19:55:13 netbsd-raspa=
wpa_supplicant[294]: ioctl[SIOCS80211, op=3D23, val=3D0, arg_len=3D0]: Inv=
alid argument =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Mar =C2=A07 1=
9:55:13 netbsd-raspa wpa_supplicant[294]: urtwn0: CTRL-EVENT-SCAN-FAILED re=
t=3D-1 retry=3D1 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Mar =C2=A07 19:55:14 netbsd-raspa=
wpa_supplicant[294]: ioctl[SIOCS80211, op=3D23, val=3D0, arg_len=3D0]: Inv=
alid argument =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Mar =C2=A07 1=
9:55:14 netbsd-raspa wpa_supplicant[294]: urtwn0: CTRL-EVENT-SCAN-FAILED re=
t=3D-1 retry=3D1 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Mar =C2=A07 19:55:15 netbsd-raspa=
wpa_supplicant[294]: ioctl[SIOCS80211, op=3D23, val=3D0, arg_len=3D0]: Inv=
alid argument =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Mar =C2=A07 1=
9:55:15 netbsd-raspa wpa_supplicant[294]: urtwn0: CTRL-EVENT-SCAN-FAILED re=
t=3D-1 retry=3D1 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Mar =C2=A07 19:55:16 netbsd-raspa=
wpa_supplicant[294]: ioctl[SIOCS80211, op=3D23, val<br><br><br><br>Finally=
, I removed the power supply and system rebooted once more, this time with =
network ok.<br><br>What could it happen? WIFI dongle got crazy?What is the =
difference between a #reboot and a full restart after removing the voltage =
supply?<br><br>Thanks so much<br> Ramiro<br><br><br>
--000000000000d5a70e06132161aa--
Home |
Main Index |
Thread Index |
Old Index