Persistent hanging/ freezing of my system

[newbietolinux]

Hi all,

Recently I have experienced system freezing. I’ve noticed the user login takes an unusually long time. On good days, I can use the browser for some time but then the tabs in Firefox freeze or the mouse just stops working. The problem is also not restricted to browser use.When this happens, the system becomes inoperable and REISUB shutdown doesn’t work. I really have no choice but to switch off at the mains, which I don’t like doing at all.

I have tried changing the kernel in the past, but it doesn’t seem to be a long-term solution.

Please can someone advise. My feeling is the problem could be 1) failing hardware, because sometimes it seems as if there are stuck processes, and also Firefox keeps crashing.

It could also be 2) NVIDIA driver issues, although it has been suggested my drivers are supported.

It could be 3) Something about my system and Manjaro.

However, I am not knowledgeable enough to identify the problem. I would be grateful if anyone can help me.

System info:

[manupc@manupc-2 ~]$ inxi --full --admin --filter --width
System:
  Kernel: 6.16.0-5-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.16-x86_64
    root=UUID=1adc77d4-359c-4d50-8e77-204cccc1b265 rw quiet apparmor=1
    security=apparmor udev.log_priority=3 ibt=off
  Desktop: Xfce v: 4.20.1 tk: Gtk v: 3.24.48 wm: xfwm4 v: 4.20.0
    with: xfce4-panel tools: light-locker vt: 7 dm: LightDM v: 1.32.0
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: PRO B660M-E DDR4 (MS-7D46) v: 1.0
    serial: <superuser required> uuid: <superuser required> UEFI: American
    Megatrends LLC. v: 2.00 date: 12/27/2021
