Re: AMD Zen 4 (Ryzen 7000) resource allocation issues (on 14.0)

From: Daniel Engberg <daniel.engberg.lists_at_pyret.net>
Date: Sat, 14 Oct 2023 14:29:41 UTC
On 2023-10-14T16:12:04.000+02:00, Gary Jennejohn <garyj@gmx.de> wrote:

> On Sat, 14 Oct 2023 15:05:22 +0200
> 
> Daniel Engberg <daniel.engberg.lists@pyret.net> wrote:
> 
>>  On 2023-10-14T13:07:11.000+02:00, Daniel Engberg
>>  
>>   <daniel.engberg.lists@pyret.net> 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

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 regards,

Daniel