Debian Debian-France Debian-Facile Debian-fr.org Debian-fr.xyz 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-10-2021 11:41:58

Magean
Membre
Inscription : 01-02-2021

[Résolu] Bullseye : écran noir à la sortie de veille

Salut,

Voilà mon problème : sur mon installation toute fraîche de Bullseye, lorsque je mets le PC en veille puis que je le réveille, je me retrouve face à un écran noir. Plus précisément, j'entends la machine se remettre en route, les LED reviennent, mais en revanche l'écran ne capte aucun signal : je le vois faire le tour de ses entrées en quête d'un signal - HDMI1, HDMI2, DVI... - avant de se remettre lui-même à dormir. Cependant, le système ne me paraît pas bloqué : une simple pression sur le bouton d'extinction de la tour amène, quelques secondes plus tard, à l'extinction de la machine. Il semble donc que la procédure d'extinction fonctionne normalement; en tout cas, je n'ai pas besoin d'éteindre la bête par la force d'une pression longue.

Les infos techniques de rigueur :

-OS : Debian 11 Bullseye, installé la semaine dernière sur une partition fraîchement formatée, en remplacement d'Ubuntu 20.04. À noter que je n'avais pas ce problème sur Ubuntu.
-Noyau : 5.10.0-8-amd64
-Carte mère : Gigabyte Z270X-Ultra Gaming
-CPU : i7-7700K @ 4.20GHz
-Carte graphique : GeForce GTX 1060 6GB, sous pilotes propriétaires 460.91.03-1. Un suspect potentiel, NVidia nous joue de sales tours de temps à autre...
-Gestionnaire d’affichage : lightdm. Un autre suspect, les pilotes NVidia posent parfois problème avec les gestionnaires d'affichage sous Linux, je me souviens avoir eu des soucis avec GDM.
-Bureau : un mélange perso de Xfce (pour le panneau et les outils de configuration graphique), bspwm (gestionnaire de fenêtres en "tuiles") et picom (fils spirituel de feu le compositeur compton). Cette installation n'est sans doute pas en tort puisque le problème de sortie de veille se manifestait déjà lorsque j'étais sous Xfce "pur".
A noter cependant que je n'ai pas installé le bureau Xfce complet proposé par Debian en fin d'installation (qui nous ramène beaucoup trop de trucs inutiles). Je suis parti d'une installation minimale et ai installé ce dont j'avais besoin (par exemple, le méta-paquet xfce4 plutôt que task-xfce-desktop), il est donc possible que j'aie raté un paquet important.

Merci d'avance pour votre aide.

Dernière modification par Magean (20-10-2021 16:00:31)

Hors ligne

#2 10-10-2021 11:49:16

hybridemoineau
Membre
Inscription : 21-02-2016

Re : [Résolu] Bullseye : écran noir à la sortie de veille

Plutôt qu'ajouter des paquets, j'en retirerais, ou plutôt je débrancherais progressivement ce qui gère la veille des écrans, à savoir :
- Le gestionnaire d'alimentation d'xfce (dans paramètres)
- L'écran de veille (dans paramètres aussi, s'il est installé, c'est xscreensaver)
- lightdm (je ne l'ai plus, du coup à part le désinstaller, installer xinit et faire un starx, je ne peux plus indiquer comment régler ses options...)

Dernière modification par hybridemoineau (10-10-2021 11:49:57)

Hors ligne

#3 10-10-2021 11:54:10

robert2a
Membre
Inscription : 15-11-2014

Re : [Résolu] Bullseye : écran noir à la sortie de veille

Bonjour
le retour de lspci


lspci
 


de glxinfo -B (du paquet mesa-utils)


glxinfo -B
 


de la présence de acpid


apt policy acpid
 


des erreurs sur la machine


journalctl -b -r -p err
 



la veille de l'écran fonctionne correctement ? , c'est la veille de la machine qui pose problème si j'ai bien compris ?
de plus le système ne freeze pas , tu perd juste le serveur X , tu a essayer de faire la combinaison de touche "Ctrl+Alt+F3" voir si tu reprend la main quand tu perds l'écran ?

Dernière modification par robert2a (10-10-2021 12:17:35)

Hors ligne

#4 10-10-2021 12:13:31

Magean
Membre
Inscription : 01-02-2021

Re : [Résolu] Bullseye : écran noir à la sortie de veille

Merci pour vos prestes réponses !

hybridemoineau a écrit :

Plutôt qu'ajouter des paquets, j'en retirerais, ou plutôt je débrancherais progressivement ce qui gère la veille des écrans, à savoir :
- Le gestionnaire d'alimentation d'xfce (dans paramètres)
- L'écran de veille (dans paramètres aussi, s'il est installé, c'est xscreensaver)
- lightdm (je ne l'ai plus, du coup à part le désinstaller, installer xinit et faire un starx, je ne peux plus indiquer comment régler ses options...)



xfce4-power-manager n'est pas coupable car j'avais déjà mon problème avant de l'installer. En fait je l'ai installé au cas où il m'aiderait (ce qui n'a pas été le cas).

xscreensaver n'est pas installé.

J'essayerai ce soir sans lightdm, il me faut le temps de me replonger dans la docu des xinitrc...

robert2a a écrit :

Bonjour
le retour de lspci


lspci
 


de glxinfo -B (du paquet mesa-utils)


glxinfo -B
 


de la présence de acpid


apt policy acpid
 


des erreurs sur la machine


journalctl -b -r -p err
 



Alors, lspci :

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05)
00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 05)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller
00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1
00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA controller [AHCI mode]
00:1b.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #17 (rev f0)
00:1b.2 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #19 (rev f0)
00:1b.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #21 (rev f0)
00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #1 (rev f0)
00:1c.2 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #3 (rev f0)
00:1c.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #5 (rev f0)
00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #9 (rev f0)
00:1f.0 ISA bridge: Intel Corporation 200 Series PCH LPC Controller (Z270)
00:1f.2 Memory controller: Intel Corporation 200 Series/Z370 Chipset Family Power Management Controller
00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio
00:1f.4 SMBus: Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V
01:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1)
03:00.0 USB controller: ASMedia Technology Inc. ASM2142 USB 3.1 Host Controller
08:00.0 SATA controller: Kingston Technology Company, Inc. HyperX Predator PCIe AHCI SSD (rev 10)



glxinfo -B :

name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 6144 MB
    Total available memory: 6144 MB
    Currently available dedicated video memory: 5906 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1060 6GB/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 460.91.03
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 460.91.03
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 460.91.03
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20



apt policy acpid :

acpid:
  Installé : (aucun)
  Candidat : 1:2.0.32-1
 Table de version :
     1:2.0.32-1 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages



journalctl -b -r -p err :

-- Journal begins at Mon 2021-10-04 12:24:00 CEST, ends at Sun 2021-10-10 12:11:34 CEST. --
oct. 10 11:09:49 martin-debian pulseaudio[723]: 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.
oct. 10 11:08:48 martin-debian pipewire[722]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
oct. 10 09:09:07 martin-debian kernel:
oct. 10 09:09:07 martin-debian kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
oct. 10 09:09:07 martin-debian kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
oct. 10 09:09:07 martin-debian kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
oct. 10 09:09:07 martin-debian kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
oct. 10 09:09:07 martin-debian kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
oct. 10 09:09:07 martin-debian kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT4._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
oct. 10 09:09:07 martin-debian kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
oct. 10 09:09:07 martin-debian kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT4._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)

Hors ligne

#5 10-10-2021 12:16:12

otyugh
CA Debian-Facile
Lieu : Quimperlé/Arzano
Distrib. : Debian Stable
Inscription : 20-09-2016
Site Web

Re : [Résolu] Bullseye : écran noir à la sortie de veille

-Carte graphique : GeForce GTX 1060 6GB, sous pilotes propriétaires 460.91.03-1. Un suspect potentiel, NVidia nous joue de sales tours de temps à autre...


Ouaip, j'essayerai de confirmer en le désinstallant, moi (oublie pas de redémarrer entre les deux pour recharger les pilotes).

Dernière modification par otyugh (10-10-2021 12:16:26)


datalove-datalove-s1-2.png agendadulibre-lagendadulibre.png arzinfo-arzinfo.png

Hors ligne

#6 10-10-2021 12:22:44

robert2a
Membre
Inscription : 15-11-2014

Re : [Résolu] Bullseye : écran noir à la sortie de veille

installe ceci


apt install acpi acpid acpi-support-base
 

Hors ligne

#7 10-10-2021 12:28:50

robert2a
Membre
Inscription : 15-11-2014

Re : [Résolu] Bullseye : écran noir à la sortie de veille

vérifie qu'il est actif


systemctl status acpid.service
 


pour moi le retour


● acpid.service - ACPI event daemon
     Loaded: loaded (/lib/systemd/system/acpid.service; disabled; vendor preset: enabled)
     Active: active (running) since Sun 2021-10-10 11:32:26 CEST; 53min ago
TriggeredBy: ● acpid.socket
             ● acpid.path
       Docs: man:acpid(8)
   Main PID: 620 (acpid)
      Tasks: 1 (limit: 17858)
     Memory: 288.0K
        CPU: 391ms
     CGroup: /system.slice/acpid.service
             └─620 /usr/sbin/acpid

oct. 10 11:32:26 debian12 systemd[1]: Started ACPI event daemon.
oct. 10 11:32:26 debian12 acpid[620]: starting up with netlink and the input layer
oct. 10 11:32:26 debian12 acpid[620]: 1 rule loaded
oct. 10 11:32:26 debian12 acpid[620]: waiting for events: event logging is off
 



ps: tu a beaucoup d'erreur acpi (ou warning) sur le retour des erreurs , on peu pas y faire grand chose

Hors ligne

#8 10-10-2021 12:37:16

robert2a
Membre
Inscription : 15-11-2014

Re : [Résolu] Bullseye : écran noir à la sortie de veille

si tu enlève le driver nvidia pense a vérifier que le firmware-misc-nonfree est installer (pour nouveau )
mais bon tous casser pour voir si ça fonctionne pas mon truc

Hors ligne

#9 10-10-2021 20:06:37

robert2a
Membre
Inscription : 15-11-2014

Re : [Résolu] Bullseye : écran noir à la sortie de veille

un exemple sur un amd driver libre (apu) , je te donnerai la même chose pour nvidia (1060 de mémoire)
pris sur le syslog , sur un bureau gnome debian bookworm gdm3 16go de ram  EFI  swap "977M Partition d'échange Linux"


