Date: Sat, 9 Apr 2022 14:47:42 -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: New iwlwifi driver seems to be good on AX200 Message-ID: <CAN6yY1vMTF-vPARwFJCyVu6jzuGE=TPoQXf1uRWBAUTVjuiPUA@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.2204010100100.68830@ai.fobar.qr> References: <CAN6yY1uQ1OMoVO1TuhUdEPJYf9qeD-sAkoDhYxG2aAfwhP7ccQ@mail.gmail.com> <alpine.BSF.2.00.2204010100100.68830@ai.fobar.qr>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Thu, Mar 31, 2022 at 6:05 PM Bjoern A. Zeeb < bzeeb-lists@lists.zabbadoz.net> wrote: > On Mon, 28 Mar 2022, Kevin Oberman wrote: > > > Updated to table/13-n250140-4cf0cc507f3 and the network seems good. > > > > A couple of oddities: > > > > First, the network is quite slow to start. The driver is loaded from > > rc.conf and seems to be up in about the same time as before the update. > The > > That should no longer be needed. devmatch should do the right. > > > > ifconfig after the network start looks good and I get: > > wlan0: Ethernet address: 6c:6a:77:ed:ce:d9 > > wlan0: link state changed to UP > > on the console, but, after the startup completes and I have a login > prompt, > > Mar 28 17:54:26 ptavv ntpd[1946]: error resolving pool > > 0.freebsd.pool.ntp.org: Name does not resolve (8) > > Mar 28 17:54:26 ptavv dhclient[1335]: send_packet: No buffer space > > available Mar 28 17:54:26 ptavv syslogd: last > > message repeated 1 times > > > > I'm guessing that these messages were generated during the network > startup, > > but no sent to the console until after getty started. This is not a > > problem, but seems odd and I have never seen it before. > > dmesg -a should show the order in which things appear more clearly > than syslog. > > i'd also check wpa_supplicant logs to see if a deassoc/deauth happened > (still happens sometimes to me right after UP) which could explain why > packets do not immediately get out. > > > > > Second, when the driver loads, I see failure to load both version 70 and > 69 > > of the firmware. 68 loads fine. I suspect that this is normal but it > seemed > > odd that a newer version of firmware would not load on a fairly new > device. > > (AX200) > > That is normal as at the time of import the driver was aware of newer > firmware but the firmware wasn't released yet. > It is out now for some but I didn't want to update everything in one > go again as then we'd not know where problems come from. > > The messages are harmless, very much like the yoyo you may or may not > see too failing to load. > > > > Neither of these impacts operation an everything seems to be running > fine. > > > > Previously my system would crash on certain high data operations and I > will > > be testing this later when I can deal with the system needing to reboot. > > Glad to hear and thanks a lot for testing and reporting back. > > Lots of health, > Bjoern > > -- > Bjoern A. Zeeb r15:7 > OK. Looking at the actual console output during boot, I see the following regarding network startup: iwlwifi0: <iwlwifi> mem 0xd1300000-0xd1303fff at device 0.0 on pci2 iwlwifi0: could not load firmware image 'iwlwifi-cc-a0-70.ucode' iwlwifi0: File size way too small! iwlwifi0: could not load firmware image 'iwlwifi-cc-a0-69.ucode' iwlwifi0: File size way too small! [Unrelated messages (acpi_wmi) elided] iwlwifi0: successfully loaded firmware image 'iwlwifi-cc-a0-68.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 68.01d30b0c.0 cc-a0-68.ucode op_mode iwlmvm iwlwifi0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 lo0: link state changed to UP iwlwifi0: Detected RF HR B3, rfid=0x10a100 iwlwifi0: base HW address: 6c:6a:77:ed:ce:d9 wlan0: Ethernet address: 6c:6a:77:ed:ce:d9 wlan0: link state changed to UP [Many non-network related lines elided] lan0: link state changed to DOWN wlan0: link state changed to UP The timing is not available on those messages, but the messages log shows one second between UP and DOWN and then: Apr 8 23:00:08 ptavv kernel: wlan0: link state changed to DOWN Apr 8 23:00:08 ptavv wpa_supplicant[1325]: wlan0: CTRL-EVENT-DISCONNECTED bssid=14:c0:3e:ec:a3:48 reason=0 Apr 8 23:00:08 ptavv ntfs-3g[1934]: Version 2017.3.23 external FUSE 29 Apr 8 23:00:08 ptavv ntfs-3g[1934]: Mounted /dev/ntfs/Windows (Read-Only, label "Windows", NTFS 3.1) Apr 8 23:00:08 ptavv ntfs-3g[1934]: Cmdline options: rw,uid=9381,gid=15,norecover,noatime Apr 8 23:00:08 ptavv ntfs-3g[1934]: Mount options: rw,allow_other,nonempty,noatime,ro,default_permissions,fsname=/dev/ntfs/Windows Apr 8 23:00:08 ptavv ntfs-3g[1934]: Global ownership and permissions enforced, configuration type 1 Apr 8 23:00:08 ptavv ntpd[1954]: ntpd 4.2.8p15-a (1): Starting Apr 8 23:00:08 ptavv kernel: Security policy loaded: MAC/ntpd (mac_ntpd) Apr 8 23:00:08 ptavv ntpd[1954]: Command line: /usr/sbin/ntpd -p /var/db/ntp/ntpd.pid -c /etc/ntp.conf -f /var/db/ntp/ntpd.drift -g [ntpd startup elided] Apr 8 23:00:09 ptavv wpa_supplicant[1325]: wlan0: Trying to associate with 14:c0:3e:ec:a3:48 (SSID='babcom' freq=2462 MHz) Apr 8 23:00:09 ptavv ntpd[1955]: error resolving pool 0.freebsd.pool.ntp.org: Name does not resolve (8) Apr 8 23:00:09 ptavv kernel: . Apr 8 23:00:09 ptavv kernel: wlan0: link state changed to UP Apr 8 23:00:09 ptavv wpa_supplicant[1325]: wlan0: Associated with 14:c0:3e:ec:a3:48 Apr 8 23:00:09 ptavv dhclient[1344]: send_packet: No buffer space available Apr 8 23:00:09 ptavv syslogd: last message repeated 1 times Apr 8 23:00:09 ptavv wpa_supplicant[1325]: wlan0: WPA: Key negotiation completed with 14:c0:3e:ec:a3:48 [PTK=CCMP GTK=CCMP] Apr 8 23:00:09 ptavv wpa_supplicant[1325]: wlan0: CTRL-EVENT-CONNECTED - Connection to 14:c0:3e:ec:a3:48 completed [id=1 id_str=] [Approx: 1700 lines of "log in vain" messages from failed DNS lookups while the network was running DHCP client. All failures were loopback requests (127.0.0.1 or ::1 for both source and destination.] Apr 8 23:00:12 ptavv kernel: Connection attempt to UDP [::1]:53 from [::1]:20629 Apr 8 23:00:12 ptavv dhclient[2240]: New Subnet Mask (wlan0): 255.255.255.0 Apr 8 23:00:12 ptavv dhclient[2244]: New Broadcast Address (wlan0): 192.168.1.255 Apr 8 23:00:12 ptavv dhclient[2248]: New Routers (wlan0): 192.168.1.1 At this point, the network is up and appears stable. SInce hte last update, I have had no loss of association or other problems. I have hit another VERY annoying shutdown issue, but I will cover this in a separate message when I have collected data. Hope this is useful. Again AX200 on stable/13-n250140-4cf0cc507f3 amd64. As soon as I can do a backup of the system, I will be updating the OS to today's 13-stable. I'll let you know if there are changes after this update. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">On Thu, Mar 31, 2022 at 6:05 PM Bjoern A. Zeeb <<a href="mailto:bzeeb-lists@lists.zabbadoz.net">bzeeb-lists@lists.zabbadoz.net</a>> wrote:<br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon, 28 Mar 2022, Kevin Oberman wrote:<br> <br> > Updated to table/13-n250140-4cf0cc507f3 and the network seems good.<br> ><br> > A couple of oddities:<br> ><br> > First, the network is quite slow to start. The driver is loaded from<br> > rc.conf and seems to be up in about the same time as before the update. The<br> <br> That should no longer be needed. devmatch should do the right.<br> <br> <br> > ifconfig after the network start looks good and I get:<br> > wlan0: Ethernet address: 6c:6a:77:ed:ce:d9<br> > wlan0: link state changed to UP<br> > on the console, but, after the startup completes and I have a login prompt,<br> > Mar 28 17:54:26 ptavv ntpd[1946]: error resolving pool<br> > <a href="http://0.freebsd.pool.ntp.org" rel="noreferrer" target="_blank">0.freebsd.pool.ntp.org</a>: Name does not resolve (8)<br> > Mar 28 17:54:26 ptavv dhclient[1335]: send_packet: No buffer space<br> > available Mar 28 17:54:26 ptavv syslogd: last<br> > message repeated 1 times<br> ><br> > I'm guessing that these messages were generated during the network startup,<br> > but no sent to the console until after getty started. This is not a<br> > problem, but seems odd and I have never seen it before.<br> <br> dmesg -a should show the order in which things appear more clearly<br> than syslog.<br> <br> i'd also check wpa_supplicant logs to see if a deassoc/deauth happened<br> (still happens sometimes to me right after UP) which could explain why<br> packets do not immediately get out.<br> <br> <br> <br> > Second, when the driver loads, I see failure to load both version 70 and 69<br> > of the firmware. 68 loads fine. I suspect that this is normal but it seemed<br> > odd that a newer version of firmware would not load on a fairly new device.<br> > (AX200)<br> <br> That is normal as at the time of import the driver was aware of newer<br> firmware but the firmware wasn't released yet.<br> It is out now for some but I didn't want to update everything in one<br> go again as then we'd not know where problems come from.<br> <br> The messages are harmless, very much like the yoyo you may or may not<br> see too failing to load.<br> <br> <br> > Neither of these impacts operation an everything seems to be running fine.<br> ><br> > Previously my system would crash on certain high data operations and I will<br> > be testing this later when I can deal with the system needing to reboot.<br> <br> Glad to hear and thanks a lot for testing and reporting back.<br> <br> Lots of health,<br> Bjoern<br> <br> -- <br> Bjoern A. Zeeb r15:7<br> </blockquote></div><br clear="all"><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">OK. Looking at the actual console output during boot, I see the following regarding network startup:</div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">iwlwifi0: <iwlwifi> mem 0xd1300000-0xd1303fff at device 0.0 on pci2<br>iwlwifi0: could not load firmware image 'iwlwifi-cc-a0-70.ucode'<br>iwlwifi0: File size way too small!<br>iwlwifi0: could not load firmware image 'iwlwifi-cc-a0-69.ucode'<br>iwlwifi0: File size way too small!</div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">[Unrelated messages (acpi_wmi) elided]<br></div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">iwlwifi0: successfully loaded firmware image 'iwlwifi-cc-a0-68.ucode'<br>iwlwifi0: api flags index 2 larger than supported by driver<br>iwlwifi0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37<br>iwlwifi0: loaded firmware version 68.01d30b0c.0 cc-a0-68.ucode op_mode iwlmvm<br>iwlwifi0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340</div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">lo0: link state changed to UP<br>iwlwifi0: Detected RF HR B3, rfid=0x10a100<br>iwlwifi0: base HW address: 6c:6a:77:ed:ce:d9<br>wlan0: Ethernet address: 6c:6a:77:ed:ce:d9<br>wlan0: link state changed to UP</div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">[Many non-network related lines elided]</div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">lan0: link state changed to DOWN<br>wlan0: link state changed to UP</div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">The timing is not available on those messages, but the messages log shows one second between UP and DOWN and then:<br></div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">Apr 8 23:00:08 ptavv kernel: wlan0: link state changed to DOWN<br>Apr 8 23:00:08 ptavv wpa_supplicant[1325]: wlan0: CTRL-EVENT-DISCONNECTED bssid=14:c0:3e:ec:a3:48 reason=0<br>Apr 8 23:00:08 ptavv ntfs-3g[1934]: Version 2017.3.23 external FUSE 29<br>Apr 8 23:00:08 ptavv ntfs-3g[1934]: Mounted /dev/ntfs/Windows (Read-Only, label "Windows", NTFS 3.1)<br>Apr 8 23:00:08 ptavv ntfs-3g[1934]: Cmdline options: rw,uid=9381,gid=15,norecover,noatime<br>Apr 8 23:00:08 ptavv ntfs-3g[1934]: Mount options: rw,allow_other,nonempty,noatime,ro,default_permissions,fsname=/dev/ntfs/Windows<br>Apr 8 23:00:08 ptavv ntfs-3g[1934]: Global ownership and permissions enforced, configuration type 1<br>Apr 8 23:00:08 ptavv ntpd[1954]: ntpd 4.2.8p15-a (1): Starting<br>Apr 8 23:00:08 ptavv kernel: Security policy loaded: MAC/ntpd (mac_ntpd)<br>Apr 8 23:00:08 ptavv ntpd[1954]: Command line: /usr/sbin/ntpd -p /var/db/ntp/ntpd.pid -c /etc/ntp.conf -f /var/db/ntp/ntpd.drift -g<br></div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">[ntpd startup elided]</div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">Apr 8 23:00:09 ptavv wpa_supplicant[1325]: wlan0: Trying to associate with 14:c0:3e:ec:a3:48 (SSID='babcom' freq=2462 MHz)<br>Apr 8 23:00:09 ptavv ntpd[1955]: error resolving pool <a href="http://0.freebsd.pool.ntp.org">0.freebsd.pool.ntp.org</a>: Name does not resolve (8)<br>Apr 8 23:00:09 ptavv kernel: .<br>Apr 8 23:00:09 ptavv kernel: wlan0: link state changed to UP<br>Apr 8 23:00:09 ptavv wpa_supplicant[1325]: wlan0: Associated with 14:c0:3e:ec:a3:48<br>Apr 8 23:00:09 ptavv dhclient[1344]: send_packet: No buffer space available<br>Apr 8 23:00:09 ptavv syslogd: last message repeated 1 times<br>Apr 8 23:00:09 ptavv wpa_supplicant[1325]: wlan0: WPA: Key negotiation completed with 14:c0:3e:ec:a3:48 [PTK=CCMP GTK=CCMP]<br>Apr 8 23:00:09 ptavv wpa_supplicant[1325]: wlan0: CTRL-EVENT-CONNECTED - Connection to 14:c0:3e:ec:a3:48 completed [id=1 id_str=]</div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">[Approx: 1700 lines of "log in vain" messages from failed DNS lookups while the network was running DHCP client. All failures were loopback requests (127.0.0.1 or ::1 for both source and destination.] <br></div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default"> Apr 8 23:00:12 ptavv kernel: Connection attempt to UDP [::1]:53 from [::1]:20629<br>Apr 8 23:00:12 ptavv dhclient[2240]: New Subnet Mask (wlan0): 255.255.255.0<br>Apr 8 23:00:12 ptavv dhclient[2244]: New Broadcast Address (wlan0): 192.168.1.255<br>Apr 8 23:00:12 ptavv dhclient[2248]: New Routers (wlan0): 192.168.1.1</div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">At this point, the network is up and appears stable. SInce hte last update, I have had no loss of association or other problems.</div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">I have hit another VERY annoying shutdown issue, but I will cover this in a separate message when I have collected data.</div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">Hope this is useful. Again AX200 on stable/13-n250140-4cf0cc507f3 amd64.<br></div><div><br></div><div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">As soon as I can do a backup of the system, I will be updating the OS to today's 13-stable. I'll let you know if there are changes after this update.<br></div></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Kevin Oberman, Part time kid herder and retired Network Engineer<br>E-mail: <a href="mailto:rkoberman@gmail.com" target="_blank">rkoberman@gmail.com</a><br></div><div>PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683</div></div></div></div></div></div></div></div></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1vMTF-vPARwFJCyVu6jzuGE=TPoQXf1uRWBAUTVjuiPUA>