Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Mar 2022 23:08:37 -0700
From:      Kevin Oberman <rkoberman@gmail.com>
To:        "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
Cc:        FreeBSD Wireless <freebsd-wireless@freebsd.org>
Subject:   Re: Unable to have network reliably start at boot time
Message-ID:  <CAN6yY1v%2BXgTSJ9umgex5-TCyLdFYck5nvXxds_hXi76qsSRQKQ@mail.gmail.com>
In-Reply-To: <alpine.BSF.2.00.2203141932250.68830@ai.fobar.qr>
References:  <CAN6yY1sByfp893XGFc_cgd5M=YUUy=5ZCWUndGnbrjMsz96p6Q@mail.gmail.com> <alpine.BSF.2.00.2203141743300.68830@ai.fobar.qr> <CAN6yY1sBJCGj8CVAPrOBcVFqez6tH_pJHLwO9DEOiOv0NWztGw@mail.gmail.com> <alpine.BSF.2.00.2203141932250.68830@ai.fobar.qr>

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

Correct. 13-STABLE from Mar. 5.

On Mon, Mar 14, 2022 at 12:36 PM Bjoern A. Zeeb <
bzeeb-lists@lists.zabbadoz.net> wrote:

> On Mon, 14 Mar 2022, Kevin Oberman wrote:
>
> > On Mon, Mar 14, 2022 at 10:47 AM Bjoern A. Zeeb <
> > bzeeb-lists@lists.zabbadoz.net> wrote:
> >
> >> On Mon, 14 Mar 2022, Kevin Oberman wrote:
> >>
> >> Hi,
> >>
> >>> I have tried loading if_iwlwifi at boot by both /boot/loader.conf and
> >>> /etc/rc.conf. In the /boot/loader case, the firmware fails to load with
> >> the
> >>> message "File size way too small!" for all available versions of
> >> microcode
> >>> including "wlwifi-cc-a0-68.ucode" which should be used for my AX200.
> For
> >>
> >> Loading from loader is discuraged;  if you really want to see this
> >> thread:
> >>
> >>
> https://lists.freebsd.org/archives/freebsd-wireless/2021-December/000153.html
> >>
> >>
> >> On FreeBSD Current, you don't even have to load the module at all
> anymore;
> >> it'll automatically loaded for you (soon also in stable/13).
> >>
> >>
> >>> /etc/rc.conf, there appears to be a race condition where the network
> >> tries
> >>> to start before the microcode load has completed.
> >>
> >> That is a weird case and I thought that should not happen anymore as
> >> the wlan interface should always only be created after the firmware
> >> successfully loaded.
> >>
> >> I see I have an email from you in my inbox as well; in case it's not
> >> in there, can you send me the console (dmesg -a) output of that case
> >> so I can have a look?
> >>
> >> /bz
> >>
> >> --
> >> Bjoern A. Zeeb                                                     r15:7
> >>
> >
> > I'm only assuming that the firmware load is leading to the problem, but
> > I've looked closer and that is likely not the case as I see:
> > iwlwifi0: <iwlwifi> mem 0xd1300000-0xd1303fff at device 0.0 on pci2
> > iwlwifi0: successfully loaded firmware image 'iwlwifi-cc-a0-67.ucode'
> > iwlwifi0: api flags index 2 larger than supported by driver
> > iwlwifi0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
> > iwlwifi0: loaded firmware version 67.8f59b80b.0 cc-a0-67.ucode op_mode
> > iwlmvm
> > iwlwifi0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
> >
> > and, after the network fails to start, I see:
> > iwlwifi0: Detected RF HR B3, rfid=0x10a100
> > iwlwifi0: base HW address: 6c:6a:77:ed:ce:d9
> >
> > The failure generates no messages. Just shows git0 and lo0 starting
> > normally. I assume that this is because wlan0 has not been created at
> this
> > point. While there are many lines of messages in the log between these
> > messages, they are all logged in the same second.
>
> I had a look.  You are on stable/13, right?
>
> If so, I just asked for e0ab0ff104cb0e817d47a1a2a235f915ec1a31f4 to be
> MFCed as that likely prevents your wlan from starting if the wlan
> interface is not there yet by the time we run (the "global") netif start.
>
> If this was on HEAD please let me know and I'll have to dig deeper.
>
> Later,
> /bz
>
> --
> Bjoern A. Zeeb                                                     r15:7
>