Oct 10 19:36:19 raven2200g systemd[1]: Starting Suspend...
Oct 10 19:36:19 raven2200g systemd-sleep[3399]: Suspending system...
Oct 10 19:36:19 raven2200g kernel: [ 1952.724397] PM: suspend entry (deep)
Oct 10 19:45:25 raven2200g kernel: [ 1952.982236] Filesystems sync: 0.257 seconds
Oct 10 19:45:25 raven2200g kernel: [ 1952.982433] Freezing user space processes ... (elapsed 0.002 seconds) done.
Oct 10 19:45:25 raven2200g kernel: [ 1952.984447] OOM killer disabled.
Oct 10 19:45:25 raven2200g kernel: [ 1952.984448] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Oct 10 19:45:25 raven2200g kernel: [ 1952.985637] printk: Suspending console(s) (use no_console_suspend to debug)
Oct 10 19:45:25 raven2200g kernel: [ 1952.988938] serial 00:05: disabled
Oct 10 19:45:25 raven2200g kernel: [ 1952.989111] r8169 0000:06:00.0 enp6s0: Link is Down
Oct 10 19:45:25 raven2200g kernel: [ 1953.003460] sd 9:0:0:0: [sdc] Synchronizing SCSI cache
Oct 10 19:45:25 raven2200g kernel: [ 1953.003515] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Oct 10 19:45:25 raven2200g kernel: [ 1953.003524] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Oct 10 19:45:25 raven2200g kernel: [ 1953.003623] sd 9:0:0:0: [sdc] Stopping disk
Oct 10 19:45:25 raven2200g kernel: [ 1953.003698] sd 0:0:0:0: [sda] Stopping disk
Oct 10 19:45:25 raven2200g kernel: [ 1953.036029] [drm] free PSP TMR buffer
Oct 10 19:45:25 raven2200g kernel: [ 1953.069149] sd 1:0:0:0: [sdb] Stopping disk
Oct 10 19:45:25 raven2200g kernel: [ 1953.351307] ACPI: PM: Preparing to enter system sleep state S3
Oct 10 19:45:25 raven2200g kernel: [ 1953.671844] ACPI: PM: Saving platform NVS memory
Oct 10 19:45:25 raven2200g kernel: [ 1953.671899] Disabling non-boot CPUs ...
Oct 10 19:45:25 raven2200g kernel: [ 1953.673572] smpboot: CPU 1 is now offline
Oct 10 19:45:25 raven2200g kernel: [ 1953.675729] smpboot: CPU 2 is now offline
Oct 10 19:45:25 raven2200g kernel: [ 1953.678018] smpboot: CPU 3 is now offline
Oct 10 19:45:25 raven2200g kernel: [ 1953.679521] ACPI: PM: Low-level resume complete
Oct 10 19:45:25 raven2200g kernel: [ 1953.679578] ACPI: PM: Restoring platform NVS memory
Oct 10 19:45:25 raven2200g kernel: [ 1953.868788] Enabling non-boot CPUs ...
Oct 10 19:45:25 raven2200g kernel: [ 1953.868827] x86: Booting SMP configuration:
Oct 10 19:45:25 raven2200g kernel: [ 1953.868827] smpboot: Booting Node 0 Processor 1 APIC 0x1
Oct 10 19:45:25 raven2200g kernel: [ 1953.869167] microcode: CPU1: patch_level=0x08101016
Oct 10 19:45:25 raven2200g kernel: [ 1953.871349] ACPI: \_PR_.C001: Found 2 idle statesOct 10 19:27:03 raven2200g systemd[1]: Starting Daily apt-listbugs preferences cleanup...
Oct 10 19:27:03 raven2200g systemd[1]: apt-listbugs.service: Succeeded.
Oct 10 19:27:03 raven2200g systemd[1]: Finished Daily apt-listbugs preferences cleanup.
Oct 10 19:28:49 raven2200g dbus-daemon[539]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.56' (uid=1000 pid=1238 comm=>
Oct 10 19:28:49 raven2200g systemd[1]: Starting Hostname Service...
Oct 10 19:28:49 raven2200g dbus-daemon[539]: [system] Successfully activated service 'org.freedesktop.hostname1'
Oct 10 19:28:49 raven2200g systemd[1]: Started Hostname Service.
Oct 10 19:29:19 raven2200g systemd[1]: systemd-hostnamed.service: Succeeded.
Oct 10 19:30:01 raven2200g CRON[3393]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Oct 10 19:33:03 raven2200g systemd[1]: Started Run anacron jobs.
Oct 10 19:33:03 raven2200g systemd[1]: anacron.service: Succeeded.
Oct 10 19:33:03 raven2200g anacron[3396]: Anacron 2.3 started on 2021-10-10
Oct 10 19:33:03 raven2200g anacron[3396]: Normal exit (0 jobs run)
Oct 10 19:34:12 raven2200g smartd[549]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 78 to 68
Oct 10 19:34:12 raven2200g smartd[549]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 22 to 32
Oct 10 19:34:13 raven2200g smartd[549]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 78 to 65
Oct 10 19:34:13 raven2200g smartd[549]: Device: /dev/sdc [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 74 to 68
Oct 10 19:36:19 raven2200g ModemManager[612]: <info>  [sleep-monitor] system is about to suspend
Oct 10 19:36:19 raven2200g systemd[1]: Reached target Sleep.
Oct 10 19:36:19 raven2200g systemd[1]: Starting Suspend...
Oct 10 19:36:19 raven2200g systemd[1]: Starting Suspend...
Oct 10 19:36:19 raven2200g systemd-sleep[3399]: Suspending system...
Oct 10 19:36:19 raven2200g kernel: [ 1952.724397] PM: suspend entry (deep)
Oct 10 19:45:25 raven2200g kernel: [ 1952.982236] Filesystems sync: 0.257 seconds
Oct 10 19:45:25 raven2200g kernel: [ 1952.982433] Freezing user space processes ... (elapsed 0.002 seconds) done.
Oct 10 19:45:25 raven2200g kernel: [ 1952.984447] OOM killer disabled.
Oct 10 19:45:25 raven2200g kernel: [ 1952.984448] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Oct 10 19:45:25 raven2200g kernel: [ 1952.985637] printk: Suspending console(s) (use no_console_suspend to debug)
Oct 10 19:45:25 raven2200g kernel: [ 1952.988938] serial 00:05: disabled
Oct 10 19:45:25 raven2200g kernel: [ 1952.989111] r8169 0000:06:00.0 enp6s0: Link is Down
Oct 10 19:45:25 raven2200g kernel: [ 1953.003460] sd 9:0:0:0: [sdc] Synchronizing SCSI cache
Oct 10 19:45:25 raven2200g kernel: [ 1953.003515] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Oct 10 19:45:25 raven2200g kernel: [ 1953.003524] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Oct 10 19:45:25 raven2200g kernel: [ 1953.003623] sd 9:0:0:0: [sdc] Stopping disk
Oct 10 19:45:25 raven2200g kernel: [ 1953.003698] sd 0:0:0:0: [sda] Stopping disk
Oct 10 19:45:25 raven2200g kernel: [ 1953.036029] [drm] free PSP TMR buffer
Oct 10 19:45:25 raven2200g kernel: [ 1953.069149] sd 1:0:0:0: [sdb] Stopping disk
Oct 10 19:45:25 raven2200g kernel: [ 1953.351307] ACPI: PM: Preparing to enter system sleep state S3
Oct 10 19:45:25 raven2200g kernel: [ 1953.671844] ACPI: PM: Saving platform NVS memory
Oct 10 19:45:25 raven2200g kernel: [ 1953.671899] Disabling non-boot CPUs ...
Oct 10 19:45:25 raven2200g kernel: [ 1953.673572] smpboot: CPU 1 is now offline
Oct 10 19:45:25 raven2200g kernel: [ 1953.675729] smpboot: CPU 2 is now offline
Oct 10 19:45:25 raven2200g kernel: [ 1953.678018] smpboot: CPU 3 is now offline
Oct 10 19:45:25 raven2200g kernel: [ 1953.679521] ACPI: PM: Low-level resume complete
Oct 10 19:45:25 raven2200g kernel: [ 1953.679578] ACPI: PM: Restoring platform NVS memory
Oct 10 19:45:25 raven2200g kernel: [ 1953.868788] Enabling non-boot CPUs ...
Oct 10 19:45:25 raven2200g kernel: [ 1953.868827] x86: Booting SMP configuration:
Oct 10 19:45:25 raven2200g kernel: [ 1953.868827] smpboot: Booting Node 0 Processor 1 APIC 0x1
Oct 10 19:45:25 raven2200g kernel: [ 1953.869167] microcode: CPU1: patch_level=0x08101016
Oct 10 19:45:25 raven2200g kernel: [ 1953.871349] ACPI: \_PR_.C001: Found 2 idle states
Oct 10 19:45:25 raven2200g kernel: [ 1953.871551] CPU1 is up
Oct 10 19:45:25 raven2200g kernel: [ 1953.871615] smpboot: Booting Node 0 Processor 2 APIC 0x2
Oct 10 19:45:25 raven2200g kernel: [ 1953.872186] microcode: CPU2: patch_level=0x08101016
Oct 10 19:45:25 raven2200g kernel: [ 1953.874361] ACPI: \_PR_.C002: Found 2 idle states
Oct 10 19:45:25 raven2200g kernel: [ 1953.874585] CPU2 is up
Oct 10 19:45:25 raven2200g kernel: [ 1953.874601] smpboot: Booting Node 0 Processor 3 APIC 0x3
Oct 10 19:45:25 raven2200g kernel: [ 1953.874941] microcode: CPU3: patch_level=0x08101016
Oct 10 19:45:25 raven2200g kernel: [ 1953.877181] ACPI: \_PR_.C003: Found 2 idle states
Oct 10 19:45:25 raven2200g kernel: [ 1953.877430] CPU3 is up
Oct 10 19:45:25 raven2200g kernel: [ 1953.877817] ACPI: PM: Waking up from system sleep state S3
Oct 10 19:45:25 raven2200g kernel: [ 1953.957676] usb usb1: root hub lost power or was reset
Oct 10 19:45:25 raven2200g kernel: [ 1953.957679] usb usb2: root hub lost power or was reset
Oct 10 19:45:25 raven2200g kernel: [ 1953.958440] serial 00:05: activated
Oct 10 19:45:25 raven2200g kernel: [ 1953.959044] [drm] PCIE GART of 1024M enabled.
Oct 10 19:45:25 raven2200g kernel: [ 1953.959048] [drm] PTB located at 0x000000F400900000
Oct 10 19:45:25 raven2200g kernel: [ 1953.959071] [drm] PSP is resuming...
Oct 10 19:45:25 raven2200g kernel: [ 1953.959244] sd 0:0:0:0: [sda] Starting disk
Oct 10 19:45:25 raven2200g kernel: [ 1953.959257] sd 1:0:0:0: [sdb] Starting disk
Oct 10 19:45:25 raven2200g kernel: [ 1953.959265] sd 9:0:0:0: [sdc] Starting disk
Oct 10 19:45:25 raven2200g kernel: [ 1953.978943] [drm] reserve 0x400000 from 0xf47fc00000 for PSP TMR
Oct 10 19:45:25 raven2200g kernel: [ 1954.039120] amdgpu 0000:08:00.0: amdgpu: RAS: optional ras ta ucode is not available
Oct 10 19:45:25 raven2200g kernel: [ 1954.043561] amdgpu 0000:08:00.0: amdgpu: RAP: optional rap ta ucode is not available
Oct 10 19:45:25 raven2200g kernel: [ 1954.043563] amdgpu 0000:08:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Oct 10 19:45:25 raven2200g kernel: [ 1954.044905] [drm] kiq ring mec 2 pipe 1 q 0
Oct 10 19:45:25 raven2200g kernel: [ 1954.045148] amdgpu: restore the fine grain parameters
Oct 10 19:45:25 raven2200g kernel: [ 1954.092460] [drm] VCN decode and encode initialized successfully(under SPG Mode).
Oct 10 19:45:25 raven2200g kernel: [ 1954.092500] amdgpu 0000:08:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
Oct 10 19:45:25 raven2200g kernel: [ 1954.092502] amdgpu 0000:08:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Oct 10 19:45:25 raven2200g kernel: [ 1954.092503] amdgpu 0000:08:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Oct 10 19:45:25 raven2200g kernel: [ 1954.092504] amdgpu 0000:08:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Oct 10 19:45:25 raven2200g kernel: [ 1954.092506] amdgpu 0000:08:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Oct 10 19:45:25 raven2200g kernel: [ 1954.092507] amdgpu 0000:08:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Oct 10 19:45:25 raven2200g kernel: [ 1954.092508] amdgpu 0000:08:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Oct 10 19:45:25 raven2200g kernel: [ 1954.092509] amdgpu 0000:08:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Oct 10 19:45:25 raven2200g kernel: [ 1954.092510] amdgpu 0000:08:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Oct 10 19:45:25 raven2200g kernel: [ 1954.092511] amdgpu 0000:08:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Oct 10 19:45:25 raven2200g kernel: [ 1954.092512] amdgpu 0000:08:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
Oct 10 19:45:25 raven2200g kernel: [ 1954.092513] amdgpu 0000:08:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
Oct 10 19:45:25 raven2200g kernel: [ 1954.092514] amdgpu 0000:08:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
Oct 10 19:45:25 raven2200g kernel: [ 1954.092515] amdgpu 0000:08:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
Oct 10 19:45:25 raven2200g kernel: [ 1954.092516] amdgpu 0000:08:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
Oct 10 19:45:25 raven2200g kernel: [ 1954.152910] r8169 0000:06:00.0 enp6s0: Link is Down
Oct 10 19:45:25 raven2200g kernel: [ 1954.270817] ata6: SATA link down (SStatus 0 SControl 300)
Oct 10 19:45:25 raven2200g kernel: [ 1954.376716] usb 1-8: reset full-speed USB device number 2 using xhci_hcd
Oct 10 19:45:25 raven2200g kernel: [ 1954.432609] ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 10 19:45:25 raven2200g kernel: [ 1954.432853] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct 10 19:45:25 raven2200g kernel: [ 1954.432974] ata10.00: supports DRM functions and may not be fully accessible
Oct 10 19:45:25 raven2200g kernel: [ 1954.436592] ata10.00: supports DRM functions and may not be fully accessible
Oct 10 19:45:25 raven2200g kernel: [ 1954.439289] ata5.00: configured for UDMA/100
Oct 10 19:45:25 raven2200g kernel: [ 1954.439719] ata10.00: configured for UDMA/133
Oct 10 19:45:25 raven2200g kernel: [ 1954.439920] ata10.00: Enabling discard_zeroes_data
Oct 10 19:45:25 raven2200g kernel: [ 1954.685324] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
Oct 10 19:45:25 raven2200g kernel: [ 1954.685337] cp210x 1-8:1.0: device disconnected
Oct 10 19:45:25 raven2200g kernel: [ 1954.685652] OOM killer enabled.
Oct 10 19:45:25 raven2200g kernel: [ 1954.685655] Restarting tasks ...
Oct 10 19:45:25 raven2200g kernel: [ 1954.685659] cp210x 1-8:1.0: cp210x converter detected
Oct 10 19:45:25 raven2200g kernel: [ 1954.688512] done.
Oct 10 19:45:25 raven2200g kernel: [ 1954.688518] PM: suspend exit
Oct 10 19:45:25 raven2200g kernel: [ 1954.689569] usb 1-8: cp210x converter now attached to ttyUSB0
Oct 10 19:45:25 raven2200g systemd-sleep[3399]: System resumed.
Oct 10 19:45:25 raven2200g /usr/libexec/gdm-x-session[1100]: (II) AMDGPU(0): EDID vendor "IVM", prod id 24851
Oct 10 19:45:28 raven2200g kernel: [ 1957.128622] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 10 19:45:28 raven2200g kernel: [ 1957.131359] ata1.00: configured for UDMA/133
Oct 10 19:45:28 raven2200g kernel: [ 1957.304648] r8169 0000:06:00.0 enp6s0: Link is Up - 1Gbps/Full - flow control rx/tx
Oct 10 19:45:30 raven2200g kernel: [ 1959.201038] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 10 19:45:30 raven2200g kernel: [ 1959.207149] ata2.00: configured for UDMA/133
Oct 10 19:45:30 raven2200g /usr/libexec/gdm-x-session[1100]: (II) AMDGPU(0): Using hsync ranges from config file
Oct 10 19:45:30 raven2200g /usr/libexec/gdm-x-session[1100]: (II) AMDGPU(0): Using vrefresh ranges from config file
Oct 10 19:45:30 raven2200g /usr/libexec/gdm-x-session[1100]: (II) AMDGPU(0): Printing DDC gathered Modelines:
Oct 10 19:45:30 raven2200g /usr/libexec/gdm-x-session[1100]: (II) AMDGPU(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
Oct 10 19:45:30 raven2200g /usr/libexec/gdm-x-session[1100]: (II) AMDGPU(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
Oct 10 19:45:30 raven2200g /usr/libexec/gdm-x-session[1100]: (II) AMDGPU(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
Oct 10 19:45:30 raven2200g /usr/libexec/gdm-x-session[1100]: (II) AMDGPU(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
Oct 10 19:45:30 raven2200g /usr/libexec/gdm-x-session[1100]: (II) AMDGPU(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
Oct 10 19:45:30 raven2200g /usr/libexec/gdm-x-session[1100]: (II) AMDGPU(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
Oct 10 19:45:30 raven2200g /usr/libexec/gdm-x-session[1100]: (II) AMDGPU(0): Modeline "1152x720"x60.0   67.32  1152 1208 1328 1504  720 721 724 746 -hsync +vsync (44.8 kHz e)
Oct 10 19:45:30 raven2200g /usr/libexec/gdm-x-session[1100]: (II) AMDGPU(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
Oct 10 19:45:30 raven2200g /usr/libexec/gdm-x-session[1100]: (II) AMDGPU(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
Oct 10 19:45:30 raven2200g /usr/libexec/gdm-x-session[1100]: (II) AMDGPU(0): Modeline "1600x1200"x0.0  162.00  1600 1664 1856 2160  1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
Oct 10 19:45:30 raven2200g /usr/libexec/gdm-x-session[1100]: (II) AMDGPU(0): Modeline "1680x1050"x0.0  119.00  1680 1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
Oct 10 19:45:30 raven2200g /usr/libexec/gdm-x-session[1100]: (II) AMDGPU(0): Modeline "1440x900"x0.0   88.75  1440 1488 1520 1600  900 903 909 926 +hsync -vsync (55.5 kHz e)
Oct 10 19:45:30 raven2200g ModemManager[612]: <info>  [sleep-monitor] system is resuming
Oct 10 19:45:30 raven2200g systemd[1]: systemd-suspend.service: Succeeded.
Oct 10 19:45:30 raven2200g ModemManager[612]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:01.2/0000:01:00.0/usb1/1-8': not supported by any plugin
Oct 10 19:45:30 raven2200g systemd[1]: Finished Suspend.
Oct 10 19:45:30 raven2200g ModemManager[612]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:01.2/0000:01:00.2/0000:02:06.0/0000:06:00.0': not supported by any plugin
Oct 10 19:45:30 raven2200g systemd[1]: Stopped target Sleep.
Oct 10 19:45:30 raven2200g systemd[1]: Reached target Suspend.
Oct 10 19:45:30 raven2200g systemd[1]: Stopped target Suspend.
Oct 10 19:45:43 raven2200g systemd[1066]: Started Application launched by gnome-shell.
Oct 10 19:45:43 raven2200g systemd[1066]: Started VTE child process 3524 launched by gnome-terminal-server process 1646.
Oct 10 19:45:43 raven2200g systemd[1066]: app-gnome-org.gnome.Terminal-3518.scope: Succeeded.
 

Hors ligne

#10 10-10-2021 21:04:29

robert2a
Membre
Inscription : 15-11-2014

Re : [Résolu] Bullseye : écran noir à la sortie de veille

re, voila la partie debian bullseye gpu nvidia sur amd r7 1700 , beaucoup moins propre mais bon ça fonctionne


Oct 10 20:38:19 debian30 systemd[1]: Starting Suspend...
Oct 10 20:38:19 debian30 systemd-sleep[1958]: Suspending system...
Oct 10 20:38:19 debian30 kernel: [ 1227.716172] PM: suspend entry (deep)
Oct 10 20:38:19 debian30 kernel: [ 1227.718695] Filesystems sync: 0.002 seconds
Oct 10 20:42:47 debian30 kernel: [ 1228.024601] Freezing user space processes ... (elapsed 0.002 seconds) done.
Oct 10 20:42:47 debian30 kernel: [ 1228.026775] OOM killer disabled.
Oct 10 20:42:47 debian30 kernel: [ 1228.026777] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Oct 10 20:42:47 debian30 kernel: [ 1228.028035] printk: Suspending console(s) (use no_console_suspend to debug)
Oct 10 20:42:47 debian30 kernel: [ 1228.029309] serial 00:03: disabled
Oct 10 20:42:47 debian30 kernel: [ 1228.058680] sd 11:0:0:0: [sda] Synchronizing SCSI cache
Oct 10 20:42:47 debian30 kernel: [ 1228.058737] sd 11:0:0:0: [sda] Stopping disk
Oct 10 20:42:47 debian30 kernel: [ 1228.195083] ACPI: Preparing to enter system sleep state S3
Oct 10 20:42:47 debian30 kernel: [ 1228.503500] PM: Saving platform NVS memory
Oct 10 20:42:47 debian30 kernel: [ 1228.503551] Disabling non-boot CPUs ...
Oct 10 20:42:47 debian30 kernel: [ 1228.505333] smpboot: CPU 1 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.508116] smpboot: CPU 2 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.510639] smpboot: CPU 3 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.513197] smpboot: CPU 4 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.515772] smpboot: CPU 5 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.518466] smpboot: CPU 6 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.520999] smpboot: CPU 7 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.523566] smpboot: CPU 8 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.525532] smpboot: CPU 9 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.528007] smpboot: CPU 10 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.530375] smpboot: CPU 11 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.532749] smpboot: CPU 12 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.535148] smpboot: CPU 13 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.537330] smpboot: CPU 14 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.539463] smpboot: CPU 15 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.540430] ACPI: Low-level resume complete
Oct 10 20:42:47 debian30 kernel: [ 1228.540473] PM: Restoring platform NVS memory
Oct 10 20:42:47 debian30 kernel: [ 1228.541024] Enabling non-boot CPUs ...
Oct 10 20:42:47 debian30 kernel: [ 1228.541062] x86: Booting SMP configuration:
Oct 10 20:42:47 debian30 kernel: [ 1228.541063] smpboot: Booting Node 0 Processor 1 APIC 0x2
Oct 10 20:42:47 debian30 kernel: [ 1228.541176] microcode: CPU1: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.543347] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.543350] ACPI: \_PR_.C002: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.543628] CPU1 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.543693] smpboot: Booting Node 0 Processor 2 APIC 0x4
Oct 10 20:42:47 debian30 kernel: [ 1228.543886] microcode: CPU2: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.546053] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.546055] ACPI: \_PR_.C004: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.546258] CPU2 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.546272] smpboot: Booting Node 0 Processor 3 APIC 0x6
Oct 10 20:42:47 debian30 kernel: [ 1228.546391] microcode: CPU3: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.548560] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.548562] ACPI: \_PR_.C006: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.548754] CPU3 is up
Oct 10 20:42:47 debian30 kernel:[  1229.353] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select"
[  1229.394] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[  1229.394] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[  1229.394] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[  1229.394] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[  1229.394] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[  1229.394] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[  1229.394] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[  1229.394] (II) NVIDIA(0):     Config Options in the README.
[  1229.422] (II) event5  - Power Button: is tagged by udev as: Keyboard
[  1229.422] (II) event5  - Power Button: device is a keyboard
[  1229.424] (II) event4  - Power Button: is tagged by udev as: Keyboard
[  1229.424] (II) event4  - Power Button: device is a keyboard
[  1229.425] (II) event0  - Microsoft  Microsoft Basic Optical Mouse v2.0 : is tagged by udev as: Mouse
[  1229.425] (II) event0  - Microsoft  Microsoft Basic Optical Mouse v2.0 : device is a pointer
[  1229.427] (II) event1  - SEM USB Keyboard: is tagged by udev as: Keyboard
[  1229.427] (II) event1  - SEM USB Keyboard: device is a keyboard
[  1229.428] (II) event2  - SEM USB Keyboard Consumer Control: is tagged by udev as: Keyboard
[  1229.428] (II) event2  - SEM USB Keyboard Consumer Control: device is a keyboard
[  1229.430] (II) event3  - SEM USB Keyboard System Control: is tagged by udev as: Keyboard
[  1229.430] (II) event3  - SEM USB Keyboard System Control: device is a keyboard
[  1229.431] (II) event7  - Eee PC WMI hotkeys: is tagged by udev as: Keyboard
[  1229.431] (II) event7  - Eee PC WMI hotkeys: device is a keyboard
[  1275.469] (EE) event1  - SEM USB Keyboard: client bug: event processing lagging behind by 33ms, your system is too slow
[  1430.932] (EE) event1  - SEM USB Keyboard: client bug: event processing lagging behind by 32ms, your system is too slow
[  1478.867] (EE) event1  - SEM USB Keyboard: client bug: event processing lagging behind by 39ms, your system is too slow
[  1484.348] (EE) event1  - SEM USB Keyboard: client bug: event processing lagging behind by 23ms, your system is too slow [ 1228.548768] smpboot: Booting Node 0 Processor 4 APIC 0x8
Oct 10 20:42:47 debian30 kernel: [ 1228.548928] microcode: CPU4: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.551118] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.551120] ACPI: \_PR_.C008: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.551359] CPU4 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.551381] smpboot: Booting Node 0 Processor 5 APIC 0xa
Oct 10 20:42:47 debian30 kernel: [ 1228.551545] microcode: CPU5: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.553716] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.553719] ACPI: \_PR_.C00A: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.553952] CPU5 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.553971] smpboot: Booting Node 0 Processor 6 APIC 0xc
Oct 10 20:42:47 debian30 kernel: [ 1228.554135] microcode: CPU6: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.556345] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.556347] ACPI: \_PR_.C00C: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.556589] CPU6 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.556609] smpboot: Booting Node 0 Processor 7 APIC 0xe
Oct 10 20:42:47 debian30 kernel: [ 1228.556774] microcode: CPU7: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.558953] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.558955] ACPI: \_PR_.C00E: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.559210] CPU7 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.559231] smpboot: Booting Node 0 Processor 8 APIC 0x1
Oct 10 20:42:47 debian30 kernel: [ 1228.559378] microcode: CPU8: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.561575] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.561577] ACPI: \_PR_.C001: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.561937] CPU8 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.561968] smpboot: Booting Node 0 Processor 9 APIC 0x3
Oct 10 20:42:47 debian30 kernel: [ 1228.562085] microcode: CPU9: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.564269] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.564271] ACPI: \_PR_.C003: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.564568] CPU9 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.564586] smpboot: Booting Node 0 Processor 10 APIC 0x5
Oct 10 20:42:47 debian30 kernel: [ 1228.564704] microcode: CPU10: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.566882] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.566884] ACPI: \_PR_.C005: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.567187] CPU10 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.567204] smpboot: Booting Node 0 Processor 11 APIC 0x7
Oct 10 20:42:47 debian30 kernel: [ 1228.567320] microcode: CPU11: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.569503] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.569505] ACPI: \_PR_.C007: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.569836] CPU11 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.569851] smpboot: Booting Node 0 Processor 12 APIC 0x9
Oct 10 20:42:47 debian30 kernel: [ 1228.570010] microcode: CPU12: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.572220] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.572223] ACPI: \_PR_.C009: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.572583] CPU12 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.572603] smpboot: Booting Node 0 Processor 13 APIC 0xb
Oct 10 20:42:47 debian30 kernel: [ 1228.572747] microcode: CPU13: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.574936] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.574938] ACPI: \_PR_.C00B: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.575289] CPU13 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.575309] smpboot: Booting Node 0 Processor 14 APIC 0xd
Oct 10 20:42:47 debian30 kernel: [ 1228.575468] microcode: CPU14: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.577658] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.577661] ACPI: \_PR_.C00D: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.578029] CPU14 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.578049] smpboot: Booting Node 0 Processor 15 APIC 0xf
Oct 10 20:42:47 debian30 kernel: [ 1228.578212] microcode: CPU15: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.580433] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.580435] ACPI: \_PR_.C00F: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.580821] CPU15 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.582418] ACPI: Waking up from system sleep state S3
Oct 10 20:42:47 debian30 kernel: [ 1228.664512] usb usb1: root hub lost power or was reset
Oct 10 20:42:47 debian30 kernel: [ 1228.664515] usb usb2: root hub lost power or was reset
Oct 10 20:42:47 debian30 kernel: [ 1228.664796] sd 11:0:0:0: [sda] Starting disk
Oct 10 20:42:47 debian30 kernel: [ 1228.665298] serial 00:03: activated
Oct 10 20:42:47 debian30 kernel: [ 1228.978609] ata2: SATA link down (SStatus 0 SControl 300)
Oct 10 20:42:47 debian30 kernel: [ 1228.979322] ata5: SATA link down (SStatus 0 SControl 300)
Oct 10 20:42:47 debian30 kernel: [ 1228.979341] ata6: SATA link down (SStatus 0 SControl 300)
Oct 10 20:42:47 debian30 kernel: [ 1229.053715] OOM killer enabled.
Oct 10 20:42:47 debian30 kernel: [ 1229.053716] Restarting tasks ... done.
Oct 10 20:42:47 debian30 kernel: [ 1229.054796] PM: suspend exit
Oct 10 20:42:47 debian30 systemd-sleep[1958]: System resumed.
Oct 10 20:42:47 debian30 kernel: [ 1229.139438] ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 10 20:42:47 debian30 kernel: [ 1229.139533] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct 10 20:42:47 debian30 kernel: [ 1229.139797] ata12.00: supports DRM functions and may not be fully accessible
Oct 10 20:42:47 debian30 kernel: [ 1229.144314] ata12.00: supports DRM functions and may not be fully accessible
Oct 10 20:42:47 debian30 kernel: [ 1229.145689] ata1.00: configured for UDMA/100
Oct 10 20:42:47 debian30 systemd-sleep[2101]: /dev/sda:
Oct 10 20:42:47 debian30 systemd-sleep[2101]:  setting Advanced Power Management level to 0xfe (254)
Oct 10 20:42:47 debian30 systemd-sleep[2101]:  APM_level#011= 254
Oct 10 20:42:47 debian30 kernel: [ 1229.149174] ata12.00: configured for UDMA/133
Oct 10 20:42:47 debian30 kernel: [ 1229.149465] ata12.00: Enabling discard_zeroes_data
Oct 10 20:42:47 debian30 systemd[1]: systemd-suspend.service: Succeeded.
Oct 10 20:42:47 debian30 systemd[1]: Finished Suspend.
Oct 10 20:42:47 debian30 systemd[1]: Stopped target Sleep.
Oct 10 20:42:47 debian30 systemd[1]: Reached target Suspend.
Oct 10 20:42:47 debian30 systemd[1]: Stopped target Suspend.
Oct 10 20:42:50 debian30 kernel: [ 1231.804443] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
 



