From nobody Sun Mar 22 00:13:33 2026 X-Original-To: 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 4fdcGj03PMz6V3HG for ; Sun, 22 Mar 2026 00:13:49 +0000 (UTC) (envelope-from ltning-freebsd-wireless@anduin.net) Received: from mail.anduin.net (mail.anduin.net [185.42.170.45]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4fdcGd0zQDz3l0D for ; Sun, 22 Mar 2026 00:13:44 +0000 (UTC) (envelope-from ltning-freebsd-wireless@anduin.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=anduin.net header.s=dkim2021 header.b=gEzV+7JH; dmarc=pass (policy=reject) header.from=anduin.net; spf=pass (mx1.freebsd.org: domain of ltning-freebsd-wireless@anduin.net designates 185.42.170.45 as permitted sender) smtp.mailfrom=ltning-freebsd-wireless@anduin.net DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=anduin.net; s=dkim2021; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From: References:To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=WhQIp/x89aICYRRPjcZ+rIEoXjijf5NFG8VQa+KreuA=; t=1774138424; x=1775002424; b=gEzV+7JH0Dcu60WKsUCzP19xCkllBkGV6mWlu8RVCt2BDZgMYCtumFa8KXqyNzoBRHUQcTGeBWT 2hYM4WMaODXfYGv2IYyDtlil6keyzcPDH3siwpfXIJ45UQ6cH+v1+V6sVM+ia6JRI3qD2eT60peJZ 5WLylRP2Nw6IUM7t2h7PG61nG9gRfD285LRjx+PC9FY/qGb0PhoUBeh/jYVJKdoYFc/hmzWO/EG1q NZnLDa3qhxyABBTtU21bMFvYlSJ6QLENBsYk4Mrn29txZMJxZrFgd9NawVd/R5ZKOJF+yrtCvK7p5 1vOXCVd/2iuiz9p1qDbzZGrAd8++hHptQDyg==; Received: by mail.anduin.net with esmtpsa (TLS1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.98.2 (FreeBSD)) (envelope-from ) id 1w46Ri-00000000ISV-2oRr for wireless@freebsd.org; Sun, 22 Mar 2026 00:13:36 +0000 Message-ID: Date: Sun, 22 Mar 2026 01:13:33 +0100 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: How is testing going? To: wireless@freebsd.org References: <6p4r5o3-4218-sn14-o712-7944359sqno6@mnoonqbm.arg> Content-Language: en-US From: ltning-freebsd-wireless@anduin.net In-Reply-To: <6p4r5o3-4218-sn14-o712-7944359sqno6@mnoonqbm.arg> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-SA-Authenticated: Yes X-Spam-Score: -1.9 X-Spam-Level: - X-Spam-Report: host: mail.modirum.com | contact: hostmaster@modirum.com | scores: BAYES_00=-1.9,NO_RELAYS=-0.001 | autolearn=no autolearn_force=no, score=0 X-Spamd-Result: default: False [-2.98 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.984]; DMARC_POLICY_ALLOW(-0.50)[anduin.net,reject]; R_SPF_ALLOW(-0.20)[+ip4:185.42.170.45/32]; R_DKIM_ALLOW(-0.20)[anduin.net:s=dkim2021]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; FROM_NO_DN(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:62248, ipnet:185.42.170.0/24, country:EE]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[wireless@freebsd.org]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[anduin.net:+] X-Rspamd-Queue-Id: 4fdcGd0zQDz3l0D X-Spamd-Bar: -- On 3/21/26 00:04, Bjoern A. Zeeb wrote: > to those who have updated.  Did you encounter further problems than > reported, > any instabilities, etc. now that it's been a few more days? Hi, I've been running stable/15-f4f418bbf8fb for a while now, and other than one crash during shutdown and one during resume, it has been stable. The behaviour is, as I reported before, the same: A crash in firmware after resume is needed to resume connectivity, and this takes some time. I've just updated to stable/15-81d2c7d3e102 and will be testing for a few more days, then report back. As I'm able to send this, I would assume there are no regressions at least. :) Thanks for your hard work (and the federation for supporting it!), /Eirik