Date: Wed, 12 Jun 2024 21:40:19 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Steven Friedrich <freebsdlouisville@gmail.com> Cc: FreeBSD Wireless <freebsd-wireless@freebsd.org> Subject: Re: Appears rtw88 driver hangs network stack. Message-ID: <oo5487r7-q881-416q-09sr-po9856op43r8@yvfgf.mnoonqbm.arg> In-Reply-To: <4eebcbb6-3c40-4646-8c2f-0c0b552d7656@gmail.com> References: <9a30f33e-f2d3-4507-a875-6b0d2d13ca43@gmail.com> <1n85118o-1qpp-ooop-9qo9-q3p72pq3r384@yvfgf.mnoonqbm.arg> <4eebcbb6-3c40-4646-8c2f-0c0b552d7656@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --1098556516-566391300-1718228225=:2327 Content-Type: text/plain; CHARSET=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT Content-ID: <qpnrnr98-s196-ps44-95q3-97sro4008681@mnoonqbm.arg> On Wed, 12 Jun 2024, Steven Friedrich wrote: > I discovered this during testing freebsd 14.1. > > System description: > > slimline is an HP Slimline Desktop - 290-p0014 > > Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz > Coffee Lake (Core i7) > Ethernet RTL8111/8168/8411 and RTL8125 2.5GbE > Wi-Fi RTL8821CE > > In an effort to reproduce, I pulled /usr/src and /usr/ports using git. > > I started a buildworld and ssh'ed in and tail -f /var/log/Phase1.log. > > After a short while, system is frozen to ssh, and can't use console either. > The latest changes were to network code, so I'll reboot and build and install > world and kernel before I continue testing... And this does not happen if you don't bring wlan0 up? You do have three interfaces all using the same logical network it seems, which makes me wonder where packets go in first place (default route?) and certainly without lagg doesn't seem to make much sense for re0 and re1. You may also want to look into getting (headless) crashdumps setup which may help you to get more information as to what is going on. Are you also using drm-kmod and X? > Here's my ifconfig before the lockup: > > re0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 > mtu 1500 > options=60251b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4,LRO,WOL_MAGIC,RXCSUM_IPV6,TXCSUM_IPV6> > ether ??:??:??:??:??:?? > inet 192.168.1.5 netmask 0xffffff00 broadcast 192.168.1.255 > media: Ethernet autoselect (1000baseT <full-duplex>) > status: active > nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > re1: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 > mtu 1500 > options=60251b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4,LRO,WOL_MAGIC,RXCSUM_IPV6,TXCSUM_IPV6> > ether ??:??:??:??:??:?? > inet 192.168.1.55 netmask 0xffffff00 broadcast 192.168.1.255 > media: Ethernet autoselect (2500Base-T <full-duplex>) > status: active > nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > lo0: flags=1008049<UP,LOOPBACK,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 16384 > options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> > inet 127.0.0.1 netmask 0xff000000 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > groups: lo > nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> > wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > options=0 > ether ??:??:??:??:??:?? > inet 192.168.1.72 netmask 0xffffff00 broadcast 192.168.1.255 > groups: wlan > ssid channel 11 (2462 MHz 11g) bssid ??:??:??:??:??:?? > regdomain FCC country US authmode WPA2/802.11i privacy ON > deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 7 scanvalid 60 > protmode CTS wme roaming MANUAL > parent interface: rtw880 > media: IEEE 802.11 Wireless Ethernet OFDM/48Mbps mode 11g > status: associated > nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > > > On 6/12/24 10:44, Bjoern A. Zeeb wrote: >> On Wed, 12 Jun 2024, Steven Friedrich wrote: >> >>> I'm running 14.1-RELEASE, with q2 ports. >>> >>> If I configure rtw88 and wlan in /etc/rc.conf, networking locks up after a >>> short while. >> >> In what way? What's the state of wireless? Do you have logs? >> >> Do you have a parallel ethernet? Is that working? Do you use lagg in >> that case? >> >> >>> Where might I find current status of this driver? Open bug reports? >> >> Open (and closed) bug reports categorized for rtw88/rtw89 are here: >> https://bugs.freebsd.org/bugzilla/showdependencytree.cgi?id=273621&hide_resolved=0 >> > > -- Bjoern A. Zeeb r15:7 --1098556516-566391300-1718228225=:2327--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?oo5487r7-q881-416q-09sr-po9856op43r8>