Plantage lors de la mise en veille

French Forum

Moderator: Laurent85

Post Reply
Francky4fingers
Level 1
Level 1
Posts: 11
Joined: Tue Oct 22, 2019 4:39 pm

Plantage lors de la mise en veille

Post by Francky4fingers » Tue Oct 22, 2019 5:04 pm

Bonsoir,

J'ai installé Linuxmint 19.2 il y a une dizaine de jours sur un pc portable toshiba de 2010 (http://il.dynabook.com/en/discontinued- ... c650d-10d/

Il y a qques jours, le 17 Octobre dernier pour être précis, j'ai rencontré un problème lors de la mise en veille. Le PC ne s'est justement pas mis en veille... Il ne répondait plus, l'écran était presque noir restaient tout de même qques pixels de lumières par endroits, les voyants lumineux restaient allumés et le ventilo se déclenchait à l'occasion... J'ai fini par l'éteindre au bouton. Je précise qu'aucun DDE ou clé USB n'était branché sur le PC (je dis ça car lorsque c'est le cas, là non plus la mise en veille ne se passe pas bien, mais bon je débranhce la clé ou le DDE et c'est réglé...).

Depuis j'ai découvert les commandes magiques ( https://doc.ubuntu-fr.org/tutoriel/lors ... steme_gele ) que j'appliquerai si cela se représente mais je me demande s'il est possible de savoir ce qui a pu poser problème.

Le lendemain de ce bug, j'ai exécuté la commande du point 4.4 de cette page https://doc.ubuntu-fr.org/diagnostic_outil mais je me retrouve avec un fichier de plus de 12000 lignes totalement inexploitables pour moi, qui couvre la période du 14 au 18/10. J'ai extrait les lignes correspondant au 17/10, au moment de la mise en veille problématique vers 19h05 et redémarrage le lendemain 18/10 :

Code: Select all

