Erreurs au démarrage ACPI USB BT

andrea · Novembre 28, 2018, 10:12am

Bonjour à tous,
nouveau sur debian, je constate quelques erreurs au démarrage.

Tout d’abord, le matos:
lspci
me donne:

00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 540M] (rev a1)
02:00.0 Ethernet controller: Broadcom Limited NetLink BCM57785 Gigabit Ethernet PCIe (rev 10)
02:00.1 SD Host controller: Broadcom Limited BCM57765/57785 SDXC/MMC Card Reader (rev 10)
02:00.2 System peripheral: Broadcom Limited BCM57765/57785 MS Card Reader (rev 10)
02:00.3 System peripheral: Broadcom Limited BCM57765/57785 xD-Picture Card Reader (rev 10)
03:00.0 Network controller: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) (rev 01)
05:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)

ensuite les erreurs en questions:

root@debian:/home/andrea#

journalctl -r -p err

-- Logs begin at Wed 2018-11-28 07:21:50 CET, end at Wed 2018-11-28 08:11:11 CET. --
nov 28 07:22:00 debian avahi-daemon[566]: chroot.c: open() failed: No such file or directory
nov 28 07:21:57 debian kernel: Bluetooth: Loading patch file failed
nov 28 07:21:57 debian kernel: usb 3-1.6: firmware: failed to load ar3k/AthrBT_0x01020200.dfu (-2)
nov 28 07:21:55 debian kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.PEG0.PEGP.DD02._BCL] (Node ffff8d45571dc4d8), AE_NOT_FOUND (201608
nov 28 07:21:55 debian kernel: ACPI Error: [\_SB_.PCI0.GFX0.DD02._BCL] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
nov 28 07:21:55 debian kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.PEG0.PEGP.DD02._BCL] (Node ffff8d45571dc4d8), AE_NOT_FOUND (201608
nov 28 07:21:55 debian kernel: ACPI Error: [\_SB_.PCI0.GFX0.DD02._BCL] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)

ensuite je ne sais pas si ça peut servir mais… :

root@debian:/home/andrea#

dmesg -l warn

[    0.011177] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.011178] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[   10.868018] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20160831/utaddress-247)
[   10.868026] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20160831/utaddress-247)
[   10.868030] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000055F (\_SB.PCI0.PEG0.PEGP.GPIO) (20160831/utaddress-247)
[   10.868033] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20160831/utaddress-247)
[   10.868036] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000055F (\_SB.PCI0.PEG0.PEGP.GPIO) (20160831/utaddress-247)
[   10.868039] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20160831/utaddress-247)
[   10.868042] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000055F (\_SB.PCI0.PEG0.PEGP.GPIO) (20160831/utaddress-247)
[   10.868045] lpc_ich: Resource conflict(s) found affecting gpio_ich
[   12.161630] MXM: GUID detected in BIOS
[   12.161735] ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[   12.161826] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[   12.161921] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[   13.369733] uvcvideo 3-1.3:1.0: Entity type for entity Extension 3 was not initialized!
[   13.369737] uvcvideo 3-1.3:1.0: Entity type for entity Processing 2 was not initialized!
[   13.369739] uvcvideo 3-1.3:1.0: Entity type for entity Camera 1 was not initialized!
[   13.903367] usb 3-1.6: Direct firmware load for ar3k/AthrBT_0x01020200.dfu failed with error -2
[   13.903407] ath3k: probe of 3-1.6:1.0 failed with error -2
[   17.931718] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[   17.932089] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)

…

Info supplémentaires : mon wifi fonctionne, mon bluetooth non, quand aux performances graphiques, je les trouve médiocres et:

root@debian:/home/andrea# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:  Debian GNU/Linux 9.6 (stretch)
Release:  9.6
Codename: stretch

…

ps: je suis suis pas superbon, alors tout en douceur les explications

un grand merci d’avance!

mattotop · Novembre 28, 2018, 8:43pm

Rien ne ressort de précis quand on googlise le message d’erreur, il faudrait peut être le dmesg dans son intégralité pour voir les messages avant/aprés ou dmesg | grep avahi

Pour ton bluetooth, il doit te manque un paquet de firmware.
Ici, ça doit être le paquet firmware-atheros, qu’il faut installer:
apt install firmware-atheros

