Date: Sun, 14 Apr 2024 15:36:17 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 263632] iwlwifi(4) crashes (freezes) a few seconds after resuming from sleep (suspend/resume not working; workaround known for now) Message-ID: <bug-263632-21060-pc4bSerzY4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-263632-21060@https.bugs.freebsd.org/bugzilla/> References: <bug-263632-21060@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263632 --- Comment #37 from Jonathan Vasquez <jon@xyinn.org> --- Hey Bjoern, I'm on stable/14 (FreeBSD leslie 14.0-STABLE FreeBSD 14.0-STABLE #0 stable/14-n267200-50f771371356: Sat Apr 13 20:23:30 EDT 2024=20=20=20=20 root@leslie:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64) and have some updates. 1. I re-transferred that 684 MB file from my home NAS again using the wirel= ess card and instead of it taking 14m, it now only took 5m48s, so a big improvement. Doing some basic 'ls -lh' while it was transferring, it was basically transferring at about 2 MB per sec. 2. After the above, I tested sleep/resume. The system came back up without crashing, but the internet connection was broken even though 'ifconfig' said that it was associated to the network. I then did 4 more sleep/resume in sequence to see if the system would crash. It didn't :). 3. After those tests were done, I then tested tear down since I remember we mentioned that the iwlwifi driver/card doesn't like being teared down and it could crash. So I first did a `service netif restart && service routing restart` and the internet worked again (doing netif alone wasn't enough, I needed routing as well.. most likely because I'm using a static ip configuration: wlans_iwlwifi0=3D"wlan0" ifconfig_wlan0=3D"WPA inet 192.168.1.101 netmask 255.255.255.0" ifconfig_wlan0_ipv6=3D"inet6 accept_rtadv" defaultrouter=3D"192.168.1.1" create_args_wlan0=3D"country US regdomain FCC" I then did two more sleep/resume and it didn't crash (but internet broke again). 4. After this, I stress tested the tear down by doing the netif/routing restarts 8 more times in a row. It did not crash. This is all good news and is an indication that your stability fixes are working, although I'll need to use it throughout the days/weeks more to see= how stable it actually is. I'll be trying to play around with if_lagg and seeing how well it works for failover recovery between my ethernet interface that'= s on an type c dongle and the built in Intel AX210 wireless card, so I can more easily switch between locations at home ;). I did hear that FreeBSD's network stack in general is at an 802.11g level so regardless of what the driver is (Atheros, Intel, etc), the maximum speed w= ill be at g speeds. Do you know what's the status with upgrading FreeBSD's wifi stack to 802.11n/ac/ax? I believe I read in one of the recent FreeBSD foundation reports that more investments will start occurring for the wireless network stack specifically. If you ha= ve any links where I can read more up on that, that would be helpful. Other info (also attached dmesg-2024-04-14-1136): wlan0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 15= 00 options=3D0 ether c8:15:4e:aa:6d:92 inet 192.168.1.101 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::ca15:4eff:feaa:6d92%wlan0 prefixlen 64 scopeid 0x2 groups: wlan ssid <redacted> channel 40 (5200 MHz 11a) bssid c8:7f:54:b5:d5:f4 regdomain FCC country US authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 3:128-bit txpower 17 bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 60 wme roaming MANUAL parent interface: iwlwifi0 media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11a status: associated nd6 options=3D23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> - Jonathan --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263632-21060-pc4bSerzY4>