What Logs Should I Collect To Troubleshoot an Issue?

[Jack_Sparrow]

My Debian installation randomly freezes, and I'd like to get to the bottom of this issue. What logs should I collect and post in order to troubleshoot this issue? At the very least, I can provide you with the output of inxi -Faz --vs --za:

inxi -Faz --vs -zainxi 3.3.38-00 (2025-04-06)System:  Kernel: 6.12.73+deb13-amd64 arch: x86_64 bits: 64 compiler: gcc v: 14.2.0    clocksource: tsc avail: hpet,acpi_pm    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.73+deb13-amd64    root=UUID=8151f34b-e904-426d-a0c2-546c1975ac09 ro quiet  Desktop: KDE Plasma v: 6.3.6 tk: Qt v: N/A info: frameworks v: 6.13.0    wm: kwin_wayland tools: avail: cinnamon-screensaver vt: 1 dm: SDDM    Distro: Debian GNU/Linux 13 (trixie)Machine:  Type: Laptop System: Dell product: Latitude E6520 v: 01    serial: <superuser required> Chassis: type: 9 serial: <superuser required>  Mobo: Dell model: 0J4TFW v: A01 serial: <superuser required>    uuid: <superuser required> BIOS: Dell v: A22 date: 09/13/2018Battery:  ID-1: BAT0 charge: 25.5 Wh (100.0%) condition: 25.5/66.6 Wh (38.3%)    volts: 12.5 min: 11.1 model: SMP DELL HTX4D2A type: Li-ion serial: <filter>    status: fullCPU:  Info: model: Intel Core i7-2620M bits: 64 type: MT MCP arch: Sandy Bridge    gen: core 2 level: v2 built: 2010-12 process: Intel 32nm family: 6    model-id: 0x2A (42) stepping: 7 microcode: 0x2F  Topology: cpus: 1x dies: 1 clusters: 2 cores: 2 threads: 4 tpc: 2    smt: enabled cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB    desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB  Speed (MHz): avg: 1379 min/max: 800/3400 scaling: driver: intel_cpufreq    governor: schedutil cores: 1: 1379 2: 1379 3: 1379 4: 1379 bogomips: 21552  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx  Vulnerabilities:  Type: gather_data_sampling status: Not affected  Type: indirect_target_selection status: Not affected  Type: itlb_multihit status: KVM: Split huge pages  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT    vulnerable  Type: mds mitigation: Clear CPU buffers; SMT vulnerable  Type: meltdown mitigation: PTI  Type: mmio_stale_data status: Unknown: No mitigations  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: Retpolines; IBPB: conditional; IBRS_FW;    STIBP: conditional; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not    affected  Type: srbds status: Not affected  Type: tsa status: Not affected  Type: tsx_async_abort status: Not affected  Type: vmscape mitigation: IBPB before exit to userspaceGraphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics    vendor: Dell driver: i915 v: kernel arch: Gen-6 code: Sandybridge    process: Intel 32nm built: 2011 ports: active: LVDS-2 empty: VGA-2    bus-ID: 00:02.0 chip-ID: 8086:0126 class-ID: 0300  Device-2: NVIDIA GF119M [NVS 4200M] vendor: Dell driver: nouveau v: kernel    non-free: series: 390.xx+ status: legacy (EOL~2022-11-22) last:    release: 390.157 kernel: 6.0 xorg: 1.21 arch: Fermi code: GF1xx    process: 40/28nm built: 2010-2016 pcie: gen: 2 speed: 5 GT/s lanes: 16    ports: active: HDMI-A-1 empty: DP-1, DP-2, LVDS-1, VGA-1 bus-ID: 01:00.0    chip-ID: 10de:1056 class-ID: 0300 temp: 48.0 C  Device-3: Ricoh Laptop_Integrated_Webcam_FHD driver: uvcvideo type: USB    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 2-1.5:4    chip-ID: 05ca:181c class-ID: 0e02  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6    compositor: kwin_wayland driver: X: loaded: modesetting unloaded: fbdev,vesa    dri: crocus,nouveau gpu: i915,nouveau d-rect: 1920x1080 display-ID: 0  Monitor-1: HDMI-A-1 pos: primary model: HISENSE serial: <filter>    built: 2023 res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 81 gamma: 1.2    size: 1095x616mm (43.11x24.25") diag: 1388mm (54.6") ratio: 16:9 modes:    max: 1920x1080 min: 640x480  Monitor-2: LVDS-2 pos: primary model: Seiko Epson 0x5448 built: 2010 res:    mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 142 gamma: 1.2    size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9    modes: 1920x1080  API: EGL v: 1.5 hw: drv: intel crocus drv: nvidia nouveau platforms:    device: 0 drv: crocus device: 1 drv: nouveau device: 2 drv: swrast gbm:    drv: crocus surfaceless: drv: crocus wayland: drv: crocus x11: drv: crocus  API: OpenGL v: 4.5 compat-v: 3.3 vendor: intel mesa v: 25.0.7-2 glx-v: 1.4    direct-render: yes renderer: Mesa Intel HD Graphics 3000 (SNB GT2)    device-ID: 8086:0126 memory: 1.46 GiB unified: yes display-ID: :1.0  API: Vulkan v: 1.4.309 layers: 3 device: 0 type: cpu name: llvmpipe (LLVM    19.1.7 256 bits) driver: mesa llvmpipe v: 25.0.7-2 (LLVM 19.1.7)    device-ID: 10005:0000 surfaces: xcb,xlib,wayland  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,    xdpyinfo, xprop, xrandrAudio:  Device-1: Intel 6 Series/C200 Series Family High Definition Audio    vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1b.0    chip-ID: 8086:1c20 class-ID: 0403  Device-2: NVIDIA GF119 HDMI Audio vendor: Dell driver: snd_hda_intel    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 16 bus-ID: 01:00.1    chip-ID: 10de:0e08 class-ID: 0403  API: ALSA v: k6.12.73+deb13-amd64 status: kernel-api    tools: alsactl,alsamixer,amixer  Server-1: PipeWire v: 1.4.2 status: active with: 1: pipewire-pulse    status: active 2: wireplumber status: active    tools: pactl,pw-cat,pw-cli,wpctlNetwork:  Device-1: Intel 82579LM Gigabit Network vendor: Dell driver: e1000e    v: kernel port: 5080 bus-ID: 00:19.0 chip-ID: 8086:1502 class-ID: 0200  IF: eno1 state: down mac: <filter>  Device-2: Broadcom BCM43228 802.11a/b/g/n vendor: Dell Wireless 1530    Half-size Mini PCIe Card driver: bcma-pci-bridge v: N/A modules: bcma    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 14e4:4359    class-ID: 0280  IF-ID-1: tun0 state: unknown speed: 10000 Mbps duplex: full mac: N/A  IF-ID-2: wlp3s0b1 state: up mac: <filter>  Info: services: apache2, NetworkManager, sshd, systemd-timesyncd,    wpa_supplicantBluetooth:  Device-1: Dell DW375 Bluetooth Module driver: btusb v: 0.8 type: USB    rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 2-1.4:3    chip-ID: 413c:8187 class-ID: fe01 serial: <filter>  Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 3.0    lmp-v: 5 sub-v: 4203 hci-v: 5 rev: 205 class-ID: 7c010c  Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch hold sniff park    link-mode: peripheral accept service-classes: rendering, capturing, object    transfer, audio, telephonyRAID:  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci    v: 3.0 port: 5060 bus-ID: 00:1f.2 chip-ID: 8086:282a rev: N/A class-ID: 0104Drives:  Local Storage: total: 238.47 GiB used: 20.35 GiB (8.5%)  SMART Message: Unable to run smartctl. Root privileges required.  ID-1: /dev/sda maj-min: 8:0 vendor: A-Data model: SU760 size: 238.47 GiB    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD    serial: <filter> fw-rev: 4R22 scheme: MBRPartition:  ID-1: / raw-size: 230.52 GiB size: 225.84 GiB (97.97%)    used: 20.35 GiB (9.0%) fs: ext4 dev: /dev/sda1 maj-min: 8:1Swap:  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no  ID-1: swap-1 type: partition size: 7.96 GiB used: 0 KiB (0.0%)    priority: -2 dev: /dev/sda5 maj-min: 8:5Sensors:  System Temperatures: cpu: 55.0 C mobo: 34.0 C sodimm: 43.0 C gpu: nouveau    temp: 48.0 C  Fan Speeds (rpm): cpu: 2711Info:  Memory: total: 8 GiB available: 7.65 GiB used: 1.73 GiB (22.6%)  Processes: 211 Power: uptime: 27m states: freeze,mem,disk suspend: deep    avail: s2idle
inxi -Faz --vs -za
inxi 3.3.38-00 (2025-04-06)
System:
  Kernel: 6.12.73+deb13-amd64 arch: x86_64 bits: 64 compiler: gcc v: 14.2.0
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.73+deb13-amd64
    root=UUID=8151f34b-e904-426d-a0c2-546c1975ac09 ro quiet
  Desktop: KDE Plasma v: 6.3.6 tk: Qt v: N/A info: frameworks v: 6.13.0
    wm: kwin_wayland tools: avail: cinnamon-screensaver vt: 1 dm: SDDM
    Distro: Debian GNU/Linux 13 (trixie)