et voila le log de X (la fin au redemarrage) des bug aussi mais ça fonctionne


[  1229.353] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select"
[  1229.394] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[  1229.394] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[  1229.394] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[  1229.394] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[  1229.394] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[  1229.394] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[  1229.394] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[  1229.394] (II) NVIDIA(0):     Config Options in the README.
[  1229.422] (II) event5  - Power Button: is tagged by udev as: Keyboard
[  1229.422] (II) event5  - Power Button: device is a keyboard
[  1229.424] (II) event4  - Power Button: is tagged by udev as: Keyboard
[  1229.424] (II) event4  - Power Button: device is a keyboard
[  1229.425] (II) event0  - Microsoft  Microsoft Basic Optical Mouse v2.0 : is tagged by udev as: Mouse
[  1229.425] (II) event0  - Microsoft  Microsoft Basic Optical Mouse v2.0 : device is a pointer
[  1229.427] (II) event1  - SEM USB Keyboard: is tagged by udev as: Keyboard
[  1229.427] (II) event1  - SEM USB Keyboard: device is a keyboard
[  1229.428] (II) event2  - SEM USB Keyboard Consumer Control: is tagged by udev as: Keyboard
[  1229.428] (II) event2  - SEM USB Keyboard Consumer Control: device is a keyboard
[  1229.430] (II) event3  - SEM USB Keyboard System Control: is tagged by udev as: Keyboard
[  1229.430] (II) event3  - SEM USB Keyboard System Control: device is a keyboard
[  1229.431] (II) event7  - Eee PC WMI hotkeys: is tagged by udev as: Keyboard
[  1229.431] (II) event7  - Eee PC WMI hotkeys: device is a keyboard
[  1275.469] (EE) event1  - SEM USB Keyboard: client bug: event processing lagging behind by 33ms, your system is too slow
[  1430.932] (EE) event1  - SEM USB Keyboard: client bug: event processing lagging behind by 32ms, your system is too slow
[  1478.867] (EE) event1  - SEM USB Keyboard: client bug: event processing lagging behind by 39ms, your system is too slow
[  1484.348] (EE) event1  - SEM USB Keyboard: client bug: event processing lagging behind by 23ms, your system is too slow
 



