Date: Sat, 14 Oct 2023 16:29:41 +0200 From: Daniel Engberg <daniel.engberg.lists@pyret.net> To: garyj@gmx.de Cc: freebsd-current@freebsd.org Subject: Re: AMD Zen 4 (Ryzen 7000) resource allocation issues (on 14.0) Message-ID: <39208aff4c6519a80ca0741e41810fc8@mail.infomaniak.com> In-Reply-To: <20231014161204.7845849b@ernst.home> References: <f62a4a2cc2f773e46d4769bb2a5d8e77@mail.infomaniak.com> <cf451c52b7974d96f91da41e8cf3ac4b@mail.infomaniak.com> <20231014161204.7845849b@ernst.home>
next in thread | previous in thread | raw e-mail | index | archive | help
--_=_swift_1697293781_c6be3ad2054c9a98ed54571b46ee38b9_=_ Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2023-10-14T16:12:04.000+02:00, Gary Jennejohn <garyj@gmx.de> wrote: = >=C2=A0On=C2=A0Sat,=C2=A014=C2=A0Oct=C2=A02023=C2=A015:05:22=C2=A0+0200= >=C2=A0 >=C2=A0Daniel=C2=A0Engberg=C2=A0<daniel.engberg.lists@pyret.ne= t>=C2=A0wrote: >=C2=A0 >>=C2=A0=C2=A0On=C2=A02023-10-14T13:07:11.000+02= :00,=C2=A0Daniel=C2=A0Engberg >>=C2=A0=C2=A0 >>=C2=A0=C2=A0=C2=A0<danie= l.engberg.lists@pyret.net>=C2=A0wrote: >>=C2=A0=C2=A0 >>>=C2=A0=C2= =A0=C2=A0Hi, >>>=C2=A0=C2=A0=C2=A0 >>>=C2=A0=C2=A0=C2=A0=C2=A0After= =C2=A0updating=C2=A0BIOS=C2=A0on=C2=A0my=C2=A0Asus=C2=A0motherboard=C2= =A0(ProArt >>>=C2=A0=C2=A0=C2=A0X670E-CREATOR >>>=C2=A0=C2=A0=C2=A0 >= >>=C2=A0=C2=A0=C2=A0=C2=A0WIFI)=C2=A0the=C2=A0kernel=C2=A0fails=C2=A0to= =C2=A0allocate=C2=A0resources=C2=A0for=C2=A0a=C2=A0bunch=C2=A0of >>>= =C2=A0=C2=A0=C2=A0devices >>>=C2=A0=C2=A0=C2=A0 >>>=C2=A0=C2=A0=C2= =A0=C2=A0including=C2=A0USB=C2=A0and=C2=A0built-in=C2=A0SATA.=C2=A0This= =C2=A0behaviour=C2=A0is=C2=A0also >>>=C2=A0=C2=A0=C2=A0observed=C2=A0on= >>>=C2=A0=C2=A0=C2=A0 >>>=C2=A0=C2=A0=C2=A0=C2=A0at=C2=A0least=C2= =A0ASRock=C2=A0boards=C2=A0too=C2=A0so=C2=A0it=C2=A0doesn't=C2=A0seem=C2= =A0to=C2=A0be=C2=A0a=C2=A0specific >>>=C2=A0=C2=A0=C2=A0issue >>>=C2= =A0=C2=A0=C2=A0 >>>=C2=A0=C2=A0=C2=A0=C2=A0to=C2=A0one=C2=A0manufacturer= =C2=A0or=C2=A0model.=C2=A0If=C2=A0anyone=C2=A0has=C2=A0any=C2=A0ideas=C2= =A0how=C2=A0to >>>=C2=A0=C2=A0=C2=A0fix >>>=C2=A0=C2=A0=C2=A0 >>>= =C2=A0=C2=A0=C2=A0=C2=A0this=C2=A0I'd=C2=A0be=C2=A0grateful. >>>=C2=A0= =C2=A0=C2=A0 >>>=C2=A0=C2=A0=C2=A0=C2=A0I've=C2=A0tried=C2=A0turning= =C2=A0off=C2=A0and=C2=A0on=C2=A0"Fast=C2=A0boot"=C2=A0in=C2=A0BIOS=C2=A0wit= hout=C2=A0any >>>=C2=A0=C2=A0=C2=A0 >>>=C2=A0=C2=A0=C2=A0=C2=A0success,= =C2=A0enabing=C2=A0SR-IOV=C2=A0makes=C2=A0the=C2=A0kernel=C2=A0hang=C2= =A0during=C2=A0boot. >>>=C2=A0=C2=A0=C2=A0 >>>=C2=A0=C2=A0=C2=A0=C2= =A0dmesg=C2=A0with=C2=A0older=C2=A0bios=C2=A0(working): >>>=C2=A0=C2= =A0=C2=A0 >>>=C2=A0=C2=A0=C2=A0=C2=A0https://forums.freebsd.org/threads/s= ata-drives-show-in-bios-but-wont-show-in-dev.89656/page-2#post-620854 >>>= =C2=A0=C2=A0=C2=A0 >>>=C2=A0=C2=A0=C2=A0=C2=A0dmesg=C2=A0with=C2=A0new= =C2=A0bios=C2=A0(not=C2=A0working): >>>=C2=A0=C2=A0=C2=A0 >>>=C2=A0= =C2=A0=C2=A0=C2=A0https://reviews.freebsd.org/P612 >>>=C2=A0=C2=A0=C2= =A0 >>>=C2=A0=C2=A0=C2=A0=C2=A0Related=C2=A0PR: >>>=C2=A0=C2=A0=C2= =A0 >>>=C2=A0=C2=A0=C2=A0=C2=A0https://bugs.freebsd.org/bugzilla/show_bug= .cgi?id=3D272507 >>>=C2=A0=C2=A0=C2=A0 >>>=C2=A0=C2=A0=C2=A0=C2=A0If= =C2=A0you=C2=A0need=C2=A0to=C2=A0more=C2=A0information=C2=A0or=C2=A0testing= =C2=A0just=C2=A0ask=C2=A0and=C2=A0please >>>=C2=A0=C2=A0=C2=A0CC=C2=A0me= >>>=C2=A0=C2=A0=C2=A0 >>>=C2=A0=C2=A0=C2=A0=C2=A0when=C2=A0replying.= >>>=C2=A0=C2=A0=C2=A0 >>>=C2=A0=C2=A0=C2=A0=C2=A0Best=C2=A0regards, = >>>=C2=A0=C2=A0=C2=A0 >>>=C2=A0=C2=A0=C2=A0=C2=A0Daniel >>=C2=A0=C2= =A0 >>=C2=A0=C2=A0=C2=A0In=C2=A0addition=C2=A0to=C2=A0the=C2=A0above,= =C2=A013.2-RELEASE=C2=A0fails=C2=A0in=C2=A0the=C2=A0same=C2=A0way, >>= =C2=A0=C2=A0also >>=C2=A0=C2=A0 >>=C2=A0=C2=A0=C2=A015.0-CURRENT=C2= =A0(20231005-8818f0f1124e-265728).=C2=A0In=C2=A0addition=C2=A0to=C2=A0that,= >>=C2=A0=C2=A0USB >>=C2=A0=C2=A0 >>=C2=A0=C2=A0=C2=A0also=C2=A0fails= =C2=A0to=C2=A0init=C2=A0so=C2=A0USB=C2=A0devices=C2=A0won't=C2=A0work=C2= =A0once=C2=A0the=C2=A0kernel >>=C2=A0=C2=A0boots. >=C2=A0 >=C2=A0Cons= idering=C2=A0that=C2=A0none=C2=A0of=C2=A0the=C2=A0current=C2=A0FreeBSD= =C2=A0versions=C2=A0work=C2=A0I=C2=A0suspect >=C2=A0 >=C2=A0that=C2= =A0you'll=C2=A0have=C2=A0to=C2=A0flash=C2=A0the=C2=A0previous=C2=A0BIOS= =C2=A0version=C2=A0to=C2=A0get=C2=A0a=C2=A0working >=C2=A0 >=C2=A0syste= m=C2=A0again. >=C2=A0 >=C2=A0-- >=C2=A0 >=C2=A0Gary=C2=A0Jennejohn= Hi, That's true although I'm going to guess it's going to be an = ongoing issue as at least one user with an ASRock board also has similar= issues (see PR). Looking into if downgrade is possible too. Best re= gards, Daniel --_=_swift_1697293781_c6be3ad2054c9a98ed54571b46ee38b9_=_ Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <div><br></div><div ><div><br></div></div><div><br></div><div class=3D"ik_m= ail_quote answerContentMessage"><div>On 2023-10-14T16:12:04.000+02:00, Gary= Jennejohn <garyj@gmx.de> wrote:<br></div><blockquote class=3D"ws-ng-= quote"><pre style=3D"white-space: normal;"><div>On Sat, 14 Oct 2023 15:05:2= 2 +0200<br></div><div>Daniel Engberg <<a href=3D"mailto:daniel.engberg.l= ists@pyret.net" class=3D"defaultMailLink">daniel.engberg.lists@pyret.net</a= >> wrote:<br></div><div><br></div><blockquote class=3D"ws-ng-quote"><div= > On 2023-10-14T13:07:11.000+02:00, Daniel Engberg<br></div><div> <<a h= ref=3D"mailto:daniel.engberg.lists@pyret.net" class=3D"defaultMailLink">dan= iel.engberg.lists@pyret.net</a>> wrote:<br></div><div><br></div><blockqu= ote class=3D"ws-ng-quote"><div> Hi,<br></div><div> <br></div><div> Afte= r updating BIOS on my Asus motherboard (ProArt X670E-CREATOR<br></div><div>= WIFI) the kernel fails to allocate resources for a bunch of devices<br></= div><div> including USB and built-in SATA. This behaviour is also observed= on<br></div><div> at least ASRock boards too so it doesn't seem to be a s= pecific issue<br></div><div> to one manufacturer or model. If anyone has a= ny ideas how to fix<br></div><div> this I'd be grateful.<br></div><div> <= br></div><div> I've tried turning off and on "Fast boot" in BIOS without a= ny<br></div><div> success, enabing SR-IOV makes the kernel hang during boo= t.<br></div><div> <br></div><div> dmesg with older bios (working):<br></d= iv><div> <br></div><div> <a href=3D"https://forums.freebsd.org/threads/sa= ta-drives-show-in-bios-but-wont-show-in-dev.89656/page-2#post-620854" class= =3D"defaultMailLink" target=3D"_blank" rel=3D"noopener noreferrer" data-ik= =3D"ik-secure">https://forums.freebsd.org/threads/sata-drives-show-in-bios-= but-wont-show-in-dev.89656/page-2#post-620854</a><br></div><div> <br></div= ><div> dmesg with new bios (not working):<br></div><div> <br></div><div> = <a href=3D"https://reviews.freebsd.org/P612" class=3D"defaultMailLink" tar= get=3D"_blank" rel=3D"noopener noreferrer" data-ik=3D"ik-secure">https://re= views.freebsd.org/P612</a><br></div><div> <br></div><div> Related PR:<br>= </div><div> <br></div><div> <a href=3D"https://bugs.freebsd.org/bugzilla/= show_bug.cgi?id=3D272507" class=3D"defaultMailLink" target=3D"_blank" rel= =3D"noopener noreferrer" data-ik=3D"ik-secure">https://bugs.freebsd.org/bug= zilla/show_bug.cgi?id=3D272507</a><br></div><div> <br></div><div> If you = need to more information or testing just ask and please CC me<br></div><div= > when replying.<br></div><div> <br></div><div> Best regards,<br></div><= div> <br></div><div> Daniel<br></div></blockquote><div> <br></div><div> I= n addition to the above, 13.2-RELEASE fails in the same way, also<br></div>= <div> 15.0-CURRENT (20231005-8818f0f1124e-265728). In addition to that, USB= <br></div><div> also fails to init so USB devices won't work once the kerne= l boots.<br></div><div><br></div></blockquote><div> <br></div><div>Consider= ing that none of the current FreeBSD versions work I suspect<br></div><div>= that you'll have to flash the previous BIOS version to get a working<br></d= iv><div>system again.<br></div><div><br></div><div>--<br></div><div>Gary Je= nnejohn<br></div></pre></blockquote></div><div>Hi,<br></div><div><br></div>= <div>That's true although I'm going to guess it's going to be an ongoing is= sue as at least one user with an ASRock board also has similar issues (see = PR). Looking into if downgrade is possible too.<br></div><div><br></div><di= v>Best regards,<br></div><div>Daniel<br></div> --_=_swift_1697293781_c6be3ad2054c9a98ed54571b46ee38b9_=_--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39208aff4c6519a80ca0741e41810fc8>