Machine:
  Type: Laptop System: Dell product: Latitude E6520 v: 01
    serial: <superuser required> Chassis: type: 9 serial: <superuser required>
  Mobo: Dell model: 0J4TFW v: A01 serial: <superuser required>
    uuid: <superuser required> BIOS: Dell v: A22 date: 09/13/2018
Battery:
  ID-1: BAT0 charge: 25.5 Wh (100.0%) condition: 25.5/66.6 Wh (38.3%)
    volts: 12.5 min: 11.1 model: SMP DELL HTX4D2A type: Li-ion serial: <filter>
    status: full
CPU:
  Info: model: Intel Core i7-2620M bits: 64 type: MT MCP arch: Sandy Bridge
    gen: core 2 level: v2 built: 2010-12 process: Intel 32nm family: 6
    model-id: 0x2A (42) stepping: 7 microcode: 0x2F
  Topology: cpus: 1x dies: 1 clusters: 2 cores: 2 threads: 4 tpc: 2
    smt: enabled cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB
    desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 1379 min/max: 800/3400 scaling: driver: intel_cpufreq
    governor: schedutil cores: 1: 1379 2: 1379 3: 1379 4: 1379 bogomips: 21552
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  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: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: conditional; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
    vendor: Dell driver: i915 v: kernel arch: Gen-6 code: Sandybridge
    process: Intel 32nm built: 2011 ports: active: LVDS-2 empty: VGA-2
    bus-ID: 00:02.0 chip-ID: 8086:0126 class-ID: 0300
  Device-2: NVIDIA GF119M [NVS 4200M] vendor: Dell driver: nouveau v: kernel
    non-free: series: 390.xx+ status: legacy (EOL~2022-11-22) last:
    release: 390.157 kernel: 6.0 xorg: 1.21 arch: Fermi code: GF1xx
    process: 40/28nm built: 2010-2016 pcie: gen: 2 speed: 5 GT/s lanes: 16
    ports: active: HDMI-A-1 empty: DP-1, DP-2, LVDS-1, VGA-1 bus-ID: 01:00.0
    chip-ID: 10de:1056 class-ID: 0300 temp: 48.0 C
  Device-3: Ricoh Laptop_Integrated_Webcam_FHD driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 2-1.5:4
    chip-ID: 05ca:181c class-ID: 0e02
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: crocus,nouveau gpu: i915,nouveau d-rect: 1920x1080 display-ID: 0
  Monitor-1: HDMI-A-1 pos: primary model: HISENSE serial: <filter>
    built: 2023 res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 81 gamma: 1.2
    size: 1095x616mm (43.11x24.25") diag: 1388mm (54.6") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  Monitor-2: LVDS-2 pos: primary model: Seiko Epson 0x5448 built: 2010 res:
    mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 142 gamma: 1.2
    size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9
    modes: 1920x1080
  API: EGL v: 1.5 hw: drv: intel crocus drv: nvidia nouveau platforms:
    device: 0 drv: crocus device: 1 drv: nouveau device: 2 drv: swrast gbm:
    drv: crocus surfaceless: drv: crocus wayland: drv: crocus x11: drv: crocus
  API: OpenGL v: 4.5 compat-v: 3.3 vendor: intel mesa v: 25.0.7-2 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel HD Graphics 3000 (SNB GT2)
    device-ID: 8086:0126 memory: 1.46 GiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.4.309 layers: 3 device: 0 type: cpu name: llvmpipe (LLVM
    19.1.7 256 bits) driver: mesa llvmpipe v: 25.0.7-2 (LLVM 19.1.7)
    device-ID: 10005:0000 surfaces: xcb,xlib,wayland
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,
    xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio
    vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:1c20 class-ID: 0403
  Device-2: NVIDIA GF119 HDMI Audio vendor: Dell driver: snd_hda_intel
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 16 bus-ID: 01:00.1
    chip-ID: 10de:0e08 class-ID: 0403
  API: ALSA v: k6.12.73+deb13-amd64 status: kernel-api
    tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.4.2 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel 82579LM Gigabit Network vendor: Dell driver: e1000e
    v: kernel port: 5080 bus-ID: 00:19.0 chip-ID: 8086:1502 class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: Broadcom BCM43228 802.11a/b/g/n vendor: Dell Wireless 1530
    Half-size Mini PCIe Card driver: bcma-pci-bridge v: N/A modules: bcma
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 14e4:4359
    class-ID: 0280
  IF-ID-1: tun0 state: unknown speed: 10000 Mbps duplex: full mac: N/A
  IF-ID-2: wlp3s0b1 state: up mac: <filter>
  Info: services: apache2, NetworkManager, sshd, systemd-timesyncd,
    wpa_supplicant
