From nobody Tue Mar 15 06:08:37 2022 X-Original-To: freebsd-wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 2BBCE1A15000 for ; Tue, 15 Mar 2022 06:09:24 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ot1-x336.google.com (mail-ot1-x336.google.com [IPv6:2607:f8b0:4864:20::336]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KHjfW5XNpz3pFy for ; Tue, 15 Mar 2022 06:09:23 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-ot1-x336.google.com with SMTP id x8-20020a9d6288000000b005b22c373759so13357783otk.8 for ; Mon, 14 Mar 2022 23:09:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EgDEoKmjmItVVcfCU1J+eN1YFN6xt+5nc8XXXnEEsMs=; b=W0HRsok9dy2LWMJ/XFJAlKFMS195s23t8VKm2obRM0OrG6ibmxB3mIXerct2TLBVyb /KjoHAuU4OzMM0jfUaRh2oTb5LjlnFaPUsGEFEi05kpyKseXhO7xnGV0h2L5lIequpUw aV1SGhWXuA1pEiD0CCWzKaqP3STNNRdXCh1+gAX8SMNWYfCm1GKFt1fSwhH+QSNP5S+L nTyBOLUVi9C6G+tLt9/D/1jK6mHBJyejWJ5/v/sVxAAc68n4DG8U2BuVpZswriI9ch3Z /4TP8AiWPq5gwcCp2OVH/CXWaIFUZ+nFuC66NYZR+v/rXWJNMaoHH4Nsp5djcD+c9gg6 noDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=EgDEoKmjmItVVcfCU1J+eN1YFN6xt+5nc8XXXnEEsMs=; b=CVtGx+XyS+D/igfq1Bz4OBA26cZM2VD19dAnH5WQETjfIzG0hi4XfUEFTtN33deGEd yY2cYZqumYBUXAjRLpJ9VRbEenEIDL93KpwcPG1Bp36aJ6KLjKCJsOsGT0sPU7AbFkbS Qp8Jz8egaVhsNPqnNBg++l8y1IRVADOMVj49gfw1t45uBOStIBioddvlswVA/Buj8flS l5c7hurXK/Q8ZlS9AsYJW4SgGoXRc8TModOtNWFUU0CAykoyQPHw/TFh276tc7fX5mXp J6BNGebY0GLHue1vSuLSUXl8vlI0w3pD2EGeP3Nihgby9JeBEiNSK+tMnv4K8f7m2V4g O/pQ== X-Gm-Message-State: AOAM533Nj9+nyXROWRS9YmgwjukQArgDkywue7pNaAC1AXpC/3D5MNB7 4rvrgE+ABL3dXxp68D5H/ceozJdtvnP36TW27Ji3MYui X-Google-Smtp-Source: ABdhPJxL6+lRLY9VAzu6i1U3e3gDBZlDHaqgm/o2fbWDJ5tW5zAp2XkReacQyX5Q0wV8+f3uTXgxIswpL/AQHW2HDTc= X-Received: by 2002:a9d:5f0e:0:b0:5c9:26c4:a196 with SMTP id f14-20020a9d5f0e000000b005c926c4a196mr10610273oti.82.1647324563132; Mon, 14 Mar 2022 23:09:23 -0700 (PDT) List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Kevin Oberman Date: Mon, 14 Mar 2022 23:08:37 -0700 Message-ID: Subject: Re: Unable to have network reliably start at boot time To: "Bjoern A. Zeeb" Cc: FreeBSD Wireless Content-Type: multipart/alternative; boundary="0000000000006a549105da3ba34d" X-Rspamd-Queue-Id: 4KHjfW5XNpz3pFy X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=W0HRsok9; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of kob6558@gmail.com designates 2607:f8b0:4864:20::336 as permitted sender) smtp.mailfrom=kob6558@gmail.com X-Spamd-Result: default: False [-3.70 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-0.999]; FORGED_SENDER(0.30)[rkoberman@gmail.com,kob6558@gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[rkoberman@gmail.com,kob6558@gmail.com]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-wireless@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::336:from]; MLMMJ_DEST(0.00)[freebsd-wireless]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N --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: 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
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, Kev= in Oberman wrote:

> On Mon, Mar 14, 2022 at 10:47 AM Bjoern A. Zeeb <
> bz= eeb-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.c= onf 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 us= ed for my AX200. For
>>
>> Loading from loader is discuraged;=C2=A0 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 n= etwork
>> 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 firmwar= e
>> 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 ca= se
>> so I can have a look?
>>
>> /bz
>>
>> --
>> 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
>>
>
> 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 p= ci2
> iwlwifi0: successfully loaded firmware image 'iwlwifi-cc-a0-67.uco= de'
> 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=3D0x340
>
> and, after the network fails to start, I see:
> iwlwifi0: Detected RF HR B3, rfid=3D0x10a100
> 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.=C2=A0 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") neti= f start.

If this was on HEAD please let me know and I'll have to dig deeper.

Later,
/bz

--
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


--
Kevin Oberman, Part time kid herder and retired Net= work Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E= 3B78C1694B318AB39EF1B055683
--0000000000006a549105da3ba34d--