Oct 17 19:04:14 pcdemary gvfsd-metadata[1726]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Oct 17 19:04:52 pcdemary kernel: [  888.123600] [UFW BLOCK] IN=enp8s0 OUT= MAC=01:00:5e:00:00:01:48:83:c7:12:59:ac:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 
Oct 17 19:04:52 pcdemary kernel: [  888.124982] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:48:83:c7:12:59:ac:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 
Oct 17 19:04:14 pcdemary gvfsd-metadata[1726]: message repeated 7 times: [ g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed]
Oct 17 19:05:06 pcdemary systemd[1]: Starting Cleanup of Temporary Directories...
Oct 17 19:05:06 pcdemary systemd[1]: Started Cleanup of Temporary Directories.
Oct 17 19:05:09 pcdemary NetworkManager[784]: <info>  [1571331909.9044] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Oct 17 19:05:09 pcdemary NetworkManager[784]: <info>  [1571331909.9045] manager: NetworkManager state is now ASLEEP
Oct 17 19:05:09 pcdemary NetworkManager[784]: <info>  [1571331909.9049] device (enp8s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Oct 17 19:05:09 pcdemary NetworkManager[784]: <info>  [1571331909.9509] device (wlp2s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Oct 17 19:05:10 pcdemary dbus-daemon[759]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=784 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Oct 17 19:05:10 pcdemary NetworkManager[784]: <info>  [1571331910.0119] device (enp8s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Withdrawing address record for 2001:861:3dc2:bc0:f0f8:54a1:f49e:cb85 on enp8s0.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Leaving mDNS multicast group on interface enp8s0.IPv6 with address 2001:861:3dc2:bc0:f0f8:54a1:f49e:cb85.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Joining mDNS multicast group on interface enp8s0.IPv6 with address 2001:861:3dc2:bc0:714:3936:4778:b7db.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Withdrawing address record for 2001:861:3dc2:bc0:714:3936:4778:b7db on enp8s0.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Leaving mDNS multicast group on interface enp8s0.IPv6 with address 2001:861:3dc2:bc0:714:3936:4778:b7db.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Joining mDNS multicast group on interface enp8s0.IPv6 with address fe80::5ffd:3544:c917:b020.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Registering new address record for fe80::5ffd:3544:c917:b020 on enp8s0.*.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Withdrawing address record for fe80::5ffd:3544:c917:b020 on enp8s0.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Leaving mDNS multicast group on interface enp8s0.IPv6 with address fe80::5ffd:3544:c917:b020.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Interface enp8s0.IPv6 no longer relevant for mDNS.
Oct 17 19:05:10 pcdemary systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 17 19:05:10 pcdemary NetworkManager[784]: <info>  [1571331910.0208] dhcp4 (enp8s0): canceled DHCP transaction, DHCP client pid 948
Oct 17 19:05:10 pcdemary NetworkManager[784]: <info>  [1571331910.0208] dhcp4 (enp8s0): state changed bound -> done
Oct 17 19:05:10 pcdemary NetworkManager[784]: <info>  [1571331910.0273] dhcp6 (enp8s0): canceled DHCP transaction
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Withdrawing address record for 192.168.1.85 on enp8s0.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Leaving mDNS multicast group on interface enp8s0.IPv4 with address 192.168.1.85.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Interface enp8s0.IPv4 no longer relevant for mDNS.
Oct 17 19:05:10 pcdemary dbus-daemon[759]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 17 19:05:10 pcdemary systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 17 19:05:10 pcdemary nm-dispatcher: req:1 'connectivity-change': new request (1 scripts)
Oct 17 19:05:10 pcdemary NetworkManager[784]: <info>  [1571331910.0591] device (wlp2s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Oct 17 19:05:10 pcdemary nm-dispatcher: req:1 'connectivity-change': start running ordered scripts...
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Withdrawing address record for 2001:861:3dc2:bc0:4085:1d61:ee3b:3d7a on wlp2s0.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address 2001:861:3dc2:bc0:4085:1d61:ee3b:3d7a.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address 2001:861:3dc2:bc0:837e:5efb:3057:85c3.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Withdrawing address record for 2001:861:3dc2:bc0:837e:5efb:3057:85c3 on wlp2s0.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address 2001:861:3dc2:bc0:837e:5efb:3057:85c3.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address fe80::7d2b:9afe:b097:10f1.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Registering new address record for fe80::7d2b:9afe:b097:10f1 on wlp2s0.*.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Withdrawing address record for fe80::7d2b:9afe:b097:10f1 on wlp2s0.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::7d2b:9afe:b097:10f1.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Interface wlp2s0.IPv6 no longer relevant for mDNS.
Oct 17 19:05:10 pcdemary NetworkManager[784]: <info>  [1571331910.0649] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP client pid 1148
Oct 17 19:05:10 pcdemary NetworkManager[784]: <info>  [1571331910.0653] dhcp4 (wlp2s0): state changed bound -> done
Oct 17 19:05:10 pcdemary nm-dispatcher: req:2 'down' [enp8s0]: new request (1 scripts)
Oct 17 19:05:10 pcdemary NetworkManager[784]: <info>  [1571331910.0670] dhcp6 (wlp2s0): canceled DHCP transaction
Oct 17 19:05:10 pcdemary nm-dispatcher: req:2 'down' [enp8s0]: start running ordered scripts...
Oct 17 19:05:10 pcdemary kernel: [  905.388778] wlp2s0: deauthenticating from 48:83:c7:12:59:a0 by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Withdrawing address record for 192.168.1.20 on wlp2s0.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.1.20.
Oct 17 19:05:10 pcdemary avahi-daemon[833]: Interface wlp2s0.IPv4 no longer relevant for mDNS.
Oct 17 19:05:10 pcdemary wpa_supplicant[832]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=48:83:c7:12:59:a0 reason=3 locally_generated=1
Oct 17 19:05:10 pcdemary nm-dispatcher: req:3 'down' [wlp2s0]: new request (1 scripts)
Oct 17 19:05:10 pcdemary NetworkManager[784]: <warn>  [1571331910.1208] sup-iface[0x55d2298bc240,wlp2s0]: connection disconnected (reason -3)
Oct 17 19:05:10 pcdemary NetworkManager[784]: <info>  [1571331910.1213] device (wlp2s0): supplicant interface state: completed -> disconnected
Oct 17 19:05:10 pcdemary NetworkManager[784]: <info>  [1571331910.1268] device (enp8s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Oct 17 19:05:10 pcdemary wpa_supplicant[832]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Oct 17 19:05:10 pcdemary NetworkManager[784]: <info>  [1571331910.1700] device (wlp2s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Oct 17 19:05:10 pcdemary nm-dispatcher: req:3 'down' [wlp2s0]: start running ordered scripts...
Oct 17 19:05:10 pcdemary wpa_supplicant[832]: nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
Oct 17 19:05:10 pcdemary systemd[1]: Starting TLP suspend/resume...
Oct 17 19:05:11 pcdemary systemd[1]: Started TLP suspend/resume.
Oct 17 19:05:11 pcdemary systemd[1]: Reached target Sleep.
Oct 17 19:05:11 pcdemary systemd[1]: Starting Suspend...
Oct 17 19:05:11 pcdemary systemd-sleep[3330]: Suspending system...
Oct 17 19:05:11 pcdemary kernel: [  906.708301] PM: suspend entry (deep)
Oct 17 19:05:11 pcdemary kernel: [  906.708304] PM: Syncing filesystems ... done.
Oct 17 19:05:22 pcdemary kernel: [  907.042566] Freezing user space processes ... (elapsed 0.003 seconds) done.
Oct 17 19:05:22 pcdemary kernel: [  907.046330] OOM killer disabled.
Oct 17 19:05:22 pcdemary kernel: [  907.046330] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Oct 17 19:05:22 pcdemary kernel: [  907.047811] Suspending console(s) (use no_console_suspend to debug)
Oct 17 19:05:22 pcdemary kernel: [  907.058364] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Oct 17 19:05:22 pcdemary kernel: [  907.134397] sd 0:0:0:0: [sda] Stopping disk
Oct 17 19:05:22 pcdemary kernel: [  908.318465] ACPI: Preparing to enter system sleep state S3
Oct 17 19:05:22 pcdemary kernel: [  908.329743] PM: Saving platform NVS memory
Oct 17 19:05:22 pcdemary kernel: [  908.332838] Disabling non-boot CPUs ...
Oct 17 19:05:22 pcdemary kernel: [  908.333176] ACPI: Low-level resume complete
Oct 17 19:05:22 pcdemary kernel: [  908.333229] PM: Restoring platform NVS memory
Oct 17 19:05:22 pcdemary kernel: [  908.334841] LVT offset 1 assigned for vector 0x400
Oct 17 19:05:22 pcdemary kernel: [  908.334850] IBS: LVT offset 1 assigned
Oct 17 19:05:22 pcdemary kernel: [  908.335103] microcode: CPU0: new patch_level=0x010000c8
Oct 17 19:05:22 pcdemary kernel: [  908.335780] ACPI: Waking up from system sleep state S3
Oct 17 19:05:22 pcdemary kernel: [  908.411014] [drm] PCIE GART of 512M enabled (table at 0x00000000C0146000).
Oct 17 19:05:22 pcdemary kernel: [  908.411060] radeon 0000:01:05.0: WB enabled
Oct 17 19:05:22 pcdemary kernel: [  908.411064] radeon 0000:01:05.0: fence driver on ring 0 use gpu addr 0x00000000a0000c00 and cpu addr 0x000000009fe1367d
Oct 17 19:05:22 pcdemary kernel: [  908.413745] radeon 0000:01:05.0: fence driver on ring 5 use gpu addr 0x00000000c0056038 and cpu addr 0x0000000006c2459e
Oct 17 19:05:22 pcdemary kernel: [  908.446964] ath: phy0: ASPM enabled: 0x42
Oct 17 19:05:22 pcdemary kernel: [  908.468484] ACPI: button: The lid device is not compliant to SW_LID.
Oct 17 19:05:22 pcdemary kernel: [  908.474164] sd 0:0:0:0: [sda] Starting disk
Oct 17 19:05:22 pcdemary kernel: [  908.482594] [drm] ring test on 0 succeeded in 1 usecs
Oct 17 19:05:22 pcdemary kernel: [  908.657455] [drm] ring test on 5 succeeded in 1 usecs
Oct 17 19:05:22 pcdemary kernel: [  908.657459] [drm] UVD initialized successfully.
Oct 17 19:05:22 pcdemary kernel: [  908.657482] [drm] ib test on ring 0 succeeded in 0 usecs
Oct 17 19:05:22 pcdemary kernel: [  908.908579] ata3: SATA link down (SStatus 0 SControl 300)
Oct 17 19:05:22 pcdemary kernel: [  908.948477] usb 3-4: reset high-speed USB device number 2 using ehci-pci
Oct 17 19:05:22 pcdemary kernel: [  909.068491] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct 17 19:05:22 pcdemary kernel: [  909.120394] ata2.00: configured for UDMA/100
Oct 17 19:05:22 pcdemary kernel: [  909.308466] [drm] ib test on ring 5 succeeded
Oct 17 19:05:22 pcdemary kernel: [  909.653577] psmouse serio1: synaptics: queried max coordinates: x [..5692], y [..4680]
Oct 17 19:05:22 pcdemary kernel: [  909.908456] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 17 19:05:22 pcdemary kernel: [  910.176247] ata1.00: configured for UDMA/133
Oct 17 19:05:22 pcdemary kernel: [  914.376468] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting
Oct 17 19:05:22 pcdemary kernel: [  914.376487] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing E978 (len 492, WS 0, PS 4) @ 0xE9B9
Oct 17 19:05:22 pcdemary kernel: [  915.744106] OOM killer enabled.
Oct 17 19:05:22 pcdemary rtkit-daemon[1525]: The canary thread is apparently starving. Taking action.
Oct 17 19:05:22 pcdemary kernel: [  915.744108] Restarting tasks ... done.
Oct 17 19:05:22 pcdemary kernel: [  915.763049] video LNXVIDEO:00: Restoring backlight state
Oct 17 19:05:22 pcdemary rtkit-daemon[1525]: Demoting known real-time threads.
Oct 17 19:05:22 pcdemary rtkit-daemon[1525]: Successfully demoted thread 1566 of process 1524 (n/a).
Oct 17 19:05:22 pcdemary rtkit-daemon[1525]: Successfully demoted thread 1565 of process 1524 (n/a).
Oct 17 19:05:22 pcdemary rtkit-daemon[1525]: Successfully demoted thread 1524 of process 1524 (n/a).
Oct 17 19:05:22 pcdemary rtkit-daemon[1525]: Demoted 3 threads.
Oct 17 19:05:22 pcdemary systemd-sleep[3330]: System resumed.
Oct 17 19:05:22 pcdemary kernel: [  915.793222] PM: suspend exit
Oct 17 19:05:22 pcdemary kernel: [  915.884595] usb 2-2: new high-speed USB device number 3 using ehci-pci
Oct 17 19:05:22 pcdemary systemd-sleep[3330]: /dev/sda:
Oct 17 19:05:22 pcdemary systemd-sleep[3330]:  setting Advanced Power Management level to 0x80 (128)
Oct 17 19:05:22 pcdemary systemd-sleep[3330]:  APM_level#011= 128
Oct 17 19:05:22 pcdemary systemd-sleep[3330]: /dev/sda:
Oct 17 19:05:22 pcdemary systemd-sleep[3330]:  setting standby to 36 (3 minutes)
Oct 17 19:05:22 pcdemary systemd[1]: Started Suspend.
Oct 17 19:05:22 pcdemary systemd[1]: sleep.target: Unit not needed anymore. Stopping.
Oct 17 19:05:22 pcdemary systemd[1]: Stopped target Sleep.
Oct 17 19:05:22 pcdemary systemd[1]: tlp-sleep.service: Unit not needed anymore. Stopping.
Oct 17 19:05:22 pcdemary systemd[1]: Stopping TLP suspend/resume...
Oct 17 19:05:22 pcdemary systemd[1]: Reached target Suspend.
Oct 17 19:05:22 pcdemary NetworkManager[784]: <info>  [1571331922.8186] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Oct 17 19:05:22 pcdemary kernel: [  916.154163] IPv6: ADDRCONF(NETDEV_UP): enp8s0: link is not ready
Oct 17 19:05:22 pcdemary NetworkManager[784]: <info>  [1571331922.8187] device (enp8s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Oct 17 19:05:22 pcdemary systemd[1]: suspend.target: Unit not needed anymore. Stopping.
Oct 17 19:05:22 pcdemary systemd[1]: Stopped target Suspend.
Oct 17 19:05:22 pcdemary kernel: [  916.173828] IPv6: ADDRCONF(NETDEV_UP): enp8s0: link is not ready
Oct 17 19:05:22 pcdemary kernel: [  916.175521] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Oct 17 19:05:22 pcdemary NetworkManager[784]: <info>  [1571331922.8401] device (wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Oct 17 19:05:22 pcdemary kernel: [  916.240751] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Oct 17 19:05:22 pcdemary NetworkManager[784]: <info>  [1571331922.9122] manager: NetworkManager state is now DISCONNECTED
Oct 17 19:05:22 pcdemary wpa_supplicant[832]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
Oct 17 19:05:22 pcdemary wpa_supplicant[832]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Oct 17 19:05:22 pcdemary wpa_supplicant[832]: dbus: Failed to construct signal
Oct 17 19:05:22 pcdemary wpa_supplicant[832]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
Oct 17 19:05:22 pcdemary NetworkManager[784]: <info>  [1571331922.9590] device (wlp2s0): supplicant interface state: starting -> ready
Oct 17 19:05:22 pcdemary NetworkManager[784]: <info>  [1571331922.9600] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Oct 17 19:05:22 pcdemary kernel: [  916.296009] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Oct 17 19:05:22 pcdemary kernel: [  916.297485] usb 2-2: New USB device found, idVendor=0bda, idProduct=0138
Oct 17 19:05:22 pcdemary kernel: [  916.297489] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 17 19:05:22 pcdemary kernel: [  916.297491] usb 2-2: Product: USB2.0-CRW
Oct 17 19:05:22 pcdemary kernel: [  916.297492] usb 2-2: Manufacturer: Generic
Oct 17 19:05:22 pcdemary kernel: [  916.297493] usb 2-2: SerialNumber: 20090516388200000
Oct 17 19:05:22 pcdemary kernel: [  916.317466] ums-realtek 2-2:1.0: USB Mass Storage device detected
Oct 17 19:05:23 pcdemary kernel: [  916.343916] scsi host3: usb-storage 2-2:1.0
Oct 17 19:05:23 pcdemary kernel: [  916.345512] usb 2-2: USB disconnect, device number 3
Oct 17 19:05:23 pcdemary wpa_supplicant[832]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.0296] policy: auto-activating connection 'Auto 3sans10'
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.0332] device (wlp2s0): Activation: starting connection 'Auto 3sans10' (815b6b68-4e7f-46da-8898-23f42ffdceab)
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.0377] device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.0395] manager: NetworkManager state is now CONNECTING
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.0477] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.0525] device (wlp2s0): Activation: (wifi) access point 'Auto 3sans10' has security, but secrets are required.
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.0529] device (wlp2s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.0541] sup-iface[0x55d2299cc650,wlp2s0]: wps: type pbc start...
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.0714] device (wlp2s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.0753] device (wlp2s0): supplicant interface state: ready -> scanning
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.0785] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.0799] device (wlp2s0): Activation: (wifi) connection 'Auto 3sans10' has security, and secrets exist.  No new secrets needed.
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.0803] Config: added 'ssid' value '3sans10'
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.0805] Config: added 'scan_ssid' value '1'
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.0807] Config: added 'bgscan' value 'simple:30:-80:86400'
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.0809] Config: added 'key_mgmt' value 'WPA-PSK'
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.0811] Config: added 'auth_alg' value 'OPEN'
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.0812] Config: added 'psk' value '<hidden>'
Oct 17 19:05:24 pcdemary wpa_supplicant[832]: wlp2s0: SME: Trying to authenticate with 48:83:c7:12:59:a0 (SSID='3sans10' freq=2462 MHz)
Oct 17 19:05:24 pcdemary kernel: [  917.445778] wlp2s0: authenticate with 48:83:c7:12:59:a0
Oct 17 19:05:24 pcdemary upowerd[1289]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:13.2/usb2/2-2/2-2:1.0
Oct 17 19:05:24 pcdemary upowerd[1289]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:13.2/usb2/2-2
Oct 17 19:05:24 pcdemary upowerd[1289]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:13.2/usb2/2-2/2-2:1.0
Oct 17 19:05:24 pcdemary upowerd[1289]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:13.2/usb2/2-2
Oct 17 19:05:24 pcdemary kernel: [  917.469595] wlp2s0: send auth to 48:83:c7:12:59:a0 (try 1/3)
Oct 17 19:05:24 pcdemary kernel: [  917.473869] wlp2s0: authenticated
Oct 17 19:05:24 pcdemary wpa_supplicant[832]: wlp2s0: Trying to associate with 48:83:c7:12:59:a0 (SSID='3sans10' freq=2462 MHz)
Oct 17 19:05:24 pcdemary kernel: [  917.480398] wlp2s0: associate with 48:83:c7:12:59:a0 (try 1/3)
Oct 17 19:05:24 pcdemary kernel: [  917.484114] wlp2s0: RX AssocResp from 48:83:c7:12:59:a0 (capab=0x411 status=0 aid=1)
Oct 17 19:05:24 pcdemary kernel: [  917.484235] wlp2s0: associated
Oct 17 19:05:24 pcdemary wpa_supplicant[832]: wlp2s0: Associated with 48:83:c7:12:59:a0
Oct 17 19:05:24 pcdemary wpa_supplicant[832]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.1510] device (wlp2s0): supplicant interface state: scanning -> associating
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.1566] device (wlp2s0): supplicant interface state: associating -> associated
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.1619] device (wlp2s0): supplicant interface state: associated -> 4-way handshake
Oct 17 19:05:24 pcdemary wpa_supplicant[832]: wlp2s0: WPA: Key negotiation completed with 48:83:c7:12:59:a0 [PTK=CCMP GTK=CCMP]
Oct 17 19:05:24 pcdemary wpa_supplicant[832]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 48:83:c7:12:59:a0 completed [id=0 id_str=]
Oct 17 19:05:24 pcdemary kernel: [  917.587199] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.2587] device (wlp2s0): supplicant interface state: 4-way handshake -> completed
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.2665] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network '3sans10'.
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.2731] device (wlp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.2754] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.2781] dhcp4 (wlp2s0): dhclient started with pid 3481
Oct 17 19:05:24 pcdemary dhclient[3481]: DHCPREQUEST of 192.168.1.20 on wlp2s0 to 255.255.255.255 port 67 (xid=0x5b5ac685)
Oct 17 19:05:24 pcdemary dhclient[3481]: DHCPACK of 192.168.1.20 from 192.168.1.254
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.3209] dhcp4 (wlp2s0):   address 192.168.1.20
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.3214] dhcp4 (wlp2s0):   plen 24 (255.255.255.0)
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.3217] dhcp4 (wlp2s0):   gateway 192.168.1.254
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.3220] dhcp4 (wlp2s0):   lease time 86400
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.3223] dhcp4 (wlp2s0):   hostname 'pcdemary'
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.3225] dhcp4 (wlp2s0):   nameserver '192.168.1.254'
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.3227] dhcp4 (wlp2s0):   domain name 'lan'
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.3229] dhcp4 (wlp2s0): state changed unknown -> bound
Oct 17 19:05:24 pcdemary avahi-daemon[833]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.1.20.
Oct 17 19:05:24 pcdemary avahi-daemon[833]: New relevant interface wlp2s0.IPv4 for mDNS.
Oct 17 19:05:24 pcdemary avahi-daemon[833]: Registering new address record for 192.168.1.20 on wlp2s0.IPv4.
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.3312] device (wlp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.3360] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.3402] device (wlp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.3425] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 17 19:05:24 pcdemary dhclient[3481]: bound to 192.168.1.20 -- renewal in 43039 seconds.
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.4235] manager: NetworkManager state is now CONNECTED_SITE
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.4276] policy: set 'Auto 3sans10' (wlp2s0) as default for IPv4 routing and DNS
Oct 17 19:05:24 pcdemary NetworkManager[784]: <info>  [1571331924.4323] device (wlp2s0): Activation: successful, device activated.
Oct 17 19:05:24 pcdemary dbus-daemon[759]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=784 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Oct 17 19:05:24 pcdemary systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 17 19:05:24 pcdemary dbus-daemon[759]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 17 19:05:24 pcdemary systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 17 19:05:24 pcdemary nm-dispatcher: req:1 'up' [wlp2s0]: new request (1 scripts)
Oct 17 19:05:24 pcdemary nm-dispatcher: req:1 'up' [wlp2s0]: start running ordered scripts...
Oct 17 19:05:24 pcdemary wpa_supplicant[832]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-35 noise=-95 txrate=58500
Oct 17 19:05:25 pcdemary ModemManager[831]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:04.0/0000:02:00.0': not supported by any plugin
Oct 17 19:05:25 pcdemary ModemManager[831]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:05.0/0000:08:00.0': not supported by any plugin
Oct 17 19:05:25 pcdemary NetworkManager[784]: <info>  [1571331925.6975] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 17 19:05:25 pcdemary nm-dispatcher: req:2 'connectivity-change': new request (1 scripts)
Oct 17 19:05:25 pcdemary nm-dispatcher: req:2 'connectivity-change': start running ordered scripts...
Oct 17 19:05:26 pcdemary avahi-daemon[833]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address fe80::7d2b:9afe:b097:10f1.
Oct 17 19:05:26 pcdemary avahi-daemon[833]: New relevant interface wlp2s0.IPv6 for mDNS.
Oct 17 19:05:26 pcdemary avahi-daemon[833]: Registering new address record for fe80::7d2b:9afe:b097:10f1 on wlp2s0.*.
Oct 17 19:05:26 pcdemary NetworkManager[784]: <info>  [1571331926.6717] dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Oct 17 19:05:26 pcdemary NetworkManager[784]: <info>  [1571331926.6753] dhcp6 (wlp2s0): dhclient started with pid 3574
Oct 17 19:05:26 pcdemary NetworkManager[784]: <info>  [1571331926.6785] policy: set 'Auto 3sans10' (wlp2s0) as default for IPv6 routing and DNS
Oct 17 19:05:26 pcdemary dhclient[3574]: XMT: Info-Request on wlp2s0, interval 980ms.
Oct 17 19:05:27 pcdemary dhclient[3574]: RCV: Reply message on wlp2s0 from fe80::4a83:c7ff:fe12:59ac.
Oct 17 19:05:27 pcdemary NetworkManager[784]: <info>  [1571331927.0278] dhcp6 (wlp2s0):   nameserver 'fe80::4a83:c7ff:fe12:59ac'
Oct 17 19:05:27 pcdemary NetworkManager[784]: <info>  [1571331927.0284] dhcp (wlp2s0):   domain search 'lan.'
Oct 17 19:05:27 pcdemary NetworkManager[784]: <info>  [1571331927.0287] dhcp6 (wlp2s0): state changed unknown -> bound
Oct 17 19:05:27 pcdemary nm-dispatcher: req:3 'dhcp6-change' [wlp2s0]: new request (1 scripts)
Oct 17 19:05:27 pcdemary nm-dispatcher: req:3 'dhcp6-change' [wlp2s0]: start running ordered scripts...
Oct 17 19:05:27 pcdemary NetworkManager[784]: <info>  [1571331927.0458] dhcp6 (wlp2s0): client pid 3574 exited with status 0
Oct 17 19:05:27 pcdemary NetworkManager[784]: <info>  [1571331927.0462] dhcp6 (wlp2s0): state changed bound -> done
Oct 17 19:05:27 pcdemary avahi-daemon[833]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::7d2b:9afe:b097:10f1.
Oct 17 19:05:27 pcdemary avahi-daemon[833]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address 2001:861:3dc2:bc0:4085:1d61:ee3b:3d7a.
Oct 17 19:05:27 pcdemary avahi-daemon[833]: Registering new address record for 2001:861:3dc2:bc0:4085:1d61:ee3b:3d7a on wlp2s0.*.
Oct 17 19:05:27 pcdemary avahi-daemon[833]: Withdrawing address record for fe80::7d2b:9afe:b097:10f1 on wlp2s0.
Oct 17 19:05:28 pcdemary avahi-daemon[833]: Registering new address record for 2001:861:3dc2:bc0:837e:5efb:3057:85c3 on wlp2s0.*.
Oct 17 19:05:32 pcdemary kernel: [  926.012453] radeon 0000:01:05.0: ring 0 stalled for more than 10244msec
Oct 17 19:05:32 pcdemary kernel: [  926.012467] radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000070d9 last fence id 0x00000000000070e4 on ring 0)
Oct 17 19:05:32 pcdemary kernel: [  926.029676] radeon 0000:01:05.0: Saved 361 dwords of commands on ring 0.
Oct 17 19:05:32 pcdemary kernel: [  926.029685] radeon 0000:01:05.0: GPU softreset: 0x00000009
Oct 17 19:05:32 pcdemary kernel: [  926.029687] radeon 0000:01:05.0:   R_008010_GRBM_STATUS      = 0xE5703030
Oct 17 19:05:32 pcdemary kernel: [  926.029689] radeon 0000:01:05.0:   R_008014_GRBM_STATUS2     = 0x00110103
Oct 17 19:05:32 pcdemary kernel: [  926.029690] radeon 0000:01:05.0:   R_000E50_SRBM_STATUS      = 0x20000040
Oct 17 19:05:32 pcdemary kernel: [  926.029692] radeon 0000:01:05.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
Oct 17 19:05:32 pcdemary kernel: [  926.029693] radeon 0000:01:05.0:   R_008678_CP_STALLED_STAT2 = 0x00008002
Oct 17 19:05:32 pcdemary kernel: [  926.029695] radeon 0000:01:05.0:   R_00867C_CP_BUSY_STAT     = 0x00008086
Oct 17 19:05:32 pcdemary kernel: [  926.029696] radeon 0000:01:05.0:   R_008680_CP_STAT          = 0x80018645
Oct 17 19:05:32 pcdemary kernel: [  926.029697] radeon 0000:01:05.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
Oct 17 19:05:32 pcdemary kernel: [  926.091095] radeon 0000:01:05.0: R_008020_GRBM_SOFT_RESET=0x00007FEF
Oct 17 19:05:32 pcdemary kernel: [  926.091147] radeon 0000:01:05.0: SRBM_SOFT_RESET=0x00000100
Oct 17 19:05:32 pcdemary kernel: [  926.093234] radeon 0000:01:05.0:   R_008010_GRBM_STATUS      = 0xA0003030
Oct 17 19:05:32 pcdemary kernel: [  926.093236] radeon 0000:01:05.0:   R_008014_GRBM_STATUS2     = 0x00000003
Oct 17 19:05:32 pcdemary kernel: [  926.093237] radeon 0000:01:05.0:   R_000E50_SRBM_STATUS      = 0x20008040
Oct 17 19:05:32 pcdemary kernel: [  926.093238] radeon 0000:01:05.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
Oct 17 19:05:32 pcdemary kernel: [  926.093240] radeon 0000:01:05.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
Oct 17 19:05:32 pcdemary kernel: [  926.093241] radeon 0000:01:05.0:   R_00867C_CP_BUSY_STAT     = 0x00000000
Oct 17 19:05:32 pcdemary kernel: [  926.093242] radeon 0000:01:05.0:   R_008680_CP_STAT          = 0x80100000
Oct 17 19:05:32 pcdemary kernel: [  926.093244] radeon 0000:01:05.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
Oct 17 19:05:32 pcdemary kernel: [  926.093248] radeon 0000:01:05.0: GPU reset succeeded, trying to resume
Oct 17 19:05:32 pcdemary kernel: [  926.114074] [drm] PCIE GART of 512M enabled (table at 0x00000000C0146000).
Oct 17 19:05:32 pcdemary kernel: [  926.114120] radeon 0000:01:05.0: WB enabled
Oct 17 19:05:32 pcdemary kernel: [  926.114124] radeon 0000:01:05.0: fence driver on ring 0 use gpu addr 0x00000000a0000c00 and cpu addr 0x000000009fe1367d
Oct 17 19:05:32 pcdemary kernel: [  926.116819] radeon 0000:01:05.0: fence driver on ring 5 use gpu addr 0x00000000c0056038 and cpu addr 0x0000000006c2459e
Oct 17 19:05:32 pcdemary kernel: [  926.154073] [drm] ring test on 0 succeeded in 1 usecs
Oct 17 19:05:33 pcdemary kernel: [  926.333450] [drm] ring test on 5 succeeded in 1 usecs
Oct 17 19:05:33 pcdemary kernel: [  926.333456] [drm] UVD initialized successfully.
Oct 17 19:05:33 pcdemary systemd[1]: Stopped TLP suspend/resume.
Oct 17 19:05:43 pcdemary kernel: [  936.764421] radeon 0000:01:05.0: ring 0 stalled for more than 10432msec
Oct 17 19:05:43 pcdemary kernel: [  936.764436] radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000070da last fence id 0x00000000000070e4 on ring 0)
Oct 17 19:05:43 pcdemary kernel: [  937.276421] radeon 0000:01:05.0: ring 0 stalled for more than 10944msec
Oct 17 19:05:43 pcdemary kernel: [  937.276434] radeon 0000:01:05.0: GPU lockup (current fence id 0x00000000000070da last fence id 0x00000000000070e4 on ring 0)
Oct 17 19:05:44 pcdemary kernel: [  937.728589] [drm:r600_ib_test [radeon]] *ERROR* radeon: fence wait failed (-35).
Oct 17 19:05:44 pcdemary kernel: [  937.728659] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on GFX ring (-35).
Oct 17 19:06:57 pcdemary kernel: [ 1010.909290] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:01:48:83:c7:12:59:ac:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 
Oct 17 19:06:59 pcdemary systemd-udevd[3750]: Process '/usr/sbin/tlp auto' failed with exit code 4.
Oct 18 17:45:01 pcdemary kernel: [    0.000000] Linux version 4.15.0-65-generic (buildd@lgw01-amd64-006) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 (Ubuntu 4.15.0-65.74-generic 4.15.18)
Oct 18 17:45:01 pcdemary kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-65-generic root=UUID=fdac86a2-fb1e-482d-836f-006402caef28 ro quiet splash vt.handoff=1
J'ai donc 2 questions :