donc la configuration de l' EFI (un bug acpi), le matériel , une application particulière qui est rester ouverte au passage en "veille profonde"
mais certainement pas le driver nvidia ou lightdm

avec un peu de chance tu peu trouver des traces dans le syslog et le log de X
ps: sur ceux je vais installer le daemon acpi  smile


journalctl -r -p err
-- Journal begins at Sun 2021-10-10 20:17:54 CEST, ends at Sun 2021-10-10 20:43:18 CEST. --
oct. 10 20:18:11 debian30 pulseaudio[812]: Error opening PCM device iec958:1: Aucun fichier ou dossier de ce type
oct. 10 20:18:10 debian30 lightdm[873]: gkr-pam: unable to locate daemon control file
 



08:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] (rev a1)
08:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1)
 

Dernière modification par robert2a (10-10-2021 21:08:41)

Hors ligne

#11 10-10-2021 22:12:10

Magean
Membre
Inscription : 01-02-2021

Re : [Résolu] Bullseye : écran noir à la sortie de veille

robert2a a écrit :

re, voila la partie debian bullseye gpu nvidia sur amd r7 1700 , beaucoup moins propre mais bon ça fonctionne


Oct 10 20:38:19 debian30 systemd[1]: Starting Suspend...
Oct 10 20:38:19 debian30 systemd-sleep[1958]: Suspending system...
Oct 10 20:38:19 debian30 kernel: [ 1227.716172] PM: suspend entry (deep)
Oct 10 20:38:19 debian30 kernel: [ 1227.718695] Filesystems sync: 0.002 seconds
Oct 10 20:42:47 debian30 kernel: [ 1228.024601] Freezing user space processes ... (elapsed 0.002 seconds) done.
Oct 10 20:42:47 debian30 kernel: [ 1228.026775] OOM killer disabled.
Oct 10 20:42:47 debian30 kernel: [ 1228.026777] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Oct 10 20:42:47 debian30 kernel: [ 1228.028035] printk: Suspending console(s) (use no_console_suspend to debug)
Oct 10 20:42:47 debian30 kernel: [ 1228.029309] serial 00:03: disabled
Oct 10 20:42:47 debian30 kernel: [ 1228.058680] sd 11:0:0:0: [sda] Synchronizing SCSI cache
Oct 10 20:42:47 debian30 kernel: [ 1228.058737] sd 11:0:0:0: [sda] Stopping disk
Oct 10 20:42:47 debian30 kernel: [ 1228.195083] ACPI: Preparing to enter system sleep state S3
Oct 10 20:42:47 debian30 kernel: [ 1228.503500] PM: Saving platform NVS memory
Oct 10 20:42:47 debian30 kernel: [ 1228.503551] Disabling non-boot CPUs ...
Oct 10 20:42:47 debian30 kernel: [ 1228.505333] smpboot: CPU 1 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.508116] smpboot: CPU 2 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.510639] smpboot: CPU 3 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.513197] smpboot: CPU 4 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.515772] smpboot: CPU 5 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.518466] smpboot: CPU 6 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.520999] smpboot: CPU 7 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.523566] smpboot: CPU 8 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.525532] smpboot: CPU 9 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.528007] smpboot: CPU 10 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.530375] smpboot: CPU 11 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.532749] smpboot: CPU 12 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.535148] smpboot: CPU 13 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.537330] smpboot: CPU 14 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.539463] smpboot: CPU 15 is now offline
Oct 10 20:42:47 debian30 kernel: [ 1228.540430] ACPI: Low-level resume complete
Oct 10 20:42:47 debian30 kernel: [ 1228.540473] PM: Restoring platform NVS memory
Oct 10 20:42:47 debian30 kernel: [ 1228.541024] Enabling non-boot CPUs ...
Oct 10 20:42:47 debian30 kernel: [ 1228.541062] x86: Booting SMP configuration:
Oct 10 20:42:47 debian30 kernel: [ 1228.541063] smpboot: Booting Node 0 Processor 1 APIC 0x2
Oct 10 20:42:47 debian30 kernel: [ 1228.541176] microcode: CPU1: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.543347] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.543350] ACPI: \_PR_.C002: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.543628] CPU1 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.543693] smpboot: Booting Node 0 Processor 2 APIC 0x4
Oct 10 20:42:47 debian30 kernel: [ 1228.543886] microcode: CPU2: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.546053] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.546055] ACPI: \_PR_.C004: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.546258] CPU2 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.546272] smpboot: Booting Node 0 Processor 3 APIC 0x6
Oct 10 20:42:47 debian30 kernel: [ 1228.546391] microcode: CPU3: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.548560] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.548562] ACPI: \_PR_.C006: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.548754] CPU3 is up
Oct 10 20:42:47 debian30 kernel:[  1229.353] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select"
[  1229.394] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[  1229.394] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[  1229.394] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[  1229.394] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[  1229.394] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[  1229.394] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[  1229.394] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[  1229.394] (II) NVIDIA(0):     Config Options in the README.
[  1229.422] (II) event5  - Power Button: is tagged by udev as: Keyboard
[  1229.422] (II) event5  - Power Button: device is a keyboard
[  1229.424] (II) event4  - Power Button: is tagged by udev as: Keyboard
[  1229.424] (II) event4  - Power Button: device is a keyboard
[  1229.425] (II) event0  - Microsoft  Microsoft Basic Optical Mouse v2.0 : is tagged by udev as: Mouse
[  1229.425] (II) event0  - Microsoft  Microsoft Basic Optical Mouse v2.0 : device is a pointer
[  1229.427] (II) event1  - SEM USB Keyboard: is tagged by udev as: Keyboard
[  1229.427] (II) event1  - SEM USB Keyboard: device is a keyboard
[  1229.428] (II) event2  - SEM USB Keyboard Consumer Control: is tagged by udev as: Keyboard
[  1229.428] (II) event2  - SEM USB Keyboard Consumer Control: device is a keyboard
[  1229.430] (II) event3  - SEM USB Keyboard System Control: is tagged by udev as: Keyboard
[  1229.430] (II) event3  - SEM USB Keyboard System Control: device is a keyboard
[  1229.431] (II) event7  - Eee PC WMI hotkeys: is tagged by udev as: Keyboard
[  1229.431] (II) event7  - Eee PC WMI hotkeys: device is a keyboard
[  1275.469] (EE) event1  - SEM USB Keyboard: client bug: event processing lagging behind by 33ms, your system is too slow
[  1430.932] (EE) event1  - SEM USB Keyboard: client bug: event processing lagging behind by 32ms, your system is too slow
[  1478.867] (EE) event1  - SEM USB Keyboard: client bug: event processing lagging behind by 39ms, your system is too slow
[  1484.348] (EE) event1  - SEM USB Keyboard: client bug: event processing lagging behind by 23ms, your system is too slow [ 1228.548768] smpboot: Booting Node 0 Processor 4 APIC 0x8
Oct 10 20:42:47 debian30 kernel: [ 1228.548928] microcode: CPU4: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.551118] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.551120] ACPI: \_PR_.C008: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.551359] CPU4 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.551381] smpboot: Booting Node 0 Processor 5 APIC 0xa
Oct 10 20:42:47 debian30 kernel: [ 1228.551545] microcode: CPU5: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.553716] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.553719] ACPI: \_PR_.C00A: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.553952] CPU5 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.553971] smpboot: Booting Node 0 Processor 6 APIC 0xc
Oct 10 20:42:47 debian30 kernel: [ 1228.554135] microcode: CPU6: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.556345] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.556347] ACPI: \_PR_.C00C: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.556589] CPU6 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.556609] smpboot: Booting Node 0 Processor 7 APIC 0xe
Oct 10 20:42:47 debian30 kernel: [ 1228.556774] microcode: CPU7: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.558953] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.558955] ACPI: \_PR_.C00E: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.559210] CPU7 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.559231] smpboot: Booting Node 0 Processor 8 APIC 0x1
Oct 10 20:42:47 debian30 kernel: [ 1228.559378] microcode: CPU8: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.561575] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.561577] ACPI: \_PR_.C001: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.561937] CPU8 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.561968] smpboot: Booting Node 0 Processor 9 APIC 0x3
Oct 10 20:42:47 debian30 kernel: [ 1228.562085] microcode: CPU9: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.564269] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.564271] ACPI: \_PR_.C003: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.564568] CPU9 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.564586] smpboot: Booting Node 0 Processor 10 APIC 0x5
Oct 10 20:42:47 debian30 kernel: [ 1228.564704] microcode: CPU10: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.566882] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.566884] ACPI: \_PR_.C005: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.567187] CPU10 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.567204] smpboot: Booting Node 0 Processor 11 APIC 0x7
Oct 10 20:42:47 debian30 kernel: [ 1228.567320] microcode: CPU11: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.569503] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.569505] ACPI: \_PR_.C007: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.569836] CPU11 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.569851] smpboot: Booting Node 0 Processor 12 APIC 0x9
Oct 10 20:42:47 debian30 kernel: [ 1228.570010] microcode: CPU12: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.572220] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.572223] ACPI: \_PR_.C009: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.572583] CPU12 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.572603] smpboot: Booting Node 0 Processor 13 APIC 0xb
Oct 10 20:42:47 debian30 kernel: [ 1228.572747] microcode: CPU13: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.574936] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.574938] ACPI: \_PR_.C00B: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.575289] CPU13 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.575309] smpboot: Booting Node 0 Processor 14 APIC 0xd
Oct 10 20:42:47 debian30 kernel: [ 1228.575468] microcode: CPU14: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.577658] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.577661] ACPI: \_PR_.C00D: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.578029] CPU14 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.578049] smpboot: Booting Node 0 Processor 15 APIC 0xf
Oct 10 20:42:47 debian30 kernel: [ 1228.578212] microcode: CPU15: patch_level=0x08001138
Oct 10 20:42:47 debian30 kernel: [ 1228.580433] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Oct 10 20:42:47 debian30 kernel: [ 1228.580435] ACPI: \_PR_.C00F: Found 2 idle states
Oct 10 20:42:47 debian30 kernel: [ 1228.580821] CPU15 is up
Oct 10 20:42:47 debian30 kernel: [ 1228.582418] ACPI: Waking up from system sleep state S3
Oct 10 20:42:47 debian30 kernel: [ 1228.664512] usb usb1: root hub lost power or was reset
Oct 10 20:42:47 debian30 kernel: [ 1228.664515] usb usb2: root hub lost power or was reset
Oct 10 20:42:47 debian30 kernel: [ 1228.664796] sd 11:0:0:0: [sda] Starting disk
Oct 10 20:42:47 debian30 kernel: [ 1228.665298] serial 00:03: activated
Oct 10 20:42:47 debian30 kernel: [ 1228.978609] ata2: SATA link down (SStatus 0 SControl 300)
Oct 10 20:42:47 debian30 kernel: [ 1228.979322] ata5: SATA link down (SStatus 0 SControl 300)
Oct 10 20:42:47 debian30 kernel: [ 1228.979341] ata6: SATA link down (SStatus 0 SControl 300)
Oct 10 20:42:47 debian30 kernel: [ 1229.053715] OOM killer enabled.
Oct 10 20:42:47 debian30 kernel: [ 1229.053716] Restarting tasks ... done.
Oct 10 20:42:47 debian30 kernel: [ 1229.054796] PM: suspend exit
Oct 10 20:42:47 debian30 systemd-sleep[1958]: System resumed.
Oct 10 20:42:47 debian30 kernel: [ 1229.139438] ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 10 20:42:47 debian30 kernel: [ 1229.139533] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct 10 20:42:47 debian30 kernel: [ 1229.139797] ata12.00: supports DRM functions and may not be fully accessible
Oct 10 20:42:47 debian30 kernel: [ 1229.144314] ata12.00: supports DRM functions and may not be fully accessible
Oct 10 20:42:47 debian30 kernel: [ 1229.145689] ata1.00: configured for UDMA/100
Oct 10 20:42:47 debian30 systemd-sleep[2101]: /dev/sda:
Oct 10 20:42:47 debian30 systemd-sleep[2101]:  setting Advanced Power Management level to 0xfe (254)
Oct 10 20:42:47 debian30 systemd-sleep[2101]:  APM_level#011= 254
Oct 10 20:42:47 debian30 kernel: [ 1229.149174] ata12.00: configured for UDMA/133
Oct 10 20:42:47 debian30 kernel: [ 1229.149465] ata12.00: Enabling discard_zeroes_data
Oct 10 20:42:47 debian30 systemd[1]: systemd-suspend.service: Succeeded.
Oct 10 20:42:47 debian30 systemd[1]: Finished Suspend.
Oct 10 20:42:47 debian30 systemd[1]: Stopped target Sleep.
Oct 10 20:42:47 debian30 systemd[1]: Reached target Suspend.
Oct 10 20:42:47 debian30 systemd[1]: Stopped target Suspend.
Oct 10 20:42:50 debian30 kernel: [ 1231.804443] igb 0000:03:00.0 enp3s0: igb: enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
 



