From nobody Mon Mar 14 19:24:20 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 3520F1A15C53 for ; Mon, 14 Mar 2022 19:25:06 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oi1-x22e.google.com (mail-oi1-x22e.google.com [IPv6:2607:f8b0:4864:20::22e]) (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 4KHRM43gt7z3CZB for ; Mon, 14 Mar 2022 19:25:04 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-oi1-x22e.google.com with SMTP id w2so10409166oie.2 for ; Mon, 14 Mar 2022 12:25:04 -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=ov6aOMfBivGYjfgOcPq+amCEyhl1MWB04eO2nFADcs4=; b=eD2WsqmHis/NUEf7AbWaXPMHpW7N3zPL343qstK7OAi8DpqM7TcN3IFeoenf4kburL Iz9f4vlY52LNIMKKgH+gi27/izLtNuWAz+fDzynBNM3r4cguen5UyRU2V0EWh0Uc0rl7 FDBRBMDMsGZY/ZYCqeeC8emvR+xFUZhPcPkV11xocSZifgoGPU5gWRQoF7s2w+EnK6kc C8ToX7ecIftvEWvqXiNqsbt/tAUHU749B/9bUrBBWHpaBs+uWnipA9dz1b+iwqgm5ld7 r/N/Ks9AnvmRepfaFCixprr74N166HrpbOqdIU4RVoXsPnzPqjNNVfiilKzjKvJNEjr6 5p7Q== 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=ov6aOMfBivGYjfgOcPq+amCEyhl1MWB04eO2nFADcs4=; b=1XXAggjKVcNgZ4waKMorSfY1l9/LhNmz3xufvLoIzjPRzbMalEbmMHMfMXrl8IzTvS kMp3NXUamnf8pp4Nqaho5IgEK7H/FwN7FRlamTDEFyFrMTRqH/mDgP8rISuiiLP4jWKP wa0WAVpHp3zs9bZzq8eqT2FbJlRjOQvzK6GAmbiUwtz0TMo29WAqs4FJsKTe2XSOHBpg zsjwrnw1C1jHCC5AZVQEsm4x1RCtNX/iF2fXIbsi0Kz+dm8TnIzBotq8sNBPLfuyCKjj y2pPDIYVVlD4ME9MBnR9sWsECizRvnJF1Ekq6N+ry67mh/Z/NJnW288XNE+q4pCeWNTA ZPMg== X-Gm-Message-State: AOAM530n/NZ/x6uLlpWYbC9omUzMvMDh5p7kKzZz+JfpZ4Msh8xkSHQr PzxsGORNCaBMPQZ5UfBwSKrUrDg6Pa6vxTAWdVD6nxqCpdI= X-Google-Smtp-Source: ABdhPJwqlDibBMPpIv1K5DTfGg1B5wI7fdSdhUuanqnr8UbB4BydRx+v49XayckJdsPgufpSSXN4xvpiyGu4bf1sQKU= X-Received: by 2002:a05:6808:1305:b0:2da:5086:fa34 with SMTP id y5-20020a056808130500b002da5086fa34mr355140oiv.230.1647285903633; Mon, 14 Mar 2022 12:25:03 -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 12:24:20 -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="000000000000212edc05da32a3eb" X-Rspamd-Queue-Id: 4KHRM43gt7z3CZB X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=eD2WsqmH; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of kob6558@gmail.com designates 2607:f8b0:4864:20::22e as permitted sender) smtp.mailfrom=kob6558@gmail.com X-Spamd-Result: default: False [-3.70 / 15.00]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; 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)[-1.000]; 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::22e:from]; MLMMJ_DEST(0.00)[freebsd-wireless]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N --000000000000212edc05da32a3eb Content-Type: text/plain; charset="UTF-8" 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. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --000000000000212edc05da32a3eb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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<= br> > /etc/rc.conf. In the /boot/loader case, the firmware fails to load wit= h the
> message "File size way too small!" for all available version= s of microcode
> including "wlwifi-cc-a0-68.ucode" which should be used for m= y AX200. For

Loading from loader is discuraged;=C2=A0 if you really want to see this
thread:
https://lists.freebsd.o= rg/archives/freebsd-wireless/2021-December/000153.html


On FreeBSD Current, you don't even have to load the module at all anymo= re;
it'll automatically loaded for you (soon also in stable/13).


> /etc/rc.conf, there appears to be a race condition where the network t= ries
> 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=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 pci2
iwlwifi0: s= uccessfully loaded firmware image 'iwlwifi-cc-a0-67.ucode'
iwlwi= fi0: 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 Int= el(R) Wi-Fi 6 AX200 160MHz, REV=3D0x340

= and, after the network fails to start, I see:
iwlwifi0: Dete= cted 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 h= as not been created at this point. While there are many lines of messages i= n the log between these messages, they are all logged in the same second.
--
Kev= in Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com<= /a>
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683=
--000000000000212edc05da32a3eb--