Ca, c’est pénible, il faut vivre avec, ça ne change rien au bon fonctionnement de la machine.
L’alternative juste pour couper le message est de désactiver l’acpi au boot, sachant que ça peut poser des problémes sur la gestion d’autres composants matériels que celui qui fait raler l’acpi.
Il parait que l’équipe acpi y travaillait, ça disparaitra peut être chez toi avec une version noyau ou acpi plus récents.

andrea · Décembre 2, 2018, 2:15pm

Merci beaucoup pour la réponse!

Alors en revenant sur les ACPI: vu que c’est la faute à personne, je suis disposé à vivre avec…
Mais il y a-t’il un moyen de masquer ces messages qui manquent d’élégance au démarage?
(surtout que j’aime bien vanter linux au milieu de mon entourage )

si non , à part ça j’ai installé le firmware-atheros et la partie erreur usb/bluetooth a disparu, et mon bluetooth fonctionne en prime… merci pour vos réponses!

mattotop · Décembre 2, 2018, 4:37pm

Bah je te l’ai dis:

en passant un argument noacpi au boot du noyau

andrea · Décembre 3, 2018, 12:41am

merci mattotop, mais est ce que cela va inpacter sur le bon fonctionnement de la machine après démarrage?

peut tu me mettre un exemple de ce que je dois rajouter et ou exactement?
merci infiniment pour ta réponse!

mattotop · Décembre 3, 2018, 2:09pm

Ben oui ça impacte…
Et c’est pour ça que tout en le mentionnant, je suggérais (peut être trop subtilement) que c’était une solution un peu trop violente.

Pour complétement désactiver l’acpi (ce qu’effectivement je ne recommande pas), il faut aller dans /etc/default/grub pour modifier GRUB_CMDLINE_LINUX="" pour y mettre GRUB_CMDLINE_LINUX=“noacpi”
Aprés, tu fais un update-grub, et ça change la manière que grub a de lancer ton noyau.

J’ai vu passer des alternatives plus fines, consistant à désactiver juste le sous systéme de l’acpi qui génère ces erreurs en passant d’autres paramètres, mais je ne sais pas comment détecter le sous système foireux ni ou trouver quel paramètre de lancement il faut passer.

anon97446390 · Décembre 3, 2018, 2:20pm

Tu es nouveau avec Debian @andrea

Couper l’ACPI pour un souci d’esthétique va probablement te créer des ennuis bien plus concrets.

Je ne le recommande pas non plus.

andrea · Décembre 5, 2018, 7:09am

Bonjour à tous, alors dernières nouvelles!

Effectivement j’ai coupé l’acpi et j’ai eu le droit à un superbe magnifique crash

par contre j’avais un problème graphique… sur un autre forum , on m’a donné la solution comment le résoudre … et sur 4 erreurs d’acpi, il ne m’en reste que deux…!

https://debian-facile.org/viewtopic.php?id=23062

Je ne sais ni pourquoi, ni comment, mais on dirait qu’on peut faire mieux que les ignorer ou vivre avec?

anon97446390 · Décembre 5, 2018, 7:49am

Bonjour @andrea

Bravo !

En expliquant un simple problème constaté, tu as eu plus facilement une réponse adaptée et une solution.

Lire la mémoire tampon de message du noyau et en déduire le comportement à adopter peut être plus difficile.

Il reste intéressant que tu mentionnes les deux erreurs ACPI restantes ; quitte à les ignorer et vivre avec.

andrea · Décembre 5, 2018, 1:51pm

r2mi, est ceque cette commande vous donne assez d’information?

