Debian Debian-France Debian-Facile Debian-fr.org Forum-Debian.fr Debian ? Communautés

Debian-facile

Bienvenue sur Debian-Facile, site d'aide pour les nouveaux utilisateurs de Debian.

Vous n'êtes pas identifié(e).

#1 10-05-2021 12:56:47

Groot
Membre
Distrib. : Debian 11 bullseye (testing)
Noyau : Linux 5.10.0-6-amd64
(G)UI : XFCE
Inscription : 10-05-2021

Freeze du système

Bonjour à tous,

Je rencontre des problèmes de gel du système. Au bout d'un moment (quelques  minutes à quelques heures après le boot), l'affichage se fige, sauf la souris. Puis la souris se fige aussi. J'ai essayé les touches spéciales Alt-SysRq-REISUB , Ctrl-Alt-Backspace (après avoir activé la combinaison), Ctrl-Alt-Suppri , rien n'y fait. La connexion par SSH vers cette machine ne fonctionne plus non plus, donc je pense que le noyau plante.

Cela se produit même lorsque je n'ai que quelques applis courantes utilisées (Firefox, nautilus, gedit).
J'ai désinstallé VMWare, essayé les drivers nvidia proprétaires prépackagés et ceux directement présents sur le site d'NVidia, ça ne change rien.

Je suis sous XFCE sur une Debian testing amd64.
Machine : CPU Ryzen 5 1600, GPU Nvidia GTX 1060, 16 Go de RAM

Infos système :

lspci


00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7
03:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset USB 3.1 xHCI Controller (rev 02)
03:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset SATA Controller (rev 02)
03:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b2 (rev 02)
04:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
04:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
04:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
1f:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 03)
21:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
23:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] (rev a1)
23:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1)
24:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function
24:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor
24:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller
25:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function
25:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
25:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller



lsusb -t


/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
    |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M
    |__ Port 8: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M



lspci -nnk | grep -iA3 vga


23:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1)
  Subsystem: Gigabyte Technology Co., Ltd GP106 [GeForce GTX 1060 3GB] [1458:373a]
  Kernel driver in use: nvidia
  Kernel modules: nouveau, nvidia_drm, nvidia



uname -a


Linux Phenix 5.10.0-6-amd64 #1 SMP Debian 5.10.28-1 (2021-04-09) x86_64 GNU/Linux



journalctl -r -p err