-- 
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:tahoma,s=
ans-serif;font-size:small">Correct. 13-STABLE from Mar. 5. <br></div></div>=
<br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon=
, Mar 14, 2022 at 12:36 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 Mon, 14 Mar 2022, Kev=
in Oberman wrote:<br>
<br>
&gt; On Mon, Mar 14, 2022 at 10:47 AM Bjoern A. Zeeb &lt;<br>
&gt; <a href=3D"mailto:bzeeb-lists@lists.zabbadoz.net" target=3D"_blank">bz=
eeb-lists@lists.zabbadoz.net</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; On Mon, 14 Mar 2022, Kevin Oberman wrote:<br>
&gt;&gt;<br>
&gt;&gt; Hi,<br>
&gt;&gt;<br>
&gt;&gt;&gt; I have tried loading if_iwlwifi at boot by both /boot/loader.c=
onf and<br>
&gt;&gt;&gt; /etc/rc.conf. In the /boot/loader case, the firmware fails to =
load with<br>
&gt;&gt; the<br>
&gt;&gt;&gt; message &quot;File size way too small!&quot; for all available=
 versions of<br>
&gt;&gt; microcode<br>
&gt;&gt;&gt; including &quot;wlwifi-cc-a0-68.ucode&quot; which should be us=
ed for my AX200. For<br>
&gt;&gt;<br>
&gt;&gt; Loading from loader is discuraged;=C2=A0 if you really want to see=
 this<br>
&gt;&gt; thread:<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"https://lists.freebsd.org/archives/freebsd-wireless/202=
1-December/000153.html" rel=3D"noreferrer" target=3D"_blank">https://lists.=
freebsd.org/archives/freebsd-wireless/2021-December/000153.html</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; On FreeBSD Current, you don&#39;t even have to load the module at =
all anymore;<br>
&gt;&gt; it&#39;ll automatically loaded for you (soon also in stable/13).<b=
r>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; /etc/rc.conf, there appears to be a race condition where the n=
etwork<br>
&gt;&gt; tries<br>
&gt;&gt;&gt; to start before the microcode load has completed.<br>
&gt;&gt;<br>
&gt;&gt; That is a weird case and I thought that should not happen anymore =
as<br>
&gt;&gt; the wlan interface should always only be created after the firmwar=
e<br>
&gt;&gt; successfully loaded.<br>
&gt;&gt;<br>
&gt;&gt; I see I have an email from you in my inbox as well; in case it&#39=
;s not<br>
&gt;&gt; in there, can you send me the console (dmesg -a) output of that ca=
se<br>
&gt;&gt; so I can have a look?<br>
&gt;&gt;<br>
&gt;&gt; /bz<br>
&gt;&gt;<br>
&gt;&gt; --<br>
&gt;&gt; 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>
&gt;&gt;<br>
&gt;<br>
&gt; I&#39;m only assuming that the firmware load is leading to the problem=
, but<br>
&gt; I&#39;ve looked closer and that is likely not the case as I see:<br>
&gt; iwlwifi0: &lt;iwlwifi&gt; mem 0xd1300000-0xd1303fff at device 0.0 on p=
ci2<br>
&gt; iwlwifi0: successfully loaded firmware image &#39;iwlwifi-cc-a0-67.uco=
de&#39;<br>
&gt; iwlwifi0: api flags index 2 larger than supported by driver<br>
&gt; iwlwifi0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37<br>
&gt; iwlwifi0: loaded firmware version 67.8f59b80b.0 cc-a0-67.ucode op_mode=
<br>
&gt; iwlmvm<br>
&gt; iwlwifi0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=3D0x340<br>
&gt;<br>
&gt; and, after the network fails to start, I see:<br>
&gt; iwlwifi0: Detected RF HR B3, rfid=3D0x10a100<br>
&gt; iwlwifi0: base HW address: 6c:6a:77:ed:ce:d9<br>
&gt;<br>
&gt; The failure generates no messages. Just shows git0 and lo0 starting<br=
>
&gt; normally. I assume that this is because wlan0 has not been created at =
this<br>
&gt; point. While there are many lines of messages in the log between these=
<br>
&gt; messages, they are all logged in the same second.<br>
<br>
I had a look.=C2=A0 You are on stable/13, right?<br>
<br>
If so, I just asked for e0ab0ff104cb0e817d47a1a2a235f915ec1a31f4 to be<br>
MFCed as that likely prevents your wlan from starting if the wlan<br>
interface is not there yet by the time we run (the &quot;global&quot;) neti=
f start.<br>
<br>
If this was on HEAD please let me know and I&#39;ll have to dig deeper.<br>
<br>
Later,<br>
/bz<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><br clear=3D"all"><br>-- <br><div dir=3D"ltr" class=3D"g=
mail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr=
"><div><div dir=3D"ltr">Kevin Oberman, Part time kid herder and retired Net=
work Engineer<br>E-mail: <a href=3D"mailto:rkoberman@gmail.com" target=3D"_=
blank">rkoberman@gmail.com</a><br></div><div>PGP Fingerprint: D03FB98AFA78E=
3B78C1694B318AB39EF1B055683</div></div></div></div></div></div></div></div>

--0000000000006a549105da3ba34d--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1v%2BXgTSJ9umgex5-TCyLdFYck5nvXxds_hXi76qsSRQKQ>