Kubuntu 20.04 freezes when left alone for a while. Auto-suspend is off?

**jorxster** · June 4th, 2020

Hi folks,

My kubuntu 18 quit booting on me so I figured it was a good time to do a fresh install of kubuntu 20.04. Only been running a couple of weeks, and have kept software packages updated.
Hardware : AMD Ryzen 3000, Nvidia GTX 1070, Asus motherboard.

However recently within the last week, I noticed that my computer will freeze with the screens off, if I leave it for an hour or two. Screens will remain off, keyboard and mouse input do nothing.
The sleep function works normally when triggered manually, but despite "Suspend Session" being turned off in System Settings > Energy Saving, it seems to be doing something and freezing when I leave it for a while.

How can I troubleshoot this?
Are there any other settings besides System Settings > Energy Saving where I can check for auto-suspend or timeouts happening?

cheers,
Jordan

P.S.

Dmesg gives me this. Not sure if related... or where else to look for logs

[ 9.164267] IPv6: ADDRCONF(NETDEV_CHANGE): enp35s0: link becomes ready
[ 1522.729949] PM: suspend entry (deep)
[ 1522.738248] Filesystems sync: 0.008 seconds
[ 1523.959487] Freezing user space processes ... (elapsed 0.004 seconds) done.
[ 1523.963679] OOM killer disabled.
[ 1523.963680] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 1523.964907] printk: Suspending console(s) (use no_console_suspend to debug)
[ 1523.993623] sd 3:0:0:0: [sdb] Synchronizing SCSI cache
[ 1523.993978] sd 2:0:0:0: [sda] Synchronizing SCSI cache
[ 1523.994118] sd 2:0:0:0: [sda] Stopping disk
[ 1523.999634] sd 3:0:0:0: [sdb] Stopping disk
[ 1525.511249] ACPI: EC: interrupt blocked
[ 1525.589845] ACPI: Preparing to enter system sleep state S3
[ 1525.917860] ACPI: EC: event blocked
[ 1525.917861] ACPI: EC: EC stopped
[ 1525.917862] PM: Saving platform NVS memory
[ 1525.917900] Disabling non-boot CPUs ...
[ 1525.919168] IRQ 75: no longer affine to CPU1
[ 1525.920236] smpboot: CPU 1 is now offline
[ 1525.923369] smpboot: CPU 2 is now offline
[ 1525.926692] smpboot: CPU 3 is now offline
[ 1525.929992] smpboot: CPU 4 is now offline
[ 1525.932290] IRQ 46: no longer affine to CPU5
[ 1525.933308] smpboot: CPU 5 is now offline
[ 1525.936498] smpboot: CPU 6 is now offline
[ 1525.939072] IRQ 31: no longer affine to CPU7
[ 1525.940083] smpboot: CPU 7 is now offline
[ 1525.943303] smpboot: CPU 8 is now offline
[ 1525.945557] IRQ 45: no longer affine to CPU9
[ 1525.946575] smpboot: CPU 9 is now offline
[ 1525.948451] IRQ 49: no longer affine to CPU10
[ 1525.949512] smpboot: CPU 10 is now offline
[ 1525.951643] IRQ 29: no longer affine to CPU11
[ 1525.951648] IRQ 30: no longer affine to CPU11
[ 1525.952667] smpboot: CPU 11 is now offline
[ 1525.954498] IRQ 58: no longer affine to CPU12
[ 1525.955514] smpboot: CPU 12 is now offline
[ 1525.958529] smpboot: CPU 13 is now offline
[ 1525.960216] IRQ 76: no longer affine to CPU14
[ 1525.961297] smpboot: CPU 14 is now offline
[ 1525.964204] smpboot: CPU 15 is now offline
[ 1525.966347] ACPI: Low-level resume complete
[ 1525.966394] ACPI: EC: EC started
[ 1525.966394] PM: Restoring platform NVS memory
[ 1525.966900] Enabling non-boot CPUs ...
[ 1525.966942] x86: Booting SMP configuration:
[ 1525.966943] smpboot: Booting Node 0 Processor 1 APIC 0x1
[ 1525.967070] microcode: CPU1: patch_level=0x08001126
[ 1525.969479] CPU1 is up
[ 1525.969512] smpboot: Booting Node 0 Processor 2 APIC 0x2
[ 1525.969618] microcode: CPU2: patch_level=0x08001126
[ 1525.971997] CPU2 is up
[ 1525.972014] smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 1525.972115] microcode: CPU3: patch_level=0x08001126
[ 1525.974581] CPU3 is up
[ 1525.974598] smpboot: Booting Node 0 Processor 4 APIC 0x4
[ 1525.974777] microcode: CPU4: patch_level=0x08001126
[ 1525.977157] CPU4 is up
[ 1525.977172] smpboot: Booting Node 0 Processor 5 APIC 0x5
[ 1525.977272] microcode: CPU5: patch_level=0x08001126
[ 1525.979684] CPU5 is up
[ 1525.979698] smpboot: Booting Node 0 Processor 6 APIC 0x6
[ 1525.979805] microcode: CPU6: patch_level=0x08001126
[ 1525.982225] CPU6 is up
[ 1525.982240] smpboot: Booting Node 0 Processor 7 APIC 0x7
[ 1525.982340] microcode: CPU7: patch_level=0x08001126
[ 1525.984793] CPU7 is up
[ 1525.984807] smpboot: Booting Node 0 Processor 8 APIC 0x8
[ 1525.984966] microcode: CPU8: patch_level=0x08001126
[ 1525.987499] CPU8 is up
[ 1525.987515] smpboot: Booting Node 0 Processor 9 APIC 0x9
[ 1525.987657] microcode: CPU9: patch_level=0x08001126
[ 1525.990205] CPU9 is up
[ 1525.990223] smpboot: Booting Node 0 Processor 10 APIC 0xa
[ 1525.990380] microcode: CPU10: patch_level=0x08001126
[ 1525.992915] CPU10 is up
[ 1525.992931] smpboot: Booting Node 0 Processor 11 APIC 0xb
[ 1525.993072] microcode: CPU11: patch_level=0x08001126
[ 1525.995664] CPU11 is up
[ 1525.995680] smpboot: Booting Node 0 Processor 12 APIC 0xc
[ 1525.995840] microcode: CPU12: patch_level=0x08001126
[ 1525.998447] CPU12 is up
[ 1525.998463] smpboot: Booting Node 0 Processor 13 APIC 0xd
[ 1525.998608] microcode: CPU13: patch_level=0x08001126
[ 1526.001271] CPU13 is up
[ 1526.001286] smpboot: Booting Node 0 Processor 14 APIC 0xe
[ 1526.001448] microcode: CPU14: patch_level=0x08001126
[ 1526.004078] CPU14 is up
[ 1526.004096] smpboot: Booting Node 0 Processor 15 APIC 0xf
[ 1526.004241] microcode: CPU15: patch_level=0x08001126
[ 1526.006914] CPU15 is up
[ 1526.008486] ACPI: Waking up from system sleep state S3
[ 1526.009222] ACPI: EC: interrupt unblocked
[ 1526.091633] ACPI: EC: event unblocked
[ 1526.091752] usb usb1: root hub lost power or was reset
[ 1526.091755] usb usb2: root hub lost power or was reset
[ 1526.092132] sd 2:0:0:0: [sda] Starting disk
[ 1526.092133] sd 3:0:0:0: [sdb] Starting disk
[ 1526.263802] nvme nvme0: 7/0/0 default/read/poll queues
[ 1526.404206] ata1: SATA link down (SStatus 0 SControl 300)
[ 1526.404590] ata8: SATA link down (SStatus 0 SControl 300)
[ 1526.406024] ata7: SATA link down (SStatus 0 SControl 300)
[ 1526.406025] ata9: SATA link down (SStatus 0 SControl 300)
[ 1526.406214] ata6: SATA link down (SStatus 0 SControl 300)
[ 1526.406234] ata2: SATA link down (SStatus 0 SControl 300)
[ 1526.406251] ata5: SATA link down (SStatus 0 SControl 300)
[ 1526.566125] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1526.566192] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1526.566874] ata3.00: supports DRM functions and may not be fully accessible
[ 1526.567538] ata3.00: supports DRM functions and may not be fully accessible
[ 1526.568113] ata3.00: configured for UDMA/133
[ 1526.570389] ata4.00: configured for UDMA/133
[ 1526.766947] usb 2-8: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 1526.915259] usb 2-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 1527.062207] usb 1-12: reset full-speed USB device number 6 using xhci_hcd
[ 1527.418199] usb 1-7: reset full-speed USB device number 3 using xhci_hcd
[ 1527.774279] usb 1-8: reset high-speed USB device number 4 using xhci_hcd
[ 1527.930862] usb 1-11: reset full-speed USB device number 5 using xhci_hcd
[ 1528.294593] usb 1-6: reset full-speed USB device number 2 using xhci_hcd
[ 1528.606601] usb 1-8.4: reset full-speed USB device number 8 using xhci_hcd
[ 1528.922571] usb 1-8.5: reset high-speed USB device number 9 using xhci_hcd
[ 1528.926534] igb 0000:23:00.0 enp35s0: Reset adapter
[ 1529.054583] usb 1-8.3: reset full-speed USB device number 7 using xhci_hcd
[ 1529.305510] fbcon: Taking over console
[ 1529.305523] OOM killer enabled.
[ 1529.305524] Restarting tasks ...
[ 1529.306911] Console: switching to colour frame buffer device 210x65
[ 1529.312559] done.
[ 1529.326131] PM: suspend exit
[ 1532.702607] igb 0000:23:00.0 enp35s0: igb: enp35s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Contr
ol: RX/TX
[ 1532.702925] IPv6: ADDRCONF(NETDEV_CHANGE): enp35s0: link becomes ready
[ 1534.487446] kauditd_printk_skb: 21 callbacks suppressed
[ 1534.487448] audit: type=1400 audit(1591215829.516:33): apparmor="DENIED" operation="capable" profil
e="/usr/sbin/cups-browsed" pid=4296 comm="cups-browsed" capability=23 capname="sys_nice"

