Announcement

Collapse
No announcement yet.

Suspend is not working

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Suspend is not working

    Hi,

    I'm relatively new to Kubuntu (and to the beta of 18.10), so i hope i can help you to understand the bug.

    What is happening?

    When i select Standby-Mode in the Plasma-menu the screen turns black, but the display is still on and the mouse-cursor is still visible. The fans of my computer are active too.
    In this state the system stays for about a minute, until the login screen appears. During this minute it is not possible to end this "freeze".

    I would be glad, if i could help to solve this bug.
    Thanks

    EDIT:
    I have to add the information, that the system needs like one minute to shut down. Because of this i think that their some kind of task running which the system can't stop.

    Another EDIT:

    I had a look at the system output while shut down.

    The Shutdown-Issue seems not to be directly connected to Kubuntu 18.10.
    https://forum.manjaro.org/t/systemd-...resolved/57335
    or https://bugzilla.redhat.com/show_bug.cgi?id=1614773

    Output of journalctl -b 0 -p 3

    Okt 08 12:19:35 ryzen-pc kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
    Okt 08 12:19:35 ryzen-pc kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
    Okt 08 12:19:35 ryzen-pc kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
    Okt 08 12:19:35 ryzen-pc kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
    Okt 08 12:19:35 ryzen-pc kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
    Okt 08 12:19:35 ryzen-pc kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
    Okt 08 12:19:35 ryzen-pc kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
    Okt 08 12:19:46 ryzen-pc spice-vdagent[1532]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: seq 3708 '/devices/pci0000:00/0000:00:07.1/0000:1e:00.2' killed
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: seq 3899 '/devices/system/cpu/cpu8' killed
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: seq 3900 '/devices/system/cpu/cpu9' killed
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: seq 3898 '/devices/system/cpu/cpu7' killed
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: seq 3889 '/devices/system/cpu/cpu0' killed
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: seq 3897 '/devices/system/cpu/cpu6' killed
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: seq 3896 '/devices/system/cpu/cpu5' killed
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: seq 3891 '/devices/system/cpu/cpu10' killed
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: seq 3893 '/devices/system/cpu/cpu2' killed
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: seq 3894 '/devices/system/cpu/cpu3' killed
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: seq 3892 '/devices/system/cpu/cpu11' killed
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: seq 3895 '/devices/system/cpu/cpu4' killed
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: seq 3890 '/devices/system/cpu/cpu1' killed
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: worker [495] failed while handling '/devices/system/cpu/cpu9'
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: worker [489] failed while handling '/devices/system/cpu/cpu7'
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: worker [490] failed while handling '/devices/system/cpu/cpu3'
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: worker [491] failed while handling '/devices/system/cpu/cpu1'
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: worker [496] failed while handling '/devices/system/cpu/cpu4'
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: worker [499] failed while handling '/devices/system/cpu/cpu6'
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: worker [505] failed while handling '/devices/system/cpu/cpu11'
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: worker [508] failed while handling '/devices/system/cpu/cpu0'
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: worker [509] failed while handling '/devices/system/cpu/cpu8'
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: worker [520] failed while handling '/devices/system/cpu/cpu10'
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: worker [521] failed while handling '/devices/system/cpu/cpu2'
    Okt 08 12:22:37 ryzen-pc systemd-udevd[486]: worker [522] failed while handling '/devices/system/cpu/cpu5'
    Okt 08 12:23:31 ryzen-pc kernel: INFO: task systemd-udevd:512 blocked for more than 120 seconds.
    Okt 08 12:23:31 ryzen-pc kernel: Not tainted 4.18.0-8-generic #9-Ubuntu
    Okt 08 12:23:31 ryzen-pc kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Okt 08 12:25:32 ryzen-pc kernel: INFO: task systemd-udevd:512 blocked for more than 120 seconds.
    Okt 08 12:25:32 ryzen-pc kernel: Not tainted 4.18.0-8-generic #9-Ubuntu
    Okt 08 12:25:32 ryzen-pc kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Okt 08 12:27:33 ryzen-pc kernel: INFO: task systemd-udevd:512 blocked for more than 120 seconds.

    ______________________
    With the information at the manjaro-forum i "solved" the shutdown-issue. The Standby Issue persist and i dont know how to log it.
Working...
X