From nobody Wed Jun 12 23:01:29 2024 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 4W01Hz02sFz5NdX9 for ; Wed, 12 Jun 2024 23:01:35 +0000 (UTC) (envelope-from freebsdlouisville@gmail.com) Received: from mail-oi1-x234.google.com (mail-oi1-x234.google.com [IPv6:2607:f8b0:4864:20::234]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4W01Hy5PVfz4Z3Y for ; Wed, 12 Jun 2024 23:01:34 +0000 (UTC) (envelope-from freebsdlouisville@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oi1-x234.google.com with SMTP id 5614622812f47-3d226c5a157so183364b6e.2 for ; Wed, 12 Jun 2024 16:01:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718233292; x=1718838092; darn=freebsd.org; h=content-transfer-encoding:in-reply-to:content-language:references :cc:to:subject:user-agent:mime-version:date:message-id:from:from:to :cc:subject:date:message-id:reply-to; bh=+Jq+HjebcKIf1gq2f5quOdTZnrPFyQWqgg9q5Gowy/8=; b=TQYa3c3MYr3TlIzzpwVbTfiNnpJbzKacK3p4OZ3u43ytbzXzzb5g0hlQM+tKzJUw3s kCJSYwoKnV6/jb3pxUznTWSOVj/VX8/WOmofyiYbqFKj3kCny7ILqFEAKupIT+MvjWmw wYI6cizjS5/IP56iI0OfrHX4pd4jJrLqqLiW8/UMZAtwGW54xHsC6oymxDeah/j/mERS AkF9ZVBOpgwjBQwP2V80jUdOYMLzEtFEvtz25nToi4KEUN551UHD3lqOonAg5rOW1/gC EFlwTYoMxLx3owzE/6TPdF6eiRSBFF7XNWBygEF8G5i8v0vsgaY4C5vVy13doqV22wbr cymg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718233292; x=1718838092; h=content-transfer-encoding:in-reply-to:content-language:references :cc:to:subject:user-agent:mime-version:date:message-id:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=+Jq+HjebcKIf1gq2f5quOdTZnrPFyQWqgg9q5Gowy/8=; b=MGO0j+Xb7SYotZZJHK6dFl1BvnpYB2ly+ZdsNKZ/0DtxKjwqAOud4Pr45Qr4P4ahbQ kAykt7k230ILcuUH1ldckryVbumViIlRzZdB7l0WIHwLgSdlr2UEzDQz2ukNEx+FMwIj gu35KST2tJpdQ+i9ur4i2zGe9PvvpmLVEeMxSiQiUV7xx4OXw6cMe+Sul/T7K6iDP/Eu s6DWrm4Xe5qqviFtdKCGoRGRBlOB57ee22kx/a0D4Ogc55lmavSaW3NwRuArpa4ni2b0 iKnlleMb6x11/SMs191gYZkjOIYUALGAqxp9qLS/Vg//jGrHyawK1Wun57q5D50nqYo+ qo5A== X-Gm-Message-State: AOJu0YzKrduh2OdMy97h3tZ7R6LEKGxDOJOvSnC3/MOrNBrt7h+31vkk 2vvyl8XWsNlEtsnz6SM9lmiWwvXv9E7+JTEgpNP+K1ECM31pzoa6XZ/k3w== X-Google-Smtp-Source: AGHT+IEeZgKsd9zE2/bk0VQX8ckO1czZIiLal92tPqMwIUJGDQpMvY4W1d/qDYKoxc8v2SGSOVpk4Q== X-Received: by 2002:a05:6870:9a23:b0:254:9c12:1fb6 with SMTP id 586e51a60fabf-25514ccf8damr3736520fac.33.1718233292047; Wed, 12 Jun 2024 16:01:32 -0700 (PDT) Received: from ?IPV6:2600:1015:a030:8fa9:179f:9841:ecd4:5ec4? ([2600:1015:a030:8fa9:179f:9841:ecd4:5ec4]) by smtp.gmail.com with ESMTPSA id af79cd13be357-798ab5b77cdsm2847185a.66.2024.06.12.16.01.30 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 12 Jun 2024 16:01:31 -0700 (PDT) From: Steven Friedrich X-Google-Original-From: Steven Friedrich Message-ID: <8e98eddd-3fbd-4ceb-8cba-074b805ac8d4@gmail.com> Date: Wed, 12 Jun 2024 19:01:29 -0400 List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-wireless@freebsd.org Sender: owner-freebsd-wireless@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Appears rtw88 driver hangs network stack. To: "Bjoern A. Zeeb" Cc: FreeBSD Wireless References: <9a30f33e-f2d3-4507-a875-6b0d2d13ca43@gmail.com> <1n85118o-1qpp-ooop-9qo9-q3p72pq3r384@yvfgf.mnoonqbm.arg> <4eebcbb6-3c40-4646-8c2f-0c0b552d7656@gmail.com> Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4W01Hy5PVfz4Z3Y Whatever it's worth, my knowledge of TCP/IP is basic.  My re0 interface is on the motherboard, I added re1 as a 2.5 G pcie card. I have been doing these git pulls and rebuilds for several weeks, including ssh'ing in and tailing the log to monitor the system. Only when I turn on the Wi-Fi (motherboard) does the system hang.  I read the description of lagg in the Handbook, and I could try that. Maybe it appears to work because the re1 (2.5G) interface outruns the re0 (1G) interface. On 6/12/24 17:40, Bjoern A. Zeeb wrote: > 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 >> metric 0 mtu 1500 >>  options=60251b >> >>     ether ??:??:??:??:??:?? >>     inet 192.168.1.5 netmask 0xffffff00 broadcast 192.168.1.255 >>     media: Ethernet autoselect (1000baseT ) >>     status: active >>     nd6 options=29 >> re1: flags=1008843 >> metric 0 mtu 1500 >>  options=60251b >> >>     ether ??:??:??:??:??:?? >>     inet 192.168.1.55 netmask 0xffffff00 broadcast 192.168.1.255 >>     media: Ethernet autoselect (2500Base-T ) >>     status: active >>     nd6 options=29 >> lo0: flags=1008049 metric 0 >> mtu 16384 >>  options=680003 >>     inet 127.0.0.1 netmask 0xff000000 >>     inet6 ::1 prefixlen 128 >>     inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 >>     groups: lo >>     nd6 options=21 >> wlan0: flags=8843 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 >> >> >> 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 >>> >> >> >