**mastablasta** · June 4th, 2020

open KsystemLog to view other logs. https://userbase.kde.org/KSystemLog

also logs are in /var/log/

Code:

[ 1525.511249] ACPI: EC: interrupt blocked
[ 1525.589845] ACPI: Preparing to enter system sleep state S3
[ 1525.917860] ACPI: EC: event blocked
[ 1525.917861] ACPI: EC: EC stopped

check settings in UEFI, check if you have it updated (or if any of the available UEFI updates fixes such an issue).

I am not sure from your post, if this only happens when PC is idle or at random.

if PC is freezing at random, make sure it is not an overheat issue. Psensor application can help you with a nice GUI for lm_sensors.

it could be an issue with ACPI. if that is the case, there are some kernel switches available as well as settings in UEFI. check what is setup.

edit:

However recently within the last week, I noticed that my computer will freeze with the screens off, if I leave it for an hour or two. Screens will remain off, keyboard and mouse input do nothing.

try pressing the ON button on the box. It could be that it is only hibernating.

**jorxster** · June 7th, 2020

Thanks Mastablasta,

The issue with KSystemLog is that it only captures logs from the current session -- once I've force rebooted, I've lost those logs, it seems. (Or are they backed up somewhere?)

By the way, I have more details. I disabled "Screen Energy Saving" to leave screens on and now what happens is this : I leave it locked, and the keyboard input no longer does anything, but the mouse is fine. So I'm stuck at a lockscreen where my mouse moves perfectly fine, but typing on the keyboard does nothing. Not even after unplugging USB and re-plugging into a different port.
Also, because my keyboard or inputs quits working, I can't switch to a pseudoterminal (teleterminal?) and access my computer that way.

