Help to identify the cause of system freeze

Hi,

I have a HP Pavilion 15-cs1056tx. Only Linux inside. Since I did a fresh install, I installed Nvidia driver and after some minutes of using it, I’m facing randomly system freeze, and I don’t know where to look at to diagnose the issue. I read some posts, and they suggested starting with

journalctl

, but there is nothing wrong there. What else can I do?

System:    Kernel: 5.3.18-59.19-default x86_64 bits: 64 compiler: gcc v: 7.5.0 Console: tty 1 
           Distro: openSUSE Leap 15.3 
Machine:   Type: Laptop System: HP product: HP Pavilion Laptop 15-cs1xxx v: Type1ProductConfigId 
           serial: <filter> 
           Mobo: HP model: 84C1 v: 15.32 serial: <filter> UEFI: Insyde v: F.23 date: 12/25/2020 
Battery:   ID-1: BAT0 charge: 24.1 Wh condition: 24.1/24.1 Wh (100%) model: HP Primary status: Full 
CPU:       Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP arch: Kaby Lake rev: B 
           L2 cache: 8192 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31999 
           Speed: 700 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 687 2: 695 3: 700 4: 700 5: 700 6: 673 
           7: 689 8: 667 
Graphics:  Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] vendor: Hewlett-Packard driver: i915 v: kernel 
           bus ID: 00:02.0 
           Device-2: NVIDIA GP108M [GeForce MX150] vendor: Hewlett-Packard driver: nvidia v: 470.63.01 
           bus ID: 02:00.0 
           Device-3: Lite-On HP Wide Vision FHD Camera type: USB driver: uvcvideo bus ID: 1-3:3 
           Display: server: X.org 1.20.3 driver: modesetting unloaded: fbdev,vesa tty: 114x30 
           Message: Advanced graphics data unavailable in console for root. 
Audio:     Device-1: Intel Cannon Point-LP High Definition Audio vendor: Hewlett-Packard driver: snd_hda_intel 
           v: kernel bus ID: 00:1f.3 
           Sound Server: ALSA v: k5.3.18-59.19-default 
Network:   Device-1: Intel Cannon Point-LP CNVi [Wireless-AC] driver: iwlwifi v: kernel port: 5000 
           bus ID: 00:14.3 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard 
           driver: r8169 v: kernel port: 3000 bus ID: 04:00.0 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 212.16 GiB (22.8%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB 
RAID:      Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 bus ID: 00:17.0 
Partition: ID-1: / size: 220.18 GiB used: 6.55 GiB (3.0%) fs: ext4 dev: /dev/sda2 
           ID-2: /home size: 694.45 GiB used: 205.60 GiB (29.6%) fs: ext4 dev: /dev/sda3 
Swap:      Alert: No Swap data was found. 
Sensors:   System Temperatures: cpu: 50.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 227 Uptime: N/A Memory: 15.52 GiB used: 1.72 GiB (11.1%) Init: systemd runlevel: 5 
           Compilers: gcc: 7.5.0 Shell: bash v: 4.4.23 inxi: 3.1.00 

Welcome to the forum!

Can you, using Ctrl+Alt+F1 still open a virtual console if the system hangs?

Yes, I can.

@oldcastle:

The system configuration indicates that you have 16 GB physical main memory installed – looking at the HP information, it’s a Laptop with 8 GB memory (by default).

  • Be that as it may, you seem to not have configured a Swap partition – if and when Hibernation with EFI lockdown becomes possible, you’ll never be able to Hibernate that Laptop.

Please consider configuring an 16 GB Swap partition.

Can you please confirm the amount of physical main memory installed in that Laptop?

Also, I suspect that, the Laptop supports UEFI – please consider using UEFI Secure Boot which means that, a 500 MB EFI partition is needed.

The size of your system partition (including /tmp /var & Co.) – usually on a Laptop, personally, I wouldn’t configure a System partition with more than 80 GB (or 80 GiB – a little bit more but, the units on the configuration tool are what really matter).

  • Actually, if “ext4
    ” partition(s) on a Laptop, consider carefully a configuration with one large combined System and User partition …

My laptop has 16GB of memory. Because of that, I had no swap setup. At least, it’s what I found on the Internet. A lot of people said that swap nowadays are not necessary anymore.

I’m doing UEFI Secure Boot.

Here my disk layout

lsblk -l
NAME   FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda                                                                           
├─sda1 vfat   FAT16       174A-4A29                               195M     2% /boot/efi
├─sda2 ext4   1.0         8a559eb3-c8f4-4be0-98fa-75d6993e3f82  202.4G     3% /
└─sda3 ext4   1.0         de0ac128-6e6d-4b72-a24f-92af352e64ec  453.5G    30% /home

Look twice. Post what you think isn’t wrong. Change log level to debug: https://freedesktop.org/wiki/Software/systemd/Debugging/

Post command + its output + new command prompt, not only output.
Disable Intel’s fake RAID in BIOS by selecting AHCI mode, then reinstall OS with setting swap 2 GiB or more.
You may select swap as a partition or as a file or as a combination.
During reinstallation set ESP as FAT32, not FAT16.

Then ask those people about your troubles.

Not needed. User may set swap file.

Not needed. See Bug 1177358.

One large combined System and User partition has its own flaws.

Yes, yes – there’s a lot of that on “the Net” …

Bottom line –

  • If the system needs to have the capability to hibernate, a Swap partition the same size as the physical memory is needed.
    *=2]Yes, yes – currently the Linux Kernel doesn’t allow hibernation if UEFI Secure Boot is enabled but, that’s currently being worked on …
    0.000000] kernel: secureboot: Secure boot enabled
    0.000000] kernel: Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7
    0.004756] kernel: secureboot: Secure boot enabled
    1.867304] *kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7*
    1.982502] systemd[1]: Created slice Slice /system/systemd-hibernate-resume.
    4.304190] systemd[1]: Reached target Initrd Root Device.
    4.304798] systemd[1]: Starting Resume from hibernation using device /dev/disk/by-id/ata-Intenso_SSD_Sata_III_AA000000000000035990-part3...
    4.309544] systemd-hibernate-resume[401]: Could not resume from '/dev/disk/by-id/ata-Intenso_SSD_Sata_III_AA000000000000035990-part3' (8:3).
    4.473748] *kernel: Lockdown: systemd-hiberna: hibernation is restricted; see man kernel_lockdown.7*
    4.473981] *kernel: PM: Image not found (code -22)*
    4.310163] systemd[1]: systemd-hibernate-resume@dev-disk-by\x2did-ata\x2dIntenso_SSD_Sata_III_AA000000000000035990\x2dpart3.service: Succeeded.
    4.310425] systemd[1]: Finished Resume from hibernation using device /dev/disk/by-id/ata-Intenso_SSD_Sata_III_AA000000000000035990-part3.
    4.310549] systemd[1]: Reached target Local File Systems (Pre).
    4.310582] systemd[1]: Reached target Local File Systems.

Bottom line –

  • systemd may, possibly, be ready to handle hibernation wake-up when the Kernel issue with the Hibernation Image has been resolved – we’re waiting in a totally relaxed fashion for the resolution of the Kernel issue with Hibernation Images …