From nobody Sat Oct 14 14:33:32 2023 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 4S75TY2J5bz4wqxh for ; Sat, 14 Oct 2023 14:33:37 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (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 4S75TW6LBsz3dWb for ; Sat, 14 Oct 2023 14:33:35 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp; dmarc=none Received: from kalamity.joker.local (123-1-80-101.area1b.commufa.jp [123.1.80.101]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 39EEXWE1055188 for ; Sat, 14 Oct 2023 23:33:33 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Sat, 14 Oct 2023 23:33:32 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Subject: Re: AMD Zen 4 (Ryzen 7000) resource allocation issues (on 14.0) Message-Id: <20231014233332.8f44810859a0b482dadc5104@dec.sakura.ne.jp> In-Reply-To: <20231014161204.7845849b@ernst.home> References: <20231014161204.7845849b@ernst.home> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spamd-Bar: - X-Spamd-Result: default: False [-1.35 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; AUTH_NA(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.85)[-0.846]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; R_DKIM_NA(0.00)[]; HAS_ORG_HEADER(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; R_SPF_NA(0.00)[no SPF record]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DMARC_NA(0.00)[sakura.ne.jp]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4S75TW6LBsz3dWb On Sat, 14 Oct 2023 14:12:04 +0000 Gary Jennejohn wrote: > On Sat, 14 Oct 2023 15:05:22 +0200 > Daniel Engberg wrote: > > > On 2023-10-14T13:07:11.000+02:00, Daniel Engberg > > wrote: > > > > > Hi, > > >  > > > After updating BIOS on my Asus motherboard (ProArt X670E-CREATOR > > > WIFI) the kernel fails to allocate resources for a bunch of devices > > > including USB and built-in SATA. This behaviour is also observed on > > > at least ASRock boards too so it doesn't seem to be a specific issue > > > to one manufacturer or model. If anyone has any ideas how to fix > > > this I'd be grateful. > > >  > > > I've tried turning off and on "Fast boot" in BIOS without any > > > success, enabing SR-IOV makes the kernel hang during boot. > > >  > > > dmesg with older bios (working): > > >  > > > https://forums.freebsd.org/threads/sata-drives-show-in-bios-but-wont-show-in-dev.89656/page-2#post-620854 > > >  > > > dmesg with new bios (not working): > > >  > > > https://reviews.freebsd.org/P612 > > >  > > > Related PR: > > >  > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272507 > > >  > > > If you need to more information or testing just ask and please CC me > > > when replying. > > >  > > > Best regards, > > >  > > > Daniel > > > > In addition to the above, 13.2-RELEASE fails in the same way, also > > 15.0-CURRENT (20231005-8818f0f1124e-265728). In addition to that, USB > > also fails to init so USB devices won't work once the kernel boots. > > > > Considering that none of the current FreeBSD versions work I suspect > that you'll have to flash the previous BIOS version to get a working > system again. > > -- > Gary Jennejohn Or check in detail for defaults on BIOS (UEFI firmware) settings changes. Hopefully, these are usually described in readme or update notes or something alike. If any, try reverting back to the previous defaults except you intentionally changed on previous BIOS. Sometimes BIOS vendors change their BIOS defaults to something FreeBSD dislikes. -- Tomoaki AOKI