1 - Est-ce que quelqu'un comprend quelque chose à ce fichier ? Si oui y a-t-il une anomalie ?

2 - Dans l'optique ou ce problème venait à se reproduire, quelles sont les infos qu'il convient de récupérer pour tenter d'obtenir un coup de mains sur ce forum ?

Merci de m'avoir lu

Laurent85
Level 16
Level 16
Posts: 6116
Joined: Tue May 26, 2015 10:11 am

Re: Plantage lors de la mise en veille

Post by Laurent85 » Wed Oct 23, 2019 8:49 am

Bonjour,
Donne les retours de :

Code: Select all

inxi -Fxxz 
inxi -tcm5
journalctl -p3 -n50
Image

Francky4fingers
Level 1
Level 1
Posts: 11
Joined: Tue Oct 22, 2019 4:39 pm

Re: Plantage lors de la mise en veille

Post by Francky4fingers » Wed Oct 23, 2019 1:23 pm

Bonsoir Laurent,

Ci-dessous les retours des 3 commandes :

Code: Select all

mary@pcdemary:~$ inxi -Fxxz
System:
  Host: pcdemary Kernel: 4.15.0-65-generic x86_64 bits: 64 compiler: gcc 
  v: 7.4.0 Desktop: Cinnamon 4.2.4 wm: muffin dm: LightDM 
  Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic 