Bluetooth:
  Device-1: Dell DW375 Bluetooth Module driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 2-1.4:3
    chip-ID: 413c:8187 class-ID: fe01 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 3.0
    lmp-v: 5 sub-v: 4203 hci-v: 5 rev: 205 class-ID: 7c010c
  Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch hold sniff park
    link-mode: peripheral accept service-classes: rendering, capturing, object
    transfer, audio, telephony
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
    v: 3.0 port: 5060 bus-ID: 00:1f.2 chip-ID: 8086:282a rev: N/A class-ID: 0104
Drives:
  Local Storage: total: 238.47 GiB used: 20.35 GiB (8.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: A-Data model: SU760 size: 238.47 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD
    serial: <filter> fw-rev: 4R22 scheme: MBR
Partition:
  ID-1: / raw-size: 230.52 GiB size: 225.84 GiB (97.97%)
    used: 20.35 GiB (9.0%) fs: ext4 dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 7.96 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda5 maj-min: 8:5
Sensors:
  System Temperatures: cpu: 55.0 C mobo: 34.0 C sodimm: 43.0 C gpu: nouveau
    temp: 48.0 C
  Fan Speeds (rpm): cpu: 2711
Info:
  Memory: total: 8 GiB available: 7.65 GiB used: 1.73 GiB (22.6%)
  Processes: 211 Power: uptime: 27m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 3.01 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Packages: 2797 pm: dpkg pkgs: 2777 libs: 1696 tools: apt, apt-get,
    gnome-software, synaptic pm: flatpak pkgs: 13 pm: snap pkgs: 7 Compilers:
    gcc: 14.2.0 Shell: Bash v: 5.2.37 running-in: konsole inxi: 3.3.38
scooby@doo:~$ inxi -Faz --vs --za
inxi 3.3.38-00 (2025-04-06)
System:
  Kernel: 6.12.73+deb13-amd64 arch: x86_64 bits: 64 compiler: gcc v: 14.2.0
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.73+deb13-amd64
    root=UUID=<filter> ro quiet
  Desktop: KDE Plasma v: 6.3.6 tk: Qt v: N/A info: frameworks v: 6.13.0
    wm: kwin_wayland tools: avail: cinnamon-screensaver vt: 1 dm: SDDM
    Distro: Debian GNU/Linux 13 (trixie)
Machine:
  Type: Laptop System: Dell product: Latitude E6520 v: 01
    serial: <superuser required> Chassis: type: 9 serial: <superuser required>
  Mobo: Dell model: 0J4TFW v: A01 serial: <superuser required>
    uuid: <superuser required> BIOS: Dell v: A22 date: 09/13/2018
Battery:
  ID-1: BAT0 charge: 25.5 Wh (100.0%) condition: 25.5/66.6 Wh (38.3%)
    volts: 12.5 min: 11.1 model: SMP DELL HTX4D2A type: Li-ion serial: <filter>
    status: full
CPU:
  Info: model: Intel Core i7-2620M bits: 64 type: MT MCP arch: Sandy Bridge
    gen: core 2 level: v2 built: 2010-12 process: Intel 32nm family: 6
    model-id: 0x2A (42) stepping: 7 microcode: 0x2F
  Topology: cpus: 1x dies: 1 clusters: 2 cores: 2 threads: 4 tpc: 2
    smt: enabled cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB
    desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 3400 min/max: 800/3400 scaling: driver: intel_cpufreq
    governor: schedutil cores: 1: 3400 2: 3400 3: 3400 4: 3400 bogomips: 21552
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
    vendor: Dell driver: i915 v: kernel arch: Gen-6 code: Sandybridge
    process: Intel 32nm built: 2011 ports: active: LVDS-2 empty: VGA-2
    bus-ID: 00:02.0 chip-ID: 8086:0126 class-ID: 0300
  Device-2: NVIDIA GF119M [NVS 4200M] vendor: Dell driver: nouveau v: kernel
    non-free: series: 390.xx+ status: legacy (EOL~2022-11-22) last:
    release: 390.157 kernel: 6.0 xorg: 1.21 arch: Fermi code: GF1xx
    process: 40/28nm built: 2010-2016 pcie: gen: 2 speed: 5 GT/s lanes: 16
    ports: active: HDMI-A-1 empty: DP-1, DP-2, LVDS-1, VGA-1 bus-ID: 01:00.0
    chip-ID: 10de:1056 class-ID: 0300 temp: 49.0 C
  Device-3: Ricoh Laptop_Integrated_Webcam_FHD driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 2-1.5:4
    chip-ID: 05ca:181c class-ID: 0e02
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: crocus,nouveau gpu: i915,nouveau d-rect: 1920x1080 display-ID: 0
  Monitor-1: HDMI-A-1 pos: primary model: HISENSE serial: <filter>
    built: 2023 res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 81 gamma: 1.2
    size: 1095x616mm (43.11x24.25") diag: 1388mm (54.6") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  Monitor-2: LVDS-2 pos: primary model: Seiko Epson 0x5448 built: 2010 res:
    mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 142 gamma: 1.2
    size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9
    modes: 1920x1080
  API: EGL v: 1.5 hw: drv: intel crocus drv: nvidia nouveau platforms:
    device: 0 drv: crocus device: 1 drv: nouveau device: 2 drv: swrast gbm:
    drv: crocus surfaceless: drv: crocus wayland: drv: crocus x11: drv: crocus
  API: OpenGL v: 4.5 compat-v: 3.3 vendor: intel mesa v: 25.0.7-2 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel HD Graphics 3000 (SNB GT2)
    device-ID: 8086:0126 memory: 1.46 GiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.4.309 layers: 3 device: 0 type: cpu name: llvmpipe (LLVM
    19.1.7 256 bits) driver: mesa llvmpipe v: 25.0.7-2 (LLVM 19.1.7)
    device-ID: 10005:0000 surfaces: xcb,xlib,wayland
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,
    xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio
    vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:1c20 class-ID: 0403
  Device-2: NVIDIA GF119 HDMI Audio vendor: Dell driver: snd_hda_intel
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 16 bus-ID: 01:00.1
    chip-ID: 10de:0e08 class-ID: 0403
  API: ALSA v: k6.12.73+deb13-amd64 status: kernel-api
    tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.4.2 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel 82579LM Gigabit Network vendor: Dell driver: e1000e
    v: kernel port: 5080 bus-ID: 00:19.0 chip-ID: 8086:1502 class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: Broadcom BCM43228 802.11a/b/g/n vendor: Dell Wireless 1530
    Half-size Mini PCIe Card driver: bcma-pci-bridge v: N/A modules: bcma
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 14e4:4359
    class-ID: 0280
  IF-ID-1: tun0 state: unknown speed: 10000 Mbps duplex: full mac: N/A
  IF-ID-2: wlp3s0b1 state: up mac: <filter>
  Info: services: apache2, NetworkManager, sshd, systemd-timesyncd,
    wpa_supplicant
Bluetooth:
  Device-1: Dell DW375 Bluetooth Module driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 2-1.4:3
    chip-ID: 413c:8187 class-ID: fe01 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 3.0
    lmp-v: 5 sub-v: 4203 hci-v: 5 rev: 205 class-ID: 7c010c
  Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch hold sniff park
    link-mode: peripheral accept service-classes: rendering, capturing, object
    transfer, audio, telephony
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
    v: 3.0 port: 5060 bus-ID: 00:1f.2 chip-ID: 8086:282a rev: N/A class-ID: 0104
Drives:
  Local Storage: total: 238.47 GiB used: 20.35 GiB (8.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: A-Data model: SU760 size: 238.47 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD
    serial: <filter> fw-rev: 4R22 scheme: MBR
Partition:
  ID-1: / raw-size: 230.52 GiB size: 225.84 GiB (97.97%)
    used: 20.35 GiB (9.0%) fs: ext4 dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 7.96 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda5 maj-min: 8:5
Sensors:
  System Temperatures: cpu: 54.0 C mobo: 34.0 C sodimm: 39.0 C gpu: nouveau
    temp: 49.0 C
  Fan Speeds (rpm): cpu: 0
Info:
  Memory: total: 8 GiB available: 7.65 GiB used: 2.22 GiB (29.0%)
  Processes: 224 Power: uptime: 41m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 3.01 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Packages: 2797 pm: dpkg pkgs: 2777 libs: 1696 tools: apt, apt-get,
    gnome-software, synaptic pm: flatpak pkgs: 13 pm: snap pkgs: 7 Compilers:
    gcc: 14.2.0 Shell: Bash v: 5.2.37 running-in: konsole inxi: 3.3.38

 

[Mike-BTU]

KDE has a simple graphical log viewer built in. Try that first.

 

[Jack_Sparrow]

KDE has a simple graphical log viewer built in. Try that first.

Sorry for the delay in reply. The freeze finally happened tonight. I'm not sure which "simple graphical log viewer" you mean, so I'm posting these logs from Application Launcher>System>Logs. Here are the last two logs recorded under the "All" category. Let me know if you need anything else.

 

[Condobloke]

kwallet, klauncher,

scooby ?

Wayland....using that?

org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"

The kded module name "kded_plasma-welcome" is invalid!

wpad-detector" is invalid

All of the above, in one form or another, are "errors".....and there are many more

Is this Debian 13 ?

 

[osprey]

Sorry for the delay in reply. The freeze finally happened tonight. I'm not sure which "simple graphical log viewer" you mean, so I'm posting these logs from Application Launcher>System>Logs. Here are the last two logs recorded under the "All" category. Let me know if you need anything else.

Something happened to the inxi output in post #1 which make it too difficult to read. All the hard returns appear to have been deleted or replaced so that the output is one long line. If you could repeat the output so that it shows as intended, it would help readers. If unsure on using code tags, perhaps have a look at this post: https://linux.org/threads/the-code-tag-and-why-it-matters.57746/#post-276419

The errors in the logs are as follows:

Errors in Logs543:

5:56:48 PM cat: [2431:2457:0402/175648.873543:ERROR:chromium/google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT

5:46:20 PM kwin_wayland: kwin_scene_opengl: 0x2: GL_INVALID_FRAMEBUFFER_OPERATION in glClear(incomplete framebuffer)

 5:46:16 PM cat: [2431:2457:0402/174616.740873:ERROR:chromium/google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT

5:45:00 PM cat: [2431:2431:0402/174500.945608:ERROR:chromium/components/os_crypt/sync/kwallet_dbus.cc:408] Error contacting kwalletd6 (close)

5:45:00 PM cat: [2431:2431:0402/174500.684579:ERROR:chromium/components/os_crypt/sync/kwallet_dbus.cc:82] Error contacting klauncher to start kwalletd6

5:44:06 PM blueman-applet: gi.repository.GLib.GError: g-io-error-quark: Timeout was reached (24)

5:43:35 PM xkbcomp: Errors from xkbcomp are not fatal to the X server

5:43:33 PM wireplumber: default: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner

6:13:37 PM systemd: drkonqi-coredump-pickup.service: Failed with result 'timeout'.

Errors in Logs625:

6:31:30 PM gvfsd-network: Couldn't create directory monitor on wsdd:///. Error: Automount failed: Failed to spawn the underlying wsdd daemon.

6:31:13 PM cat: [2323:2349:0402/183113.320667:ERROR:chromium/google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT

6:28:50 PM kwin_wayland: kwin_core: XCB error: 3 (BadWindow), sequence: 749, resource id: 23068700, major code: 129 (SHAPE), minor code: 6 (Input)

6:28:49 PM cat: [2323:2323:0402/182849.671040:ERROR:chromium/ui/gfx/x/atom_cache.cc:232] Add chromium/from-privileged to kAtomsToCache

6:28:26 PM cat: [2323:2323:0402/182826.895436:ERROR:chromium/components/os_crypt/sync/kwallet_dbus.cc:408] Error contacting kwalletd6 (close)

6:28:26 PM cat: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed

6:28:26 PM cat: [2323:2323:0402/182826.620793:ERROR:chromium/components/os_crypt/sync/kwallet_dbus.cc:82] Error contacting klauncher to start kwalletd6

6:26:23 PM gnome-logs: Error retrieving the sender timestamps: Cannot assign requested address

There are a lot of errors associated with the browser, which appears to be vivaldi, but they are not usually associated with a freeze.

The long way in this investigation is to take each error message, plug it into the search engine and see what can be found about the consequences of each. One needs to be able to assess the findings and separate the oats from the chaff, so to speak. None of them look to me like system freeze makers, rather than perhaps a GUI freeze, but one would need to check on each to know precisely.

Another approach is to look at issues that commonly cause freezes and try and address the issue that way. These are some of the issues that one can look into:

Is the issue associated with hardware acceleration? One can turn the hardware acceleration in a browser off. I don't use vivaldi so can't say, but in firefox there's a tick box for it.

Is the issue some conflict between the chromium browser and the wayland display server? One can try and select X as the display server to look at the issue, or, perhaps try a different non-chromium browser like firefox.

Is the issue a corrupt browser profile? One can create a new profile in the browser.

There are other issues to look at. If you can show the inxi output in post #1 in a readable format, that may provide some pointers to further investigation.

 

[Jack_Sparrow]

kwallet, klauncher,

scooby ?

Wayland....using that?

org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"

The kded module name "kded_plasma-welcome" is invalid!

wpad-detector" is invalid

All of the above, in one form or another, are "errors".....and there are many more

Is this Debian 13 ?

This is my kid brother's computer. He thought it would be clever to name his system scooby@doo.

Yes, this is the latest Debian 13.

 

[Jack_Sparrow]

Something happened to the inxi output in post #1 which make it too difficult to read. All the hard returns appear to have been deleted or replaced so that the output is one long line. If you could repeat the output so that it shows as intended, it would help readers. If unsure on using code tags, perhaps have a look at this post: https://linux.org/threads/the-code-tag-and-why-it-matters.57746/#post-276419

The errors in the logs are as follows:

Errors in Logs543:

5:56:48 PM cat: [2431:2457:0402/175648.873543:ERROR:chromium/google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT

5:46:20 PM kwin_wayland: kwin_scene_opengl: 0x2: GL_INVALID_FRAMEBUFFER_OPERATION in glClear(incomplete framebuffer)

 5:46:16 PM cat: [2431:2457:0402/174616.740873:ERROR:chromium/google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT

5:45:00 PM cat: [2431:2431:0402/174500.945608:ERROR:chromium/components/os_crypt/sync/kwallet_dbus.cc:408] Error contacting kwalletd6 (close)

5:45:00 PM cat: [2431:2431:0402/174500.684579:ERROR:chromium/components/os_crypt/sync/kwallet_dbus.cc:82] Error contacting klauncher to start kwalletd6

5:44:06 PM blueman-applet: gi.repository.GLib.GError: g-io-error-quark: Timeout was reached (24)

5:43:35 PM xkbcomp: Errors from xkbcomp are not fatal to the X server

5:43:33 PM wireplumber: default: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner

6:13:37 PM systemd: drkonqi-coredump-pickup.service: Failed with result 'timeout'.

Errors in Logs625:

6:31:30 PM gvfsd-network: Couldn't create directory monitor on wsdd:///. Error: Automount failed: Failed to spawn the underlying wsdd daemon.

6:31:13 PM cat: [2323:2349:0402/183113.320667:ERROR:chromium/google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT

6:28:50 PM kwin_wayland: kwin_core: XCB error: 3 (BadWindow), sequence: 749, resource id: 23068700, major code: 129 (SHAPE), minor code: 6 (Input)

6:28:49 PM cat: [2323:2323:0402/182849.671040:ERROR:chromium/ui/gfx/x/atom_cache.cc:232] Add chromium/from-privileged to kAtomsToCache

6:28:26 PM cat: [2323:2323:0402/182826.895436:ERROR:chromium/components/os_crypt/sync/kwallet_dbus.cc:408] Error contacting kwalletd6 (close)

6:28:26 PM cat: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed

6:28:26 PM cat: [2323:2323:0402/182826.620793:ERROR:chromium/components/os_crypt/sync/kwallet_dbus.cc:82] Error contacting klauncher to start kwalletd6

6:26:23 PM gnome-logs: Error retrieving the sender timestamps: Cannot assign requested address

There are a lot of errors associated with the browser, which appears to be vivaldi, but they are not usually associated with a freeze.

The long way in this investigation is to take each error message, plug it into the search engine and see what can be found about the consequences of each. One needs to be able to assess the findings and separate the oats from the chaff, so to speak. None of them look to me like system freeze makers, rather than perhaps a GUI freeze, but one would need to check on each to know precisely.

Another approach is to look at issues that commonly cause freezes and try and address the issue that way. These are some of the issues that one can look into:

Is the issue associated with hardware acceleration? One can turn the hardware acceleration in a browser off. I don't use vivaldi so can't say, but in firefox there's a tick box for it.

Is the issue some conflict between the chromium browser and the wayland display server? One can try and select X as the display server to look at the issue, or, perhaps try a different non-chromium browser like firefox.

Is the issue a corrupt browser profile? One can create a new profile in the browser.

There are other issues to look at. If you can show the inxi output in post #1 in a readable format, that may provide some pointers to further investigation.

All right, I think I fixed the formatting issue in post #1. I think it's a full fledge system freeze because the mouse freezes wherever it's positioned in the middle of the screen. I don't think the browser profile is corrupted. I'll try turning off the hardware acceleration and see if the freezing stops.

Thank you guys for all your replies!!! Your help means a lot to me.

 

[osprey]

All right, I think I fixed the formatting issue in post #1. I think it's a full fledge system freeze because the mouse freezes wherever it's positioned in the middle of the screen. I don't think the browser profile is corrupted. I'll try turning off the hardware acceleration and see if the freezing stops.

Thank you guys for all your replies!!! Your help means a lot to me.

Thanks for the inxi output format. It helped.

There may be an issue with the battery health. Its condition of "25.5/66.6 Wh (38.3%)" means that the maximum charge it can now hold is 25.5 watt hours compared to the original design capacity of 66.6 watt hours, so the battery has only about 38% if what it once had. It's lost 62% of its original capacity so it's quite worn out.

The battery may have occasional voltage drops, or momentary failures to meet system demands which can cause freezes. It can happen when the cpu or gpu generates load spikes and the battery may not be able to supply enough power for those moments. The way of telling whether it's battery or not is to run the machine on mains power and see if freezes occur in that context.

From here onwards in an investigation, the following are the sort of steps I'd begin with. The commands are best run as root or sudo in a terminal. For explanation of the options, one can check out the relevant manpages.

First, it's worth checking the logs for any info, including possible info on power issues:

journalctl -b -x -p 3

Check the health of the drive:

smartctl -a /dev/sda

From the inxi output, /dev/sda is the drive

To check the RAM install memtest86+, read the docs and run it.

Check the temperatures with:

sensors

Check that the temperatures are within the ranges shown in the output data.

Check for missing firmware and microcode with:

dmesg | grep -i firmware
dmesg | grep -i microcode

If any is missing, try and install it.

Check for filesystem corruption or badblocks with:

e2fsck -c /dev/sda

That needs to be run on an umounted filesystem. It's safe to run from a live disk, which is how it's done here.

On the hardware acceleration front, to turn hardware acceleration off for the gpu rather than just the browser in wayland, is something I haven't done and am investigating myself. It was easy in X11, but apparently not so with the wayland compositor.

 

[Blue_bird]

Focus on Hardware Acceleration and Wayland/X11 compatibility first. In 90% of Linux "system freezes" triggered by a browser, the fault lies in the Graphics Driver/Display Server layer, not the application code itself.

Launch Vivaldi from the terminal with vivaldi --disable-gpu. If the freezes stop, the issue is your graphics stack or the driver’s interaction with Chromium.

Run dmesg -T | grep -i "oom-killer". If you see entries there, you aren't dealing with a "bug," but a resource exhaustion issue.

Run vivaldi --user-data-dir="/tmp/vivaldi-test".
This launches a completely fresh instance. If it's stable, your main profile is the culprit.

 

[bob466]

Since switching to Linux..do you know how many times I've looked at log files...never.
This reminds my of back in the old days of windoze trying to find the reason for the blue screen of death...running the hexi-decimal number it showed.

If there's problems I always look at hardware or user error. Last month I pressed the power button and my Tower wouldn't start...when I dragged the Tower forward to swap SSDs it dislodged the power cable.
Some problems like power supply failure...HDD failure...Monitor failure...no sound or Motherboard failure...you wouldn't get the chance to look at logs.

The only test I run every 6 months is the SMART test just for fun. If you took your computer to a computer shop with some problem...would they look at logs...no. I think knowing what to look for hardware wise is the best solution but that's me.

 

[Condobloke]

I would agree with @bob466's comments above.

The likelihood of an actual OS failure/software failure etc are quite low, in my experience.

There are caveats to that statement, which bear keeping in mind. For example, if one has been 'screwing around' with system files, then by all means investigate your own actions first ! by the same token, if there is any possibility of 'alterations' etc that have caused an 'oops' moment, your best friend may be Timeshift...simply restore to a snapshot taken before the moment occurred, and all will be well.

If you maintain any of the more well known distros in a logical manner (and you dont 'tinker' with the os) and you have a sudden "change' in the behaviour of your PC...... hardware rises up the list of suspects.

Don't dismiss the possibility, all your hardware is connected electronically in some manner or other.... failures where electronics are concerned, can happen in an instant. Where an old fashioned HDD is concerned, it can almost be expected at some inconvenient time. It is just a matter of when.

 

[jpnilson]

sudo dmesg -T | grep -i "killed process" I would like to see the output of this

 

[Jack_Sparrow]

Thanks for the inxi output format. It helped.

There may be an issue with the battery health. Its condition of "25.5/66.6 Wh (38.3%)" means that the maximum charge it can now hold is 25.5 watt hours compared to the original design capacity of 66.6 watt hours, so the battery has only about 38% if what it once had. It's lost 62% of its original capacity so it's quite worn out.

The battery may have occasional voltage drops, or momentary failures to meet system demands which can cause freezes. It can happen when the cpu or gpu generates load spikes and the battery may not be able to supply enough power for those moments. The way of telling whether it's battery or not is to run the machine on mains power and see if freezes occur in that context.

From here onwards in an investigation, the following are the sort of steps I'd begin with. The commands are best run as root or sudo in a terminal. For explanation of the options, one can check out the relevant manpages.

First, it's worth checking the logs for any info, including possible info on power issues:

journalctl -b -x -p 3

Check the health of the drive:

smartctl -a /dev/sda

From the inxi output, /dev/sda is the drive

To check the RAM install memtest86+, read the docs and run it.

Check the temperatures with:

sensors

Check that the temperatures are within the ranges shown in the output data.

Check for missing firmware and microcode with:

dmesg | grep -i firmware
dmesg | grep -i microcode

If any is missing, try and install it.

Check for filesystem corruption or badblocks with:

e2fsck -c /dev/sda

That needs to be run on an umounted filesystem. It's safe to run from a live disk, which is how it's done here.

On the hardware acceleration front, to turn hardware acceleration off for the gpu rather than just the browser in wayland, is something I haven't done and am investigating myself. It was easy in X11, but apparently not so with the wayland compositor.

Thank you so much! That paragraph about the battery is interesting. I'm definitely going to keep that in mind. Anywho, I ran all of the commands requested with the exception of memtest86+ and e2fsck since I don't have time to do so right at this moment (I do plan on doing so later this weekend). However, attached to this reply are text outputs of the rest of the commands. I also tried the journalctl command, but some weirdness happened when I tried to do so. I've attached a screenshot of what I saw.

Hope this helps, and thank you for your advice!

 

[Jack_Sparrow]

Focus on Hardware Acceleration and Wayland/X11 compatibility first. In 90% of Linux "system freezes" triggered by a browser, the fault lies in the Graphics Driver/Display Server layer, not the application code itself.

Launch Vivaldi from the terminal with vivaldi --disable-gpu. If the freezes stop, the issue is your graphics stack or the driver’s interaction with Chromium.

Run dmesg -T | grep -i "oom-killer". If you see entries there, you aren't dealing with a "bug," but a resource exhaustion issue.

Run vivaldi --user-data-dir="/tmp/vivaldi-test".
This launches a completely fresh instance. If it's stable, your main profile is the culprit.

I did disable Hardware Acceleration in the Settings, however, I will also try running Vivaldi using the commands you gave me here. We're definitely on the right track when it comes to checking out how Vivaldi gets along with the rest of the system. This computer is primarily used as a "streaming" computer: it's permanently hooked up to the main TV via HDMI, and we use it to watch movies, TV shows, and DVDs. Almost no other programs on the computer are actually used.

=========================EDIT=========================

I almost forgot to mention, no entries were output after I ran the dmesg command.

 

[Jack_Sparrow]

Since switching to Linux..do you know how many times I've looked at log files...never.
This reminds my of back in the old days of windoze trying to find the reason for the blue screen of death...running the hexi-decimal number it showed.

If there's problems I always look at hardware or user error. Last month I pressed the power button and my Tower wouldn't start...when I dragged the Tower forward to swap SSDs it dislodged the power cable.
Some problems like power supply failure...HDD failure...Monitor failure...no sound or Motherboard failure...you wouldn't get the chance to look at logs.

The only test I run every 6 months is the SMART test just for fun. If you took your computer to a computer shop with some problem...would they look at logs...no. I think knowing what to look for hardware wise is the best solution but that's me. View attachment 31195

Not to get off topic, but nobody diagnosed a BSOD by running the hexi-decimal number it showed. You were supposed to use Blue Screen View in order to troubleshoot your issue. It darn near comes right out and tells you exactly what caused the crash.

 

[Jack_Sparrow]

sudo dmesg -T | grep -i "killed process" I would like to see the output of this

I'm not sure what I did wrong, but I didn't get an output. Attached is a screenshot of the Terminal.

 

[osprey]

Thank you so much! That paragraph about the battery is interesting. I'm definitely going to keep that in mind. Anywho, I ran all of the commands requested with the exception of memtest86+ and e2fsck since I don't have time to do so right at this moment (I do plan on doing so later this weekend). However, attached to this reply are text outputs of the rest of the commands. I also tried the journalctl command, but some weirdness happened when I tried to do so. I've attached a screenshot of what I saw.

Hope this helps, and thank you for your advice!

Thanks for those logs. After inspecting them, there did not appear to be anything critical in relation to freezing, except for one journal entry which was this:

nouveau 0000:01:00.0: drm: failed to create cd channel, -22

This error, or failure message as it is, comes from the nouveau gpu driver. The number 22 is an error code with the meaning that there's been an invalid argument in the code which has caused a failure. Error meaning check here:

[~]$ errno -l | grep 22
EINVAL 22 Invalid argument

The nouveau driver has tried to initialise part of the gpu processes, but the expected argument, or option the gpu expected, wasn't provided. The problem with this is simply that it leaves the gpu in a state that is less than optimal, which is going to make it vulnerable, and freezing is certainly going to be a possible behaviour as a result of the "Invalid argument".

This is the only vulnerability related to freezing that I could see in all the logs you provided, and so I guess that this is where I'd be applying some attention to try and resolve the issue.

The nouveau driver is used here on a number of machines, but they have more modern graphics cards than yours, and this issue hasn't arisen. The "NVIDIA GF119M [NVS 4200M]" graphics card was released in 2011 I found online, which makes it old.

The nvidia proprietary driver for that card, the 390.xx, is EOL (end of line). It was never used here anyway so I can't say anything about it.

The machine you have runs hybrid graphics with the intel and nvidia cards. They are the graphics devices 1 and 2 respectively in the inxi output in post #1.

It's probably worth trying to disable the nvidia card altogether and just run the intel card, since the intel card is supported with the i915 driver, and there are no errors associated with it anyway.

There are few ways of disabling nouveau. Nouveau can be blacklisted by creating a blacklist file named: blacklist-nouveau.conf, and placed in the directory: /etc/modprobe.d/. It'll look like:
/etc/modprobe.d/blacklist-nouveau.conf. This needs root or sudo permissions of course.
The contents of the file: blacklist-nouveau.conf should be:

blacklist nouveau
options nouveau modeset=0

Then one needs to update the initramfs as root or sudo running:

update-initramfs -u

Then reboot. On rebooting one can check to see if the nouveau driver has been loaded with:

lsmod | grep nouveau

The output should be null for nouveau, that is, no nouveau shown.

An alternative means of disabling nouveau is to add the following kernel parameters to the linux kernel line:

modprobe.blacklist=nouveau nouveau.modeset=0

If unsure about adding kernel parameters, see here: https://linuxconfig.org/how-to-set-kernel-boot-parameters-on-linux. Again, after booting, one can check to see if the nouveau driver is absent, with the above lsmod command.
The above is how I'd deal with the issue to see if it works. If not, it's all reversible, and one can start again.

 

[bob466]

Not to get off topic, but nobody diagnosed a BSOD by running the hexi-decimal number it showed. You were supposed to use Blue Screen View in order to troubleshoot your issue. It darn near comes right out and tells you exactly what caused the crash.

Really...what do you think it is...an error code and what do you do with an error code...you look it up but did that fix the problem...no.

Look this one up...0x0000007B

​

 

[Jack_Sparrow]

Thanks for those logs. After inspecting them, there did not appear to be anything critical in relation to freezing, except for one journal entry which was this:

nouveau 0000:01:00.0: drm: failed to create cd channel, -22

This error, or failure message as it is, comes from the nouveau gpu driver. The number 22 is an error code with the meaning that there's been an invalid argument in the code which has caused a failure. Error meaning check here:

[~]$ errno -l | grep 22
EINVAL 22 Invalid argument

The nouveau driver has tried to initialise part of the gpu processes, but the expected argument, or option the gpu expected, wasn't provided. The problem with this is simply that it leaves the gpu in a state that is less than optimal, which is going to make it vulnerable, and freezing is certainly going to be a possible behaviour as a result of the "Invalid argument".

This is the only vulnerability related to freezing that I could see in all the logs you provided, and so I guess that this is where I'd be applying some attention to try and resolve the issue.

The nouveau driver is used here on a number of machines, but they have more modern graphics cards than yours, and this issue hasn't arisen. The "NVIDIA GF119M [NVS 4200M]" graphics card was released in 2011 I found online, which makes it old.

The nvidia proprietary driver for that card, the 390.xx, is EOL (end of line). It was never used here anyway so I can't say anything about it.

The machine you have runs hybrid graphics with the intel and nvidia cards. They are the graphics devices 1 and 2 respectively in the inxi output in post #1.

It's probably worth trying to disable the nvidia card altogether and just run the intel card, since the intel card is supported with the i915 driver, and there are no errors associated with it anyway.

There are few ways of disabling nouveau. Nouveau can be blacklisted by creating a blacklist file named: blacklist-nouveau.conf, and placed in the directory: /etc/modprobe.d/. It'll look like:
/etc/modprobe.d/blacklist-nouveau.conf. This needs root or sudo permissions of course.
The contents of the file: blacklist-nouveau.conf should be:

blacklist nouveau
options nouveau modeset=0

Then one needs to update the initramfs as root or sudo running:

update-initramfs -u

Then reboot. On rebooting one can check to see if the nouveau driver has been loaded with:

lsmod | grep nouveau

The output should be null for nouveau, that is, no nouveau shown.

An alternative means of disabling nouveau is to add the following kernel parameters to the linux kernel line:

modprobe.blacklist=nouveau nouveau.modeset=0

If unsure about adding kernel parameters, see here: https://linuxconfig.org/how-to-set-kernel-boot-parameters-on-linux. Again, after booting, one can check to see if the nouveau driver is absent, with the above lsmod command.
The above is how I'd deal with the issue to see if it works. If not, it's all reversible, and one can start again.

You sir, are the Greatest Technician who Ever Lived. We'll be watching a few movies over the weekend. I'll be able to let you know by Monday at the latest if this worked. Again, thank you for all of your help! I greatly appreciate it.

 

[Jack_Sparrow]

Really...what do you think it is...an error code and what do you do with an error code...you look it up but did that fix the problem...no.

Look this one up...0x0000007B View attachment 31286

​

I wouldn't. I would instead ask you to upload the .dmp file in your next reply, then run it through Blue Screen View. I'd have the cause of the BSOD in less than 20 seconds: far quicker than it would take you to even Google search the hex code.