root@debian:/home/andrea# dmesg -l warn
[    0.011178] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.011179] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[    9.728381] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20160831/utaddress-247)
[    9.728389] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20160831/utaddress-247)
[    9.728392] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000055F (\_SB.PCI0.PEG0.PEGP.GPIO) (20160831/utaddress-247)
[    9.728396] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20160831/utaddress-247)
[    9.728399] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000055F (\_SB.PCI0.PEG0.PEGP.GPIO) (20160831/utaddress-247)
[    9.728402] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20160831/utaddress-247)
[    9.728405] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000055F (\_SB.PCI0.PEG0.PEGP.GPIO) (20160831/utaddress-247)
[    9.728408] lpc_ich: Resource conflict(s) found affecting gpio_ich
[   11.972015] uvcvideo 3-1.3:1.0: Entity type for entity Extension 3 was not initialized!
[   11.972021] uvcvideo 3-1.3:1.0: Entity type for entity Processing 2 was not initialized!
[   11.972024] uvcvideo 3-1.3:1.0: Entity type for entity Camera 1 was not initialized!
[   21.611079] bbswitch: loading out-of-tree module taints kernel.
[   21.611871] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[   21.613031] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[  914.235471] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6
[  936.030127] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6
[ 1033.090884] atkbd serio0: Unknown key pressed (translated set 2, code 0x93 on isa0060/serio0).
[ 1033.090891] atkbd serio0: Use 'setkeycodes e013 <keycode>' to make it known.
[ 1033.104805] atkbd serio0: Unknown key released (translated set 2, code 0x93 on isa0060/serio0).
[ 1033.104822] atkbd serio0: Use 'setkeycodes e013 <keycode>' to make it known.
[ 1033.635420] atkbd serio0: Unknown key pressed (translated set 2, code 0x93 on isa0060/serio0).
[ 1033.635428] atkbd serio0: Use 'setkeycodes e013 <keycode>' to make it known.
[ 1033.647509] atkbd serio0: Unknown key released (translated set 2, code 0x93 on isa0060/serio0).
[ 1033.647516] atkbd serio0: Use 'setkeycodes e013 <keycode>' to make it known.
[ 1034.465154] atkbd serio0: Unknown key pressed (translated set 2, code 0x93 on isa0060/serio0).
[ 1034.465160] atkbd serio0: Use 'setkeycodes e013 <keycode>' to make it known.
[ 1034.475652] atkbd serio0: Unknown key released (translated set 2, code 0x93 on isa0060/serio0).
[ 1034.475659] atkbd serio0: Use 'setkeycodes e013 <keycode>' to make it known.
[ 1037.299594] atkbd serio0: Unknown key pressed (translated set 2, code 0x93 on isa0060/serio0).
[ 1037.299605] atkbd serio0: Use 'setkeycodes e013 <keycode>' to make it known.
[ 1037.320634] atkbd serio0: Unknown key released (translated set 2, code 0x93 on isa0060/serio0).
[ 1037.320642] atkbd serio0: Use 'setkeycodes e013 <keycode>' to make it known.
[ 1040.820286] atkbd serio0: Unknown key pressed (translated set 2, code 0x93 on isa0060/serio0).
[ 1040.820295] atkbd serio0: Use 'setkeycodes e013 <keycode>' to make it known.
[ 1040.831846] atkbd serio0: Unknown key released (translated set 2, code 0x93 on isa0060/serio0).
[ 1040.831855] atkbd serio0: Use 'setkeycodes e013 <keycode>' to make it known.
[ 1064.891672] Suspending console(s) (use no_console_suspend to debug)
[ 1067.467572] NOHZ: local_softirq_pending 202
[ 1067.467576] NOHZ: local_softirq_pending 202
[ 1067.479946]  cache: parent cpu1 should not be sleeping
[ 1067.482931]  cache: parent cpu2 should not be sleeping
[ 1067.485960]  cache: parent cpu3 should not be sleeping
[ 1067.489550]  cache: parent cpu4 should not be sleeping
[ 1067.493167]  cache: parent cpu5 should not be sleeping
[ 1067.496823]  cache: parent cpu6 should not be sleeping
[ 1067.500038]  cache: parent cpu7 should not be sleeping
[ 1067.893321] ACPI : button: The lid device is not compliant to SW_LID.
[ 1068.580322] done.
[ 1068.941472] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[ 1096.027236] Suspending console(s) (use no_console_suspend to debug)
[ 1098.552289]  cache: parent cpu1 should not be sleeping
[ 1098.555297]  cache: parent cpu2 should not be sleeping
[ 1098.558844]  cache: parent cpu3 should not be sleeping
[ 1098.562458]  cache: parent cpu4 should not be sleeping
[ 1098.566124]  cache: parent cpu5 should not be sleeping
[ 1098.569272]  cache: parent cpu6 should not be sleeping
[ 1098.572488]  cache: parent cpu7 should not be sleeping
[ 1100.237607] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[ 1370.637501] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6
[ 1373.404150] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6

anon97446390 · Décembre 5, 2018, 11:00am

pour deux erreurs, ça fait un tas.

Personnellement, je ne vais pas m’en occuper car je ne connais pas assez.

Tu peux me tutoyer, il n’y avait pas d’offense.