Machine:
  Type: Laptop System: TOSHIBA product: Satellite C650D v: PSC16E-007008FR 
  serial: <filter> Chassis: AMD type: 10 serial: <filter> 
  Mobo: TOSHIBA model: Portable PC serial: <filter> BIOS: Insyde v: 1.40 
  date: 05/19/2010 
Battery:
  ID-1: BAT0 charge: 51.9 Wh condition: 55.2/56.2 Wh (98%) volts: 10.8/10.8 
  model: PA3817U-1BRS serial: <filter> status: Discharging 
CPU:
  Topology: Single Core model: AMD V120 bits: 64 type: UP arch: K10 rev: 3 
  L2 cache: 512 KiB 
  flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 4388 
  Speed: 800 MHz min/max: 800/2200 MHz Core speed (MHz): 1: 800 
Graphics:
  Device-1: AMD RS880M [Mobility Radeon HD 4225/4250] 
  vendor: Toshiba America Info Systems driver: radeon v: kernel 
  bus ID: 01:05.0 chip ID: 1002:9712 
  Display: x11 server: X.Org 1.19.6 driver: ati,radeon 
  unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz 
  OpenGL: renderer: AMD RS880 (DRM 2.50.0 / 4.15.0-65-generic LLVM 8.0.0) 
  v: 3.3 Mesa 19.0.8 compat-v: 3.0 direct render: Yes 
