From nobody Mon Aug 18 19:10:27 2025 X-Original-To: freebsd-current@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 4c5Mk51lv7z64M7W for ; Mon, 18 Aug 2025 19:10:37 +0000 (UTC) (envelope-from saper@saper.info) Received: from q.saper.info (q.saper.info [IPv6:2605:2700:0:2:a800:ff:fec7:5c61]) (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-signature ECDSA (secp384r1) client-digest SHA384) (Client CN "q.saper.info", Issuer "E6" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4c5Mk41D3fz3TY5 for ; Mon, 18 Aug 2025 19:10:36 +0000 (UTC) (envelope-from saper@saper.info) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=saper.info header.s=Sep2014 header.b=FXrGIe33; dmarc=none; spf=none (mx1.freebsd.org: domain of saper@saper.info has no SPF policy when checking 2605:2700:0:2:a800:ff:fec7:5c61) smtp.mailfrom=saper@saper.info Received: from q.saper.info (localhost [127.0.0.1]) by q.saper.info (8.18.1/8.18.1) with ESMTPS id 57IJAR0v074637 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Mon, 18 Aug 2025 19:10:27 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1755544228; bh=AznfHMhTpvSAV3ue/HljUDK2A5f16XLUw1vkZCgdd7Y=; h=Date:From:To:Subject; b=FXrGIe33oYDjyZMgTgiWxArrivv6IsYBKdbtcj7zLePCsPd0FhQ2ZQqQ2hTPzSDts +7XFKOcOTunM941oVddTGwJjf9iPFos1b4LrE6WaKgArQyoI4x4i81gpC283MzALv3 hwVFi9zXKh2s9aDGstoeEkmmKagFF8ZcBsTfLlLs= Received: from localhost (saper@localhost) by q.saper.info (8.18.1/8.18.1/Submit) with ESMTP id 57IJAR4n074634 for ; Mon, 18 Aug 2025 19:10:27 GMT (envelope-from saper@saper.info) X-Authentication-Warning: q.saper.info: saper owned process doing -bs Date: Mon, 18 Aug 2025 19:10:27 +0000 From: Marcin Cieslak To: FreeBSD Current Subject: wifibox/passthrough broken after May 2025? Message-ID: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=ISO-8859-15 Content-Transfer-Encoding: 8BIT X-Spamd-Bar: - X-Spamd-Result: default: False [-1.69 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.89)[-0.892]; CTE_CASE(0.50)[]; R_DKIM_ALLOW(-0.20)[saper.info:s=Sep2014]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[saper.info]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:47066, ipnet:2605:2700::/32, country:US]; MISSING_XM_UA(0.00)[]; R_SPF_NA(0.00)[no SPF record]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@FreeBSD.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; HAS_XAW(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RECEIVED_HELO_LOCALHOST(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[saper.info:+] X-Rspamd-Queue-Id: 4c5Mk41D3fz3TY5 After the upgrade to this: commit ac641d55ea0622f06baa60b9d22ef4880007d8c4 (HEAD -> main, 15-current-running-18-aug-2025) Author: Dag-Erling Smørgrav Date: Sat Aug 2 01:18:16 2025 +0200 wifibox is no longer starting because it seems trying to fight the ppc0 device: >From /var/log/wifibox.log: 2025-08-04T11:35:07+0200 WARN PPT device pci2:0:0 could not be destroyed 2025-08-04T11:35:13+0200 WARN Guest is not up after 5 seconds 2025-08-04T11:35:14+0200 WARN PPT device pci2:0:0 could not be destroyed 2025-08-04T11:35:20+0200 WARN PPT device pci2:0:0 could not be destroyed 2025-08-04T11:35:27+0200 WARN PPT device pci2:0:0 could not be destroyed 2025-08-04T11:35:34+0200 WARN PPT device pci2:0:0 could not be destroyed 2025-08-04T11:35:40+0200 WARN PPT device pci2:0:0 could not be destroyed 2025-08-04T11:35:47+0200 WARN PPT device pci2:0:0 could not be destroyed 2025-08-04T11:35:54+0200 WARN PPT device pci2:0:0 could not be destroyed 2025-08-04T11:36:00+0200 WARN PPT device pci2:0:0 could not be destroyed ppt0 seems to get attached/detached all the time Which change could have caused this? It all works fine when running boot environment built with this commit: commit 3d2957336c7ddaa0a29cf60cfd458c07df1f5be9 (15-current-running-02-aug-2025) Author: Jasper Tran O'Leary Date: Tue May 20 23:34:45 2025 +0000 This is a MacBookPro13,1 with ppt0@pci0:2:0:0: class=0x028000 rev=0x05 hdr=0x00 vendor=0x14e4 device=0x43a3 subvendor=0x106b subdevice=0x0159 vendor = 'Broadcom Inc. and subsidiaries' device = 'BCM4350 802.11ac Wireless Network Adapter' class = network > grep -v '^#' /usr/local/etc/wifibox/bhyve.conf |grep -v '^$' cpus=1 memory=128M console=yes passthru=2/0/0 priority=50 stop_wait_max=30