et voila le log de X (la fin au redemarrage) des bug aussi mais ça fonctionne


[  1229.353] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select"
[  1229.394] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[  1229.394] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[  1229.394] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[  1229.394] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[  1229.394] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[  1229.394] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[  1229.394] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[  1229.394] (II) NVIDIA(0):     Config Options in the README.
[  1229.422] (II) event5  - Power Button: is tagged by udev as: Keyboard
[  1229.422] (II) event5  - Power Button: device is a keyboard
[  1229.424] (II) event4  - Power Button: is tagged by udev as: Keyboard
[  1229.424] (II) event4  - Power Button: device is a keyboard
[  1229.425] (II) event0  - Microsoft  Microsoft Basic Optical Mouse v2.0 : is tagged by udev as: Mouse
[  1229.425] (II) event0  - Microsoft  Microsoft Basic Optical Mouse v2.0 : device is a pointer
[  1229.427] (II) event1  - SEM USB Keyboard: is tagged by udev as: Keyboard
[  1229.427] (II) event1  - SEM USB Keyboard: device is a keyboard
[  1229.428] (II) event2  - SEM USB Keyboard Consumer Control: is tagged by udev as: Keyboard
[  1229.428] (II) event2  - SEM USB Keyboard Consumer Control: device is a keyboard
[  1229.430] (II) event3  - SEM USB Keyboard System Control: is tagged by udev as: Keyboard
[  1229.430] (II) event3  - SEM USB Keyboard System Control: device is a keyboard
[  1229.431] (II) event7  - Eee PC WMI hotkeys: is tagged by udev as: Keyboard
[  1229.431] (II) event7  - Eee PC WMI hotkeys: device is a keyboard
[  1275.469] (EE) event1  - SEM USB Keyboard: client bug: event processing lagging behind by 33ms, your system is too slow
[  1430.932] (EE) event1  - SEM USB Keyboard: client bug: event processing lagging behind by 32ms, your system is too slow
[  1478.867] (EE) event1  - SEM USB Keyboard: client bug: event processing lagging behind by 39ms, your system is too slow
[  1484.348] (EE) event1  - SEM USB Keyboard: client bug: event processing lagging behind by 23ms, your system is too slow
 



donc la configuration de l' EFI (un bug acpi), le matériel , une application particulière qui est rester ouverte au passage en "veille profonde"
mais certainement pas le driver nvidia ou lightdm

avec un peu de chance tu peu trouver des traces dans le syslog et le log de X
ps: sur ceux je vais installer le daemon acpi  smile


journalctl -r -p err
-- Journal begins at Sun 2021-10-10 20:17:54 CEST, ends at Sun 2021-10-10 20:43:18 CEST. --
oct. 10 20:18:11 debian30 pulseaudio[812]: Error opening PCM device iec958:1: Aucun fichier ou dossier de ce type
oct. 10 20:18:10 debian30 lightdm[873]: gkr-pam: unable to locate daemon control file
 



08:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] (rev a1)
08:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1)
 



Grand merci pour ton aide, j'ai installé acpi, acpid et acpi-support-base.
Le démon est bien actif :

acpid.service - ACPI event daemon
     Loaded: loaded (/lib/systemd/system/acpid.service; disabled; vendor preset: enabled)
     Active: active (running) since Sun 2021-10-10 22:06:02 CEST; 3min 47s ago
TriggeredBy: ● acpid.path
             ● acpid.socket
       Docs: man:acpid(8)
   Main PID: 541 (acpid)
      Tasks: 1 (limit: 19096)
     Memory: 288.0K
        CPU: 47ms
     CGroup: /system.slice/acpid.service
             └─541 /usr/sbin/acpid

oct. 10 22:06:02 martin-debian systemd[1]: Started ACPI event daemon.
oct. 10 22:06:02 martin-debian acpid[541]: starting up with netlink and the input layer
oct. 10 22:06:02 martin-debian acpid[541]: 1 rule loaded
oct. 10 22:06:02 martin-debian acpid[541]: waiting for events: event logging is off
oct. 10 22:06:03 martin-debian acpid[541]: client connected from 653[0:0]
oct. 10 22:06:03 martin-debian acpid[541]: 1 client rule loaded



Mais le problème persiste.

Merci aussi pour les retours sur NVidia, ta 1060 est bien sous la version 460.xxx du pilote propriétaire ?

Hors ligne

#12 11-10-2021 10:08:38

robert2a
Membre
Inscription : 15-11-2014

Re : [Résolu] Bullseye : écran noir à la sortie de veille

Bonjour
oui normalement même version que toi sur bullseye a jour , le driver des dépôt debian sur mate + lightdm


glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 3072 MB
    Total available memory: 3072 MB
    Currently available dedicated video memory: 2954 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1060 3GB/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 460.91.03
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 460.91.03
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 460.91.03
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
 



pas facile a trouver la cause quand ça plante
sinon tu a réussi a trouver des choses dans syslog et Xorg.0.log ?
ps: tu remarque que le driver libre est plus bavard que le driver propriétaire sur les logs du mode "suspend"

Hors ligne

#13 11-10-2021 11:21:32

robert2a
Membre
Inscription : 15-11-2014

Re : [Résolu] Bullseye : écran noir à la sortie de veille

re,
je cherche (suis pas un utilisateur de la veille prolongée) , il doit avoir un sujet sur le forum assez ancien
donc moi il semble que sur plusieurs machines je suis en "s3" => suspend to ram
il serait bon de vérifier comment tu est configurer ( dans ton bios EFI)
la nuance c'est que la machine reste alimenté (cpu0 et ram) en s3
sinon c'est le mode "to disk" ou la machine n'est plus alimenté (juste pour le réveil )
deux liens
=> https://wiki-ubuntu-com.translate.goog/ … pto=nui,sc
=> https://doc.ubuntu-fr.org/veille_et_hibernation

ps: désactiver l'erp dans le bios (mode économie d'énergie ) , l'option porte peut être un autre nom
et regarder les modes disponibles "s1 a s5) de mémoire

pour ta CM par exemple


ErP Determines whether to let the system consume least power in S5 (shutdown) state. (Default: Disabled)
Note: When this item is set to Enabled, the following functions will become unavailable: Resume by Alarm,
PME event wake up, power on by mouse, power on by keyboard, and wake on LAN.
 


il semble désactiver par défaut

Dernière modification par robert2a (11-10-2021 11:30:20)

Hors ligne

#14 11-10-2021 11:27:26

Magean
Membre
Inscription : 01-02-2021

Re : [Résolu] Bullseye : écran noir à la sortie de veille

robert2a a écrit :

re,
je cherche (suis pas un utilisateur de la veille prolongée) , il doit avoir un sujet sur le forum assez ancien
donc moi il semble que sur plusieurs machines je suis en "s3" => suspend to ram
il serait bon de vérifier comment tu est configurer ( dans ton bios EFI)
la nuance c'est que la machine reste alimenté (cpu0 et ram) en s3
sinon c'est le mode "to disk" ou la machine n'est plus alimenté (juste pour le réveil )
deux liens
=> https://wiki-ubuntu-com.translate.goog/ … pto=nui,sc
=> https://doc.ubuntu-fr.org/veille_et_hibernation

ps: désactiver l'erp dans le bios (mode économie d'énergie ) , l'option porte peut être un autre nom
et regarder les modes disponibles "s1 a s5) de mémoire



Merci pour tes recherches.

Je n'utilise pas non plus la veille prolongée, il s'agit de veille "normale".

Cela dit, quand j'étais sous Ubuntu 20.04, je n'avais pas ce problème. Entre-temps rien n'a changé dans le bios EFI...

J'éplucherai les logs tout à l'heure.

Hors ligne

#15 11-10-2021 11:34:18

robert2a
Membre
Inscription : 15-11-2014

Re : [Résolu] Bullseye : écran noir à la sortie de veille

donc tu est en s3 aussi ?
ps: j'ai une CM  Asus avec le même cpu que toi , pour l'instant juste avec l'igpu intel (pas de gpu nvidia)

je connais 2 veille , celle de l'écran et celle du PC (qui est désactivé par défaut)
la je parle de celle du PC smile

testé une machine Asus cpu 7700 et son igpu , ça fonctionne en suspend s3 bullseye+mate+lightdm
je poste rien identique au dessus avec driver libre amd , ici le driver du noyau pour intel
je monte une GTX1060 Zotac 6Go de mémoire et je te tien au courant
ps: sur cette machine le voyant d'alimentation clignote quand il passe en suspend

Dernière modification par robert2a (11-10-2021 13:13:39)

Hors ligne

#16 11-10-2021 13:42:11

robert2a
Membre
Inscription : 15-11-2014

Re : [Résolu] Bullseye : écran noir à la sortie de veille

voila la machine est configuré


lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05)
00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 05)
00:02.0 Display controller: Intel Corporation HD Graphics 630 (rev 04)
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller
00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1
00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA controller [AHCI mode]
00:1b.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #17 (rev f0)
00:1b.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #21 (rev f0)
00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #1 (rev f0)
00:1c.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #5 (rev f0)
00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #9 (rev f0)
00:1f.0 ISA bridge: Intel Corporation 200 Series PCH LPC Controller (Z270)
00:1f.2 Memory controller: Intel Corporation 200 Series/Z370 Chipset Family Power Management Controller
00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio
00:1f.4 SMBus: Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V
01:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1)
03:00.0 SATA controller: Kingston Technology Company, Inc. HyperX Predator PCIe AHCI SSD (rev 10)
05:00.0 USB controller: ASMedia Technology Inc. ASM2142 USB 3.1 Host Controller
 



glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 6144 MB
    Total available memory: 6144 MB
    Currently available dedicated video memory: 5959 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1060 6GB/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 460.91.03
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 460.91.03
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 460.91.03
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
 


mise en veille écran 5mn
mise en veille PC 30mn


Nom de modèle :                         Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
 

Hors ligne

#17 11-10-2021 14:32:16

robert2a
Membre
Inscription : 15-11-2014

Re : [Résolu] Bullseye : écran noir à la sortie de veille

re,
voila correct aussi , je te met juste la fin du syslog
je sais pas ce qui cloche chez toi


Oct 11 14:23:21 kabylake1 kernel: [ 2745.175901] Restarting tasks ... done.
Oct 11 14:23:21 kabylake1 kernel: [ 2745.176495] PM: suspend exit
Oct 11 14:23:21 kabylake1 kernel: [ 2745.176878] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
Oct 11 14:23:21 kabylake1 acpid: client 588[0:0] has disconnected
Oct 11 14:23:21 kabylake1 systemd-sleep[4485]: System resumed.
Oct 11 14:23:21 kabylake1 rtkit-daemon[668]: Supervising 3 threads of 2 processes of 1 users.
Oct 11 14:23:21 kabylake1 systemd[1]: systemd-suspend.service: Succeeded.
Oct 11 14:23:21 kabylake1 systemd[1]: Finished Suspend.
Oct 11 14:23:21 kabylake1 systemd[1]: Stopped target Sleep.
Oct 11 14:23:21 kabylake1 systemd[1]: Reached target Suspend.
Oct 11 14:23:21 kabylake1 systemd[1]: Stopped target Suspend.
Oct 11 14:23:21 kabylake1 rtkit-daemon[668]: Successfully made thread 4601 of process 740 owned by '1000' RT at priority 5.
Oct 11 14:23:21 kabylake1 rtkit-daemon[668]: Supervising 4 threads of 2 processes of 1 users.
Oct 11 14:23:21 kabylake1 rtkit-daemon[668]: Supervising 3 threads of 2 processes of 1 users.
Oct 11 14:23:21 kabylake1 rtkit-daemon[668]: Successfully made thread 4602 of process 740 owned by '1000' RT at priority 5.
Oct 11 14:23:21 kabylake1 rtkit-daemon[668]: Supervising 4 threads of 2 processes of 1 users.
Oct 11 14:23:21 kabylake1 acpid: client connected from 588[0:0]
Oct 11 14:23:21 kabylake1 acpid: 1 client rule loaded
Oct 11 14:23:21 kabylake1 rtkit-daemon[668]: Supervising 3 threads of 2 processes of 1 users.
Oct 11 14:23:21 kabylake1 rtkit-daemon[668]: Successfully made thread 4603 of process 740 owned by '1000' RT at priority 5.
Oct 11 14:23:21 kabylake1 rtkit-daemon[668]: Supervising 4 threads of 2 processes of 1 users.
Oct 11 14:23:26 kabylake1 kernel: [ 2750.206710] e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
 


toujours en mode "s3"


Oct 11 14:23:21 kabylake1 kernel: [ 2743.183073] ACPI: Preparing to enter system sleep state S3
 

Hors ligne

#18 12-10-2021 11:23:02

Magean
Membre
Inscription : 01-02-2021

Re : [Résolu] Bullseye : écran noir à la sortie de veille

Bonjour,

Voilà mon syslog après une mise en veille suivie d'un réveil sur écran noir. J'ai eu un peu de mal à l'attraper, le bug ne survenant pas systématiquement.