Audio:
  Device-1: AMD SBx00 Azalia vendor: Toshiba America Info Systems 
  driver: snd_hda_intel v: kernel bus ID: 00:14.2 chip ID: 1002:4383 
  Sound Server: ALSA v: k4.15.0-65-generic 
Network:
  Device-1: Qualcomm Atheros AR9285 Wireless Network Adapter vendor: Askey 
  driver: ath9k v: kernel port: 7000 bus ID: 02:00.0 chip ID: 168c:002b 
  IF: wlp2s0 state: up mac: <filter> 
  Device-2: Qualcomm Atheros AR8152 v1.1 Fast Ethernet 
  vendor: Toshiba America Info Systems driver: atl1c v: 1.0.1.1-NAPI 
  port: 2000 bus ID: 08:00.0 chip ID: 1969:2060 
  IF: enp8s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 261.70 GiB used: 10.92 GiB (4.2%) 
  ID-1: /dev/sda vendor: Seagate model: ST9250315AS size: 232.89 GiB 
  speed: 3.0 Gb/s serial: <filter> 
  ID-2: /dev/sdb type: USB vendor: Verbatim model: STORE N GO 
  size: 28.82 GiB serial: <filter> 
Partition:
  ID-1: / size: 27.37 GiB used: 6.70 GiB (24.5%) fs: ext4 dev: /dev/sda1 
  ID-2: /home size: 197.06 GiB used: 2.23 GiB (1.1%) fs: ext4 dev: /dev/sda3 
  ID-3: swap-1 size: 3.73 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 49.2 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 159 Uptime: 9m Memory: 2.68 GiB used: 902.1 MiB (32.9%) 
  Init: systemd v: 237 runlevel: 5 Compilers: gcc: 7.4.0 alt: 7 Shell: bash 
  v: 4.4.20 running in: gnome-terminal inxi: 3.0.32
  
   
