From nobody Fri Jun 14 19:59:00 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 4W198S4g16z5PQYm for ; Fri, 14 Jun 2024 19:59:04 +0000 (UTC) (envelope-from freebsdlouisville@gmail.com) Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 4W198R5XpKz4QPb for ; Fri, 14 Jun 2024 19:59:03 +0000 (UTC) (envelope-from freebsdlouisville@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b="FY8ZS2G/"; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of freebsdlouisville@gmail.com designates 2607:f8b0:4864:20::d2b as permitted sender) smtp.mailfrom=freebsdlouisville@gmail.com Received: by mail-io1-xd2b.google.com with SMTP id ca18e2360f4ac-7eb6aedcabcso96522939f.0 for ; Fri, 14 Jun 2024 12:59:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718395143; x=1718999943; 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=rYW0SDSJkuLLz44bqnJOLF7p27LULjPYF4hWVK/sY64=; b=FY8ZS2G/9nXSEMJo6IcEPHGpJi+NwU9R+55f8vRtVW6hm+6unYbraImYmrOQR947cH hEzgNlA7pP3SgBzMEsVTCZX3ymAnYxzPAIOsLXHdClavXcLIIJYT+kxcW2gJUsj71izl 2bV19BVdqYSqiQgMXCvChyQEZqJvlUzFARGICZP/lSw+F7JA+imWAueHdgg7xblQkU3V BY6hkdGvNHS48OydI3BFJoN1kstB2zieKk6GFYzYEjHwv4+W1DpEcR2CTwjEjewrQpCN zbQ+gRPFoceua+oxCO6u/bL/WfPdMYF5PS5Os6o4TzUNudphwp1zDTpIevGzeYBgAXp1 zAIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718395143; x=1718999943; 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=rYW0SDSJkuLLz44bqnJOLF7p27LULjPYF4hWVK/sY64=; b=jI5T7qPBTaLJ5+Eg8B7/UlayU4Y3W0abjcrGKKPP8yQbC+hMKoH1nbN21lO40Xy7B4 C65V4Dbtq1qkm0e0NRQEZH29bo6AsOCUsYUh74BFUQDr2TMtOtB2XRH4O1nFkIRFxCf3 bFH8rx6PTLwHUchwHRwxnwDEtsBsIbHiOXgwQhUS6fCbc/H+cy0NNy3/5WWvyJlwF/V1 uLILJ0jlGeQbE1MhjJskl1jVlZodJcRIuaZq4dUGDj3BvYV3IRs3ecw+qNiqSQjiMXFO FU2TVQL03XmMNgFc96xmschXZ2KSsqH6YUkvr3SHxiiPAl9JZaO/NpadO4rIYOoqzZPg J+gQ== X-Gm-Message-State: AOJu0Yz4SlBOqF1quNfyZSEA/GXA4Usmhq37bbAvPETOYLoK0c48ycmf A7VEzl8WyHMuC3ps6Sgc1EmLtVFv+C66a78+7I0kPXmneqg4RH2XdqwhUw== X-Google-Smtp-Source: AGHT+IEztzBxkpSn3nVp9ovbL0aqvVscehcixzdvj46WcXpyOUQ1lrIeioCnB+IHCDPib29LHNA4IQ== X-Received: by 2002:a05:6602:13c6:b0:7eb:81d6:c929 with SMTP id ca18e2360f4ac-7ebeb49936fmr380740739f.1.1718395142630; Fri, 14 Jun 2024 12:59:02 -0700 (PDT) Received: from ?IPV6:2600:1015:a030:8fa9:8a4f:7376:2bc4:b93a? ([2600:1015:a030:8fa9:8a4f:7376:2bc4:b93a]) by smtp.gmail.com with ESMTPSA id 8926c6da1cb9f-4b956a1f7ecsm1077536173.122.2024.06.14.12.59.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 14 Jun 2024 12:59:02 -0700 (PDT) From: Steven Friedrich X-Google-Original-From: Steven Friedrich Message-ID: Date: Fri, 14 Jun 2024 15:59:00 -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-Spamd-Result: default: False [-3.03 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_SHORT(-0.04)[-0.041]; XM_UA_NO_VERSION(0.01)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TO_DN_ALL(0.00)[]; ARC_NA(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-wireless@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-wireless@freebsd.org]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::d2b:from] X-Rspamd-Queue-Id: 4W198R5XpKz4QPb I am now using lagg for re0, re1, and wlan0.  I will continue testing rtw88 driver. Thanks for your patience. 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 >>> >> >> >