Bullseye : clavier et pavé tactile gelés

Support Debian
#1

voilà 2 fois de suite , 2 sessions différentes , que mon clavier ne répond plus du tout , le pavé tactile non plus mais par contre la souris fonctionne normalement . Pour en sortir , sachant qu’ouvrir une nouvelle session est impossible à cause du mot de passe que je ne peux pas entrer ( pas de clavier ) , j’ai essayé 2 méthodes qui ont fonctionné :

  • redémarrage
  • mise en veille puis sortie de veille

ma question : que faut-il que je fasse comme tests pour cerner au mieux la source du problème lorsque cela m’arrivera une 3ème fois ?

#2

Clavier et pavé tactile intégrés à l’ordinateur (portable) ou externes USB, PS/2, sans fil, bluetooth ?
Souris USB, PS/2, sans fil, bluetooth ?

Après rétablissement, il faudrait examiner les logs du noyau dans /var/log/kern.log à l’heure précise de survenue du problème.

#3

pavé et clavier intégrés (portable) . Par contre souris sans fil .

je regarde les logs . Je n’ai pas pensé à regarder l’heure exacte ( j’en comprends la nécessité au vu du log ) mais à partir de l’heure d’enregistrement du post j’ai essayé de sélectionner la bonne partie . De plus c’étair un peu avant la mise en veille ( ça doit être enregistré je suppose : system sleep du log ? )