-- Journal begins at Wed 2021-02-24 19:18:01 CET, ends at Mon 2021-05-10 12:49:52 CEST. --
mai 10 10:12:14 Phenix pulseaudio[1288]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
mai 10 10:11:53 Phenix pipewire[1287]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
mai 10 10:11:53 Phenix sddm-helper[1265]: gkr-pam: unable to locate daemon control file
mai 10 10:11:48 Phenix pipewire[1112]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
mai 10 10:11:45 Phenix kernel:
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 203: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104b, and key code 202: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 149: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1049, and key code 148: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 234: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1047, and key code 210: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1046, and key code 182: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1045, and key code 131: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1044, and key code 425: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1043, and key code 423: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1042, and key code 421: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1041, and key code 138: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1032, and key code 223: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1031, and key code 218: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102d, and key code 150: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102c, and key code 464: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102b, and key code 154: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102a, and key code 158: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1029, and key code 410: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1028, and key code 371: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1027, and key code 139: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1023, and key code 206: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1021, and key code 420: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1020, and key code 418: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101f, and key code 419: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101c, and key code 154: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101b, and key code 186: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101a, and key code 185: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1019, and key code 184: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1018, and key code 171: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1017, and key code 161: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1016, and key code 213: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1015, and key code 167: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1014, and key code 152: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1013, and key code 212: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1012, and key code 402: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1011, and key code 403: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1010, and key code 185: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100f, and key code 184: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100c, and key code 208: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100b, and key code 168: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100a, and key code 235: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1005, and key code 442: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1004, and key code 393: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1003, and key code 392: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1002, and key code 212: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1001, and key code 216: Invalid argument
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Invalid argument
mai 10 10:11:45 Phenix kernel: iommu ivhd0: AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:00.0 pasid=0x00000 address=0xfffffffdf8000000 flags=0x0a00]
-- Boot e65c3ea9fc3841cab798c8be08ca6935 --
mai 10 00:48:56 Phenix libvirtd[867]: internal error: End of file from qemu monitor
mai 09 22:20:04 Phenix pulseaudio[1277]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
mai 09 22:19:46 Phenix pipewire[1276]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
mai 09 22:19:46 Phenix sddm-helper[1254]: gkr-pam: unable to locate daemon control file
mai 09 22:19:38 Phenix pipewire[1100]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
mai 09 22:19:35 Phenix kernel:
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 203: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104b, and key code 202: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 149: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1049, and key code 148: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 234: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1047, and key code 210: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1046, and key code 182: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1045, and key code 131: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1044, and key code 425: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1043, and key code 423: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1042, and key code 421: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1041, and key code 138: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1032, and key code 223: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1031, and key code 218: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102d, and key code 150: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102c, and key code 464: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102b, and key code 154: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102a, and key code 158: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1029, and key code 410: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1028, and key code 371: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1027, and key code 139: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1023, and key code 206: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1021, and key code 420: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1020, and key code 418: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101f, and key code 419: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101c, and key code 154: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101b, and key code 186: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101a, and key code 185: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1019, and key code 184: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1018, and key code 171: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1017, and key code 161: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1016, and key code 213: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1015, and key code 167: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1014, and key code 152: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1013, and key code 212: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1012, and key code 402: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1011, and key code 403: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1010, and key code 185: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100f, and key code 184: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100c, and key code 208: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100b, and key code 168: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100a, and key code 235: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1005, and key code 442: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1004, and key code 393: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1003, and key code 392: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1002, and key code 212: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1001, and key code 216: Invalid argument
mai 09 22:19:35 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Invalid argument
mai 09 22:19:35 Phenix kernel: iommu ivhd0: AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:00.0 pasid=0x00000 address=0xfffffffdf8000000 flags=0x0a00]
-- Boot c4896f38fa79401488192aab1aaf3552 --
mai 09 22:19:09 Phenix kernel: watchdog: watchdog0: watchdog did not stop!
mai 09 22:19:06 Phenix libvirtd[886]: End of file while reading data: Erreur d'entrée/sortie
mai 09 21:46:46 Phenix pulseaudio[1284]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
mai 09 21:46:25 Phenix pipewire[1283]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
mai 09 21:46:24 Phenix sddm-helper[1261]: gkr-pam: unable to locate daemon control file
mai 09 21:46:20 Phenix pipewire[1108]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
mai 09 21:46:17 Phenix kernel:
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 203: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104b, and key code 202: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 149: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1049, and key code 148: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 234: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1047, and key code 210: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1046, and key code 182: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1045, and key code 131: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1044, and key code 425: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1043, and key code 423: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1042, and key code 421: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1041, and key code 138: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1032, and key code 223: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1031, and key code 218: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102d, and key code 150: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102c, and key code 464: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102b, and key code 154: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102a, and key code 158: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1029, and key code 410: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1028, and key code 371: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1027, and key code 139: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1023, and key code 206: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1021, and key code 420: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1020, and key code 418: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101f, and key code 419: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101c, and key code 154: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101b, and key code 186: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101a, and key code 185: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1019, and key code 184: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1018, and key code 171: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1017, and key code 161: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1016, and key code 213: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1015, and key code 167: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1014, and key code 152: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1013, and key code 212: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1012, and key code 402: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1011, and key code 403: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1010, and key code 185: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100f, and key code 184: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100c, and key code 208: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100b, and key code 168: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100a, and key code 235: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1005, and key code 442: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1004, and key code 393: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1003, and key code 392: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1002, and key code 212: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1001, and key code 216: Invalid argument
mai 09 21:46:17 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Invalid argument
mai 09 21:46:17 Phenix kernel: iommu ivhd0: AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:00.0 pasid=0x00000 address=0xfffffffdf8000000 flags=0x0a00]
-- Boot 72c7930e48bd41ce8467561fddb3ecbe --
mai 09 15:44:51 Phenix pulseaudio[1353]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
mai 09 15:44:32 Phenix pipewire[1352]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
mai 09 15:44:32 Phenix sddm-helper[1330]: gkr-pam: unable to locate daemon control file
mai 09 15:44:25 Phenix pipewire[1115]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
mai 09 15:44:22 Phenix kernel:
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 203: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104b, and key code 202: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 149: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1049, and key code 148: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 234: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1047, and key code 210: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1046, and key code 182: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1045, and key code 131: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1044, and key code 425: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1043, and key code 423: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1042, and key code 421: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1041, and key code 138: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1032, and key code 223: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1031, and key code 218: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102d, and key code 150: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102c, and key code 464: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102b, and key code 154: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102a, and key code 158: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1029, and key code 410: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1028, and key code 371: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1027, and key code 139: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1023, and key code 206: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1021, and key code 420: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1020, and key code 418: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101f, and key code 419: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101c, and key code 154: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101b, and key code 186: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101a, and key code 185: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1019, and key code 184: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1018, and key code 171: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1017, and key code 161: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1016, and key code 213: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1015, and key code 167: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1014, and key code 152: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1013, and key code 212: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1012, and key code 402: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1011, and key code 403: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1010, and key code 185: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100f, and key code 184: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100c, and key code 208: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100b, and key code 168: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100a, and key code 235: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1005, and key code 442: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1004, and key code 393: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1003, and key code 392: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1002, and key code 212: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1001, and key code 216: Invalid argument
mai 09 15:44:22 Phenix systemd-udevd[367]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Invalid argument
mai 09 15:44:22 Phenix kernel: iommu ivhd0: AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:00.0 pasid=0x00000 address=0xfffffffdf8000000 flags=0x0a00]
-- Boot b8489189659d4bbfb7d44b093a8cfd77 --
mai 09 15:43:58 Phenix kernel: watchdog: watchdog0: watchdog did not stop!
mai 09 15:43:37 Phenix kernel:
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 203: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104b, and key code 202: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 149: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1049, and key code 148: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 234: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1047, and key code 210: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1046, and key code 182: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1045, and key code 131: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1044, and key code 425: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1043, and key code 423: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1042, and key code 421: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1041, and key code 138: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1032, and key code 223: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1031, and key code 218: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102d, and key code 150: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102c, and key code 464: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102b, and key code 154: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102a, and key code 158: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1029, and key code 410: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1028, and key code 371: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1027, and key code 139: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1023, and key code 206: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1021, and key code 420: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1020, and key code 418: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101f, and key code 419: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101c, and key code 154: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101b, and key code 186: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101a, and key code 185: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1019, and key code 184: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1018, and key code 171: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1017, and key code 161: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1016, and key code 213: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1015, and key code 167: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1014, and key code 152: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1013, and key code 212: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1012, and key code 402: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1011, and key code 403: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1010, and key code 185: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100f, and key code 184: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100c, and key code 208: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100b, and key code 168: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100a, and key code 235: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1005, and key code 442: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1004, and key code 393: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1003, and key code 392: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1002, and key code 212: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1001, and key code 216: Invalid argument
mai 09 15:39:28 Phenix systemd-udevd[377]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Invalid argument
mai 09 15:39:28 Phenix kernel: iommu ivhd0: AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:00.0 pasid=0x00000 address=0xfffffffdf8000000 flags=0x0a00]
-- Boot 28d490c14a5f47d2b282fb5e88c5fc3d --
mai 09 15:38:58 Phenix kernel: watchdog: watchdog0: watchdog did not stop!
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 203: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104b, and key code 202: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 149: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1049, and key code 148: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 234: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1047, and key code 210: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1046, and key code 182: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1045, and key code 131: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1044, and key code 425: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1043, and key code 423: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1042, and key code 421: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1041, and key code 138: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1032, and key code 223: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1031, and key code 218: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102d, and key code 150: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102c, and key code 464: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102b, and key code 154: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102a, and key code 158: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1029, and key code 410: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1028, and key code 371: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1027, and key code 139: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1023, and key code 206: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1021, and key code 420: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1020, and key code 418: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101f, and key code 419: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101c, and key code 154: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101b, and key code 186: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101a, and key code 185: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1019, and key code 184: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1018, and key code 171: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1017, and key code 161: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1016, and key code 213: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1015, and key code 167: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1014, and key code 152: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1013, and key code 212: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1012, and key code 402: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1011, and key code 403: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1010, and key code 185: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100f, and key code 184: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100c, and key code 208: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100b, and key code 168: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100a, and key code 235: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1005, and key code 442: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1004, and key code 393: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1003, and key code 392: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1002, and key code 212: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1001, and key code 216: Invalid argument
mai 09 15:29:57 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Invalid argument
mai 09 15:29:57 Phenix kernel: iommu ivhd0: AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:00.0 pasid=0x00000 address=0xfffffffdf8000000 flags=0x0a00]
-- Boot 4beb84116dab494eb18b884f5f5e65e7 --
mai 09 15:29:18 Phenix kernel: watchdog: watchdog0: watchdog did not stop!
mai 09 15:23:59 Phenix kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
mai 09 15:23:58 Phenix kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
mai 09 15:23:58 Phenix kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 203: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104b, and key code 202: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 149: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1049, and key code 148: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 234: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1047, and key code 210: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1046, and key code 182: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1045, and key code 131: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1044, and key code 425: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1043, and key code 423: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1042, and key code 421: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1041, and key code 138: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1032, and key code 223: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1031, and key code 218: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102d, and key code 150: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102c, and key code 464: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102b, and key code 154: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102a, and key code 158: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1029, and key code 410: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1028, and key code 371: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1027, and key code 139: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1023, and key code 206: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1021, and key code 420: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1020, and key code 418: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101f, and key code 419: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101c, and key code 154: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101b, and key code 186: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101a, and key code 185: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1019, and key code 184: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1018, and key code 171: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1017, and key code 161: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1016, and key code 213: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1015, and key code 167: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1014, and key code 152: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1013, and key code 212: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1012, and key code 402: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1011, and key code 403: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1010, and key code 185: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100f, and key code 184: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100c, and key code 208: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100b, and key code 168: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100a, and key code 235: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1005, and key code 442: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1004, and key code 393: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1003, and key code 392: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1002, and key code 212: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1001, and key code 216: Invalid argument
mai 09 15:23:58 Phenix systemd-udevd[380]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Invalid argument
mai 09 15:23:58 Phenix kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
mai 09 15:23:58 Phenix kernel: iommu ivhd0: AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:00.0 pasid=0x00000 address=0xfffffffdf8000000 flags=0x0a00]
-- Boot 5d79701df76243ab87c95f32e32bd953 --
mai 09 15:23:28 Phenix kernel: watchdog: watchdog0: watchdog did not stop!
mai 09 15:23:18 Phenix sddm[1087]: Could not start Display server on vt 7
mai 09 15:23:18 Phenix sddm[1087]: Failed to read display number from pipe
mai 09 15:23:16 Phenix systemd[1]: Failed to start NVIDIA Persistence Daemon.
mai 09 15:23:16 Phenix nvidia-persistenced[832]: Failed to open libnvidia-cfg.so.1: libnvidia-cfg.so.1: cannot open shared object file: No such file or directory
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 203: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104b, and key code 202: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 149: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1049, and key code 148: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 234: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1047, and key code 210: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1046, and key code 182: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1045, and key code 131: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1044, and key code 425: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1043, and key code 423: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1042, and key code 421: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1041, and key code 138: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1032, and key code 223: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1031, and key code 218: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102d, and key code 150: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102c, and key code 464: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102b, and key code 154: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102a, and key code 158: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1029, and key code 410: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1028, and key code 371: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1027, and key code 139: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1023, and key code 206: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1021, and key code 420: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1020, and key code 418: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101f, and key code 419: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101c, and key code 154: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101b, and key code 186: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101a, and key code 185: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1019, and key code 184: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1018, and key code 171: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1017, and key code 161: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1016, and key code 213: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1015, and key code 167: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1014, and key code 152: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1013, and key code 212: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1012, and key code 402: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1011, and key code 403: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1010, and key code 185: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100f, and key code 184: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100c, and key code 208: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100b, and key code 168: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100a, and key code 235: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1005, and key code 442: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1004, and key code 393: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1003, and key code 392: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1002, and key code 212: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1001, and key code 216: Invalid argument
mai 09 15:23:15 Phenix systemd-udevd[362]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Invalid argument
mai 09 15:23:15 Phenix kernel: iommu ivhd0: AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:00.0 pasid=0x00000 address=0xfffffffdf8000000 flags=0x0a00]
-- Boot 913d2deded3b45e2ae80f46def173838 --
mai 09 15:22:44 Phenix kernel: watchdog: watchdog0: watchdog did not stop!
mai 09 15:21:48 Phenix sddm[906]: Could not start Display server on vt 7
mai 09 15:21:48 Phenix sddm[906]: Failed to read display number from pipe
mai 09 15:21:48 Phenix systemd[1]: Failed to start Set console font and keymap.
mai 09 15:21:48 Phenix systemd[1]: Failed to start NVIDIA Persistence Daemon.
mai 09 15:21:48 Phenix nvidia-persistenced[845]: Failed to open libnvidia-cfg.so.1: libnvidia-cfg.so.1: cannot open shared object file: No such file or directory
mai 09 15:21:47 Phenix kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
mai 09 15:21:47 Phenix kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
mai 09 15:21:47 Phenix kernel:
mai 09 15:21:47 Phenix kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 203: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc104b, and key code 202: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 149: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1049, and key code 148: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 234: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1047, and key code 210: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1046, and key code 182: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1045, and key code 131: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1044, and key code 425: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1043, and key code 423: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1042, and key code 421: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1041, and key code 138: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1032, and key code 223: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1031, and key code 218: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc102d, and key code 150: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc102c, and key code 464: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc102b, and key code 154: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc102a, and key code 158: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1029, and key code 410: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1028, and key code 371: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1027, and key code 139: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1023, and key code 206: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1021, and key code 420: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1020, and key code 418: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc101f, and key code 419: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc101c, and key code 154: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc101b, and key code 186: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc101a, and key code 185: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1019, and key code 184: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1018, and key code 171: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1017, and key code 161: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1016, and key code 213: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1015, and key code 167: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1014, and key code 152: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1013, and key code 212: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1012, and key code 402: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1011, and key code 403: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1010, and key code 185: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc100f, and key code 184: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc100c, and key code 208: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc100b, and key code 168: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc100a, and key code 235: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1005, and key code 442: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1004, and key code 393: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1003, and key code 392: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1002, and key code 212: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc1001, and key code 216: Invalid argument
mai 09 15:21:47 Phenix systemd-udevd[385]: event3: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Invalid argument
mai 09 15:21:47 Phenix kernel: iommu ivhd0: AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:00.0 pasid=0x00000 address=0xfffffffdf8000000 flags=0x0a00]
-- Boot 4de855aa5b164c048525795d461f695c --
mai 09 15:21:21 Phenix kernel: watchdog: watchdog0: watchdog did not stop!
mai 09 15:21:21 Phenix sddm[913]: Could not start Display server on vt 7
mai 09 15:21:21 Phenix sddm[913]: Failed to read display number from pipe
mai 09 14:23:01 Phenix pulseaudio[1326]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
mai 09 14:22:59 Phenix pipewire[1325]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
mai 09 14:22:59 Phenix sddm-helper[1302]: gkr-pam: unable to locate daemon control file
mai 09 14:22:35 Phenix pipewire[1147]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
mai 09 14:22:32 Phenix kernel:
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 203: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104b, and key code 202: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 149: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1049, and key code 148: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 234: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1047, and key code 210: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1046, and key code 182: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1045, and key code 131: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1044, and key code 425: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1043, and key code 423: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1042, and key code 421: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1041, and key code 138: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1032, and key code 223: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1031, and key code 218: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102d, and key code 150: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102c, and key code 464: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102b, and key code 154: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102a, and key code 158: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1029, and key code 410: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1028, and key code 371: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1027, and key code 139: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1023, and key code 206: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1021, and key code 420: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1020, and key code 418: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101f, and key code 419: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101c, and key code 154: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101b, and key code 186: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101a, and key code 185: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1019, and key code 184: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1018, and key code 171: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1017, and key code 161: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1016, and key code 213: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1015, and key code 167: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1014, and key code 152: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1013, and key code 212: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1012, and key code 402: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1011, and key code 403: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1010, and key code 185: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100f, and key code 184: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100c, and key code 208: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100b, and key code 168: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100a, and key code 235: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1005, and key code 442: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1004, and key code 393: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1003, and key code 392: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1002, and key code 212: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1001, and key code 216: Invalid argument
mai 09 14:22:32 Phenix systemd-udevd[378]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Invalid argument
mai 09 14:22:32 Phenix kernel: iommu ivhd0: AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:00.0 pasid=0x00000 address=0xfffffffdf8000000 flags=0x0a00]
-- Boot a9877f28a7484fcabe8af456c988522d --
mai 08 17:11:42 Phenix kernel: watchdog: BUG: soft lockup - CPU#9 stuck for 22s! [pool-/home/nimi:4068]
mai 08 17:11:22 Phenix kernel: watchdog: BUG: soft lockup - CPU#8 stuck for 23s! [pool-/home/nimi:3256]
mai 08 17:11:17 Phenix kernel: rcu:         9-....: (5249 ticks this GP) idle=6fa/1/0x4000000000000000 softirq=857016/857016 fqs=2624
mai 08 17:11:17 Phenix kernel: rcu: INFO: rcu_sched self-detected stall on CPU
mai 05 10:53:32 Phenix pulseaudio[1649]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
mai 05 10:53:06 Phenix pipewire[1648]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
mai 05 10:53:06 Phenix sddm-helper[1625]: gkr-pam: unable to locate daemon control file
mai 05 04:00:50 Phenix pulseaudio[1111]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
mai 05 04:00:24 Phenix pipewire[1110]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
mai 05 04:00:21 Phenix kernel:
mai 05 04:00:21 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 203: Invalid argument
mai 05 04:00:21 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104b, and key code 202: Invalid argument
mai 05 04:00:21 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 149: Invalid argument
mai 05 04:00:21 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1049, and key code 148: Invalid argument
mai 05 04:00:21 Phenix systemd-udevd[387]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 234: Invalid argument
 



