Errors during bootup

English Applications
1

Good Morning,

My computer was damaged by a nearby lightning strike. I just finished building a new one to replace it. The new computer, a Minisforum MS-A1 is equipped with a Ryzen 9 9950X CPU, a substantial upgrade from my former Intel i5. Luckily, my SSD was not damaged and when I installed it in the new computer it worked fine, but not without an error I see on bootup. The messages disappear after a few seconds. They are as follows:

[ 0.041596][ T0] RDSEED32 is broken. Disabling the corresponding CPUID bit.
[ 0.199343][ T1] ACPI BIOS Error (bug): Failure creating named object [_SB.PCI0.GP17.XHC0._PRW], AE_ALREADY_EXISTS (20251212/dswload-326)
[ 0.199351][ T1] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20251212/psobject-220)
[ 0.199367][ T1] ACPI BIOS Error (bug): Failure creating named object [_SB.PCI0.GP17.XHC1._PRW], AE_ALREADY-EXISTS (20251212/dswload2-326)
[ 0.199369][ T1] ACPI Error: AE_ALREADY-EXISTS, During name lookup/catalog (20251212/psobject-220)
[ 0.199393][ T1] ACPI BIOS Error (bug): Failure creating named object [_PE._L19], AE_ALREADY-EXISTS (20251212/dswload2-326)
[ 0.199395][ T1] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20251212/psobject-220)

A friend who knows more about Tumbleweed and computers in general says it appears to have something to do with a random number generator, and may be related to the Ryzen 9 CPU. I wouldn’t know, so I am asking here in hopes I can get some help. In all other respects, the computer works very well and is lightning fast.

Thanks for any help!

Ken Alexander
So Phisai, Thailand

2

These are not actually problems that need to be resolved.

  • RDSEED32 is broken is a kernel mitigation to disable some unpatched microcode. It doesn’t affect 64-bit random number generation.

  • AE_ALREADY_EXISTS - this has turned up here before. It’s due to an imperfect motherboard firmware compliance with the ACPI specification. It’s completely benign.

3

Hi Jim

Thanks for the quick reply!

I understand these are not serious problems, but is there a way to make them go away?

Thanks again,

Ken
So Phisai, Thailand OK18sc

4

You should be able to hide those warnings by adding loglevel=3 to your boot command line.
Please be aware that doing so does not fix the problem.

5

Not every message that’s labeled as an ‘error’ needs to be fixed.

I suppose replacing the hardware with compliant hardware is the way to ‘fix’ these issues, but you may discover other issues down the road if other hardware-based exploits (in the case of the RDSEED32 issue) are discovered that a kernel mitigation is introduced for.

You may be able to, as OrsoBruno said, hide the messages. That won’t fix the issues; there isn’t a software “fix” for a non-compliant ACPI implementation in your BIOS.

There is never really a realistic goal in computing of “fixing” everything that reports an “error”. Many “error” messages are really just informational, even though the developers label them as “errors”.