Aug 26 12:48:48 ssd2 kernel: [21245.823623] rfkill: input handler enabled
Aug 26 12:48:49 ssd2 kernel: [21246.732113] azx_single_wait_for_response: 176 callbacks suppressed
Aug 26 12:48:49 ssd2 kernel: [21247.026418] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -5
Aug 26 12:48:52 ssd2 kernel: [21249.207405] rfkill: input handler disabled
Aug 26 12:48:56 ssd2 kernel: [21253.201129] azx_single_send_cmd: 214 callbacks suppressed
Aug 26 12:50:54 ssd2 kernel: [21371.298997] r8169 0000:01:00.1 enp1s0f1: Link is Down
Aug 26 12:50:54 ssd2 kernel: [21371.326047] PM: suspend entry (deep)
Aug 26 12:50:54 ssd2 kernel: [21371.331289] Filesystems sync: 0.005 seconds
Aug 26 12:51:01 ssd2 kernel: [21371.331606] (NULL device *): firmware: direct-loading firmware regulatory.db
Aug 26 12:51:01 ssd2 kernel: [21371.331608] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s
Aug 26 12:51:01 ssd2 kernel: [21371.332154] (NULL device *): firmware: direct-loading firmware iwlwifi-9260-th-b0-jf-b0-46.ucode
Aug 26 12:51:01 ssd2 kernel: [21371.332178] Freezing user space processes ... (elapsed 0.607 seconds) done.
Aug 26 12:51:01 ssd2 kernel: [21371.939927] OOM killer disabled.
Aug 26 12:51:01 ssd2 kernel: [21371.939930] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Aug 26 12:51:01 ssd2 kernel: [21371.941595] printk: Suspending console(s) (use no_console_suspend to debug)
Aug 26 12:51:01 ssd2 kernel: [21371.955742] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Aug 26 12:51:01 ssd2 kernel: [21371.955891] sd 0:0:0:0: [sda] Stopping disk
Aug 26 12:51:01 ssd2 kernel: [21372.132585] ACPI: EC: interrupt blocked
Aug 26 12:51:01 ssd2 kernel: [21372.173116] ACPI: Preparing to enter system sleep state S3
Aug 26 12:51:01 ssd2 kernel: [21372.280689] ACPI: EC: event blocked
Aug 26 12:51:01 ssd2 kernel: [21372.280692] ACPI: EC: EC stopped
Aug 26 12:51:01 ssd2 kernel: [21372.280694] PM: Saving platform NVS memory
Aug 26 12:51:01 ssd2 kernel: [21372.280704] Disabling non-boot CPUs ...
Aug 26 12:51:01 ssd2 kernel: [21372.282579] smpboot: CPU 1 is now offline
Aug 26 12:51:01 ssd2 kernel: [21372.287129] smpboot: CPU 2 is now offline
Aug 26 12:51:01 ssd2 kernel: [21372.291497] smpboot: CPU 3 is now offline
Aug 26 12:51:01 ssd2 kernel: [21372.297202] ACPI: Low-level resume complete
Aug 26 12:51:01 ssd2 kernel: [21372.297329] ACPI: EC: EC started
Aug 26 12:51:01 ssd2 kernel: [21372.297331] PM: Restoring platform NVS memory
Aug 26 12:51:01 ssd2 kernel: [21372.298221] Enabling non-boot CPUs ...
Aug 26 12:51:01 ssd2 kernel: [21372.298322] x86: Booting SMP configuration:
Aug 26 12:51:01 ssd2 kernel: [21372.298325] smpboot: Booting Node 0 Processor 1 APIC 0x2
Aug 26 12:51:01 ssd2 kernel: [21372.300473] CPU1 is up
Aug 26 12:51:01 ssd2 kernel: [21372.300575] smpboot: Booting Node 0 Processor 2 APIC 0x4
Aug 26 12:51:01 ssd2 kernel: [21372.302729] CPU2 is up
Aug 26 12:51:01 ssd2 kernel: [21372.302806] smpboot: Booting Node 0 Processor 3 APIC 0x6
Aug 26 12:51:01 ssd2 kernel: [21372.304967] CPU3 is up
Aug 26 12:51:01 ssd2 kernel: [21372.305290] ACPI: Waking up from system sleep state S3
Aug 26 12:51:01 ssd2 kernel: [21372.520977] ACPI: EC: interrupt unblocked
Aug 26 12:51:01 ssd2 kernel: [21372.561416] ACPI: EC: event unblocked
Aug 26 12:51:01 ssd2 kernel: [21372.571772] sd 0:0:0:0: [sda] Starting disk
Aug 26 12:51:01 ssd2 kernel: [21372.815986] usb 1-3: reset full-speed USB device number 2 using xhci_hcd
Aug 26 12:51:01 ssd2 kernel: [21373.047588] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Aug 26 12:51:01 ssd2 kernel: [21373.051608] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Aug 26 12:51:01 ssd2 kernel: [21373.057727] ata2.00: configured for UDMA/133
Aug 26 12:51:01 ssd2 kernel: [21373.066844] ata1.00: configured for UDMA/133
Aug 26 12:51:01 ssd2 kernel: [21373.091868] usb 1-6: reset high-speed USB device number 4 using xhci_hcd
Aug 26 12:51:01 ssd2 kernel: [21373.268859] acpi LNXPOWER:01: Turning OFF
Aug 26 12:51:01 ssd2 kernel: [21373.268935] acpi LNXPOWER:00: Turning OFF
Aug 26 12:51:01 ssd2 kernel: [21373.268992] OOM killer enabled.
Aug 26 12:51:01 ssd2 kernel: [21373.268994] Restarting tasks ... done.
Aug 26 12:51:01 ssd2 kernel: [21373.286534] thermal thermal_zone4: failed to read out thermal zone (-61)
Aug 26 12:51:01 ssd2 kernel: [21373.287090] PM: suspend exit
Aug 26 12:51:02 ssd2 kernel: [21373.303994] r8169 0000:01:00.1: firmware: failed to load rtl_nic/rtl8411-2.fw (-2)
Aug 26 12:51:02 ssd2 kernel: [21373.304002] r8169 0000:01:00.1: Direct firmware load for rtl_nic/rtl8411-2.fw failed with error -2
Aug 26 12:51:02 ssd2 kernel: [21373.304007] r8169 0000:01:00.1: Unable to load firmware rtl_nic/rtl8411-2.fw (-2)
Aug 26 12:51:02 ssd2 kernel: [21373.331485] Generic FE-GE Realtek PHY r8169-101:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-101:00, irq=IGNORE)
Aug 26 12:51:02 ssd2 kernel: [21373.375028] mei_hdcp 0000:00:0f.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
Aug 26 12:51:02 ssd2 kernel: [21373.459772] r8169 0000:01:00.1 enp1s0f1: Link is Down
Aug 26 12:51:03 ssd2 kernel: [21374.622590] psmouse serio2: synaptics: queried max coordinates: x [..5674], y [..4764]
Aug 26 12:51:03 ssd2 kernel: [21374.749642] psmouse serio2: synaptics: queried min coordinates: x [1266..], y [1086..]
Aug 26 12:51:03 ssd2 kernel: [21374.749663] psmouse serio2: synaptics: Your touchpad (PNP: SYN1221 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-input@vger.kernel.org.
Aug 26 12:51:03 ssd2 kernel: [21374.905528] psmouse serio2: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 0xf00223/0x840300/0x26800/0x0, board id: 3189, fw id: 2302754
Aug 26 12:51:03 ssd2 kernel: [21374.959314] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio2/input/input57
Aug 26 12:51:04 ssd2 kernel: [21375.300742] Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015
Aug 26 12:51:04 ssd2 kernel: [21375.301805] Bluetooth: hci0: Device revision is 2
Aug 26 12:51:04 ssd2 kernel: [21375.301808] Bluetooth: hci0: Secure boot is enabled
Aug 26 12:51:04 ssd2 kernel: [21375.301810] Bluetooth: hci0: OTP lock is enabled
Aug 26 12:51:04 ssd2 kernel: [21375.301811] Bluetooth: hci0: API lock is enabled
Aug 26 12:51:04 ssd2 kernel: [21375.301813] Bluetooth: hci0: Debug lock is disabled
Aug 26 12:51:04 ssd2 kernel: [21375.301816] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Aug 26 12:51:04 ssd2 kernel: [21375.302285] bluetooth hci0: firmware: direct-loading firmware intel/ibt-18-16-1.sfi
Aug 26 12:51:04 ssd2 kernel: [21375.302291] Bluetooth: hci0: Found device firmware: intel/ibt-18-16-1.sfi
Aug 26 12:51:05 ssd2 kernel: [21376.359552] r8169 0000:01:00.1 enp1s0f1: Link is Up - 1Gbps/Full - flow control rx/tx
Aug 26 12:51:05 ssd2 kernel: [21376.359578] IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0f1: link becomes ready
Aug 26 12:51:05 ssd2 kernel: [21377.076764] Bluetooth: hci0: Waiting for firmware download to complete
Aug 26 12:51:05 ssd2 kernel: [21377.077740] Bluetooth: hci0: Firmware loaded in 1735947 usecs
Aug 26 12:51:05 ssd2 kernel: [21377.077857] Bluetooth: hci0: Waiting for device to boot
Aug 26 12:51:05 ssd2 kernel: [21377.091650] Bluetooth: hci0: Device booted in 13569 usecs
Aug 26 12:51:05 ssd2 kernel: [21377.091771] bluetooth hci0: firmware: direct-loading firmware intel/ibt-18-16-1.ddc
Aug 26 12:51:05 ssd2 kernel: [21377.091782] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-18-16-1.ddc
Aug 26 12:51:05 ssd2 kernel: [21377.093823] Bluetooth: hci0: Applying Intel DDC parameters completed
Aug 26 12:51:05 ssd2 kernel: [21377.096694] Bluetooth: hci0: Firmware revision 0.1 build 168 week 48 2020
Aug 26 12:51:25 ssd2 kernel: [21396.327031] rfkill: input handler enabled
Aug 26 12:51:25 ssd2 kernel: [21396.401625] azx_single_wait_for_response: 176 callbacks suppressed
Aug 26 12:51:25 ssd2 kernel: [21396.680801] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -5
Aug 26 12:51:27 ssd2 kernel: [21399.285637] rfkill: input handler disabled
Aug 26 12:51:32 ssd2 kernel: [21403.343499] azx_single_send_cmd: 214 callbacks suppressed

merci pour la mise en forme que j’aimerais bien connaître pour une prochaine fois .

ok j’ai trouvé .

#4

Cet extrait contient surtout les messages liés à la mise en veille que tu as dû faire. Il faudrait regarder un peu avant.

#5

j’enlève toutes les lignes relatives à bluetooth ( je suis en mode « avion » et donc il doit être OFF si j’ai bien compris ) .

ug 26 12:38:42 ssd2 kernel: [20817.067111] r8169 0000:01:00.1 enp1s0f1: Link is Down
Aug 26 12:38:42 ssd2 kernel: [20817.095641] PM: suspend entry (deep)
Aug 26 12:41:40 ssd2 kernel: [20817.100460] Filesystems sync: 0.004 seconds
Aug 26 12:41:40 ssd2 kernel: [20817.100709] (NULL device *): firmware: direct-loading firmware regulatory.db
Aug 26 12:41:40 ssd2 kernel: [20817.100739] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s
Aug 26 12:41:40 ssd2 kernel: [20817.100761] (NULL device *): firmware: direct-loading firmware intel/ibt-18-16-1.ddc
Aug 26 12:41:40 ssd2 kernel: [20817.101150] (NULL device *): firmware: direct-loading firmware intel/ibt-18-16-1.sfi
Aug 26 12:41:40 ssd2 kernel: [20817.101405] (NULL device *): firmware: direct-loading firmware iwlwifi-9260-th-b0-jf-b0-46.ucode
Aug 26 12:41:40 ssd2 kernel: [20817.101430] Freezing user space processes ... (elapsed 0.002 seconds) done.
Aug 26 12:41:40 ssd2 kernel: [20817.103987] OOM killer disabled.
Aug 26 12:41:40 ssd2 kernel: [20817.103988] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Aug 26 12:41:40 ssd2 kernel: [20817.105439] printk: Suspending console(s) (use no_console_suspend to debug)
Aug 26 12:41:40 ssd2 kernel: [20817.124066] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Aug 26 12:41:40 ssd2 kernel: [20817.124479] sd 0:0:0:0: [sda] Stopping disk
Aug 26 12:41:40 ssd2 kernel: [20817.888533] ACPI: EC: interrupt blocked
Aug 26 12:41:40 ssd2 kernel: [20817.929420] ACPI: Preparing to enter system sleep state S3
Aug 26 12:41:40 ssd2 kernel: [20818.036363] ACPI: EC: event blocked
Aug 26 12:41:40 ssd2 kernel: [20818.036364] ACPI: EC: EC stopped
Aug 26 12:41:40 ssd2 kernel: [20818.036365] PM: Saving platform NVS memory
Aug 26 12:41:40 ssd2 kernel: [20818.036371] Disabling non-boot CPUs ...
Aug 26 12:41:40 ssd2 kernel: [20818.037808] smpboot: CPU 1 is now offline
Aug 26 12:41:40 ssd2 kernel: [20818.040350] smpboot: CPU 2 is now offline
Aug 26 12:41:40 ssd2 kernel: [20818.042872] smpboot: CPU 3 is now offline
Aug 26 12:41:40 ssd2 kernel: [20818.046090] ACPI: Low-level resume complete
Aug 26 12:41:40 ssd2 kernel: [20818.046215] ACPI: EC: EC started
Aug 26 12:41:40 ssd2 kernel: [20818.046217] PM: Restoring platform NVS memory
Aug 26 12:41:40 ssd2 kernel: [20818.047139] Enabling non-boot CPUs ...
Aug 26 12:41:40 ssd2 kernel: [20818.047242] x86: Booting SMP configuration:
Aug 26 12:41:40 ssd2 kernel: [20818.047244] smpboot: Booting Node 0 Processor 1 APIC 0x2
Aug 26 12:41:40 ssd2 kernel: [20818.049411] CPU1 is up
Aug 26 12:41:40 ssd2 kernel: [20818.049610] smpboot: Booting Node 0 Processor 2 APIC 0x4
Aug 26 12:41:40 ssd2 kernel: [20818.051770] CPU2 is up
Aug 26 12:41:40 ssd2 kernel: [20818.051847] smpboot: Booting Node 0 Processor 3 APIC 0x6
Aug 26 12:41:40 ssd2 kernel: [20818.054065] CPU3 is up
Aug 26 12:41:40 ssd2 kernel: [20818.054392] ACPI: Waking up from system sleep state S3
Aug 26 12:41:40 ssd2 kernel: [20818.272064] ACPI: EC: interrupt unblocked
Aug 26 12:41:40 ssd2 kernel: [20818.312583] ACPI: EC: event unblocked
Aug 26 12:41:40 ssd2 kernel: [20818.319485] i8042: failed to resume active multiplexor, mouse won't work
Aug 26 12:41:40 ssd2 kernel: [20818.322894] sd 0:0:0:0: [sda] Starting disk
Aug 26 12:41:40 ssd2 kernel: [20818.575101] usb 1-3: reset full-speed USB device number 2 using xhci_hcd
Aug 26 12:41:40 ssd2 kernel: [20818.798676] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Aug 26 12:41:40 ssd2 kernel: [20818.802674] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Aug 26 12:41:40 ssd2 kernel: [20818.808830] ata2.00: configured for UDMA/133
Aug 26 12:41:40 ssd2 kernel: [20818.818058] ata1.00: configured for UDMA/133
Aug 26 12:41:40 ssd2 kernel: [20818.850936] usb 1-6: reset high-speed USB device number 4 using xhci_hcd
Aug 26 12:41:40 ssd2 kernel: [20819.027858] acpi LNXPOWER:01: Turning OFF
Aug 26 12:41:40 ssd2 kernel: [20819.028119] mei_hdcp 0000:00:0f.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
Aug 26 12:41:40 ssd2 kernel: [20819.028492] acpi LNXPOWER:00: Turning OFF
Aug 26 12:41:40 ssd2 kernel: [20819.028549] OOM killer enabled.
Aug 26 12:41:40 ssd2 kernel: [20819.028551] Restarting tasks ... 


Aug 26 12:41:41 ssd2 kernel: [20819.045681] done.
Aug 26 12:41:41 ssd2 kernel: [20819.047943] thermal thermal_zone4: failed to read out thermal zone (-61)
Aug 26 12:41:41 ssd2 kernel: [20819.048406] PM: suspend exit
Aug 26 12:41:41 ssd2 kernel: [20819.085169] r8169 0000:01:00.1: firmware: failed to load rtl_nic/rtl8411-2.fw (-2)
Aug 26 12:41:41 ssd2 kernel: [20819.085178] r8169 0000:01:00.1: Direct firmware load for rtl_nic/rtl8411-2.fw failed with error -2
Aug 26 12:41:41 ssd2 kernel: [20819.085183] r8169 0000:01:00.1: Unable to load firmware rtl_nic/rtl8411-2.fw (-2)
Aug 26 12:41:41 ssd2 kernel: [20819.110518] Generic FE-GE Realtek PHY r8169-101:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-101:00, irq=IGNORE)
Aug 26 12:41:41 ssd2 kernel: [20819.238751] r8169 0000:01:00.1 enp1s0f1: Link is Down

