Error start server - ACPI BIOS ERROR (bug): Failure creating named object

Support
1

What type of hardware are you using: Old laptop or computer
What YunoHost version are you running: 12.0.14
How are you able to access your server: Direct access via physical keyboard/screen
Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: no

Describe your issue

English (google traduc) :

Hello everyone,

I’m new to Yunohost. I installed Yunohost on a ThinkCentre V530s.

The installation went well. I was able to install NextCloud (my main use), everything works, and I was able to sync my files without any issues.

I’m joining the forum because I noticed errors when I started the machine.

I took a photo with my smartphone and I’m posting it.

I don’t know if the issue is serious or if it can be resolved.

Thanks to the community.

French:

Bonjour a tous

je suis nouveau avec yunohost. j’ai installé yunohost sur un thinkcentre v530s.

Tout c’est bien passé pour l’installation, j’ai pu installé nextcloud (usage principal), tout fonctionne et j’ai pu synchroniser mes fichiers sans problème.

Si je vous rejoinds sur le forum c’est parce que je me suis rendu compte qu’au démarage de la machine il y avait des erreurs.

j’ai fait une photo avec mon smartphone que je vous poste.

je ne sais pas si le soucis est grave, si on peut le résoudre.

merci à la communauté.

Share relevant logs or error messages

[ 0.176854] ACPI BIOS Error (bug): Failure creating named object [_SB.PCIO.XRHUB.SS00._UPC], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.176861] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.176866] ACPI BIOS Error (bug): Failure creating named object [_SB.PCIO.XRHUB.SS08._PLD], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.176873] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.176877] ACPI BIOS Error (bug): Failure creating named object [_SB.PCIO.XRHUB.SS09._UPC], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.176883] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.176888] ACPI BIOS Error (bug): Failure creating named object [_SB.PCIO.XRHUB.SS10._UPC], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.176894] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.179241] ACPI BIOS Error (bug): Failure creating named object [_SB.PCIO.XRHUB.SS10._PLD], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.179248] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.179654] ACPI BIOS Error (bug): Failure creating named object [_SB.PCIO.XRHUB.SS10._UPC], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.179661] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)

[ 3.791012] /dev/nvme0n1p2: clean, 111976/29212672 files, 3325664/116801232 blocks

2

This ain’t a YunoHost issue, it’s more something related to hardward / kernel / low-level …

Anyway, googling the error message I end up on https://askubuntu.com/questions/1480809/acpi-bios-errorbug-failure-creating-named-object-sb-pcio-gppo-vga-ae-al

with a comment suggesting that :

The notice is benign, is not the cause of a hangup, All it is is a mismatch between the bios and the kernel where the bios does not live up to its specifications. By the way: we all get these since as of kernel 5.19 the kernel devs decided to show these (before that they got suppressed).

or in another thread :

Some BIOS/UEFI developers are just lazy and don’t implement the entire ACPI specification into their BIOS/UEFI, or more worse, they implement it in the wrong way. When Linux tries to read some specific ACPI parameters, which don’t exist, or are wrong, it fails and reports this kind of error.

So TL;DR, i wouldn’t mind too much about it and just ignore it …