Oct 12 10:28:49 martin-debian systemd[1]: Starting Cleanup of Temporary Directories...
Oct 12 10:28:49 martin-debian systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Oct 12 10:28:49 martin-debian systemd[1]: Finished Cleanup of Temporary Directories.
Oct 12 10:29:09 martin-debian ModemManager[636]: <info>  [sleep-monitor] system is about to suspend
Oct 12 10:29:09 martin-debian NetworkManager[557]: <info>  [1634027349.3020] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Oct 12 10:29:09 martin-debian systemd[1]: Reached target Sleep.
Oct 12 10:29:09 martin-debian systemd[1]: Starting Suspend...
Oct 12 10:29:09 martin-debian systemd-sleep[2166]: Suspending system...
Oct 12 10:29:09 martin-debian kernel: [  951.394747] PM: suspend entry (deep)
Oct 12 10:29:09 martin-debian kernel: [  951.404050] Filesystems sync: 0.009 seconds
Oct 12 10:58:08 martin-debian kernel: [  951.754451] Freezing user space processes ... (elapsed 0.001 seconds) done.
Oct 12 10:58:08 martin-debian kernel: [  951.755973] OOM killer disabled.
Oct 12 10:58:08 martin-debian kernel: [  951.755973] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Oct 12 10:58:08 martin-debian kernel: [  951.757095] printk: Suspending console(s) (use no_console_suspend to debug)
Oct 12 10:58:08 martin-debian kernel: [  951.759127] e1000e: EEE TX LPI TIMER: 00000011
Oct 12 10:58:08 martin-debian kernel: [  951.778304] pcieport 0000:00:1c.2: Intel SPT PCH root port ACS workaround enabled
Oct 12 10:58:08 martin-debian kernel: [  951.778305] pcieport 0000:00:1c.4: Intel SPT PCH root port ACS workaround enabled
Oct 12 10:58:08 martin-debian kernel: [  951.778306] pcieport 0000:00:1b.4: Intel SPT PCH root port ACS workaround enabled
Oct 12 10:58:08 martin-debian kernel: [  951.792022] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Oct 12 10:58:08 martin-debian kernel: [  951.792023] sd 6:0:0:0: [sdb] Synchronizing SCSI cache
Oct 12 10:58:08 martin-debian kernel: [  951.792096] sd 0:0:0:0: [sda] Stopping disk
Oct 12 10:58:08 martin-debian kernel: [  951.792105] sd 6:0:0:0: [sdb] Stopping disk
Oct 12 10:58:08 martin-debian kernel: [  954.159673] ACPI: Preparing to enter system sleep state S3
Oct 12 10:58:08 martin-debian kernel: [  954.161689] PM: Saving platform NVS memory
Oct 12 10:58:08 martin-debian kernel: [  954.161792] Disabling non-boot CPUs ...
Oct 12 10:58:08 martin-debian kernel: [  954.163553] smpboot: CPU 1 is now offline
Oct 12 10:58:08 martin-debian kernel: [  954.168067] smpboot: CPU 2 is now offline
Oct 12 10:58:08 martin-debian kernel: [  954.169942] smpboot: CPU 3 is now offline
Oct 12 10:58:08 martin-debian kernel: [  954.171530] smpboot: CPU 4 is now offline
Oct 12 10:58:08 martin-debian kernel: [  954.173245] smpboot: CPU 5 is now offline
Oct 12 10:58:08 martin-debian kernel: [  954.174823] smpboot: CPU 6 is now offline
Oct 12 10:58:08 martin-debian kernel: [  954.176485] smpboot: CPU 7 is now offline
Oct 12 10:58:08 martin-debian kernel: [  954.178585] ACPI: Low-level resume complete
Oct 12 10:58:08 martin-debian kernel: [  954.178643] PM: Restoring platform NVS memory
Oct 12 10:58:08 martin-debian kernel: [  954.179303] Enabling non-boot CPUs ...
Oct 12 10:58:08 martin-debian kernel: [  954.179326] x86: Booting SMP configuration:
Oct 12 10:58:08 martin-debian kernel: [  954.179327] smpboot: Booting Node 0 Processor 1 APIC 0x2
Oct 12 10:58:08 martin-debian kernel: [  954.179760] CPU1 is up
Oct 12 10:58:08 martin-debian kernel: [  954.179774] smpboot: Booting Node 0 Processor 2 APIC 0x4
Oct 12 10:58:08 martin-debian kernel: [  954.180206] CPU2 is up
Oct 12 10:58:08 martin-debian kernel: [  954.180218] smpboot: Booting Node 0 Processor 3 APIC 0x6
Oct 12 10:58:08 martin-debian kernel: [  954.180405] smpboot: Scheduler frequency invariance went wobbly, disabling!
Oct 12 10:58:08 martin-debian kernel: [  954.180660] CPU3 is up
Oct 12 10:58:08 martin-debian kernel: [  954.180673] smpboot: Booting Node 0 Processor 4 APIC 0x1
Oct 12 10:58:08 martin-debian kernel: [  954.181221] CPU4 is up
Oct 12 10:58:08 martin-debian kernel: [  954.181236] smpboot: Booting Node 0 Processor 5 APIC 0x3
Oct 12 10:58:08 martin-debian kernel: [  954.181676] CPU5 is up
Oct 12 10:58:08 martin-debian kernel: [  954.181689] smpboot: Booting Node 0 Processor 6 APIC 0x5
Oct 12 10:58:08 martin-debian kernel: [  954.182145] CPU6 is up
Oct 12 10:58:08 martin-debian kernel: [  954.182158] smpboot: Booting Node 0 Processor 7 APIC 0x7
Oct 12 10:58:08 martin-debian kernel: [  954.182616] CPU7 is up
Oct 12 10:58:08 martin-debian kernel: [  954.184489] ACPI: Waking up from system sleep state S3
Oct 12 10:58:08 martin-debian kernel: [  954.204581] pcieport 0000:00:1c.4: Intel SPT PCH root port ACS workaround enabled
Oct 12 10:58:08 martin-debian kernel: [  954.204584] pcieport 0000:00:1b.2: Intel SPT PCH root port ACS workaround enabled
Oct 12 10:58:08 martin-debian kernel: [  954.204585] pcieport 0000:00:1b.4: Intel SPT PCH root port ACS workaround enabled
Oct 12 10:58:08 martin-debian kernel: [  954.208513] pcieport 0000:00:1d.0: Intel SPT PCH root port ACS workaround enabled
Oct 12 10:58:08 martin-debian kernel: [  954.208571] pcieport 0000:00:1c.2: Intel SPT PCH root port ACS workaround enabled
Oct 12 10:58:08 martin-debian kernel: [  955.310335] sd 0:0:0:0: [sda] Starting disk
Oct 12 10:58:08 martin-debian kernel: [  955.320311] sd 6:0:0:0: [sdb] Starting disk
Oct 12 10:58:08 martin-debian kernel: [  955.639120] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 12 10:58:08 martin-debian kernel: [  955.640634] ata7.00: configured for UDMA/133
Oct 12 10:58:08 martin-debian kernel: [  955.682560] ata3: SATA link down (SStatus 4 SControl 300)
Oct 12 10:58:08 martin-debian kernel: [  955.682584] ata6: SATA link down (SStatus 4 SControl 300)
Oct 12 10:58:08 martin-debian kernel: [  955.683030] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct 12 10:58:08 martin-debian kernel: [  955.683181] ata4: SATA link down (SStatus 4 SControl 300)
Oct 12 10:58:08 martin-debian kernel: [  955.683197] ata2: SATA link down (SStatus 4 SControl 300)
Oct 12 10:58:08 martin-debian kernel: [  955.688921] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT4._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Oct 12 10:58:08 martin-debian kernel: [  955.688924] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Oct 12 10:58:08 martin-debian kernel: [  955.699846] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT4._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Oct 12 10:58:08 martin-debian kernel: [  955.699849] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Oct 12 10:58:08 martin-debian kernel: [  955.699853] ata5.00: configured for UDMA/133
Oct 12 10:58:08 martin-debian kernel: [  959.083014] e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Oct 12 10:58:08 martin-debian kernel: [  960.720477] ata1: link is slow to respond, please be patient (ready=0)
Oct 12 10:58:08 martin-debian kernel: [  963.593687] acpi LNXPOWER:16: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.593729] acpi LNXPOWER:15: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.593770] acpi LNXPOWER:14: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.593810] acpi LNXPOWER:13: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.593850] acpi LNXPOWER:12: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.593889] acpi LNXPOWER:11: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.593927] acpi LNXPOWER:10: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.593965] acpi LNXPOWER:0f: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.594004] acpi LNXPOWER:0e: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.594042] acpi LNXPOWER:0d: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.594079] acpi LNXPOWER:0c: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.594118] acpi LNXPOWER:0b: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.594157] acpi LNXPOWER:0a: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.594196] acpi LNXPOWER:09: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.594235] acpi LNXPOWER:08: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.594273] acpi LNXPOWER:07: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.594311] acpi LNXPOWER:06: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.594349] acpi LNXPOWER:05: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.594387] acpi LNXPOWER:04: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.594426] acpi LNXPOWER:03: Turning OFF
Oct 12 10:58:08 martin-debian kernel: [  963.594456] OOM killer enabled.
Oct 12 10:58:08 martin-debian kernel: [  963.594457] Restarting tasks ... done.
Oct 12 10:58:08 martin-debian kernel: [  963.595989] PM: suspend exit
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: The canary thread is apparently starving. Taking action.
Oct 12 10:58:09 martin-debian systemd-sleep[2166]: System resumed.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Demoting known real-time threads.
Oct 12 10:58:09 martin-debian systemd[1]: systemd-suspend.service: Succeeded.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Successfully demoted thread 1921 of process 1366.
Oct 12 10:58:09 martin-debian systemd[1]: Finished Suspend.
Oct 12 10:58:09 martin-debian acpid: client 658[0:0] has disconnected
Oct 12 10:58:09 martin-debian systemd[1]: Stopped target Sleep.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Successfully demoted thread 1297 of process 858.
Oct 12 10:58:09 martin-debian systemd[1]: Reached target Suspend.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Successfully demoted thread 753 of process 751.
Oct 12 10:58:09 martin-debian systemd[1]: Stopped target Suspend.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Successfully demoted thread 751 of process 751.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Successfully demoted thread 1189 of process 728.
Oct 12 10:58:09 martin-debian NetworkManager[557]: <info>  [1634029089.0095] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Successfully demoted thread 728 of process 728.
Oct 12 10:58:09 martin-debian NetworkManager[557]: <info>  [1634029089.0095] device (enp0s31f6): state change: activated -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Successfully demoted thread 730 of process 727.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Successfully demoted thread 727 of process 727.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Demoted 8 threads.
Oct 12 10:58:09 martin-debian ModemManager[636]: <info>  [sleep-monitor] system is resuming
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 10:58:09 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:09 martin-debian NetworkManager[557]: <info>  [1634029089.0465] dhcp4 (enp0s31f6): canceled DHCP transaction
Oct 12 10:58:09 martin-debian NetworkManager[557]: <info>  [1634029089.0465] dhcp4 (enp0s31f6): state changed bound -> done
Oct 12 10:58:09 martin-debian avahi-daemon[553]: Withdrawing address record for 192.168.1.68 on enp0s31f6.
Oct 12 10:58:09 martin-debian avahi-daemon[553]: Withdrawing address record for 192.168.1.98 on enp0s31f6.
Oct 12 10:58:09 martin-debian avahi-daemon[553]: Leaving mDNS multicast group on interface enp0s31f6.IPv4 with address 192.168.1.98.
Oct 12 10:58:09 martin-debian avahi-daemon[553]: Interface enp0s31f6.IPv4 no longer relevant for mDNS.
Oct 12 10:58:09 martin-debian avahi-daemon[553]: Withdrawing address record for fe80::8424:3070:d283:3516 on enp0s31f6.
Oct 12 10:58:09 martin-debian avahi-daemon[553]: Leaving mDNS multicast group on interface enp0s31f6.IPv6 with address fe80::8424:3070:d283:3516.
Oct 12 10:58:09 martin-debian avahi-daemon[553]: Interface enp0s31f6.IPv6 no longer relevant for mDNS.
Oct 12 10:58:09 martin-debian dhclient[592]: receive_packet failed on enp0s31f6: Network is down
Oct 12 10:58:09 martin-debian kernel: [  963.724090] e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down
Oct 12 10:58:09 martin-debian NetworkManager[557]: <info>  [1634029089.1311] device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 12 10:58:09 martin-debian dbus-daemon[556]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=557 comm="/usr/sbin/NetworkManager --no-daemon ")
Oct 12 10:58:09 martin-debian systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 12 10:58:09 martin-debian dbus-daemon[556]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 12 10:58:09 martin-debian systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 12 10:58:09 martin-debian acpid: client connected from 658[0:0]
Oct 12 10:58:09 martin-debian acpid: 1 client rule loaded
Oct 12 10:58:09 martin-debian kernel: [  964.096476] ------------[ cut here ]------------
Oct 12 10:58:09 martin-debian kernel: [  964.096484] WARNING: CPU: 3 PID: 2268 at /var/lib/dkms/nvidia-current/460.91.03/build/nvidia-drm/nvidia-drm-drv.c:530 nv_drm_master_set+0x22/0x30 [nvidia_drm]
Oct 12 10:58:09 martin-debian kernel: [  964.096485] Modules linked in: rfkill intel_rapl_msr intel_rapl_common nvidia_drm(POE) x86_pkg_temp_thermal intel_powerclamp coretemp drm_kms_helper kvm_intel snd_hda_codec_realtek snd_hda_codec_generic cec snd_hda_codec_hdmi ledtrig_audio nls_ascii kvm nls_cp437 snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation vfat irqbypass snd_soc_core nvidia_modeset(POE) fat ghash_clmulni_intel mei_hdcp snd_compress soundwire_cadence aesni_intel libaes snd_hda_codec crypto_simd cryptd glue_helper rapl snd_hda_core intel_cstate snd_hwdep intel_uncore soundwire_bus efi_pstore snd_pcm joydev intel_wmi_thunderbolt pcspkr iTCO_wdt intel_pmc_bxt iTCO_vendor_support watchdog ee1004 snd_timer snd mei_me soundcore mei sg intel_pmc_core acpi_pad evdev nvidia(POE) parport_pc ppdev drm lp parport fuse configfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic hid_generic usbhid hid sr_mod sd_mod cdrom t10_pi crc_t10dif crct10dif_generic xhci_pci ahci e1000e
Oct 12 10:58:09 martin-debian kernel: [  964.096526]  libahci xhci_hcd libata mxm_wmi ptp pps_core usbcore scsi_mod crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel i2c_i801 i2c_smbus usb_common fan wmi video button
Oct 12 10:58:09 martin-debian kernel: [  964.096535] CPU: 3 PID: 2268 Comm: Xorg.wrap Tainted: P           OE     5.10.0-9-amd64 #1 Debian 5.10.70-1
Oct 12 10:58:09 martin-debian kernel: [  964.096535] Hardware name: Gigabyte Technology Co., Ltd. Z270X-Ultra Gaming/Z270X-Ultra Gaming-CF, BIOS F9d 03/09/2018
Oct 12 10:58:09 martin-debian kernel: [  964.096538] RIP: 0010:nv_drm_master_set+0x22/0x30 [nvidia_drm]
Oct 12 10:58:09 martin-debian kernel: [  964.096539] Code: b4 59 a0 d9 0f 1f 40 00 0f 1f 44 00 00 48 8b 47 48 48 8b 78 20 48 8b 05 0c 5d 00 00 48 8b 40 28 e8 43 19 d5 d9 84 c0 74 01 c3 <0f> 0b c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 80 3d 4c
Oct 12 10:58:09 martin-debian kernel: [  964.096539] RSP: 0018:ffffae2243b13bc8 EFLAGS: 00010246
Oct 12 10:58:09 martin-debian kernel: [  964.096540] RAX: 0000000000000000 RBX: ffff91ee40b76200 RCX: 0000000000000008
Oct 12 10:58:09 martin-debian kernel: [  964.096541] RDX: ffffffffc2f52e98 RSI: 0000000000000286 RDI: ffffffffc2f52e60
Oct 12 10:58:09 martin-debian kernel: [  964.096541] RBP: ffff91ee40cc8000 R08: 0000000000000008 R09: ffffae2243b13bb0
Oct 12 10:58:09 martin-debian kernel: [  964.096542] R10: 0000000000000000 R11: 0000000000000000 R12: ffff91ee783e6300
Oct 12 10:58:09 martin-debian kernel: [  964.096542] R13: 0000000000000000 R14: ffff91ee40b76210 R15: 0000000046a3ef28
Oct 12 10:58:09 martin-debian kernel: [  964.096543] FS:  00007fefafca5740(0000) GS:ffff91f16ecc0000(0000) knlGS:0000000000000000
Oct 12 10:58:09 martin-debian kernel: [  964.096543] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 12 10:58:09 martin-debian kernel: [  964.096544] CR2: 00007fefafcf8e40 CR3: 00000001a7cba005 CR4: 00000000003706e0
Oct 12 10:58:09 martin-debian kernel: [  964.096544] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct 12 10:58:09 martin-debian kernel: [  964.096545] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Oct 12 10:58:09 martin-debian kernel: [  964.096545] Call Trace:
Oct 12 10:58:09 martin-debian kernel: [  964.096557]  drm_new_set_master+0x95/0x110 [drm]
Oct 12 10:58:09 martin-debian kernel: [  964.096568]  drm_master_open+0x85/0xb0 [drm]
Oct 12 10:58:09 martin-debian kernel: [  964.096575]  drm_open+0xf8/0x250 [drm]
Oct 12 10:58:09 martin-debian kernel: [  964.096585]  drm_stub_open+0xab/0x130 [drm]
Oct 12 10:58:09 martin-debian kernel: [  964.096589]  chrdev_open+0xed/0x230
Oct 12 10:58:09 martin-debian kernel: [  964.096590]  ? cdev_device_add+0x90/0x90
Oct 12 10:58:09 martin-debian kernel: [  964.096592]  do_dentry_open+0x14b/0x360
Oct 12 10:58:09 martin-debian kernel: [  964.096593]  path_openat+0xb82/0x1080
Oct 12 10:58:09 martin-debian kernel: [  964.096596]  ? alloc_set_pte+0xec/0x620
Oct 12 10:58:09 martin-debian kernel: [  964.096597]  ? filemap_map_pages+0x223/0x410
Oct 12 10:58:09 martin-debian kernel: [  964.096599]  do_filp_open+0x88/0x130
Oct 12 10:58:09 martin-debian kernel: [  964.096600]  ? getname_flags.part.0+0x29/0x1a0
Oct 12 10:58:09 martin-debian kernel: [  964.096601]  ? __check_object_size+0x136/0x150
Oct 12 10:58:09 martin-debian kernel: [  964.096603]  do_sys_openat2+0x97/0x150
Oct 12 10:58:09 martin-debian kernel: [  964.096605]  __x64_sys_openat+0x54/0x90
Oct 12 10:58:09 martin-debian kernel: [  964.096607]  do_syscall_64+0x33/0x80
Oct 12 10:58:09 martin-debian kernel: [  964.096608]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Oct 12 10:58:09 martin-debian kernel: [  964.096609] RIP: 0033:0x7fefafe80767
Oct 12 10:58:09 martin-debian kernel: [  964.096611] Code: 25 00 00 41 00 3d 00 00 41 00 74 47 64 8b 04 25 18 00 00 00 85 c0 75 6b 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 95 00 00 00 48 8b 4c 24 28 64 48 2b 0c 25
Oct 12 10:58:09 martin-debian kernel: [  964.096611] RSP: 002b:00007ffd106ccbe0 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
Oct 12 10:58:09 martin-debian kernel: [  964.096612] RAX: ffffffffffffffda RBX: 00007ffd106ccd60 RCX: 00007fefafe80767
Oct 12 10:58:09 martin-debian kernel: [  964.096613] RDX: 0000000000000002 RSI: 00007ffd106ccd60 RDI: 00000000ffffff9c
Oct 12 10:58:09 martin-debian kernel: [  964.096614] RBP: 00007ffd106ccd60 R08: 0000000000000000 R09: 00007ffd106ccaf0
Oct 12 10:58:09 martin-debian kernel: [  964.096614] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002
Oct 12 10:58:09 martin-debian kernel: [  964.096615] R13: 0000000000000000 R14: 0000000000000000 R15: 00007ffd106ccc80
Oct 12 10:58:09 martin-debian kernel: [  964.096616] ---[ end trace 8b1dc7b4e92980c9 ]---
Oct 12 10:58:09 martin-debian kernel: [  964.101115] ------------[ cut here ]------------
Oct 12 10:58:09 martin-debian kernel: [  964.101121] WARNING: CPU: 3 PID: 2268 at /var/lib/dkms/nvidia-current/460.91.03/build/nvidia-drm/nvidia-drm-drv.c:530 nv_drm_master_set+0x22/0x30 [nvidia_drm]
Oct 12 10:58:09 martin-debian kernel: [  964.101121] Modules linked in: rfkill intel_rapl_msr intel_rapl_common nvidia_drm(POE) x86_pkg_temp_thermal intel_powerclamp coretemp drm_kms_helper kvm_intel snd_hda_codec_realtek snd_hda_codec_generic cec snd_hda_codec_hdmi ledtrig_audio nls_ascii kvm nls_cp437 snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation vfat irqbypass snd_soc_core nvidia_modeset(POE) fat ghash_clmulni_intel mei_hdcp snd_compress soundwire_cadence aesni_intel libaes snd_hda_codec crypto_simd cryptd glue_helper rapl snd_hda_core intel_cstate snd_hwdep intel_uncore soundwire_bus efi_pstore snd_pcm joydev intel_wmi_thunderbolt pcspkr iTCO_wdt intel_pmc_bxt iTCO_vendor_support watchdog ee1004 snd_timer snd mei_me soundcore mei sg intel_pmc_core acpi_pad evdev nvidia(POE) parport_pc ppdev drm lp parport fuse configfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic hid_generic usbhid hid sr_mod sd_mod cdrom t10_pi crc_t10dif crct10dif_generic xhci_pci ahci e1000e
Oct 12 10:58:09 martin-debian kernel: [  964.101156]  libahci xhci_hcd libata mxm_wmi ptp pps_core usbcore scsi_mod crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel i2c_i801 i2c_smbus usb_common fan wmi video button
Oct 12 10:58:09 martin-debian kernel: [  964.101166] CPU: 3 PID: 2268 Comm: Xorg Tainted: P        W  OE     5.10.0-9-amd64 #1 Debian 5.10.70-1
Oct 12 10:58:09 martin-debian kernel: [  964.101168] Hardware name: Gigabyte Technology Co., Ltd. Z270X-Ultra Gaming/Z270X-Ultra Gaming-CF, BIOS F9d 03/09/2018
Oct 12 10:58:09 martin-debian kernel: [  964.101169] RIP: 0010:nv_drm_master_set+0x22/0x30 [nvidia_drm]
Oct 12 10:58:09 martin-debian kernel: [  964.101171] Code: b4 59 a0 d9 0f 1f 40 00 0f 1f 44 00 00 48 8b 47 48 48 8b 78 20 48 8b 05 0c 5d 00 00 48 8b 40 28 e8 43 19 d5 d9 84 c0 74 01 c3 <0f> 0b c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 80 3d 4c
Oct 12 10:58:09 martin-debian kernel: [  964.101172] RSP: 0018:ffffae2243b13bc8 EFLAGS: 00010246
Oct 12 10:58:09 martin-debian kernel: [  964.101173] RAX: 0000000000000000 RBX: ffff91ee40b74000 RCX: 0000000000000008
Oct 12 10:58:09 martin-debian kernel: [  964.101173] RDX: ffffffffc2f52e98 RSI: 0000000000000286 RDI: ffffffffc2f52e60
Oct 12 10:58:09 martin-debian kernel: [  964.101174] RBP: ffff91ee40cc8000 R08: 0000000000000008 R09: ffffae2243b13bb0
Oct 12 10:58:09 martin-debian kernel: [  964.101175] R10: 0000000000000000 R11: 0000000000000000 R12: ffff91ee783e69c0
Oct 12 10:58:09 martin-debian kernel: [  964.101175] R13: 0000000000000000 R14: ffff91ee40b74010 R15: 0000000046a3ef28
Oct 12 10:58:09 martin-debian kernel: [  964.101177] FS:  00007fe1be738a40(0000) GS:ffff91f16ecc0000(0000) knlGS:0000000000000000
Oct 12 10:58:09 martin-debian kernel: [  964.101177] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 12 10:58:09 martin-debian kernel: [  964.101178] CR2: 00005636e0a920f8 CR3: 00000001a7c56006 CR4: 00000000003706e0
Oct 12 10:58:09 martin-debian kernel: [  964.101178] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct 12 10:58:09 martin-debian kernel: [  964.101179] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Oct 12 10:58:09 martin-debian kernel: [  964.101179] Call Trace:
Oct 12 10:58:09 martin-debian kernel: [  964.101192]  drm_new_set_master+0x95/0x110 [drm]
Oct 12 10:58:09 martin-debian kernel: [  964.101200]  drm_master_open+0x85/0xb0 [drm]
Oct 12 10:58:09 martin-debian kernel: [  964.101208]  drm_open+0xf8/0x250 [drm]
Oct 12 10:58:09 martin-debian kernel: [  964.101217]  drm_stub_open+0xab/0x130 [drm]
Oct 12 10:58:09 martin-debian kernel: [  964.101220]  chrdev_open+0xed/0x230
Oct 12 10:58:09 martin-debian kernel: [  964.101221]  ? cdev_device_add+0x90/0x90
Oct 12 10:58:09 martin-debian kernel: [  964.101222]  do_dentry_open+0x14b/0x360
Oct 12 10:58:09 martin-debian kernel: [  964.101224]  path_openat+0xb82/0x1080
Oct 12 10:58:09 martin-debian kernel: [  964.101226]  ? balance_dirty_pages_ratelimited+0x1a0/0x3c0
Oct 12 10:58:09 martin-debian kernel: [  964.101228]  do_filp_open+0x88/0x130
Oct 12 10:58:09 martin-debian kernel: [  964.101229]  ? getname_flags.part.0+0x29/0x1a0
Oct 12 10:58:09 martin-debian kernel: [  964.101230]  ? __check_object_size+0x136/0x150
Oct 12 10:58:09 martin-debian kernel: [  964.101231]  do_sys_openat2+0x97/0x150
Oct 12 10:58:09 martin-debian kernel: [  964.101233]  __x64_sys_openat+0x54/0x90
Oct 12 10:58:09 martin-debian kernel: [  964.101235]  do_syscall_64+0x33/0x80
Oct 12 10:58:09 martin-debian kernel: [  964.101236]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Oct 12 10:58:09 martin-debian kernel: [  964.101238] RIP: 0033:0x7fe1bec89767
Oct 12 10:58:09 martin-debian kernel: [  964.101239] Code: 25 00 00 41 00 3d 00 00 41 00 74 47 64 8b 04 25 18 00 00 00 85 c0 75 6b 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 95 00 00 00 48 8b 4c 24 28 64 48 2b 0c 25
Oct 12 10:58:09 martin-debian kernel: [  964.101240] RSP: 002b:00007ffd55e08bb0 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
Oct 12 10:58:09 martin-debian kernel: [  964.101241] RAX: ffffffffffffffda RBX: 00000000ffffffff RCX: 00007fe1bec89767
Oct 12 10:58:09 martin-debian kernel: [  964.101241] RDX: 0000000000080002 RSI: 00005636e0a903e0 RDI: 00000000ffffff9c
Oct 12 10:58:09 martin-debian kernel: [  964.101242] RBP: 00005636e0a903e0 R08: 0000000000000031 R09: 0000000000000000
Oct 12 10:58:09 martin-debian kernel: [  964.101242] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000080002
Oct 12 10:58:09 martin-debian kernel: [  964.101242] R13: 00005636e0a903e0 R14: 00005636e0a903e0 R15: 00005636e0a82260
Oct 12 10:58:09 martin-debian kernel: [  964.101244] ---[ end trace 8b1dc7b4e92980ca ]---
Oct 12 10:58:10 martin-debian kernel: [  965.116533] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 12 10:58:10 martin-debian kernel: [  965.117609] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Oct 12 10:58:10 martin-debian kernel: [  965.117612] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Oct 12 10:58:10 martin-debian kernel: [  965.118961] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Oct 12 10:58:10 martin-debian kernel: [  965.118964] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Oct 12 10:58:10 martin-debian kernel: [  965.119190] ata1.00: configured for UDMA/133
Oct 12 10:58:11 martin-debian acpid: client 658[0:0] has disconnected
Oct 12 10:58:11 martin-debian acpid: client connected from 2268[0:0]
Oct 12 10:58:11 martin-debian acpid: 1 client rule loaded
Oct 12 10:58:11 martin-debian ModemManager[636]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1f.6': not supported by any plugin
Oct 12 10:58:11 martin-debian lightdm[2279]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Oct 12 10:58:11 martin-debian systemd[1]: Created slice User Slice of UID 111.
Oct 12 10:58:11 martin-debian systemd[1]: Starting User Runtime Directory /run/user/111...
Oct 12 10:58:11 martin-debian systemd[1]: Finished User Runtime Directory /run/user/111.
Oct 12 10:58:11 martin-debian systemd[1]: Starting User Manager for UID 111...
Oct 12 10:58:11 martin-debian systemd[2289]: gpgconf: erreur d'exécution de « /usr/lib/gnupg/scdaemon » : il n'est sans doute pas installé
Oct 12 10:58:12 martin-debian systemd[2283]: Queued start job for default target Main User Target.
Oct 12 10:58:12 martin-debian systemd[2283]: Created slice User Application Slice.
Oct 12 10:58:12 martin-debian systemd[2283]: Reached target Paths.
Oct 12 10:58:12 martin-debian systemd[2283]: Reached target Timers.
Oct 12 10:58:12 martin-debian systemd[2283]: Starting D-Bus User Message Bus Socket.
Oct 12 10:58:12 martin-debian systemd[2283]: Listening on GnuPG network certificate management daemon.
Oct 12 10:58:12 martin-debian systemd[2283]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Oct 12 10:58:12 martin-debian systemd[2283]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Oct 12 10:58:12 martin-debian systemd[2283]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Oct 12 10:58:12 martin-debian systemd[2283]: Listening on GnuPG cryptographic agent and passphrase cache.
Oct 12 10:58:12 martin-debian systemd[2283]: Listening on Multimedia System.
Oct 12 10:58:12 martin-debian systemd[2283]: Listening on debconf communication socket.
Oct 12 10:58:12 martin-debian systemd[2283]: Listening on Sound System.
Oct 12 10:58:12 martin-debian systemd[2283]: Listening on D-Bus User Message Bus Socket.
Oct 12 10:58:12 martin-debian systemd[2283]: Reached target Sockets.
Oct 12 10:58:12 martin-debian systemd[2283]: Reached target Basic System.
Oct 12 10:58:12 martin-debian systemd[1]: Started User Manager for UID 111.
Oct 12 10:58:12 martin-debian systemd[2283]: Started Multimedia Service.
Oct 12 10:58:12 martin-debian systemd[1]: Started Session c1 of user lightdm.
Oct 12 10:58:12 martin-debian systemd[2283]: Starting Sound Service...
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 10:58:12 martin-debian pipewire[2304]: could not set nice-level to -11: Permission denied
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian pipewire[2304]: could not make thread realtime: Permission denied
Oct 12 10:58:12 martin-debian systemd[2283]: Started D-Bus User Message Bus.
Oct 12 10:58:12 martin-debian pipewire[2304]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian pipewire-media-session[2308]: could not set nice-level to -11: Permission denied
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian pipewire-media-session[2308]: could not make thread realtime: Permission denied
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian dbus-daemon[2307]: [session uid=111 pid=2307] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.4' (uid=111 pid=2309 comm="/usr/sbin/lightdm-gtk-greeter ")
Oct 12 10:58:12 martin-debian systemd[2283]: Starting Accessibility services bus...
Oct 12 10:58:12 martin-debian dbus-daemon[2307]: [session uid=111 pid=2307] Successfully activated service 'org.a11y.Bus'
Oct 12 10:58:12 martin-debian systemd[2283]: Started Accessibility services bus.
Oct 12 10:58:12 martin-debian dbus-daemon[2307]: [session uid=111 pid=2307] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.6' (uid=111 pid=2309 comm="/usr/sbin/lightdm-gtk-greeter ")
Oct 12 10:58:12 martin-debian systemd[2283]: Starting Virtual filesystem service...
Oct 12 10:58:12 martin-debian dbus-daemon[2307]: [session uid=111 pid=2307] Successfully activated service 'org.gtk.vfs.Daemon'
Oct 12 10:58:12 martin-debian systemd[2283]: Started Virtual filesystem service.
Oct 12 10:58:12 martin-debian at-spi-bus-launcher[2318]: dbus-daemon[2318]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=111 pid=2309 comm="/usr/sbin/lightdm-gtk-greeter ")
Oct 12 10:58:12 martin-debian at-spi-bus-launcher[2318]: dbus-daemon[2318]: Successfully activated service 'org.a11y.atspi.Registry'
Oct 12 10:58:12 martin-debian at-spi-bus-launcher[2343]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Oct 12 10:58:12 martin-debian kernel: [  967.435013] e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Oct 12 10:58:12 martin-debian kernel: [  967.435097] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link becomes ready
Oct 12 10:58:12 martin-debian NetworkManager[557]: <info>  [1634029092.8416] device (enp0s31f6): carrier: link connected
Oct 12 10:58:12 martin-debian NetworkManager[557]: <info>  [1634029092.8422] device (enp0s31f6): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 12 10:58:12 martin-debian NetworkManager[557]: <info>  [1634029092.8441] policy: auto-activating connection 'Ifupdown (enp0s31f6)' (1f655066-2072-fa99-0d37-faaf50873c3e)
Oct 12 10:58:12 martin-debian NetworkManager[557]: <info>  [1634029092.8457] device (enp0s31f6): Activation: starting connection 'Ifupdown (enp0s31f6)' (1f655066-2072-fa99-0d37-faaf50873c3e)
Oct 12 10:58:12 martin-debian NetworkManager[557]: <info>  [1634029092.8461] device (enp0s31f6): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 12 10:58:12 martin-debian NetworkManager[557]: <info>  [1634029092.8474] device (enp0s31f6): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 12 10:58:12 martin-debian NetworkManager[557]: <info>  [1634029092.8484] device (enp0s31f6): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 12 10:58:12 martin-debian NetworkManager[557]: <info>  [1634029092.8492] dhcp4 (enp0s31f6): activation: beginning transaction (timeout in 45 seconds)
Oct 12 10:58:12 martin-debian avahi-daemon[553]: Joining mDNS multicast group on interface enp0s31f6.IPv6 with address fe80::8424:3070:d283:3516.
Oct 12 10:58:12 martin-debian avahi-daemon[553]: New relevant interface enp0s31f6.IPv6 for mDNS.
Oct 12 10:58:12 martin-debian avahi-daemon[553]: Registering new address record for fe80::8424:3070:d283:3516 on enp0s31f6.*.
Oct 12 10:58:12 martin-debian NetworkManager[557]: <info>  [1634029092.8747] dhcp4 (enp0s31f6): state changed unknown -> bound, address=192.168.1.98
Oct 12 10:58:12 martin-debian avahi-daemon[553]: Joining mDNS multicast group on interface enp0s31f6.IPv4 with address 192.168.1.98.
Oct 12 10:58:12 martin-debian avahi-daemon[553]: New relevant interface enp0s31f6.IPv4 for mDNS.
Oct 12 10:58:12 martin-debian avahi-daemon[553]: Registering new address record for 192.168.1.98 on enp0s31f6.IPv4.
Oct 12 10:58:12 martin-debian NetworkManager[557]: <info>  [1634029092.8779] device (enp0s31f6): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oct 12 10:58:12 martin-debian NetworkManager[557]: <info>  [1634029092.8819] device (enp0s31f6): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oct 12 10:58:12 martin-debian NetworkManager[557]: <info>  [1634029092.8826] device (enp0s31f6): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oct 12 10:58:12 martin-debian NetworkManager[557]: <info>  [1634029092.8868] policy: set 'Ifupdown (enp0s31f6)' (enp0s31f6) as default for IPv4 routing and DNS
Oct 12 10:58:12 martin-debian NetworkManager[557]: <info>  [1634029092.8981] device (enp0s31f6): Activation: successful, device activated.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 10:58:12 martin-debian rtkit-daemon[734]: Recovering from system lockup, not allowing further RT threads.
Oct 12 10:58:12 martin-debian dbus-daemon[556]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.104' (uid=111 pid=2305 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo")
Oct 12 10:58:12 martin-debian systemd[1]: Condition check resulted in Bluetooth service being skipped.
Oct 12 10:58:12 martin-debian systemd[2283]: Started Sound Service.
Oct 12 10:58:12 martin-debian systemd[2283]: Reached target Main User Target.
Oct 12 10:58:12 martin-debian systemd[2283]: Startup finished in 1.004s.
Oct 12 10:58:23 martin-debian systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Oct 12 10:58:37 martin-debian pulseaudio[2305]: 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.