CPU:
  Info: model: 12th Gen Intel Core i5-12400F bits: 64 type: MT MCP
    arch: Alder Lake gen: core 12 level: v3 note: check built: 2021+
    process: Intel 7 (10nm ESF) family: 6 model-id: 0x97 (151) stepping: 2
    microcode: 0x3A
  Topology: cpus: 1x dies: 1 clusters: 6 cores: 6 threads: 12 tpc: 2
    smt: enabled cache: L1: 480 KiB desc: d-6x48 KiB; i-6x32 KiB L2: 7.5 MiB
    desc: 6x1.2 MiB L3: 18 MiB desc: 1x18 MiB
  Speed (MHz): avg: 800 min/max: 800/5600 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
    8: 800 9: 800 10: 800 11: 800 12: 800 bogomips: 59904
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB: conditional;
    PBRSB-eIBRS: SW sequence; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GK208B [GeForce GT 730] vendor: ASUSTeK driver: nvidia
    v: 470.256.02 alternate: nouveau,nova_core,nvidia_drm non-free:
    series: 470.xx+ status: legacy-active (EOL~2024-09-xx) arch: Kepler-2
    code: GKxxx process: TSMC 28nm built: 2012-2018 pcie: gen: 2 speed: 5 GT/s
    lanes: 4 link-max: gen: 3 speed: 8 GT/s lanes: 8 ports: active: none
    off: HDMI-A-1 empty: DVI-D-1,VGA-1 bus-ID: 01:00.0 chip-ID: 10de:1287
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.18 compositor: xfwm4 v: 4.20.0 driver:
    X: loaded: N/A failed: nvidia gpu: nvidia,nvidia-nvswitch display-ID: :0.0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 509x286mm (20.04x11.26")
    s-diag: 584mm (22.99")
  Monitor-1: HDMI-0 res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 102
    size: 476x268mm (18.74x10.55") diag: 546mm (21.51") modes: N/A
  API: OpenGL Message: Unable to show GL data. glxinfo is missing.
  Info: Tools: de: xfce4-display-settings gpu: nvidia-settings,nvidia-smi
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl
    bus-ID: 00:1f.3 chip-ID: 8086:7ad0 class-ID: 0403
  Device-2: NVIDIA GK208 HDMI/DP Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel alternate: nova_core pcie: gen: 2 speed: 5 GT/s lanes: 4 link-max:
    gen: 3 speed: 8 GT/s lanes: 8 bus-ID: 01:00.1 chip-ID: 10de:0e0f
    class-ID: 0403
  API: ALSA v: k6.16.0-5-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.7 status: off tools: pw-cli
  Server-3: PulseAudio v: 17.0-43-g3e2bb status: active with: pulseaudio-alsa
    type: plugin tools: pacat,pactl,pavucontrol
Network:
  Device-1: Intel Ethernet I219-V vendor: Micro-Star MSI driver: e1000e
    v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:1a1d class-ID: 0200
  IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter>
  Info: services: httpd, NetworkManager, systemd-timesyncd


Drives:
  Local Storage: total: 476.94 GiB used: 123.11 GiB (25.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Hikvision
    model: HS-SSD-E3000 512G size: 476.94 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: SN06738 temp: 43.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 476.64 GiB size: 468.09 GiB (98.21%)
    used: 123.11 GiB (26.3%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 316 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 34.0 C mobo: N/A gpu: nvidia temp: 32 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB available: 15.47 GiB used: 1.64 GiB (10.6%)
  Processes: 279 Power: uptime: 12m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.14 GiB services: upowerd,xfce4-power-manager
    Init: systemd v: 257 default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 1499 libs: 431 tools: pamac,yay pm: flatpak
    pkgs: 0 Compilers: clang: 20.1.8 gcc: 15.1.1 Shell: Bash v: 5.3.3
    running-in: xfce4-terminal inxi: 3.3.38

[manupc@manupc-2 ~]$ mhwd -l -li
> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2024.05.06                true            PCI
    video-nvidia-470xx            2023.03.23               false            PCI


Warning: No installed USB configs!
> 0000:01:00.0 (0300:10de:1287) Display controller nVidia Corporation:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
    video-nvidia-470xx            2023.03.23               false            PCI
    video-nvidia-390xx            2023.03.23               false            PCI
           video-linux            2024.05.06                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI

[manupc@manupc-2 ~]$ journalctl -b-1 -p4 --no-pager
Aug 20 18:53:18 manjaro kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Aug 20 18:53:18 manjaro kernel: nvme nvme0: missing or invalid SUBNQN field.
Aug 20 18:53:19 manjaro kernel: usb: port power management may be unreliable
Aug 20 18:53:37 manupc-2 kernel: nvidia: loading out-of-tree module taints kernel.
Aug 20 18:53:37 manupc-2 kernel: nvidia: module license 'NVIDIA' taints kernel.
Aug 20 18:53:37 manupc-2 kernel: Disabling lock debugging due to kernel taint
Aug 20 18:53:37 manupc-2 kernel: nvidia: module license taints kernel.
Aug 20 18:53:37 manupc-2 systemd-journald[450]: File /var/log/journal/ebf5243cc0eb4919864f933cbe3fa929/system.journal corrupted or uncleanly shut down, renaming and replacing.
Aug 20 18:53:37 manupc-2 kernel: 
Aug 20 18:53:37 manupc-2 kernel: spi-nor spi0.0: supply vcc not found, using dummy regulator
Aug 20 18:53:37 manupc-2 kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  470.256.02  Thu May  2 14:37:44 UTC 2024
Aug 20 18:53:37 manupc-2 kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
Aug 20 18:53:53 manupc-2 kernel: kauditd_printk_skb: 155 callbacks suppressed
Aug 20 18:53:54 manupc-2 dbus-broker-launch[804]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.
Aug 20 18:53:55 manupc-2 dbus-broker-launch[1195]: Service file '/usr/share//dbus-1/services/org.xfce.Thunar.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
Aug 20 18:53:55 manupc-2 dbus-broker-launch[1195]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.xfce.Thunar.FileManager1.service'
Aug 20 18:53:55 manupc-2 dbus-broker-launch[1195]: Service file '/usr/share//dbus-1/services/org.xfce.Tumbler.Cache1.service' is not named after the D-Bus name 'org.freedesktop.thumbnails.Cache1'.
Aug 20 18:53:55 manupc-2 dbus-broker-launch[1195]: Service file '/usr/share//dbus-1/services/org.xfce.Tumbler.Manager1.service' is not named after the D-Bus name 'org.freedesktop.thumbnails.Manager1'.
Aug 20 18:53:55 manupc-2 dbus-broker-launch[1195]: Service file '/usr/share//dbus-1/services/org.xfce.Tumbler.Thumbnailer1.service' is not named after the D-Bus name 'org.freedesktop.thumbnails.Thumbnailer1'.
Aug 20 18:53:55 manupc-2 dbus-broker-launch[1195]: Service file '/usr/share//dbus-1/services/org.xfce.xfce4-notifyd.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Aug 20 18:53:55 manupc-2 dbus-broker-launch[1195]: Service file '/usr/share//dbus-1/services/org.xfce.xfce4-notifyd.Notifyd.service' is not named after the D-Bus name 'org.xfce.Notifyd'.
Aug 20 18:53:57 manupc-2 dbus-broker-launch[804]: Activation request for 'org.freedesktop.resolve1' failed: The systemd unit 'dbus-org.freedesktop.resolve1.service' could not be found.
Aug 20 18:54:06 manupc-2 lightdm[1227]: gkr-pam: unable to locate daemon control file
Aug 20 18:54:13 manupc-2 kernel: [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:01:b4:b0:24:52:c9:13:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=84 PROTO=2 
Aug 20 18:54:19 manupc-2 systemd-journald[450]: Failed to read journal file /var/log/journal/ebf5243cc0eb4919864f933cbe3fa929/user-1000.journal for rotation, trying to move it out of the way: Device or resource busy
Aug 20 18:54:19 manupc-2 NetworkManager[806]: <warn>  [1755708859.5078] dns-mgr: update-pending changed: DNS plugin did not become ready again. Assume something is wrong
Aug 20 18:54:19 manupc-2 systemd-xdg-autostart-generator[1263]: Configuration file /home/manupc/.config/autostart/xfce-panel-workaround.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
Aug 20 18:54:19 manupc-2 systemd-xdg-autostart-generator[1263]: Configuration file /home/manupc/.config/autostart/xfce-pbw.sh is marked executable. Please remove executable permission bits. Proceeding anyway.
Aug 20 18:54:19 manupc-2 dbus-broker-launch[1273]: Service file '/usr/share//dbus-1/services/org.xfce.Thunar.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
Aug 20 18:54:19 manupc-2 dbus-broker-launch[1273]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.xfce.Thunar.FileManager1.service'
Aug 20 18:54:19 manupc-2 dbus-broker-launch[1273]: Service file '/usr/share//dbus-1/services/org.xfce.Tumbler.Cache1.service' is not named after the D-Bus name 'org.freedesktop.thumbnails.Cache1'.
Aug 20 18:54:19 manupc-2 dbus-broker-launch[1273]: Service file '/usr/share//dbus-1/services/org.xfce.Tumbler.Manager1.service' is not named after the D-Bus name 'org.freedesktop.thumbnails.Manager1'.
Aug 20 18:54:19 manupc-2 dbus-broker-launch[1273]: Service file '/usr/share//dbus-1/services/org.xfce.Tumbler.Thumbnailer1.service' is not named after the D-Bus name 'org.freedesktop.thumbnails.Thumbnailer1'.
Aug 20 18:54:19 manupc-2 dbus-broker-launch[1273]: Service file '/usr/share//dbus-1/services/org.xfce.xfce4-notifyd.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Aug 20 18:54:19 manupc-2 dbus-broker-launch[1273]: Service file '/usr/share//dbus-1/services/org.xfce.xfce4-notifyd.Notifyd.service' is not named after the D-Bus name 'org.xfce.Notifyd'.
Aug 20 18:54:21 manupc-2 colord[1451]: failed to get edid data: EDID length is too small
Aug 20 18:54:22 manupc-2 kernel: nvme nvme0: using unchecked data buffer
Aug 20 18:54:22 manupc-2 tumblerd[1489]: Failed to load plugin "tumbler-gepub-thumbnailer.so": libgepub-0.7.so.0: cannot open shared object file: No such file or directory
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: GFileInfo created without standard::name
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: file ../glib/gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: GFileInfo created without standard::name
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: file ../glib/gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: GFileInfo created without standard::name
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: file ../glib/gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: GFileInfo created without standard::name
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: file ../glib/gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: GFileInfo created without standard::name
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: file ../glib/gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: GFileInfo created without standard::name
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: file ../glib/gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: GFileInfo created without standard::name
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: file ../glib/gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: GFileInfo created without standard::name
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: file ../glib/gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: GFileInfo created without standard::name
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: file ../glib/gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: GFileInfo created without standard::name
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: file ../glib/gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: GFileInfo created without standard::name
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: file ../glib/gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: GFileInfo created without standard::name
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: file ../glib/gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: GFileInfo created without standard::name
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: file ../glib/gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: GFileInfo created without standard::name
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: file ../glib/gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: GFileInfo created without standard::name
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: file ../glib/gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: GFileInfo created without standard::name
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: file ../glib/gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: GFileInfo created without standard::name
Aug 20 18:54:22 manupc-2 gvfsd-trash[1653]: file ../glib/gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
Aug 20 18:54:22 manupc-2 pulseaudio[1365]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.bluez': unit failed
Aug 20 18:56:17 manupc-2 kernel: [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:01:b4:b0:24:52:c9:13:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=182 PROTO=2 
Aug 20 18:58:22 manupc-2 kernel: [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:01:b4:b0:24:52:c9:13:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=214 PROTO=2 
Aug 20 19:00:20 manupc-2 kernel: nvme nvme0: I/O tag 332 (b14c) opcode 0x2 (Read) QID 3 timeout, aborting req_op:READ(0) size:151552
Aug 20 19:00:26 manupc-2 kernel: nvme nvme0: I/O tag 333 (f14d) opcode 0x2 (Read) QID 3 timeout, aborting req_op:READ(0) size:151552
Aug 20 19:00:26 manupc-2 kernel: nvme0n1: Read(0x2) @ LBA 95585480, 296 blocks, Command Abort Requested (sct 0x0 / sc 0x7) 
Aug 20 19:00:26 manupc-2 kernel: I/O error, dev nvme0n1, sector 95585480 op 0x0:(READ) flags 0x80700 phys_seg 7 prio class 0
Aug 20 19:00:26 manupc-2 kernel: nvme nvme0: Abort status: 0x0
Aug 20 19:00:26 manupc-2 kernel: nvme nvme0: Abort status: 0x0
Aug 20 19:00:27 manupc-2 kernel: [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:01:b4:b0:24:52:c9:13:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=234 PROTO=2 
Aug 20 19:02:32 manupc-2 kernel: [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:01:b4:b0:24:52:c9:13:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=259 PROTO=2 
Aug 20 19:04:37 manupc-2 kernel: [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:01:b4:b0:24:52:c9:13:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=279 PROTO=2 
Aug 20 19:06:42 manupc-2 kernel: [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:01:b4:b0:24:52:c9:13:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=287 PROTO=2 
Aug 20 19:07:19 manupc-2 kernel: nvme nvme0: I/O tag 359 (7167) opcode 0x2 (Read) QID 3 timeout, aborting req_op:READ(0) size:167936
Aug 20 19:07:21 manupc-2 kernel: nvme nvme0: I/O tag 37 (a025) opcode 0x2 (Read) QID 4 timeout, aborting req_op:READ(0) size:167936
Aug 20 19:07:21 manupc-2 kernel: nvme0n1: Read(0x2) @ LBA 86504312, 328 blocks, Command Abort Requested (sct 0x0 / sc 0x7) 
Aug 20 19:07:21 manupc-2 kernel: I/O error, dev nvme0n1, sector 86504312 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
Aug 20 19:07:21 manupc-2 kernel: nvme nvme0: Abort status: 0x0
Aug 20 19:07:24 manupc-2 kernel: nvme nvme0: Abort status: 0x0
Aug 20 19:08:47 manupc-2 kernel: [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:01:b4:b0:24:52:c9:13:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=318 PROTO=2 
Aug 20 19:09:06 manupc-2 tumblerd[1489]: Error: Timeout was reached
Aug 20 19:09:53 manupc-2 kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Aug 20 19:09:53 manupc-2 kernel: pcieport 0000:00:01.0:   device [8086:460d] error status/mask=00000001/00002000
Aug 20 19:09:53 manupc-2 kernel: pcieport 0000:00:01.0:    [ 0] RxErr                  (First)
Aug 20 19:09:53 manupc-2 kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Aug 20 19:09:53 manupc-2 kernel: pcieport 0000:00:01.0:   device [8086:460d] error status/mask=00000001/00002000
Aug 20 19:09:53 manupc-2 kernel: pcieport 0000:00:01.0:    [ 0] RxErr                  (First)
Aug 20 19:09:53 manupc-2 kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Aug 20 19:09:53 manupc-2 kernel: pcieport 0000:00:01.0:   device [8086:460d] error status/mask=00000001/00002000
Aug 20 19:09:53 manupc-2 kernel: pcieport 0000:00:01.0:    [ 0] RxErr                  (First)
Aug 20 19:09:53 manupc-2 kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Aug 20 19:09:53 manupc-2 kernel: pcieport 0000:00:01.0:   device [8086:460d] error status/mask=00000001/00002000
Aug 20 19:09:53 manupc-2 kernel: pcieport 0000:00:01.0:    [ 0] RxErr                  (First)
Aug 20 19:09:53 manupc-2 kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Aug 20 19:09:53 manupc-2 kernel: pcieport 0000:00:01.0:   device [8086:460d] error status/mask=00000001/00002000
Aug 20 19:09:53 manupc-2 kernel: pcieport 0000:00:01.0:    [ 0] RxErr                  (First)
Aug 20 19:09:53 manupc-2 kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Aug 20 19:09:53 manupc-2 kernel: pcieport 0000:00:01.0:   device [8086:460d] error status/mask=00000001/00002000
Aug 20 19:09:53 manupc-2 kernel: pcieport 0000:00:01.0:    [ 0] RxErr                  (First)
Aug 20 19:09:55 manupc-2 kernel: NVRM: GPU at PCI:0000:01:00: GPU-1bb351b3-3af0-bc61-8962-96bc46cbecaf
Aug 20 19:09:55 manupc-2 kernel: NVRM: Xid (PCI:0000:01:00): 79, pid=948, GPU has fallen off the bus.
Aug 20 19:09:55 manupc-2 kernel: NVRM: GPU 0000:01:00.0: GPU has fallen off the bus.
Aug 20 19:09:55 manupc-2 kernel: NVRM: A GPU crash dump has been created. If possible, please run
                                 NVRM: nvidia-bug-report.sh as root to collect this data before
                                 NVRM: the NVIDIA kernel module is unloaded.
Aug 20 19:10:01 manupc-2 kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
Aug 20 19:10:11 manupc-2 kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
Aug 20 19:10:21 manupc-2 kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
Aug 20 19:10:31 manupc-2 kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
Aug 20 19:10:42 manupc-2 kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices

[omano]

@newbietolinux

Swap:
  Alert: No swap data was found.

Usual suspect.

Swap

SWAP file is easy and quick to setup.

[Fangdrasil]

@newbietolinux

Micro-Star model: PRO B660M-E DDR4

Can you update your BIOS? If it’s out of date, that’s the first thing I would do.

[Pille]

You have 16 GB of RAM but no swap is set up. That can work, but over time the symptoms you see can occur.

[newbietolinux]

Thank you, @omano, @Fangdrasil @Pille

Maybe SWAP is the problem. I use the shutdown command regularly, could this make things worse with no SWAP?

Could someone please walk me through an optimal SWAP for my configuration?

How often should I update the BIOS and how would i go about doing that?

Finally, what does
Aug 20 19:09:55 manupc-2 kernel: NVRM: GPU 0000:01:00.0: GPU has fallen off the bus. mean in the journalctl output. Is this significant to my problem or is it more of a result of the problem?

Thank you all for your advice and assistance.

[soundofthunder]

@newbietolinux

Could someone please walk me through an optimal SWAP for my configuration?

@omano

Swap - Manjaro

SWAP file is easy and quick to setup.

@newbietolinux

At a very basic level, the amount of swap suitable for any given system can vary depending on whether or not you want to use hibernation.

By way of example, when installing Manjaro using Calamares the defaults are;

• With hibernation: A swap partition is created to equal the amount of physical RAM in your system. It’s also common practice to add a few GB on top of that amount.
• Without hibernation: Approximately half that size.

The link already given by @omano should ideally be the only walkthrough you need; though the Arch Wiki also features some more advanced information which might be of interest.

• Swap (Arch Wiki)
• Zswap (Arch Wiki)
• Improving performance - Zram / Zswap (Arch Wiki)
• Power management - Suspend / Hibernate (Arch Wiki)

---

@newbietolinux

could this make things worse with no SWAP?

Having no swap (at all) can be a contributor in cases such as you describe. If using a swap file, if / is running low on space, this can also be a factor.

---

@newbietolinux

How often should I update the BIOS and how would i go about doing that?

There is no golden answer to that.

Although, it’s probably a good idea to check the mainboard manufacturer website every three to six months in case an updated non-beta BIOS is available; follow the information they provide to determine if it’s relevant to your hardware.

Directions for updating the BIOS can vary across brands, but instructions are typically found on the manufacturer site. While you’re on the site, I’d recommend you also download any user manuals or guides available for your machine.

Regards.

[omano]

@newbietolinux

Could someone please walk me through an optimal SWAP for my configuration?

Open the WIKI page, follow instructions to add a SWAP file (the Creating and Enabling a Static Swapfile part), maybe edit the first command so you make a bigger SWAP file (I would do at least 16G - 16384, instead of 4G - 4096).

You should also monitor hardware for failure, check temperatures maybe it overheats and crash. Commands:

CPU: s-tui install it if command not found
GPU: nvidia-smi

[newbietolinux]

Thank you @omano @soundofthunder

I will use the WIKI page to add a Swap file and check hardware as directed.I will also see if I can update the BIOS.

I hope you will all allow me to come back to you if i run into problems, but let’s see what I can do.

Thank you.

[omano]

before updating the BIOS, I would make sure the package install-grub is installed, and ran sudo install-grub to make sure you can boot Manjaro after the BIOS update, or else you will need a Manjaro live USB ISO to restore GRUB manually.

[terashy88]

For your swapfile you can run my script and from your 500 GB Disk I would give like 8000 MB for your Swapfile and see how it goes.

swapfile

swap-activate() {
    # swapfile
    # https://wiki.manjaro.org/index.php/Swap
    set -e

    # set swapfile path
    path_="/swapfile"

    # convert diskspace to MB
    diskspace="$(df --output=avail -B1 / | tail -n 1)"
    diskspace=$((diskspace / 1024 / 1024)) # Convert GB to MB

    while true; do

        echo "How much MB should your swapfile have?"
        echo "Free space is $diskspace MB"
        echo "   Enter here: "
        read -r i

        # number check
        if ! [[ "$i" =~ ^[0-9]+$ ]]; then

            echo "Memory size must be numbers"
            continue
        fi

        # Diskspace check
        if [[ $i -ge $diskspace ]]; then

            echo "Not enough disk space to create a swapfile of ${i} MB."
            continue
        fi

        # lesser then 1
        if [[ $i -le 0 ]]; then
            echo "${i} MB is a invalid value."
            continue
        fi

        break
    done

    echo -e 'Do you want to use \e[38;2;242;29;0m'"${i}"'\e[0m MB?'
    echo "Press y are Enter to continue"

    read -r r

    if [[ "$r" =~ ^[Yy]$ ]] || [[ "$r" == "" ]]; then

        # Trap signals to perform cleanup actions
        cleanup_() {
            pid=''

            if swapon --show | grep -q "file"; then
                echo "deleting old swapfile"
                sudo swapoff $path_ &
                pid=$!

                while kill -0 ${pid} >/dev/null 2>&1; do
                    sleep 2
                    echo "please wait"
                done
            fi

            [[ -e $path_ ]] && sh -c "sudo rm $path_"

        }
        cleanup_

        # build swapfile
        sudo dd if=/dev/zero of=$path_ bs=1M count="$i" status=progress || {
            echo "Error creating swapfile"
            sleep 3
        }
        # set permission
        if sh -c "sudo chmod 600 $path_"; then
            echo "chmod 600 $path_"
        else
            echo "Error changing permissions"
            sleep 3
            exit 1
        fi
        # create swapfile
        sudo mkswap $path_ || {
            echo "Error setting up swap"
            sleep 3
            exit 1
        }
        # aktive swap
        sudo swapon $path_ || {
            echo "Error activating swap"
            sleep 3
            exit 1
        }

        # config swap
        sudo sh -c " cat <<'EOF' >/etc/sysctl.d/99-swappiness.conf

    vm.swappiness=11
    vm.vfs_cache_pressure=66
    vm.dirty_ratio=3
    # sudo sysctl vm.vfs_cache_pressure=100
    # sudo sysctl vm.swappiness=60
    # sudo mkinitcpio -P
    # sudo sysctl --system
EOF
"

        # set fstab
        if sudo sh -c "grep -q $path_ /etc/fstab"; then
            echo "Entry already exists in /etc/fstab"
        else
            sudo sh -c "echo \"$path_ none swap defaults 0 0\" >> /etc/fstab"
            echo "Entry added to /etc/fstab"
        fi
    else
        echo "swapfile cancelled.."
    fi

    # show swap
    if [[ -e $path_ ]]; then
        swapon --show
    fi
}
swap-activate

[newbietolinux]

@omano @soundofthunder @terashy88

Can I just clarify: do i need to make the swap file from chroot in a live USB or can I make changes with a straightforward login?

Also, I welcome all assistance and two trusted opinions suggest 16384 and 8000, is it a big difference between the two?

[terashy88]

No, you can run it from the terminal, just make sure you’re not using a lot of RAM in the background at the time.

And you can run the script at any time again to change the size.

I would go with 8000 MB first and if you’re still having problem you can go higher.

Also with htop you could first check the RAM uses in the first place if you are running out of RAM and adjust the swap-file correctly

[newbietolinux]

@terashy88 @omano

The problem is so bad that the system keeps freezing even as I read this forum page.

I have therefore booted with a live USB using open source drivers and will have to make the swap file through chroot.

So can I copy-paste the script as is into the terminal or do i need to change values within the script? The script looks a bit of a challenge for a newbie as i need to know which values to change and where, for example, where to set 8000.
It may be easier for me to input the commands laid out in the Wiki page. Will this have the identical effect?

Actually, can it be done through chroot at all? I’m thinking manjaro-chroot -a as my chroot command and then just copy-pasting the script or the commands laid out in the Wiki ?
Sorry, still quite a newbie.

[terashy88]

I did not test it in chroot, it should work if you are su to your USERNAME.

Run it in the terminal means run it in the terminal by copy and paste it and be login as USER (Your Username).

If you want to do it while on a live USB then please check with the official page:

Swap

[newbietolinux]

So I just copy-paste the script when logged as a user? Great.

I will try login as a user. Maybe i can get by without another system freeze.

There is still a chance that the system will freeze mid-process and i will have no choice but to switch off at the mains. Could i lose my entire system if that happens?

[terashy88]

@newbietolinux

Could i lose my entire system if that happens?

Should not, but make sure you have backup does stuff that is important for you:

[HowTo] make a crash-proof backup in Manjaro for your entire system

Difficulty: ★★☆☆☆ If you follow the tutorial completely, you will be able to create a backup of your entire system not only limited to Manjaro, but also including Windows, RHEL, Ubuntu, … and whatever else you might have installed on your system! Even if you replace your HDD by an SSD, your HDD crashes, your entire system gets stolen, … you can always restore a Cold System backup to an identical system (You cannot restore E.G. a Dell XPS onto a Dell PowerEdge and then expect that to w…

[newbietolinux]

@terashy88

Is that it? Do i need to do more?

How do I view my new swap file in system? And thank you so very much for making this script.

manupc-2 manupc]#  swapfile


swap-activate() {
    # swapfile
    # https://wiki.manjaro.org/index.php/Swap
    set -e

    # set swapfile path
    path_="/swapfile"

    # convert diskspace to MB
    diskspace="$(df --output=avail -B1 / | tail -n 1)"
    diskspace=$((diskspace / 1024 / 1024)) # Convert GB to MB

    while true; do

        echo "How much MB should your swapfile have?"
        echo "Free space is $diskspace MB"
        echo "   Enter here: "
        read -r i

        # number check
        if ! [[ "$i" =~ ^[0-9]+$ ]]; then

            echo "Memory size must be numbers"
            continue
        fi

        # Diskspace check
        if [[ $i -ge $diskspace ]]; then

            echo "Not enough disk space to create a swapfile of ${i} MB."
            continue
        fi

        # lesser then 1
        if [[ $i -le 0 ]]; then
            echo "${i} MB is a invalid value."
            continue
        fi

        break
    done

    echo -e 'Do you want to use \e[38;2;242;29;0m'"${i}"'\e[0m MB?'
    echo "Press y are Enter to continue"

    read -r r

    if [[ "$r" =~ ^[Yy]$ ]] || [[ "$r" == "" ]]; then

        # Trap signals to perform cleanup actions
        cleanup_() {
            pid=''

            if swapon --show | grep -q "file"; then
                echo "deleting old swapfile"
                sudo swapoff $path_ &
                pid=$!

                while kill -0 ${pid} >/dev/null 2>&1; do
                    sleep 2
                    echo "please wait"
                done
            fi

            [[ -e $path_ ]] && sh -c "sudo rm $path_"

        }
        cleanup_

        # build swapfile
        sudo dd if=/dev/zero of=$path_ bs=1M count="$i" status=progress || {
            echo "Error creating swapfile"
            sleep 3
            exit 1
        }
        # set permission
        if sh -c "sudo chmod 600 $path_"; then
            echo "chmod 600 $path_"
        else
            echo "Error changing permissions"
            sleep 3
            exit 1
        fi
        # create swapfile
        sudo mkswap $path_ || {
            echo "Error setting up swap"
            sleep 3
            exit 1
        }
        # aktive swap
        sudo swapon $path_ || {
            echo "Error activating swap"
            sleep 3
            exit 1
        }

        # config swap
        sudo sh -c " cat <<'EOF' >/etc/sysctl.d/99-swappiness.conf

    vm.swappiness=11
    vm.vfs_cache_pressure=66
    vm.dirty_ratio=3
    # sudo sysctl vm.vfs_cache_pressure=100
    # sudo sysctl vm.swappiness=60
    # sudo mkinitcpio -P
    # sudo sysctl --system
EOF
"

        # set fstab
        if sudo sh -c "grep -q $path_ /etc/fstab"; then
            echo "Entry already exists in /etc/fstab"
        else
            sudo sh -c "echo \"$path_ none swap defaults 0 0\" >> /etc/fstab"
            echo "Entry added to /etc/fstab"
        fi
    else
        echo "swapfile cancelled.."
    fi

    # show swap
    if [[ -e $path_ ]]; then
        swapon --show
    fi
}
swap-activate


bash: swapfile: command not found
How much MB should your swapfile have?
Free space is 330279 MB
   Enter here: 
8000
Do you want to use 8000 MB?
Press y are Enter to continue
y
[manupc@manupc-2 ~]$

[terashy88]

Did you run it?

If it works, you should see it with:

  swapon --show

What does your swapon --show print out?

[newbietolinux]

@terashy88

swapon --show

No print out.

[manupc@manupc-2 ~]$ swapon --show
[manupc@manupc-2 ~]$

Maybe a really dumb question, but was i meant to run the script only after the commands from the Wiki page?

[terashy88]

@newbietolinux

Do you want to use 8000 MB?
Press y are Enter to continue
y

After you type y you have to Press Enter as well…

❯ swap-activate
How much MB should your swapfile have?
Free space is 298778 MB
   Enter here: 
44444
Do you want to use 44444 MB?
Press y are Enter to continue
y
deleting old swapfile
[4] 59373
please wait
please wait