Aug 26 12:41:44 ssd2 kernel: [20822.138392] r8169 0000:01:00.1 enp1s0f1: Link is Up - 1Gbps/Full - flow control rx/tx
#6

je pense à un autre problème : pour avoir une heure exacte il faudrait que je sois en train d’utiliser le clavier , or quand j’y repense c’est finalement relativement rare d’où un décalage temporel possiblement important . D’où :

  • existe-t-il , comme pour /var/log/cups/log_error , une version « debug » qui indiquerait directement les erreurs ?
  • quel type d’erreur faut-il chercher dans le log ? Ça me permettrait peut-être de sélectionner la partie intéressante .
#7

Utilise le pavé tactile au lieu de la souris puisqu’il tombe en panne en même temps que le clavier.

En première intention, je dirais les messages qui contiennent « i8042 » (le contrôleur clavier/touchpad) ou « serio ». Par exemple avec :

egrep "i8042|serio" /var/log/kern.log

D’ailleurs on en voit deux intéressants :

psmouse serio2: synaptics: Your touchpad (PNP: SYN1221 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1

i8042: failed to resume active multiplexor, mouse won't work
#8

ok merci
comme le remède pour récupérer est simple , à voir si ça va marcher à tous les coups , je vais attendre qu’une mise à jour règle éventuellement l’affaire .