Pour Xorg.0.log en revanche, je ne sais pas trop comment lire les marqueurs de temps sur le côté : où commencer, où m'arrêter.

Merci pour tant de dévouement smile

Hors ligne

#19 12-10-2021 12:07:11

robert2a
Membre
Inscription : 15-11-2014

Re : [Résolu] Bullseye : écran noir à la sortie de veille

Bonjour
tu peu utiliser "dmesg" et "grep" pour trier des informations
par exemple pour le syslog (corrigé erreur)


dmesg | grep -i acpi
 


pour récupérer les informations "acpi" ou "ACPI"
par exemple pour moi


ACPI: PM: (supports S0 S3 S4 S5)
 


sur un amd (faut que je retourne sur la machine intel avec la gtx1060)


j'ai oublié de te dire sur bullseye sur mes machines , j'ai quelques paquets absent
plymouth , network-manager pipewire sinon mon bureau est assez complet (application) mais reste basic (juste conky installé)
je sais pas si une influence
tu est bien en s3


Oct 12 10:58:08 martin-debian kernel: [  954.159673] ACPI: Preparing to enter system sleep state S3
 



ceci je sais pas ce que cela veut dire ? (que le début de ligne , très longue )


096476] ------------[ cut here ]------------
Oct 12 10:58:09 martin-debian kernel: [  964.096484] WARNING: CPU: 3 PID: 2268 at /var/lib/dkms/nvidia-current/460.91.03/
 