Je ne vois plus trop quoi faire.. si vous avez des idées n'hésites pas !
Merci de m'avoir lu

Hors ligne

#2 10-05-2021 14:29:09

tux12
Membre
Lieu : ./
Distrib. : stable
Noyau : celui de la stable
(G)UI : KDE
Inscription : 27-02-2008

Re : Freeze du système

Bonjour,

Sans aucune certitude quand à la pertinence de ma proposition, je suggère néanmoins d'effectuer un memtest pour valider la RAM et un test smartctl du HD, certaines lignes du log pouvant laisser penser à un problème d'accès à des fichiers.

Edit: Dans le cas ou le système se planterait avant la fin du test smartctl, tu peux laisser le test se terminer en attendant la fin du délai annoncé en début de test sans couper l'alimentation; le test SMART est en effet interne au disque et ne devrait pas être perturbé par un plantage. Le log ainsi créé sera dispo au redémarrage.

Dernière modification par tux12 (10-05-2021 14:44:39)


Tout est un sauf zéro. - Wau Holland

Hors ligne

#3 10-05-2021 14:49:19

Groot
Membre
Distrib. : Debian 11 bullseye (testing)
Noyau : Linux 5.10.0-6-amd64
(G)UI : XFCE
Inscription : 10-05-2021

Re : Freeze du système

J'avais en tête un problème logiciel car je n'ai pas de souci lorsque j'utilise Windows (j'aurais du le préciser). Mais je vais faire les tests et je vais voir.
Merci pour la réponse, et merci pour les précisions ! Effectivement sans savoir, en cas de plantage lors du test j'aurai juste redémarré le pc.

Hors ligne

#4 10-05-2021 15:13:28

--gilles--
Membre
Lieu : Orléans - La Source
Distrib. : debian 11
Noyau : Linux 5.10.0-17-amd64
(G)UI : mutter 3.38.6-2~deb11u2
Inscription : 15-02-2016

Re : Freeze du système

Bonjour Groot smile

Puisque tout fonctionne avec Windows, il faudrait que nous puissions :

Voir les états d'activité du processeur :

ls /sys/devices/system/cpu/cpu0/cpuidle



Voir si le temps d'initialisation de la génération des nombres aléatoires n'est pas trop long :

dmesg | grep random



Estimer la quantité d'entropie du processeur sans outil particulier :

cat /proc/sys/kernel/random/entropy_avail



Voir quel est le pilote qui gère les états IDLE et quels C-STATE correspondent à l'état IDLE :

dmesg | grep idle


« Quand la vérité n'est pas libre, la liberté n'est pas vraie. » Jacques Prévert

Hors ligne

#5 10-05-2021 18:08:54

Groot
Membre
Distrib. : Debian 11 bullseye (testing)
Noyau : Linux 5.10.0-6-amd64
(G)UI : XFCE
Inscription : 10-05-2021

Re : Freeze du système

Bonjour Gilles !

Voici déjà le résultats des commandes indiquées par Gilles :

ls /sys/devices/system/cpu/cpu0/cpuidle


state0  state1  state2



dmesg | grep random


[    0.000000] random: get_random_u64 called from __kmem_cache_create+0x2e/0x550 with crng_init=0
[    0.000000] random: crng done (trusting CPU's manufacturer)



cat /proc/sys/kernel/random/entropy_avail


3479



dmesg | grep idle


[    0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
[    0.000000] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484873504 ns
[    0.000002] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x2e1e387ba13, max_idle_ns: 440795353586 ns
[    0.156877] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.156877] cpuidle: using governor ladder
[    0.156877] cpuidle: using governor menu
[    0.314831] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    1.096212] ACPI: \_PR_.P000: Found 2 idle states
[    1.096264] ACPI: \_PR_.P001: Found 2 idle states
[    1.096613] ACPI: \_PR_.P002: Found 2 idle states
[    1.096664] ACPI: \_PR_.P003: Found 2 idle states
[    1.096738] ACPI: \_PR_.P004: Found 2 idle states
[    1.096800] ACPI: \_PR_.P005: Found 2 idle states
[    1.096873] ACPI: \_PR_.P006: Found 2 idle states
[    1.097034] ACPI: \_PR_.P007: Found 2 idle states
[    1.097128] ACPI: \_PR_.P008: Found 2 idle states
[    1.097184] ACPI: \_PR_.P009: Found 2 idle states
[    1.097280] ACPI: \_PR_.P00A: Found 2 idle states
[    1.097341] ACPI: \_PR_.P00B: Found 2 idle states
[    2.116037] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2e2048a8b6b, max_idle_ns: 440795205530 ns

Hors ligne

#6 10-05-2021 21:32:17

--gilles--
Membre
Lieu : Orléans - La Source
Distrib. : debian 11
Noyau : Linux 5.10.0-17-amd64
(G)UI : mutter 3.38.6-2~deb11u2
Inscription : 15-02-2016

Re : Freeze du système

À  mon avis, cela serait la configuration d'une entrée qui mettrait le désordre et engendrerait énormément de messages d'erreur

systemd-udevd[]: event: Failed to call EVIOCSKEYCODE with scan code 0x, and key code : Invalid argument


voir :

https://duckduckgo.com/?t=ffab&q=system … ent&ia=web


Que donne :

cat /proc/bus/input/devices

Dernière modification par --gilles-- (10-05-2021 21:40:03)


« Quand la vérité n'est pas libre, la liberté n'est pas vraie. » Jacques Prévert

Hors ligne

#7 10-05-2021 22:20:56

Groot
Membre
Distrib. : Debian 11 bullseye (testing)
Noyau : Linux 5.10.0-6-amd64
(G)UI : XFCE
Inscription : 10-05-2021

Re : Freeze du système

Je m'interrogeai sur ces nombreuses lignes justement.. voici :

cat /proc/bus/input/devices


I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=10000000000000 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=10000000000000 0

I: Bus=0003 Vendor=1bcf Product=0005 Version=0110
N: Name="USB Optical Mouse"
P: Phys=usb-0000:03:00.0-8/input0
S: Sysfs=/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-8/1-8:1.0/0003:1BCF:0005.0003/input/input3
U: Uniq=
H: Handlers=mouse0 event2
B: PROP=0
B: EV=17
B: KEY=1f0000 0 0 0 0
B: REL=1943
B: MSC=10

I: Bus=0003 Vendor=046d Product=0068 Version=0111
N: Name="Logitech Wireless Keyboard PID:0068"
P: Phys=usb-0000:24:00.3-1/input1:3
S: Sysfs=/devices/pci0000:00/0000:00:07.1/0000:24:00.3/usb3/3-1/3-1:1.1/0003:046D:C517.0002/0003:046D:0068.0005/input/input13
U: Uniq=
H: Handlers=sysrq kbd leds event3
B: PROP=0
B: EV=12001f
B: KEY=3f000301ff 0 10000 483ffff17aff32d bfdc444600000000 1 130ff78f37cc07 ffff7bfadd71dfff ffbeffdfffefffff fffffffffffffffe
B: REL=1040
B: ABS=100000000
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=046d Product=0085 Version=0111
N: Name="Logitech Wireless Mouse PID:0085"
P: Phys=usb-0000:24:00.3-1/input1:1
S: Sysfs=/devices/pci0000:00/0000:00:07.1/0000:24:00.3/usb3/3-1/3-1:1.1/0003:046D:C517.0002/0003:046D:0085.0004/input/input14
U: Uniq=
H: Handlers=mouse1 event4
B: PROP=0
B: EV=17
B: KEY=ff00ff 0 0 0 0
B: REL=1943
B: MSC=10

I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input15
U: Uniq=
H: Handlers=kbd event5
B: PROP=0
B: EV=40001
B: SND=6

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.1/0000:23:00.1/sound/card0/input16
U: Uniq=
H: Handlers=event6
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.1/0000:23:00.1/sound/card0/input17
U: Uniq=
H: Handlers=event7
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.1/0000:23:00.1/sound/card0/input18
U: Uniq=
H: Handlers=event8
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=9"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.1/0000:23:00.1/sound/card0/input19
U: Uniq=
H: Handlers=event9
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=10"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.1/0000:23:00.1/sound/card0/input20
U: Uniq=
H: Handlers=event10
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=11"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.1/0000:23:00.1/sound/card0/input21
U: Uniq=
H: Handlers=event11
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=12"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.1/0000:23:00.1/sound/card0/input22
U: Uniq=
H: Handlers=event12
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Front Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:25:00.3/sound/card1/input23
U: Uniq=
H: Handlers=event13
B: PROP=0
B: EV=21
B: SW=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Rear Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:25:00.3/sound/card1/input24
U: Uniq=
H: Handlers=event14
B: PROP=0
B: EV=21
B: SW=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Line"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:25:00.3/sound/card1/input25
U: Uniq=
H: Handlers=event15
B: PROP=0
B: EV=21
B: SW=2000

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Line Out Front"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:25:00.3/sound/card1/input26
U: Uniq=
H: Handlers=event16
B: PROP=0
B: EV=21
B: SW=40

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Line Out Surround"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:25:00.3/sound/card1/input27
U: Uniq=
H: Handlers=event17
B: PROP=0
B: EV=21
B: SW=40

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Line Out CLFE"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:25:00.3/sound/card1/input28
U: Uniq=
H: Handlers=event18
B: PROP=0
B: EV=21
B: SW=40

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Line Out Side"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:25:00.3/sound/card1/input29
U: Uniq=
H: Handlers=event19
B: PROP=0
B: EV=21
B: SW=40

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Front Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:08.1/0000:25:00.3/sound/card1/input30
U: Uniq=
H: Handlers=event20
B: PROP=0
B: EV=21
B: SW=4



