Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 Feb 2022 18:25:39 -0500
From:      John Schneider <john.a.schneider@gmail.com>
To:        "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
Cc:        freebsd-wireless@freebsd.org
Subject:   Re: My iwn device can no longer scan for access points with stable/13
Message-ID:  <CAJdGomU3n5LhFyvSHvLKM5OPvO-n9c2zsN5hXR-6He83=SmA5g@mail.gmail.com>
In-Reply-To: <alpine.BSF.2.00.2202170032550.68830@ai.fobar.qr>
References:  <CAJdGomXa9mYqEiJFh88SwCgoXcYn6y_KskbHECeavxx7Kn-wXQ@mail.gmail.com> <alpine.BSF.2.00.2202170032550.68830@ai.fobar.qr>

next in thread | previous in thread | raw e-mail | index | archive | help
--00000000000025aa2b05d83f16d8
Content-Type: text/plain; charset="UTF-8"

I did the normal upgrade process described in the handbook - buildworld,
buildkernel, installkernel, reboot, installworld, etc.  iwn works fine
after stable/13 installkernel and reboot (which is at that point
releng/13.0 world with stable/13 kernel.  In fact I am sending this email
via iwn while using stable/13 kernel. It is only after installing stable/13
world and rebooting that iwn can no longer scan.

I am happy to re-install stable/13 world and produce more debugging info.
Just let me know what would be helpful.

Thanks,
John

On Wed, Feb 16, 2022 at 7:46 PM Bjoern A. Zeeb <
bzeeb-lists@lists.zabbadoz.net> wrote:

> On Wed, 16 Feb 2022, John Schneider wrote:
>
> Hi,
>
> > Today I upgraded from releng/13.0 to stable/13 but found my iwn device
> > could no longer scan for access points.  I rolled back to releng/13.0 and
> > everything was fine again.  No config changes were made during the
> upgrade
> > or rollback process.
> >
> > /var/log/messages contained messages such as the one below with each scan
> > attempt:
> > Feb 16 16:12:33 mobile1 wpa_supplicant[385]: wlan0:
> CTRL-EVENT-SCAN-FAILED
> > ret=-1 retry=1
>
> -1 is nothing the kernel should return so I don't know what the actual
> error is.
>
>
> > I didn't see any other errors except ACPI stuff which looked normal to me
> > for this machine.  For reference, here is the pciconf output for my
> device:
> >
> > iwn0@pci0:2:0:0:        class=0x028000 rev=0x35 hdr=0x00 vendor=0x8086
> > device=0x
> > 422b subvendor=0x8086 subdevice=0x1121
> >   vendor     = 'Intel Corporation'
> >   device     = 'Centrino Ultimate-N 6300'
> >   class      = network
> >
> > Is it possible that work being done for iwlwifi could affect scanning
> with
> > iwn and other drivers?
>
> It shouldn't as there were very little functional changes to net80211
> itself so far relating to this.
>
> I would more likely think of wpa_supplicant updates but even that we'd
> probably have heard a lot more noise.  You could run that with
>
>         wpa_supplicant_flags="-sdd"
>
> in rc.conf (from the top of my head) and see.
>
> Also did you update kernel and world or was that just a kernel update
> (which would rule out the above wpa_supplicant update theory)?
>
>
> I also only see 3 changes to iwn(4) in main and 2 of them in stable/13
> since releng/13.0:
>
>
> https://cgit.freebsd.org/src/commit/sys/dev/iwn?h=stable/13&id=d61f10a8780ef94f82e384248ce40d24fc27ad2b
>
> https://cgit.freebsd.org/src/commit/sys/dev/iwn?h=stable/13&id=67b7e2de4fc5dc1165feee8ca281c44444425d0f
>
> and the one Adrian did not MFC:
>
> https://cgit.freebsd.org/src/commit/sys/dev/iwn?id=b6fd00791f2b9690b0a5d8670fc03f74eda96da2&h=stable%2F13
>
>
> In case you are willing to go back to stable/13 and re-test things
> let me know so we can crank some debugging/logging up to see where the
> error comes from.
>
>
>
> > On a separate subject, I had tested iwlwifi on a
> > separate machine with stable/13 and an AX201 and it was quite stable
> > (though slow as has been reported by others). Keep up the great work!
>
> Thanks for testing.  I'll try to make it more stable and then faster :)
>
> Best Regards,
> Bjoern
>
> --
> Bjoern A. Zeeb                                                     r15:7
>

--00000000000025aa2b05d83f16d8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I did the normal upgrade process described in the han=
dbook - buildworld, buildkernel, installkernel, reboot, installworld, etc.=
=C2=A0 iwn works fine after stable/13 installkernel and reboot (which is at=
 that point releng/13.0 world with stable/13 kernel.=C2=A0 In fact I am sen=
ding this email via iwn while using stable/13 kernel. It is only after inst=
alling stable/13 world and rebooting that iwn can no longer scan.</div><div=
><br></div><div>I am happy to re-install stable/13 world and produce more d=
ebugging info.=C2=A0 Just let me know what would be helpful.</div><div><br>=
</div><div>Thanks,</div><div>John<br></div></div><br><div class=3D"gmail_qu=
ote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Feb 16, 2022 at 7:46 PM =
Bjoern A. Zeeb &lt;<a href=3D"mailto:bzeeb-lists@lists.zabbadoz.net">bzeeb-=
lists@lists.zabbadoz.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex">On Wed, 16 Feb 2022, John Schneider wrote:<br>
<br>
Hi,<br>
<br>
&gt; Today I upgraded from releng/13.0 to stable/13 but found my iwn device=
<br>
&gt; could no longer scan for access points.=C2=A0 I rolled back to releng/=
13.0 and<br>
&gt; everything was fine again.=C2=A0 No config changes were made during th=
e upgrade<br>
&gt; or rollback process.<br>
&gt;<br>
&gt; /var/log/messages contained messages such as the one below with each s=
can<br>
&gt; attempt:<br>
&gt; Feb 16 16:12:33 mobile1 wpa_supplicant[385]: wlan0: CTRL-EVENT-SCAN-FA=
ILED<br>
&gt; ret=3D-1 retry=3D1<br>
<br>
-1 is nothing the kernel should return so I don&#39;t know what the actual<=
br>
error is.<br>
<br>
<br>
&gt; I didn&#39;t see any other errors except ACPI stuff which looked norma=
l to me<br>
&gt; for this machine.=C2=A0 For reference, here is the pciconf output for =
my device:<br>
&gt;<br>
&gt; iwn0@pci0:2:0:0:=C2=A0 =C2=A0 =C2=A0 =C2=A0 class=3D0x028000 rev=3D0x3=
5 hdr=3D0x00 vendor=3D0x8086<br>
&gt; device=3D0x<br>
&gt; 422b subvendor=3D0x8086 subdevice=3D0x1121<br>
&gt;=C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D &#39;Intel Corporation&#39;<=
br>
&gt;=C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D &#39;Centrino Ultimate-N 630=
0&#39;<br>
&gt;=C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D network<br>
&gt;<br>
&gt; Is it possible that work being done for iwlwifi could affect scanning =
with<br>
&gt; iwn and other drivers?<br>
<br>
It shouldn&#39;t as there were very little functional changes to net80211<b=
r>
itself so far relating to this.<br>
<br>
I would more likely think of wpa_supplicant updates but even that we&#39;d<=
br>
probably have heard a lot more noise.=C2=A0 You could run that with<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 wpa_supplicant_flags=3D&quot;-sdd&quot;<br>
<br>
in rc.conf (from the top of my head) and see.<br>
<br>
Also did you update kernel and world or was that just a kernel update<br>
(which would rule out the above wpa_supplicant update theory)?<br>
<br>
<br>
I also only see 3 changes to iwn(4) in main and 2 of them in stable/13<br>
since releng/13.0:<br>
<br>
<a href=3D"https://cgit.freebsd.org/src/commit/sys/dev/iwn?h=3Dstable/13&am=
p;id=3Dd61f10a8780ef94f82e384248ce40d24fc27ad2b" rel=3D"noreferrer" target=
=3D"_blank">https://cgit.freebsd.org/src/commit/sys/dev/iwn?h=3Dstable/13&a=
mp;id=3Dd61f10a8780ef94f82e384248ce40d24fc27ad2b</a><br>
<a href=3D"https://cgit.freebsd.org/src/commit/sys/dev/iwn?h=3Dstable/13&am=
p;id=3D67b7e2de4fc5dc1165feee8ca281c44444425d0f" rel=3D"noreferrer" target=
=3D"_blank">https://cgit.freebsd.org/src/commit/sys/dev/iwn?h=3Dstable/13&a=
mp;id=3D67b7e2de4fc5dc1165feee8ca281c44444425d0f</a><br>
<br>
and the one Adrian did not MFC:<br>
<a href=3D"https://cgit.freebsd.org/src/commit/sys/dev/iwn?id=3Db6fd00791f2=
b9690b0a5d8670fc03f74eda96da2&amp;h=3Dstable%2F13" rel=3D"noreferrer" targe=
t=3D"_blank">https://cgit.freebsd.org/src/commit/sys/dev/iwn?id=3Db6fd00791=
f2b9690b0a5d8670fc03f74eda96da2&amp;h=3Dstable%2F13</a><br>
<br>
<br>
In case you are willing to go back to stable/13 and re-test things<br>
let me know so we can crank some debugging/logging up to see where the<br>
error comes from.<br>
<br>
<br>
<br>
&gt; On a separate subject, I had tested iwlwifi on a<br>
&gt; separate machine with stable/13 and an AX201 and it was quite stable<b=
r>
&gt; (though slow as has been reported by others). Keep up the great work!<=
br>
<br>
Thanks for testing.=C2=A0 I&#39;ll try to make it more stable and then fast=
er :)<br>
<br>
Best Regards,<br>
Bjoern<br>
<br>
-- <br>
Bjoern A. Zeeb=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 =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=A0r15:7<br>
</blockquote></div>

--00000000000025aa2b05d83f16d8--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJdGomU3n5LhFyvSHvLKM5OPvO-n9c2zsN5hXR-6He83=SmA5g>