So something is locking up X or KDE / blocking my keyboard after being left idle for an hour, and I can't figure out what it is... my only option is to force reboot the machine.

Do my logs get backed up somewhere else?

cheers,
Jordan

**CelticWarrior** · June 7th, 2020

Have you installed Nvidia drivers? Not mentioned so I assume not installed.

**jorxster** · June 10th, 2020

Originally Posted by CelticWarrior

Have you installed Nvidia drivers? Not mentioned so I assume not installed.

Thank you CelticWarrior -- I do have the latest installed via Ubuntu official sources -- nvidia-driver-440.
That's an interesting point, maybe I should try downgrading to 435 to see if that helps.

**mastablasta** · June 11th, 2020

Originally Posted by jorxster

Do my logs get backed up somewhere else?

how to view log files in temrinal: https://www.cyberciti.biz/faq/linux-...ew-logs-files/

they are found in /var/log

you will find the old ones with extension .old next to them. sometimes they are compressed (.tar.gz). and if i am not mistaking, there should be an option in KsystemLog to see old logs as well.

https://docs.kde.org/trunk5/en/kdead...g/reading.html

if you can't open them in KsystemLog, you can view them in Kate (the KDE text editor) just as well. unkompress them using ark (if they are compressed) and then double click them or right click and open with Kate. they might also open in log viewer. i just got used to view them in editor.