mary@pcdemary:~$ inxi -tcm5
Processes: CPU top: 5 
           1: cpu: 7.2% command: firefox pid: 2084 
           2: cpu: 4.3% command: cinnamon pid: 1520 
           3: cpu: 3.6% command: firefox pid: 2302 
           4: cpu: 2.9% command: xed pid: 2607 
           5: cpu: 1.6% command: firefox pid: 2147 
           System RAM: total: 2.68 GiB used: 959.8 MiB (35.0%) 
           Memory top: 5 
           1: mem: 265.9 MiB (9.6%) command: firefox pid: 2084 
           2: mem: 166.7 MiB (6.0%) command: firefox pid: 2302 
           3: mem: 150.0 MiB (5.4%) command: firefox pid: 2219 
           4: mem: 142.3 MiB (5.1%) command: firefox pid: 2147 
           5: mem: 125.5 MiB (4.5%) command: cinnamon pid: 1520
           
            
mary@pcdemary:~$ journalctl -p3 -n50
-- Logs begin at Fri 2019-10-11 00:33:01 CEST, end at Wed 2019-10-23 19:12:56 CEST. --
oct. 20 20:41:14 pcdemary systemd-coredump[5191]: Process 905 (Xorg) of user 0 dumped core.
                                                  
                                                  Stack trace of thread 905:
                                                  #0  0x00007ff1b08dee97 __GI_raise (libc.so.6)
                                                  #1  0x00007ff1b08e0801 __GI_abort (libc.so.6)
                                                  #2  0x000055f64495380a OsAbort (Xorg)
                                                  #3  0x000055f64482b3dc ddxGiveUp (Xorg)
                                                  #4  0x000055f644959312 n/a (Xorg)
                                                  #5  0x000055f64495a155 FatalError (Xorg)
                                                  #6  0x000055f6449508ae n/a (Xorg)
                                                  #7  0x00007ff1b0ca3890 __restore_rt (libpthread.so.0)
                                                  #8  0x00007ff1add520b2 n/a (radeon_drv.so)
                                                  #9  0x00007ff1add5306b n/a (radeon_drv.so)
                                                  #10 0x000055f644860cea n/a (Xorg)
                                                  #11 0x000055f64486b9f1 n/a (Xorg)
                                                  #12 0x000055f64486bda4 n/a (Xorg)
                                                  #13 0x000055f64486a730 n/a (Xorg)
                                                  #14 0x000055f64486622e n/a (Xorg)
                                                  #15 0x000055f6448ad007 ProcRRSetCrtcGamma (Xorg)
                                                  #16 0x000055f6447e6e98 n/a (Xorg)
                                                  #17 0x000055f6447eaee0 n/a (Xorg)
                                                  #18 0x00007ff1b08c1b97 __libc_start_main (libc.so.6)
                                                  #19 0x000055f6447d4b8a _start (Xorg)
                                                  
                                                  Stack trace of thread 1147:
                                                  #0  0x00007ff1b0ca210d __lll_lock_wait (libpthread.so.0)
                                                  #1  0x00007ff1b0c9b098 __GI___pthread_mutex_lock (libpthread.so.0)
                                                  #2  0x000055f64494e990 input_lock (Xorg)
                                                  #3  0x000055f64494ec21 n/a (Xorg)
                                                  #4  0x000055f644951331 n/a (Xorg)
                                                  #5  0x000055f64494ea7e n/a (Xorg)
                                                  #6  0x00007ff1b0c986db start_thread (libpthread.so.0)
                                                  #7  0x00007ff1b09c188f __clone (libc.so.6)