J'ai une souris verticale filaire Anker ("USB Optical Mouse", event2),
et j'ai un clavier sans fil Logitech (event3) qui était associé à une souris (je n'utilise pas cette dernière), les deux associés à un même récepteur. "event4" dans les erreurs semble correspondre à cette souris non branchée si je lis bien le résultat de la commande.

Je vais regarder les résultats du lien, voir si je trouve des solutions possibles. Merci !

Hors ligne

#8 10-05-2021 23:21:04

Groot
Membre
Distrib. : Debian 11 bullseye (testing)
Noyau : Linux 5.10.0-6-amd64
(G)UI : XFCE
Inscription : 10-05-2021

Re : Freeze du système

Le test du disque dur s'est terminé, il n'y a pas d'erreur:

smartctl --test=long /dev/sdb
[..]
smartctl -l selftest /dev/sdb


smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-6-amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%      5736         -


J'ai aussi un SSD (sur lequel il y la racine du système) mais je ne l'ai pas encore testé

Hors ligne

#9 10-05-2021 23:40:15

tux12
Membre
Lieu : ./
Distrib. : stable
Noyau : celui de la stable
(G)UI : KDE
Inscription : 27-02-2008

Re : Freeze du système

Pour pouvoir exploiter le résultat j'aurais besoin du retour de smartctl -a /dev/sdb. Ce n'est utile que si il y a des parties du système sur ce disque (programmes, libs, fichiers de config...).
Pour ce qui est du SSD je suggère d'attendre quelqu'un qui connait.

Tout est un sauf zéro. - Wau Holland

Hors ligne

#10 11-05-2021 00:06:07

Groot
Membre
Distrib. : Debian 11 bullseye (testing)
Noyau : Linux 5.10.0-6-amd64
(G)UI : XFCE
Inscription : 10-05-2021

Re : Freeze du système

tux12 a écrit :

Pour pouvoir exploiter le résultat j'aurais besoin du retour de smartctl -a /dev/sdb. Ce n'est utile que si il y a des parties du système sur ce disque (programmes, libs, fichiers de config...).
Pour ce qui est du SSD je suggère d'attendre quelqu'un qui connait.


Alors effectivement, le disque est monté et il y a mes données, mais il n'est pas utilisé pour le système. J'ai quand même mis le résultat ci-dessous, tout à l'air normal.

smartctl -a /dev/sdb


smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-6-amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate BarraCuda 3.5
Device Model:     ST2000DM006-2DM164
Serial Number:    Z560PQXX
LU WWN Device Id: 5 000c50 0a60a0cf0
Firmware Version: CC26
User Capacity:    2000398934016 bytes [2,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon May 10 23:59:43 2021 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
          was completed without error.
          Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
          without error or no self-test has ever
          been run.
Total time to complete Offline
data collection:    (   89) seconds.
Offline data collection
capabilities:        (0x7b) SMART execute Offline immediate.
          Auto Offline data collection on/off support.
          Suspend Offline collection upon new
          command.
          Offline surface scan supported.
          Self-test supported.
          Conveyance Self-test supported.
          Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
          power-saving mode.
          Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
          General Purpose Logging supported.
Short self-test routine
recommended polling time:    (   1) minutes.
Extended self-test routine
recommended polling time:    ( 216) minutes.
Conveyance self-test routine
recommended polling time:    (   2) minutes.
SCT capabilities:          (0x1085) SCT Status supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   120   099   006    Pre-fail  Always       -       241781360
  3 Spin_Up_Time            0x0003   096   094   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   097   097   020    Old_age   Always       -       3984
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   075   060   030    Pre-fail  Always       -       36194926
  9 Power_On_Hours          0x0032   094   094   000    Old_age   Always       -       5738
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       869
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       0 1 1
189 High_Fly_Writes         0x003a   093   093   000    Old_age   Always       -       7
190 Airflow_Temperature_Cel 0x0022   070   062   045    Old_age   Always       -       30 (Min/Max 18/33)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       1
193 Load_Cycle_Count        0x0032   083   083   000    Old_age   Always       -       35438
194 Temperature_Celsius     0x0022   030   040   000    Old_age   Always       -       30 (0 13 0 0 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       3343h+29m+16.746s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       19318953571
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       410447787654

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%      5736         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay



Par ailleurs je suis passé sur le pilote "nouveau" pour l'affichage au lieu de "nvidia", au cas où ça viendrais de là..

Hors ligne

#11 11-05-2021 01:54:48

tux12
Membre
Lieu : ./
Distrib. : stable
Noyau : celui de la stable
(G)UI : KDE
Inscription : 27-02-2008

Re : Freeze du système

Tout à l'air normal concernant ce disque. Une piste de moins.

Tout est un sauf zéro. - Wau Holland

Hors ligne

#12 11-05-2021 02:10:04

robert2a
Membre
Distrib. : Buster 10 version 10.11
Noyau : kernel buster backports
(G)UI : Mate
Inscription : 15-11-2014

Re : Freeze du système

Bonsoir
une chose me dérange  sur ton #1 , ceci


lspci -nnk | grep -iA3 vga


23:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1)
  Subsystem: Gigabyte Technology Co., Ltd GP106 [GeForce GTX 1060 3GB] [1458:373a]
  Kernel driver in use: nvidia
  Kernel modules: nouveau, nvidia_drm, nvidia
 



tu ne peu pas avoir :   nouveau , nvidia_drm et nvidia
pour moi par exemple (avec le driver nouveau)


Kernel driver in use: nouveau
Kernel modules: nouveau
 


ton installation du driver nvidia doit être mauvaise


Machines : kabylake I7 7700 , AMD 1700(X) ,AMD threadripper gen1 , AMD Raven R3 2200G , AMD FX(tm)-8320

Hors ligne

#13 11-05-2021 02:38:59

robert2a
Membre
Distrib. : Buster 10 version 10.11
Noyau : kernel buster backports
(G)UI : Mate
Inscription : 15-11-2014

Re : Freeze du système

voila avec le driver nvidia


lspci -nnk | grep -iA3 vga
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2)
  Subsystem: Micro-Star International Co., Ltd. [MSI] GM107 [GeForce GTX 750] [1462:8a9c]
  Kernel driver in use: nvidia
  Kernel modules: nvidia
 



les erreurs avec le driver nvidia


journalctl -r -p err
-- Journal begins at Tue 2021-05-11 02:18:08 CEST, ends at Tue 2021-05-11 02:26:03 CEST. --
mai 11 02:18:08 opteron kernel:
 



dmesg | grep drm
 



[    3.703406] systemd[1]: Starting Load Kernel Module drm...
[    3.744018] systemd[1]: modprobe@drm.service: Succeeded.
[    3.744326] systemd[1]: Finished Load Kernel Module drm.
[    4.400524] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[    4.400530] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
 



sinon pour la souris , mettre clavier/souris filaire pour les tests et voir stabilité et erreurs
je te conseille aussi ceci


apt-get --reinstall install linux-image-amd64 linux-headers-amd64 acpid acpi acpi-support-base
 


pour vérifier que tout est présent (installé)
pour installer le driver nvidia , la commande : (la machine doit être propre , pas de résidu d une ancienne installation)


apt install nvidia-driver
 



que ce soit nouveau ou nvidia le serveur X doit être stable (parfois avec certaines cartes , nouveau bug )


Machines : kabylake I7 7700 , AMD 1700(X) ,AMD threadripper gen1 , AMD Raven R3 2200G , AMD FX(tm)-8320

Hors ligne

#14 11-05-2021 02:50:19

robert2a
Membre
Distrib. : Buster 10 version 10.11
Noyau : kernel buster backports
(G)UI : Mate
Inscription : 15-11-2014

Re : Freeze du système

pour toi les erreurs sont celle ci :


-- Journal begins at Wed 2021-02-24 19:18:01 CET, ends at Mon 2021-05-10 12:49:52 CEST. --
mai 10 10:12:14 Phenix pulseaudio[1288]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
mai 10 10:11:53 Phenix pipewire[1287]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
mai 10 10:11:53 Phenix sddm-helper[1265]: gkr-pam: unable to locate daemon control file
mai 10 10:11:48 Phenix pipewire[1112]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
mai 10 10:11:45 Phenix kernel:
mai 10 10:11:45 Phenix systemd-udevd[371]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 203: Invalid argument
 



avec "EVIOCSKEYCODE" qui renvoie pas mal d'erreurs a vérifier si a cause du sans fil usb (souris "et ou" clavier en radio )

tu a aussi regarder le log de X si pas des erreurs


cat /var/log/Xorg.0.log
 

Dernière modification par robert2a (11-05-2021 02:52:56)


Machines : kabylake I7 7700 , AMD 1700(X) ,AMD threadripper gen1 , AMD Raven R3 2200G , AMD FX(tm)-8320

Hors ligne

#15 11-05-2021 22:07:12

Groot
Membre
Distrib. : Debian 11 bullseye (testing)
Noyau : Linux 5.10.0-6-amd64
(G)UI : XFCE
Inscription : 10-05-2021

Re : Freeze du système

Bonsoir robert2a,
Merci pour tes messages. Pour être sûr qu'il n'y ait pas de soucis à cause de résidus de configurations précédentes ou autre, je viens de finir de réinstaller une Debian stable en parallèle. Surtout que je commence une formation à distance dans quelques jours en plus du boulot, donc il me faut vraiment un système stable.

L'anomalie au niveau des drivers nouveau/nvidia tous deux présents est résolue :

lspci -nnk | grep -iA3 vga


23:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1)
  Subsystem: Gigabyte Technology Co., Ltd GP106 [GeForce GTX 1060 3GB] [1458:373a]
  Kernel driver in use: nvidia
  Kernel modules: nvidia



dmesg | grep drm


[    4.058787] [drm] [nvidia-drm] [GPU ID 0x00002300] Loading driver
[    4.058790] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:23:00.0 on minor 0



J'ai quelques messages d'erreur, je suis en train de regarder ça. Je vais me débrouiller pour trouver un autre clavier et tester si les erreurs à ce niveau disparaissent (ça semble probable)

journalctl -r -p err


-- Logs begin at Tue 2021-05-11 21:12:48 CEST, end at Tue 2021-05-11 21:49:28 CEST. --
mai 11 21:35:48 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:48 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:48 Phenix systemd[5907]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:48 Phenix systemd[5882]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:48 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:48 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:48 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:48 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:48 Phenix systemd[5826]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:47 Phenix systemd[5798]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:47 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:47 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:47 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:47 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:47 Phenix systemd[5753]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:47 Phenix systemd[5730]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:47 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:47 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:47 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:47 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:47 Phenix systemd[5707]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:47 Phenix systemd[5684]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:47 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:47 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:46 Phenix systemd[5651]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:46 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:46 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:46 Phenix systemd[5631]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:46 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:46 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:46 Phenix systemd[5615]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:46 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:46 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:46 Phenix systemd[5596]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:46 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:46 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:46 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:45 Phenix systemd[5577]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:45 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:45 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:45 Phenix systemd[5558]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:45 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:45 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:45 Phenix systemd[5539]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:45 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:45 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:45 Phenix systemd[5517]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:45 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:45 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:44 Phenix systemd[5494]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:44 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:44 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:44 Phenix systemd[5470]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:44 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:44 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:40 Phenix systemd[5180]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:40 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:40 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:40 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:40 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:35:40 Phenix systemd[5156]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:40 Phenix systemd[5128]: /usr/lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1.
mai 11 21:35:40 Phenix lvm2-activation-generator: Activation generator failed.
mai 11 21:35:40 Phenix lvm2-activation-generator: lvmconfig failed
mai 11 21:12:48 Phenix systemd-udevd[389]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 162: Invalid argument
mai 11 21:12:48 Phenix systemd-udevd[389]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 136: Invalid argument
mai 11 21:12:48 Phenix systemd-udevd[389]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 430: Invalid argument
mai 11 21:12:48 Phenix systemd-udevd[389]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc1046, and key code 203: Invalid argument
mai 11 21:12:48 Phenix systemd-udevd[389]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc1045, and key code 202: Invalid argument
mai 11 21:12:48 Phenix systemd-udevd[389]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc1044, and key code 149: Invalid argument
mai 11 21:12:48 Phenix systemd-udevd[389]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc1043, and key code 397: Invalid argument
mai 11 21:12:48 Phenix systemd-udevd[389]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc1042, and key code 423: Invalid argument
mai 11 21:12:48 Phenix systemd-udevd[389]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc1041, and key code 421: Invalid argument
mai 11 21:12:48 Phenix systemd-udevd[389]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc1020, and key code 103: Invalid argument
mai 11 21:12:48 Phenix systemd-udevd[389]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc101f, and key code 108: Invalid argument
mai 11 21:12:48 Phenix systemd-udevd[389]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc1005, and key code 212: Invalid argument
mai 11 21:12:48 Phenix systemd-udevd[389]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Invalid argument
mai 11 21:12:48 Phenix kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
mai 11 21:12:48 Phenix kernel: iommu ivhd0: Event logged [INVALID_DEVICE_REQUEST device=00:00.0 pasid=0x00000 address=0xfffffffdf8000000 flags=0x0a00]



Concernant Xorg il ne semble pas y avoir d'erreurs à présent :

cat /var/log/Xorg.0.log


[     6.146]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[     6.146] Build Operating System: Linux 5.10.0-6-amd64 x86_64 Debian
[     6.146] Current Operating System: Linux Phenix 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64
[     6.146] Kernel command line: BOOT_IMAGE=/vmlinuz-4.19.0-16-amd64 root=UUID=2b51450b-8b6c-44c6-9176-c6d58a8d4d42 ro quiet
[     6.146] Build Date: 19 April 2021  09:34:38AM
[     6.146] xorg-server 2:1.20.4-1+deb10u3 (https://www.debian.org/support)
[     6.146] Current version of pixman: 0.36.0
[     6.146]  Before reporting problems, check http://wiki.x.org
  to make sure that you have the latest version.
[     6.146] Markers: (--) probed, (**) from config file, (==) default setting,
  (++) from command line, (!!) notice, (II) informational,
  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     6.146] (==) Log file: "/var/log/Xorg.0.log", Time: Tue May 11 21:12:50 2021
[     6.147] (==) Using config file: "/etc/X11/xorg.conf"
[     6.147] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[     6.149] (==) ServerLayout "Layout0"
[     6.149] (**) |-->Screen "Screen0" (0)
[     6.149] (**) |   |-->Monitor "Monitor0"
[     6.150] (**) |   |-->Device "Device0"
[     6.150] (**) |-->Input Device "Keyboard0"
[     6.150] (**) |-->Input Device "Mouse0"
[     6.150] (**) Option "Xinerama" "0"
[     6.150] (==) Automatically adding devices
[     6.150] (==) Automatically enabling devices
[     6.150] (==) Automatically adding GPU devices
[     6.150] (==) Max clients allowed: 256, resource mask: 0x1fffff
[     6.152] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[     6.152]  Entry deleted from font path.
[     6.154] (==) FontPath set to:
  /usr/share/fonts/X11/misc,
  /usr/share/fonts/X11/100dpi/:unscaled,
  /usr/share/fonts/X11/75dpi/:unscaled,
  /usr/share/fonts/X11/Type1,
  /usr/share/fonts/X11/100dpi,
  /usr/share/fonts/X11/75dpi,
  built-ins
[     6.154] (==) ModulePath set to "/usr/lib/xorg/modules"
[     6.154] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[     6.154] (WW) Disabling Keyboard0
[     6.154] (WW) Disabling Mouse0
[     6.154] (II) Loader magic: 0x56382c61ce20
[     6.154] (II) Module ABI versions:
[     6.154]  X.Org ANSI C Emulation: 0.4
[     6.154]  X.Org Video Driver: 24.0
[     6.154]  X.Org XInput driver : 24.1
[     6.154]  X.Org Server Extension : 10.0
[     6.154] (++) using VT number 7

