System freeze after wake up from Sleep

I recently went from one version of Kernel to another 5.4.124-1-MANJARO to 5.10.42-1-MANJARO #1 SMP PREEMPT and now I just get black screens after ‘Waking Up’.

inxi -Fza

 System:    Kernel: 5.10.42-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 
            parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64 
            root=UUID=a66ca518-1630-4d5f-9a30-977822520ecd rw loglevel=3 quiet 
            Desktop: KDE Plasma 5.21.5 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM 
            Distro: Manjaro Linux base: Arch Linux 
 Machine:   Type: Desktop Mobo: ASUSTeK model: P7P55D-E v: Rev 1.xx serial: <filter> 
            BIOS: American Megatrends v: 1601 date: 06/26/2012 
 CPU:       Info: Quad Core model: Intel Core i7 860 bits: 64 type: MT MCP arch: Nehalem 
            family: 6 model-id: 1E (30) stepping: 5 microcode: A cache: L2: 8 MiB 
            flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 58592 
            Speed: 1799 MHz min/max: N/A Core speeds (MHz): 1: 1799 2: 2335 3: 2673 4: 2294 
            5: 1989 6: 3038 7: 1975 8: 2104 
            Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
            Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
            Type: mds 
            status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable 
            Type: meltdown mitigation: PTI 
            Type: spec_store_bypass 
            mitigation: Speculative Store Bypass disabled via prctl and seccomp 
            Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
            Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
            STIBP: conditional, RSB filling 
            Type: srbds status: Not affected 
            Type: tsx_async_abort status: Not affected 
 Graphics:  Device-1: NVIDIA GM206 [GeForce GTX 960] vendor: Gigabyte driver: nvidia v: 465.31 
            alternate: nouveau,nvidia_drm bus-ID: 06:00.0 chip-ID: 10de:1401 class-ID: 0300 
            Device-2: Huawei UVC Camera type: USB driver: snd-usb-audio,uvcvideo bus-ID: 2-1.4:4 
            chip-ID: 12d1:4321 class-ID: 0102 serial: <filter> 
            Display: x11 server: X.Org 1.20.11 compositor: kwin_x11 driver: loaded: nvidia 
            display-ID: :0 screens: 1 
            Screen-1: 0 s-res: 5888x1152 s-dpi: 101 s-size: 1481x293mm (58.3x11.5") 
            s-diag: 1510mm (59.4") 
            Monitor-1: DVI-I-1 res: 2048x1152 hz: 60 dpi: 102 size: 510x290mm (20.1x11.4") 
            diag: 587mm (23.1") 
            Monitor-2: HDMI-0 res: 1920x1080 dpi: 93 size: 527x296mm (20.7x11.7") 
            diag: 604mm (23.8") 
            Monitor-3: DP-0 res: 1920x1080 hz: 60 dpi: 96 size: 509x286mm (20.0x11.3") 
            diag: 584mm (23") 
            OpenGL: renderer: NVIDIA GeForce GTX 960/PCIe/SSE2 v: 4.6.0 NVIDIA 465.31 
            direct render: Yes 
 Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: ASUSTeK 
            driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56 class-ID: 0403 
            Device-2: NVIDIA GM206 High Definition Audio vendor: Gigabyte driver: snd_hda_intel 
            v: kernel bus-ID: 06:00.1 chip-ID: 10de:0fba class-ID: 0403 
            Device-3: Huawei UVC Camera type: USB driver: snd-usb-audio,uvcvideo bus-ID: 2-1.4:4 
            chip-ID: 12d1:4321 class-ID: 0102 serial: <filter> 
            Sound Server-1: ALSA v: k5.10.42-1-MANJARO running: yes 
            Sound Server-2: JACK v: 0.125.0 running: no 
            Sound Server-3: PulseAudio v: 14.2 running: yes 
            Sound Server-4: PipeWire v: 0.3.30 running: no 
 Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
            vendor: ASUSTeK M4A785/P7P55 driver: r8169 v: kernel port: a800 bus-ID: 02:00.0 
            chip-ID: 10ec:8168 class-ID: 0200 
            IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
 Drives:    Local Storage: total: 1.39 TiB used: 311.02 GiB (21.8%) 
            SMART Message: Unable to run smartctl. Root privileges required. 
            ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10EARS-00Y5B1 
            size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: <unknown> 
            serial: <filter> rev: 0A80 scheme: MBR 
            ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 EVO 500GB 
            size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: <unknown> 
            rotation: SSD serial: <filter> rev: 3B6Q scheme: MBR 
            ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: SanDisk model: Ultra Luxe 
            size: 28.65 GiB block-size: physical: 512 B logical: 512 B serial: <filter> rev: 1.00 
            scheme: MBR 
            SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
 Partition: ID-1: / raw-size: 368.03 GiB size: 361.25 GiB (98.16%) used: 298.77 GiB (82.7%) 
            fs: ext4 dev: /dev/sdb2 maj-min: 8:18 
 Swap:      Alert: No swap data was found. 
 Sensors:   System Temperatures: cpu: 35.5 C mobo: 27.0 C gpu: nvidia temp: 46 C 
            Fan Speeds (RPM): cpu: 1430 psu: 0 case-1: 0 case-2: 0 gpu: nvidia fan: 0% 
            Power: 12v: 12.26 5v: N/A 3.3v: 3.41 vbat: N/A 
 Info:      Processes: 239 Uptime: 27m wakeups: 0 Memory: 15.63 GiB used: 3.8 GiB (24.3%) 
            Init: systemd v: 248 tool: systemctl Compilers: gcc: 11.1.0 Packages: 1525 
            pacman: 1520 lib: 436 flatpak: 0 snap: 5 Shell: Bash v: 5.1.8 running-in: konsole 
            inxi: 3.3.04 

This system is a Frankenstein, and certainly due for at least a new Mobo (on the most recent BIOS I believe)/CPU - which will happen eventually. I could go back to 5.4.124-1, but 5.10.42-1 seems much snappier…?

I edited your post so that the command output has a more appropriate formatting.

Thanks! I appreciate the cleanup, and will try not to repeat.


[samuela@SAManjaro ~]$ uname -a
Linux SAManjaro **5.13.19-2-MANJARO #**1 SMP PREEMPT Sun Sep 19 21:31:53 UTC 2021 x86_64 GNU/Linux

Kind of wish I knew what the problem was, but I’ll take it!

That kernel is EOL and you should switch to latest LTS or a newer one.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.