lines 1-34
Dans tous les cas merci de ton aide
Bonne soirée

Francky4fingers
Level 1
Level 1
Posts: 11
Joined: Tue Oct 22, 2019 4:39 pm

Re: Plantage lors de la mise en veille

Post by Francky4fingers » Wed Oct 23, 2019 2:21 pm

complément :

Je viens à l'instant de rencontrer le même problème. Au moment de la mise en veille, écran bizarre pixélisé puis retour sur l'écran de login de mint sauf que la zone de saisie du mot de passe n'apparaît pas. J'ai tenté les fameuses commandes magiques mais sans succès (j'ai pourtant été patient) et j'ai fini par éteindre au bouton. Un clé USB était branché sur le PC. Peut être que ça se lit dans les retours que j'ai fourni mais il y a visiblement un problème avec des ports USB qui gênent la mise en veille.
J'ai bien trouvé ça (http://www.sublimigeek.fr/ubuntu-fixer- ... ibernation) mais je ne sais pas si cela est toujours pertinent et suis pas sûr d'avoir le niveau...

Merci

Laurent85
Level 16
Level 16
Posts: 6116
Joined: Tue May 26, 2015 10:11 am

Re: Plantage lors de la mise en veille

Post by Laurent85 » Thu Oct 24, 2019 7:55 am

Dans les logs on voit que la suspension commence puis s'interrompt. Quelque chose se passe mal pendant la procédure.

On voit aussi que le serveur graphique Xorg plante, les 2 sont probablement liés. L'échec de la suspension étant la conséquence du plantage Xorg, plus particulièrement du pilote de la carte graphique (libellé radeon et/ou drm dans les logs)

La suspension interrompue tente de remettre le système dans l'état initial mais comme le serveur graphique à planté ça bug, plus d'affichage correct.

Essaie de désinstaller le paquet tlp, la gestion de l'économie d'énergie entre peut-être en conflit avec la suspension. Désinstalle tlp, redémarre, et teste à nouveau la suspension.

Autre chose, ce pc est sous-dimensionné pour une utilisation du bureau Cinnamon. Tu devrais installer LM Mate ou Xfce, tu auras moins de bug avec la carte graphique, Cinnamon est exigeant en ressources 3D, et sur les matériels anciens le développement de la couche graphique 3D est plus ou moins en friches.
Image

Francky4fingers
Level 1
Level 1
Posts: 11
Joined: Tue Oct 22, 2019 4:39 pm

Re: Plantage lors de la mise en veille

Post by Francky4fingers » Thu Oct 24, 2019 2:42 pm

Malheureusement ça n'a pas changé grand chose :-(
Changer de bureau, pourquoi pas, d'autant qu'il ventile peut être un peu trop, ça ne pourrait pas nuire !!
Visiblement il n'est pas indispensable de passer par une réinstallation complète mais ça semble hasardeux non ? (ex : viewtopic.php?t=164083)

Merci en tous cas

Laurent85
Level 16
Level 16
Posts: 6116
Joined: Tue May 26, 2015 10:11 am

Re: Plantage lors de la mise en veille

Post by Laurent85 » Sat Oct 26, 2019 10:56 am

Francky4fingers wrote:
Thu Oct 24, 2019 2:42 pm
Visiblement il n'est pas indispensable de passer par une réinstallation complète mais ça semble hasardeux non ?
Ça peut mais à l'origine les bureaux ne sont pas vraiment conçus pour être en concurrence, il peut y avoir des effets de bord indésirables.
Image

Francky4fingers
Level 1
Level 1
Posts: 11
Joined: Tue Oct 22, 2019 4:39 pm

Re: Plantage lors de la mise en veille

Post by Francky4fingers » Tue Nov 05, 2019 4:34 pm

Bonjour,

Désolé pour l'absence de suivi!
Bon je n'ai pas installé Mate me contentant dans un premier temps de voir si le problème existait sur une live session. Eh bien oui :-(
La mise en veille a duré 2 secondes puis l'écran s'est rallumé. Sur ce coup cela n'a pas été trop problématique puisque tout (clavier, souris, écran) fonctionnait parfaitement.

Je vais continuer à creuser mais c'est pas gagné !
Si quelqu'un a malgré tout une idée je suis preneur
Merci

Post Reply

Return to “Français (French)”