[     6.154] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[     6.155] (II) xfree86: Adding drm device (/dev/dri/card0)
[     6.160] (--) PCI:*(35@0:0:0) 10de:1c02:1458:373a rev 161, Mem @ 0xfc000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[     6.160] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[     6.160] (II) LoadModule: "dbe"
[     6.160] (II) Module "dbe" already built-in
[     6.160] (II) LoadModule: "extmod"
[     6.160] (II) Module "extmod" already built-in
[     6.160] (II) LoadModule: "glx"
[     6.160] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     6.169] (II) Module glx: vendor="X.Org Foundation"
[     6.169]  compiled for 1.20.4, module version = 1.0.0
[     6.169]  ABI class: X.Org Server Extension, version 10.0
[     6.169] (II) LoadModule: "nvidia"
[     6.171] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[     6.179] (II) Module nvidia: vendor="NVIDIA Corporation"
[     6.179]  compiled for 4.0.2, module version = 1.0.0
[     6.179]  Module class: X.Org Video Driver
[     6.181] (II) NVIDIA dlloader X Driver  418.181.07  Sun Dec 27 18:56:05 UTC 2020
[     6.181] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[     6.185] (II) Loading sub module "fb"
[     6.185] (II) LoadModule: "fb"
[     6.185] (II) Loading /usr/lib/xorg/modules/libfb.so
[     6.186] (II) Module fb: vendor="X.Org Foundation"
[     6.186]  compiled for 1.20.4, module version = 1.0.0
[     6.186]  ABI class: X.Org ANSI C Emulation, version 0.4
[     6.186] (II) Loading sub module "wfb"
[     6.186] (II) LoadModule: "wfb"
[     6.187] (II) Loading /usr/lib/xorg/modules/libwfb.so
[     6.188] (II) Module wfb: vendor="X.Org Foundation"
[     6.188]  compiled for 1.20.4, module version = 1.0.0
[     6.188]  ABI class: X.Org ANSI C Emulation, version 0.4
[     6.188] (II) Loading sub module "ramdac"
[     6.188] (II) LoadModule: "ramdac"
[     6.188] (II) Module "ramdac" already built-in
[     6.189] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[     6.189] (==) NVIDIA(0): RGB weight 888
[     6.189] (==) NVIDIA(0): Default visual is TrueColor
[     6.189] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[     6.190] (**) NVIDIA(0): Option "Stereo" "0"
[     6.190] (**) NVIDIA(0): Option "nvidiaXineramaInfoOrder" "DFP-4"
[     6.190] (**) NVIDIA(0): Option "SLI" "Off"
[     6.190] (**) NVIDIA(0): Option "MultiGPU" "Off"
[     6.190] (**) NVIDIA(0): Option "BaseMosaic" "off"
[     6.190] (**) NVIDIA(0): Stereo disabled by request
[     6.190] (**) NVIDIA(0): NVIDIA SLI disabled.
[     6.190] (**) NVIDIA(0): NVIDIA Multi-GPU disabled.
[     6.190] (**) NVIDIA(0): Option "MetaModes" "DP-4: nvidia-auto-select +1920+0, HDMI-0: nvidia-auto-select +0+0, DP-2: nvidia-auto-select +0+0"
[     6.190] (**) NVIDIA(0): Enabling 2D acceleration
[     6.190] (II) Loading sub module "glxserver_nvidia"
[     6.190] (II) LoadModule: "glxserver_nvidia"
[     6.190] (II) Loading /usr/lib/xorg/modules/extensions/libglxserver_nvidia.so
[     6.239] (II) Module glxserver_nvidia: vendor="NVIDIA Corporation"
[     6.239]  compiled for 4.0.2, module version = 1.0.0
[     6.239]  Module class: X.Org Server Extension
[     6.240] (II) NVIDIA GLX Module  418.181.07  Sun Dec 27 18:55:20 UTC 2020
[     6.245] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:35:0:0
[     6.245] (--) NVIDIA(0):     DFP-0
[     6.245] (--) NVIDIA(0):     DFP-1
[     6.245] (--) NVIDIA(0):     DFP-2
[     6.245] (--) NVIDIA(0):     DFP-3
[     6.245] (--) NVIDIA(0):     DFP-4
[     6.245] (--) NVIDIA(0):     DFP-5
[     6.245] (--) NVIDIA(0):     DFP-6 (boot)
[     6.245] (--) NVIDIA(0):     DFP-7
[     6.246] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 1060 3GB (GP106-A) at PCI:35:0:0
[     6.246] (II) NVIDIA(0):     (GPU-0)
[     6.246] (--) NVIDIA(0): Memory: 3145728 kBytes
[     6.246] (--) NVIDIA(0): VideoBIOS: 86.06.3c.00.7d
[     6.246] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[     6.247] (--) NVIDIA(GPU-0): DFP-0: disconnected
[     6.247] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[     6.247] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[     6.247] (--) NVIDIA(GPU-0):
[     6.276] (--) NVIDIA(GPU-0): LG Electronics LG TV (DFP-1): connected
[     6.276] (--) NVIDIA(GPU-0): LG Electronics LG TV (DFP-1): Internal TMDS
[     6.276] (--) NVIDIA(GPU-0): LG Electronics LG TV (DFP-1): 600.0 MHz maximum pixel clock
[     6.276] (--) NVIDIA(GPU-0):
[     6.276] (--) NVIDIA(GPU-0): DFP-2: disconnected
[     6.276] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[     6.276] (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock
[     6.276] (--) NVIDIA(GPU-0):
[     6.277] (--) NVIDIA(GPU-0): DFP-3: disconnected
[     6.277] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[     6.277] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[     6.277] (--) NVIDIA(GPU-0):
[     6.277] (--) NVIDIA(GPU-0): AOC 24G2W1G5 (DFP-4): connected
[     6.277] (--) NVIDIA(GPU-0): AOC 24G2W1G5 (DFP-4): Internal DisplayPort
[     6.277] (--) NVIDIA(GPU-0): AOC 24G2W1G5 (DFP-4): 1440.0 MHz maximum pixel clock
[     6.277] (--) NVIDIA(GPU-0):
[     6.278] (--) NVIDIA(GPU-0): DFP-5: disconnected
[     6.278] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[     6.278] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
[     6.278] (--) NVIDIA(GPU-0):
[     6.284] (--) NVIDIA(GPU-0): AOC 24G2W1G4 (DFP-6): connected
[     6.284] (--) NVIDIA(GPU-0): AOC 24G2W1G4 (DFP-6): Internal DisplayPort
[     6.284] (--) NVIDIA(GPU-0): AOC 24G2W1G4 (DFP-6): 1440.0 MHz maximum pixel clock
[     6.284] (--) NVIDIA(GPU-0):
[     6.287] (--) NVIDIA(GPU-0): DFP-7: disconnected
[     6.287] (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
[     6.287] (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
[     6.287] (--) NVIDIA(GPU-0):
[     6.304] (II) NVIDIA(0): Validated MetaModes:
[     6.304] (II) NVIDIA(0):    
[     6.304] (II) NVIDIA(0):     "DP-4:nvidia-auto-select+1920+0,HDMI-0:nvidia-auto-select+0+0,DP-2:nvidia-auto-select+0+0"
[     6.304] (II) NVIDIA(0): Virtual screen size determined to be 3840 x 1080
[     6.313] (--) NVIDIA(0): DPI set to (42, 42); computed from "UseEdidDpi" X config
[     6.313] (--) NVIDIA(0):     option
[     6.314] (II) NVIDIA: Using 24576.00 MB of virtual memory for indirect memory
[     6.314] (II) NVIDIA:     access.
[     6.316] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[     6.316] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[     6.316] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[     6.316] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[     6.316] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[     6.316] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[     6.316] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[     6.316] (II) NVIDIA(0):     Config Options in the README.
[     6.334] (II) NVIDIA(0): Setting mode "DP-4:nvidia-auto-select+1920+0,HDMI-0:nvidia-auto-select+0+0,DP-2:nvidia-auto-select+0+0"
[     6.617] (==) NVIDIA(0): Disabling shared memory pixmaps
[     6.617] (==) NVIDIA(0): Backing store enabled
[     6.617] (==) NVIDIA(0): Silken mouse enabled
[     6.618] (**) NVIDIA(0): DPMS enabled
[     6.620] (II) Loading sub module "dri2"
[     6.620] (II) LoadModule: "dri2"
[     6.620] (II) Module "dri2" already built-in
[     6.620] (II) NVIDIA(0): [DRI2] Setup complete
[     6.620] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[     6.620] (II) Initializing extension Generic Event Extension
[     6.620] (II) Initializing extension SHAPE
[     6.620] (II) Initializing extension MIT-SHM
[     6.620] (II) Initializing extension XInputExtension
[     6.621] (II) Initializing extension XTEST
[     6.621] (II) Initializing extension BIG-REQUESTS
[     6.621] (II) Initializing extension SYNC
[     6.621] (II) Initializing extension XKEYBOARD
[     6.621] (II) Initializing extension XC-MISC
[     6.621] (II) Initializing extension SECURITY
[     6.621] (II) Initializing extension XFIXES
[     6.621] (II) Initializing extension RENDER
[     6.621] (II) Initializing extension RANDR
[     6.621] (II) Initializing extension COMPOSITE
[     6.621] (II) Initializing extension DAMAGE
[     6.622] (II) Initializing extension MIT-SCREEN-SAVER
[     6.622] (II) Initializing extension DOUBLE-BUFFER
[     6.622] (II) Initializing extension RECORD
[     6.622] (II) Initializing extension DPMS
[     6.622] (II) Initializing extension Present
[     6.622] (II) Initializing extension DRI3
[     6.622] (II) Initializing extension X-Resource
[     6.622] (II) Initializing extension XVideo
[     6.622] (II) Initializing extension XVideo-MotionCompensation
[     6.622] (II) Initializing extension SELinux
[     6.622] (II) SELinux: Disabled on system
[     6.622] (II) Initializing extension GLX
[     6.622] (II) Initializing extension GLX
[     6.622] (II) Indirect GLX disabled.
[     6.622] (II) GLX: Another vendor is already registered for screen 0
[     6.622] (II) Initializing extension XFree86-VidModeExtension
[     6.622] (II) Initializing extension XFree86-DGA
[     6.622] (II) Initializing extension XFree86-DRI
[     6.622] (II) Initializing extension DRI2
[     6.623] (II) Initializing extension NV-GLX
[     6.623] (II) Initializing extension NV-CONTROL
[     6.623] (II) Initializing extension XINERAMA
[     6.689] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[     6.689] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[     6.689] (II) LoadModule: "libinput"
[     6.689] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[     6.695] (II) Module libinput: vendor="X.Org Foundation"
[     6.695]  compiled for 1.20.4, module version = 0.28.2
[     6.695]  Module class: X.Org XInput Driver
[     6.695]  ABI class: X.Org XInput driver, version 24.1
[     6.695] (II) Using input driver 'libinput' for 'Power Button'
[     6.695] (**) Power Button: always reports core events
[     6.695] (**) Option "Device" "/dev/input/event1"
[     6.695] (**) Option "_source" "server/udev"
[     6.697] (II) event1  - Power Button: is tagged by udev as: Keyboard
[     6.697] (II) event1  - Power Button: device is a keyboard
[     6.698] (II) event1  - Power Button: device removed
[     6.728] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[     6.728] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[     6.728] (**) Option "xkb_model" "pc105"
[     6.728] (**) Option "xkb_layout" "fr"
[     6.728] (**) Option "xkb_variant" "azerty"
[     6.728] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[     6.751] (II) event1  - Power Button: is tagged by udev as: Keyboard
[     6.751] (II) event1  - Power Button: device is a keyboard
[     6.751] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[     6.751] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[     6.751] (II) Using input driver 'libinput' for 'Power Button'
[     6.751] (**) Power Button: always reports core events
[     6.751] (**) Option "Device" "/dev/input/event0"
[     6.751] (**) Option "_source" "server/udev"
[     6.753] (II) event0  - Power Button: is tagged by udev as: Keyboard
[     6.753] (II) event0  - Power Button: device is a keyboard
[     6.753] (II) event0  - Power Button: device removed
[     6.772] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0"
[     6.772] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[     6.772] (**) Option "xkb_model" "pc105"
[     6.772] (**) Option "xkb_layout" "fr"
[     6.772] (**) Option "xkb_variant" "azerty"
[     6.772] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[     6.772] (II) event0  - Power Button: is tagged by udev as: Keyboard
[     6.772] (II) event0  - Power Button: device is a keyboard
[     6.773] (II) config/udev: Adding input device USB Optical Mouse (/dev/input/event3)
[     6.773] (**) USB Optical Mouse: Applying InputClass "libinput pointer catchall"
[     6.773] (II) Using input driver 'libinput' for 'USB Optical Mouse'
[     6.773] (**) USB Optical Mouse: always reports core events
[     6.773] (**) Option "Device" "/dev/input/event3"
[     6.773] (**) Option "_source" "server/udev"
[     6.832] (II) event3  - USB Optical Mouse: is tagged by udev as: Mouse
[     6.832] (II) event3  - USB Optical Mouse: device is a pointer
[     6.832] (II) event3  - USB Optical Mouse: device removed
[     6.872] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-8/1-8:1.0/0003:1BCF:0005.0003/input/input3/event3"
[     6.872] (II) XINPUT: Adding extended input device "USB Optical Mouse" (type: MOUSE, id 8)
[     6.872] (**) Option "AccelerationScheme" "none"
[     6.872] (**) USB Optical Mouse: (accel) selected scheme none/0
[     6.872] (**) USB Optical Mouse: (accel) acceleration factor: 2.000
[     6.872] (**) USB Optical Mouse: (accel) acceleration threshold: 4
[     6.933] (II) event3  - USB Optical Mouse: is tagged by udev as: Mouse
[     6.933] (II) event3  - USB Optical Mouse: device is a pointer
[     6.933] (II) config/udev: Adding input device USB Optical Mouse (/dev/input/mouse0)
[     6.933] (II) No input driver specified, ignoring this device.
[     6.933] (II) This device may have been added with another device file.
[     6.934] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event14)
[     6.934] (II) No input driver specified, ignoring this device.
[     6.934] (II) This device may have been added with another device file.
[     6.934] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event15)
[     6.934] (II) No input driver specified, ignoring this device.
[     6.934] (II) This device may have been added with another device file.
[     6.934] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event16)
[     6.934] (II) No input driver specified, ignoring this device.
[     6.934] (II) This device may have been added with another device file.
[     6.934] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event17)
[     6.934] (II) No input driver specified, ignoring this device.
[     6.934] (II) This device may have been added with another device file.
[     6.935] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event2)
[     6.935] (**) Logitech USB Receiver: Applying InputClass "libinput keyboard catchall"
[     6.935] (II) Using input driver 'libinput' for 'Logitech USB Receiver'
[     6.935] (**) Logitech USB Receiver: always reports core events
[     6.935] (**) Option "Device" "/dev/input/event2"
[     6.935] (**) Option "_source" "server/udev"
[     6.935] (II) event2  - Logitech USB Receiver: is tagged by udev as: Keyboard
[     6.935] (II) event2  - Logitech USB Receiver: device is a keyboard
[     6.935] (II) event2  - Logitech USB Receiver: device removed
[     6.948] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:07.1/0000:24:00.3/usb3/3-1/3-1:1.0/0003:046D:C517.0001/input/input2/event2"
[     6.948] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 9)
[     6.948] (**) Option "xkb_model" "pc105"
[     6.948] (**) Option "xkb_layout" "fr"
[     6.948] (**) Option "xkb_variant" "azerty"
[     6.948] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[     6.949] (II) event2  - Logitech USB Receiver: is tagged by udev as: Keyboard
[     6.949] (II) event2  - Logitech USB Receiver: device is a keyboard
[     6.950] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event4)
[     6.950] (**) Logitech USB Receiver: Applying InputClass "libinput pointer catchall"
[     6.950] (**) Logitech USB Receiver: Applying InputClass "libinput keyboard catchall"
[     6.950] (II) Using input driver 'libinput' for 'Logitech USB Receiver'
[     6.950] (**) Logitech USB Receiver: always reports core events
[     6.950] (**) Option "Device" "/dev/input/event4"
[     6.950] (**) Option "_source" "server/udev"
[     6.950] (II) event4  - Logitech USB Receiver: is tagged by udev as: Keyboard Mouse
[     6.950] (II) event4  - Logitech USB Receiver: device set to 950 DPI
[     6.950] (II) event4  - Logitech USB Receiver: device is a pointer
[     6.950] (II) event4  - Logitech USB Receiver: device is a keyboard
[     6.950] (II) event4  - Logitech USB Receiver: device removed
[     6.972] (II) libinput: Logitech USB Receiver: needs a virtual subdevice
[     6.972] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:07.1/0000:24:00.3/usb3/3-1/3-1:1.1/0003:046D:C517.0002/input/input4/event4"
[     6.972] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: MOUSE, id 10)
[     6.972] (**) Option "AccelerationScheme" "none"
[     6.972] (**) Logitech USB Receiver: (accel) selected scheme none/0
[     6.972] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[     6.973] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[     6.974] (II) event4  - Logitech USB Receiver: is tagged by udev as: Keyboard Mouse
[     6.974] (II) event4  - Logitech USB Receiver: device set to 950 DPI
[     6.975] (II) event4  - Logitech USB Receiver: device is a pointer
[     6.975] (II) event4  - Logitech USB Receiver: device is a keyboard
[     6.975] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse1)
[     6.975] (II) No input driver specified, ignoring this device.
[     6.975] (II) This device may have been added with another device file.
[     6.976] (II) config/udev: Adding input device HD-Audio Generic Line Out Surround (/dev/input/event10)
[     6.976] (II) No input driver specified, ignoring this device.
[     6.976] (II) This device may have been added with another device file.
[     6.976] (II) config/udev: Adding input device HD-Audio Generic Line Out CLFE (/dev/input/event11)
[     6.976] (II) No input driver specified, ignoring this device.
[     6.976] (II) This device may have been added with another device file.
[     6.977] (II) config/udev: Adding input device HD-Audio Generic Line Out Side (/dev/input/event12)
[     6.977] (II) No input driver specified, ignoring this device.
[     6.977] (II) This device may have been added with another device file.
[     6.977] (II) config/udev: Adding input device HD-Audio Generic Front Headphone (/dev/input/event13)
[     6.977] (II) No input driver specified, ignoring this device.
[     6.977] (II) This device may have been added with another device file.
[     6.978] (II) config/udev: Adding input device HD-Audio Generic Front Mic (/dev/input/event6)
[     6.978] (II) No input driver specified, ignoring this device.
[     6.978] (II) This device may have been added with another device file.
[     6.978] (II) config/udev: Adding input device HD-Audio Generic Rear Mic (/dev/input/event7)
[     6.978] (II) No input driver specified, ignoring this device.
[     6.978] (II) This device may have been added with another device file.
[     6.979] (II) config/udev: Adding input device HD-Audio Generic Line (/dev/input/event8)
[     6.979] (II) No input driver specified, ignoring this device.
[     6.979] (II) This device may have been added with another device file.
[     6.979] (II) config/udev: Adding input device HD-Audio Generic Line Out Front (/dev/input/event9)
[     6.979] (II) No input driver specified, ignoring this device.
[     6.979] (II) This device may have been added with another device file.
[     6.980] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
[     6.980] (II) No input driver specified, ignoring this device.
[     6.980] (II) This device may have been added with another device file.
[     6.985] (**) Logitech USB Receiver: Applying InputClass "libinput pointer catchall"
[     6.985] (**) Logitech USB Receiver: Applying InputClass "libinput keyboard catchall"
[     6.985] (II) Using input driver 'libinput' for 'Logitech USB Receiver'
[     6.985] (**) Logitech USB Receiver: always reports core events
[     6.985] (**) Option "Device" "/dev/input/event4"
[     6.985] (**) Option "_source" "_driver/libinput"
[     6.985] (II) libinput: Logitech USB Receiver: is a virtual subdevice
[     6.985] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:07.1/0000:24:00.3/usb3/3-1/3-1:1.1/0003:046D:C517.0002/input/input4/event4"
[     6.985] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 11)
[     6.985] (**) Option "xkb_model" "pc105"
[     6.985] (**) Option "xkb_layout" "fr"
[     6.985] (**) Option "xkb_variant" "azerty"
[     6.985] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[    17.004] (--) NVIDIA(GPU-0): DFP-0: disconnected
[    17.004] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[    17.004] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[    17.004] (--) NVIDIA(GPU-0):
[    17.033] (--) NVIDIA(GPU-0): LG Electronics LG TV (DFP-1): connected
[    17.033] (--) NVIDIA(GPU-0): LG Electronics LG TV (DFP-1): Internal TMDS
[    17.033] (--) NVIDIA(GPU-0): LG Electronics LG TV (DFP-1): 600.0 MHz maximum pixel clock
[    17.033] (--) NVIDIA(GPU-0):
[    17.033] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    17.033] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[    17.033] (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock
[    17.033] (--) NVIDIA(GPU-0):
[    17.033] (--) NVIDIA(GPU-0): DFP-3: disconnected
[    17.033] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[    17.033] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[    17.033] (--) NVIDIA(GPU-0):
[    17.034] (--) NVIDIA(GPU-0): AOC 24G2W1G5 (DFP-4): connected
[    17.034] (--) NVIDIA(GPU-0): AOC 24G2W1G5 (DFP-4): Internal DisplayPort
[    17.034] (--) NVIDIA(GPU-0): AOC 24G2W1G5 (DFP-4): 1440.0 MHz maximum pixel clock
[    17.034] (--) NVIDIA(GPU-0):
[    17.035] (--) NVIDIA(GPU-0): DFP-5: disconnected
[    17.035] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[    17.035] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
[    17.035] (--) NVIDIA(GPU-0):
[    17.035] (--) NVIDIA(GPU-0): AOC 24G2W1G4 (DFP-6): connected
[    17.035] (--) NVIDIA(GPU-0): AOC 24G2W1G4 (DFP-6): Internal DisplayPort
[    17.035] (--) NVIDIA(GPU-0): AOC 24G2W1G4 (DFP-6): 1440.0 MHz maximum pixel clock
[    17.035] (--) NVIDIA(GPU-0):
[    17.039] (--) NVIDIA(GPU-0): DFP-7: disconnected
[    17.039] (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
[    17.039] (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
[    17.039] (--) NVIDIA(GPU-0):
[    17.276] (--) NVIDIA(GPU-0): DFP-0: disconnected
[    17.276] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[    17.276] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[    17.276] (--) NVIDIA(GPU-0):
[    17.306] (--) NVIDIA(GPU-0): LG Electronics LG TV (DFP-1): connected
[    17.306] (--) NVIDIA(GPU-0): LG Electronics LG TV (DFP-1): Internal TMDS
[    17.306] (--) NVIDIA(GPU-0): LG Electronics LG TV (DFP-1): 600.0 MHz maximum pixel clock
[    17.306] (--) NVIDIA(GPU-0):
[    17.306] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    17.306] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[    17.306] (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock
[    17.306] (--) NVIDIA(GPU-0):
[    17.306] (--) NVIDIA(GPU-0): DFP-3: disconnected
[    17.306] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[    17.306] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[    17.306] (--) NVIDIA(GPU-0):
[    17.306] (--) NVIDIA(GPU-0): AOC 24G2W1G5 (DFP-4): connected
[    17.306] (--) NVIDIA(GPU-0): AOC 24G2W1G5 (DFP-4): Internal DisplayPort
[    17.306] (--) NVIDIA(GPU-0): AOC 24G2W1G5 (DFP-4): 1440.0 MHz maximum pixel clock
[    17.306] (--) NVIDIA(GPU-0):
[    17.308] (--) NVIDIA(GPU-0): DFP-5: disconnected
[    17.308] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[    17.308] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
[    17.308] (--) NVIDIA(GPU-0):
[    17.308] (--) NVIDIA(GPU-0): AOC 24G2W1G4 (DFP-6): connected
[    17.308] (--) NVIDIA(GPU-0): AOC 24G2W1G4 (DFP-6): Internal DisplayPort
[    17.308] (--) NVIDIA(GPU-0): AOC 24G2W1G4 (DFP-6): 1440.0 MHz maximum pixel clock
[    17.308] (--) NVIDIA(GPU-0):
[    17.312] (--) NVIDIA(GPU-0): DFP-7: disconnected
[    17.312] (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
[    17.312] (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
[    17.312] (--) NVIDIA(GPU-0):
[    17.670] (--) NVIDIA(GPU-0): DFP-0: disconnected
[    17.670] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[    17.670] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[    17.670] (--) NVIDIA(GPU-0):
[    17.699] (--) NVIDIA(GPU-0): LG Electronics LG TV (DFP-1): connected
[    17.699] (--) NVIDIA(GPU-0): LG Electronics LG TV (DFP-1): Internal TMDS
[    17.699] (--) NVIDIA(GPU-0): LG Electronics LG TV (DFP-1): 600.0 MHz maximum pixel clock
[    17.699] (--) NVIDIA(GPU-0):
[    17.699] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    17.699] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[    17.699] (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock
[    17.699] (--) NVIDIA(GPU-0):
[    17.699] (--) NVIDIA(GPU-0): DFP-3: disconnected
[    17.699] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[    17.699] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[    17.699] (--) NVIDIA(GPU-0):
[    17.700] (--) NVIDIA(GPU-0): AOC 24G2W1G5 (DFP-4): connected
[    17.700] (--) NVIDIA(GPU-0): AOC 24G2W1G5 (DFP-4): Internal DisplayPort
[    17.700] (--) NVIDIA(GPU-0): AOC 24G2W1G5 (DFP-4): 1440.0 MHz maximum pixel clock
[    17.700] (--) NVIDIA(GPU-0):
[    17.701] (--) NVIDIA(GPU-0): DFP-5: disconnected
[    17.701] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[    17.701] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
[    17.701] (--) NVIDIA(GPU-0):
[    17.701] (--) NVIDIA(GPU-0): AOC 24G2W1G4 (DFP-6): connected
[    17.701] (--) NVIDIA(GPU-0): AOC 24G2W1G4 (DFP-6): Internal DisplayPort
[    17.701] (--) NVIDIA(GPU-0): AOC 24G2W1G4 (DFP-6): 1440.0 MHz maximum pixel clock
[    17.701] (--) NVIDIA(GPU-0):
[    17.705] (--) NVIDIA(GPU-0): DFP-7: disconnected
[    17.705] (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
[    17.705] (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
[    17.705] (--) NVIDIA(GPU-0):
[    18.083] (--) NVIDIA(GPU-0): DFP-0: disconnected
[    18.083] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[    18.083] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[    18.083] (--) NVIDIA(GPU-0):
[    18.113] (--) NVIDIA(GPU-0): LG Electronics LG TV (DFP-1): connected
[    18.113] (--) NVIDIA(GPU-0): LG Electronics LG TV (DFP-1): Internal TMDS
[    18.113] (--) NVIDIA(GPU-0): LG Electronics LG TV (DFP-1): 600.0 MHz maximum pixel clock
[    18.113] (--) NVIDIA(GPU-0):
[    18.113] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    18.113] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[    18.113] (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock
[    18.113] (--) NVIDIA(GPU-0):
[    18.113] (--) NVIDIA(GPU-0): DFP-3: disconnected
[    18.113] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[    18.113] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[    18.113] (--) NVIDIA(GPU-0):
[    18.114] (--) NVIDIA(GPU-0): AOC 24G2W1G5 (DFP-4): connected
[    18.114] (--) NVIDIA(GPU-0): AOC 24G2W1G5 (DFP-4): Internal DisplayPort
[    18.114] (--) NVIDIA(GPU-0): AOC 24G2W1G5 (DFP-4): 1440.0 MHz maximum pixel clock
[    18.114] (--) NVIDIA(GPU-0):
[    18.115] (--) NVIDIA(GPU-0): DFP-5: disconnected
[    18.115] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[    18.115] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
[    18.115] (--) NVIDIA(GPU-0):
[    18.115] (--) NVIDIA(GPU-0): AOC 24G2W1G4 (DFP-6): connected
[    18.115] (--) NVIDIA(GPU-0): AOC 24G2W1G4 (DFP-6): Internal DisplayPort
[    18.115] (--) NVIDIA(GPU-0): AOC 24G2W1G4 (DFP-6): 1440.0 MHz maximum pixel clock
[    18.115] (--) NVIDIA(GPU-0):
[    18.119] (--) NVIDIA(GPU-0): DFP-7: disconnected
[    18.119] (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
[    18.119] (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
[    18.119] (--) NVIDIA(GPU-0):
[    18.119] (--) NVIDIA(GPU-0): DFP-0: disconnected
[    18.119] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[    18.119] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[    18.119] (--) NVIDIA(GPU-0):
[    18.148] (--) NVIDIA(GPU-0): LG Electronics LG TV (DFP-1): connected
[    18.148] (--) NVIDIA(GPU-0): LG Electronics LG TV (DFP-1): Internal TMDS
[    18.148] (--) NVIDIA(GPU-0): LG Electronics LG TV (DFP-1): 600.0 MHz maximum pixel clock
[    18.148] (--) NVIDIA(GPU-0):
[    18.148] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    18.148] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[    18.148] (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock
[    18.148] (--) NVIDIA(GPU-0):
[    18.148] (--) NVIDIA(GPU-0): DFP-3: disconnected
[    18.148] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[    18.148] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[    18.148] (--) NVIDIA(GPU-0):
[    18.149] (--) NVIDIA(GPU-0): AOC 24G2W1G5 (DFP-4): connected
[    18.149] (--) NVIDIA(GPU-0): AOC 24G2W1G5 (DFP-4): Internal DisplayPort
[    18.149] (--) NVIDIA(GPU-0): AOC 24G2W1G5 (DFP-4): 1440.0 MHz maximum pixel clock
[    18.149] (--) NVIDIA(GPU-0):
[    18.150] (--) NVIDIA(GPU-0): DFP-5: disconnected
[    18.150] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[    18.150] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
[    18.150] (--) NVIDIA(GPU-0):
[    18.150] (--) NVIDIA(GPU-0): AOC 24G2W1G4 (DFP-6): connected
[    18.150] (--) NVIDIA(GPU-0): AOC 24G2W1G4 (DFP-6): Internal DisplayPort
[    18.150] (--) NVIDIA(GPU-0): AOC 24G2W1G4 (DFP-6): 1440.0 MHz maximum pixel clock
[    18.150] (--) NVIDIA(GPU-0):
[    18.154] (--) NVIDIA(GPU-0): DFP-7: disconnected
[    18.154] (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
[    18.154] (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
[    18.154] (--) NVIDIA(GPU-0):



A présent je vais voir si le système ne freeze plus et continuer à regarder les erreurs. Merci encore pour ton votre aide en tous cas merci.gif

Hors ligne

#16 12-05-2021 01:15:13

robert2a
Membre
Distrib. : Buster 10 version 10.11
Noyau : kernel buster backports
(G)UI : Mate
Inscription : 15-11-2014

Re : Freeze du système

Bonsoir
c'est quoi toutes ces erreurs ?


lvm2-activation-generator: Activation generator failed.
 



=>  https://bugs.debian.org/cgi-bin/bugrepo … bug=950510

Dernière modification par robert2a (12-05-2021 01:18:29)


Machines : kabylake I7 7700 , AMD 1700(X) ,AMD threadripper gen1 , AMD Raven R3 2200G , AMD FX(tm)-8320

Hors ligne

#17 12-05-2021 09:38:26

--gilles--
Membre
Lieu : Orléans - La Source
Distrib. : debian 11
Noyau : Linux 5.10.0-17-amd64
(G)UI : mutter 3.38.6-2~deb11u2
Inscription : 15-02-2016

Re : Freeze du système

Bonjour smile

Vous pouvez voir aussi des erreurs avec :

systemctl list-units --state=error



systemctl list-units --state=failed


« Quand la vérité n'est pas libre, la liberté n'est pas vraie. » Jacques Prévert

Hors ligne

#18 14-05-2021 22:50:56

Groot
Membre
Distrib. : Debian 11 bullseye (testing)
Noyau : Linux 5.10.0-6-amd64
(G)UI : XFCE
Inscription : 10-05-2021

Re : Freeze du système

Bonsoir smile

Je n'ai pas l'impression d'avoir fait quoi que ce soit à ce sujet, mais les erreurs relatives à LVM2 ne sont plus présentes. La machine est stable, tout fonctionne bien !
J'ai eu quelques autres erreurs que j'ai pu régler.
Les commandes

systemctl list-units --state=error
systemctl list-units --state=failed


Ne renvoient pas d'erreur.

Le journal systemd renvoie quelques erreurs mais ça ne semble pas critique. Pour l'instant je vais laisser tel quel (je n'ai pas encore l'autre clavier, ça devrait résoudre la plupart) :

journalctl -r -p err


-- Logs begin at Fri 2021-05-14 22:29:57 CEST, end at Fri 2021-05-14 22:30:30 CEST. --
mai 14 22:29:57 Phenix systemd-udevd[557]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 162: Invalid argument
mai 14 22:29:57 Phenix systemd-udevd[557]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 136: Invalid argument
mai 14 22:29:57 Phenix systemd-udevd[557]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 430: Invalid argument
mai 14 22:29:57 Phenix systemd-udevd[557]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc1046, and key code 203: Invalid argument
mai 14 22:29:57 Phenix systemd-udevd[557]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc1045, and key code 202: Invalid argument
mai 14 22:29:57 Phenix systemd-udevd[557]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc1044, and key code 149: Invalid argument
mai 14 22:29:57 Phenix systemd-udevd[557]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc1043, and key code 397: Invalid argument
mai 14 22:29:57 Phenix systemd-udevd[557]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc1042, and key code 423: Invalid argument
mai 14 22:29:57 Phenix systemd-udevd[557]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc1041, and key code 421: Invalid argument
mai 14 22:29:57 Phenix systemd-udevd[557]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc1020, and key code 103: Invalid argument
mai 14 22:29:57 Phenix systemd-udevd[557]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc101f, and key code 108: Invalid argument
mai 14 22:29:57 Phenix systemd-udevd[557]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc1005, and key code 212: Invalid argument
mai 14 22:29:57 Phenix systemd-udevd[557]: event2: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Invalid argument
mai 14 22:29:57 Phenix kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
mai 14 22:29:57 Phenix kernel: iommu ivhd0: Event logged [INVALID_DEVICE_REQUEST device=00:00.0 pasid=0x00000 address=0xfffffffdf8000000 flags=0x0a00]



Je vais pouvoir commencer ma formation à distance après-demain dans de bonnes conditions, merci beaucoup !
Ça va pas mal m'occuper pendant 2 mois, je repasserai au plus tard après. Bonne soirée !

Hors ligne

Pied de page des forums