nota: au dessus ça touche le module nvidia  hmm

sinon je vois la mise en suspend , mais du mal a retrouver la reprise (sortir du mode suspend) sur ton log
tu précise pas systématique , parfois la sortie de veille est correcte  roll

ps : c'est un peu la loterie ce mode de veille sur GNU Linux

Dernière modification par robert2a (12-10-2021 13:05:53)

Hors ligne

#20 12-10-2021 13:37:42

robert2a
Membre
Inscription : 15-11-2014

Re : [Résolu] Bullseye : écran noir à la sortie de veille

je cherche mais .........
pour le retour de "acpi" comme erreur ou warning ceci


PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration
 


pour les paquets nonfree j'ai ceci installé


apt policy intel-microcode firmware-intel-sound
 


ps: pour kabylake et skylake (comme cpu intel)

re: quelques infos
https://debian-facile.org/viewtopic.php?id=26862
je n'ai pas light-loocker installé (pas de verrouillage d"écran sur mate )

paquet "pm-utils" a voir

https://debian-facile.org/viewtopic.php?id=28521&p=2
ps: le poste en #32 , explication de Croutons
il y a la veille en ram et la veille sur le disque mais peut être faire les  tests pour trouver ce qui bloque

Dernière modification par robert2a (12-10-2021 14:12:21)

Hors ligne

#21 13-10-2021 15:24:02

Magean
Membre
Inscription : 01-02-2021

Re : [Résolu] Bullseye : écran noir à la sortie de veille

Du neuf, j'ai tenté un ctrl+alt+f7 face à mon écran noir. L'écran se réveille et m'affiche "cette session est verrouillée, vous allez être redirigé vers la fenêtre de déverrouillage dans quelques instants". Sauf qu'après ça il ne se passe rien, l'écran retournant dormir. Pour les sessions en tty (les autres ctrl-alt-f*), la led de l'écran se "réveille" puis se rendort.

Ce serait donc peut-être lightdm ?

Hors ligne

#22 13-10-2021 15:41:52

robert2a
Membre
Inscription : 15-11-2014

Re : [Résolu] Bullseye : écran noir à la sortie de veille

Bonjour
il te faut désactiver le verrouillage de l'écran
sur mate , c'est pas lightdm mais un paquet qui permet de verrouiller l'écran pour xfce ce doit être la même chose

pour mate j'ai le paquet mate-screensaver (qui verrouille en autre l'écran)
et le paquet mate-power-manager  qui permet la suspension en ram

moi le verrouillage de l'écran est désactivé , ainsi que l'économiseur d'écran , juste passer l"écran en mode veille au bout de 5 mn

Dernière modification par robert2a (13-10-2021 15:49:14)

Hors ligne

#23 13-10-2021 17:36:15

Magean
Membre
Inscription : 01-02-2021

Re : [Résolu] Bullseye : écran noir à la sortie de veille

Mais bizarrement, d'après les paramètres, le verrouillage est désactivé :
JWpTMecl.png


Oh, bizarrement, il y avait peut-être un conflit entre deux réglages, celui-là était activé :
epPtt8sl.png


Je vais voir ce que ça donne si je le coupe.

Dernière modification par Magean (13-10-2021 18:25:04)

Hors ligne

#24 13-10-2021 18:30:59

robert2a
Membre
Inscription : 15-11-2014

Re : [Résolu] Bullseye : écran noir à la sortie de veille

non les deux sont identique
le premier => mise hors tension => verrouiller l'écran avant la mise en veille
le second => verrouiller l'écran quand le système se met en veille

tu verrouille dans les deux cas , faut demander aux utilisateurs de xfce

c'est pas lui "XScreensaver" , il est installé ? (voir le #2 )


XScreensaver est un économiseur d'écran modulaire et un verrou de session
pour X11 contenant plus de 200 économiseurs d'écran.

Ce paquet comprend le strict minimum nécessaire pour masquer et verrouiller
un écran. Installez ce paquet pour utiliser le moteur xscreensaver pour
contrôler l’occultation et le lancement de modes d’affichage (« hacks »).
Pour utiliser d’autres moteurs d’économiseur d’écran, l’installation de ce
paquet n’est pas nécessaire.

Les modes d'affichage graphique sont dans les paquets xscreensaver-data,
xscreensaver-data-extra, xscreensaver-gl et xscreensaver-gl-extra.
 

Dernière modification par robert2a (13-10-2021 18:49:28)

Hors ligne

#25 14-10-2021 20:56:49

Magean
Membre
Inscription : 01-02-2021

Re : [Résolu] Bullseye : écran noir à la sortie de veille

Bizarrement ça a l'air de tenir depuis hier soir, depuis que j'ai remis d'accord ces deux paramètres.

Ne crions pas victoire trop vite, l'écran noir survenait très souvent mais pas toujours, il est donc possible qu'il revienne...

Hors ligne

Pied de page des forums