Unable to find the exact reason why computer crash (possibly a hardware problem, not related to MX)

Message
Author
User avatar
crackbarrel
Posts: 75
Joined: Sun Mar 24, 2024 11:11 am

Unable to find the exact reason why computer crash (possibly a hardware problem, not related to MX)

#1 Post by crackbarrel »

Problem: The system becomes sort of unresponsive. Sometimes I get a black screen and it writes stuff when I press power button but I can't do anything. Sometimes, everything looks fine but I can't actually do anything (except music seems totally normal for some reason) . For instance, I can open a terminal and type, but it reapeat the same thing (don't recall exactly what it is). Apps won't launch and icons disappear. I can't save anything which makes me believe it has something to do with the SSD which I've changed recently.

I also believe it only happens while I'm using AwesomeWM so that would defeit my first conclusion. But these crashes are so random that it could be possible it did not happen while using XFCE (or it did happened but forgot about it).

Is there a way to tell it is the SSD? I've tried smartctl, I get results that seems fine to me:

Code: Select all

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        31 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    13,197,241 [6.75 TB]
Data Units Written:                 16,499,111 [8.44 TB]
Host Read Commands:                 155,057,046
Host Write Commands:                217,298,508
Controller Busy Time:               742
Power Cycles:                       738
Power On Hours:                     4,414
Unsafe Shutdowns:                   93
Media and Data Integrity Errors:    0
Error Information Log Entries:      1
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0

Error Information (NVMe Log 0x01, 16 of 256 entries)
No Errors Logged
I'm currently using SystemD as I thought it solved it, but it doesn't.

I also got a problem with splash screen in sysvinit. I've changed the boot splash and since that, I cannot boot sysvinit with any splash screen so it is disabled. I don't know if SystemD will boot with splash screen though.
Last edited by crackbarrel on Tue May 28, 2024 9:24 am, edited 1 time in total.

User avatar
Eadwine Rose
Administrator
Posts: 14633
Joined: Wed Jul 12, 2006 2:10 am

Re: Unable to find the exact reason why computer crash (possibly a hardware problem, not related to MX)

#2 Post by Eadwine Rose »

Please share your full Quick System Info, found in the menu. Press the Copy for forum button, then click paste in a reply.. thanks.
MX-23.6_x64 July 31 2023 * 6.1.0-37amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030

User avatar
crackbarrel
Posts: 75
Joined: Sun Mar 24, 2024 11:11 am

Re: Unable to find the exact reason why computer crash (possibly a hardware problem, not related to MX)

#3 Post by crackbarrel »

Code: Select all

Snapshot created on: 20240408_1406
System:
  Kernel: 6.1.0-21-amd64 [6.1.90-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-21-amd64 root=UUID=<filter> ro quiet
    init=/lib/systemd/systemd
  Desktop: awesome v: 4.3 info: xfce4-panel vt: 7 dm: LightDM v: 1.26.0 Distro: MX-23.3_x64
    Libretto January 21 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: Dell product: Inspiron 5515 v: 1.4.0 serial: <superuser required> Chassis:
    type: 10 v: 1.4.0 serial: <superuser required>
  Mobo: Dell model: 0KDKG8 v: A00 serial: <superuser required> UEFI: Dell v: 1.4.0
    date: 07/12/2021
Battery:
  ID-1: BAT0 charge: 41.3 Wh (100.0%) condition: 41.3/54.0 Wh (76.5%) volts: 16.8 min: 15.0
    model: SMP-ATL3.66 DELL XDY9K18 type: Li-poly serial: <filter> status: full
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325 serial: <filter>
    charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
  Info: model: AMD Ryzen 7 5700U with Radeon Graphics bits: 64 type: MT MCP arch: Zen 2 gen: 3
    level: v3 note: check built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23)
    model-id: 0x68 (104) stepping: 1 microcode: 0x8608103
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB
    desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 8 MiB desc: 2x4 MiB
  Speed (MHz): avg: 1846 high: 3970 min/max: 1400/4370 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1735 2: 1459 3: 1424 4: 1298 5: 1674 6: 1833
    7: 1744 8: 1514 9: 3233 10: 3970 11: 1400 12: 1591 13: 1542 14: 1929 15: 1805 16: 1400
    bogomips: 57490
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling 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: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP protection
  Type: spec_rstack_overflow mitigation: safe RET
  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; STIBP: always-on; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Lucienne vendor: Dell driver: amdgpu v: kernel arch: GCN-5 code: Vega
    process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s ports: active: HDMI-A-1,eDP-1 empty: DP-1 bus-ID: 03:00.0 chip-ID: 1002:164c
    class-ID: 0300 temp: 52.0 C
  Device-2: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 3-1:2
    chip-ID: 0c45:6725 class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 compositor: Picom v: 9.1 driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x286mm (40.00x11.26")
    s-diag: 1055mm (41.55")
  Monitor-1: HDMI-A-1 mapped: HDMI-A-0 pos: left model: Dell ST2320L serial: <filter> built: 2011
    res: 1920x1080 hz: 60 dpi: 96 gamma: 1.2 size: 509x286mm (20.04x11.26") diag: 585mm (23")
    ratio: 16:9 modes: max: 1920x1080 min: 720x400
  Monitor-2: eDP-1 mapped: eDP pos: primary,right model: AU Optronics 0x1f92 built: 2020
    res: 1920x1080 hz: 60 dpi: 142 gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5")
    ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon Graphics (renoir LLVM 15.0.6 DRM 3.49
    6.1.0-21-amd64) direct-render: Yes
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio vendor: Dell driver: snd_hda_intel
    bus-ID: 3-2.2:5 v: kernel chip-ID: a604:0715 pcie: gen: 3 class-ID: 0301 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.1 chip-ID: 1002:1637 class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Dell driver: snd_rn_pci_acp3x v: kernel
    alternate: snd_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio vendor: Dell driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  Device-4: 2.4G Composite Devic Wireless type: USB driver: hid-generic,snd-usb-audio,usbhid
  API: ALSA v: k6.1.0-21-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter vendor: Dell
    driver: ath10k_pci v: kernel modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0
    chip-ID: 168c:003e class-ID: 0280 temp: 51.0 C
  IF: wlan0 state: up mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
  Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 3-3:4 chip-ID: 0cf3:e007
    class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
    sub-v: 25a hci-v: 4.2
  Info: acl-mtu: 1024:8 sco-mtu: 50:8 link-policy: rswitch hold sniff
    link-mode: peripheral accept service-classes: rendering, capturing, audio, telephony
Drives:
  Local Storage: total: 1.02 TiB used: 237.46 GiB (22.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WDS100T2B0C-00PXH0
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 211070WD temp: 30.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 type: USB vendor: Kingston model: DataTraveler 3.0 size: 115.59 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: PMAP scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 931.26 GiB size: 915.57 GiB (98.31%) used: 237.46 GiB (25.9%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 276 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 46.0 C mobo: 41.0 C gpu: amdgpu temp: 53.0 C
  Fan Speeds (RPM): cpu: 3690
Repos:
  Packages: 3554 pm: dpkg pkgs: 2877 libs: 1293 tools: apt,apt-get,aptitude,nala,synaptic
    pm: nix-default pkgs: 0 pm: nix-sys pkgs: 0 pm: nix-usr pkgs: 677 libs: 201 pm: rpm pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/librewolf.list
    1: deb [arch=amd64] http://deb.librewolf.net bookworm main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/signal-xenial-added-by-mxpi.list
    1: deb [arch=amd64] https://updates.signal.org/desktop/apt xenial main
  Active apt repos in: /etc/apt/sources.list.d/spotify.list
    1: deb http://repository.spotify.com stable non-free
Info:
  Processes: 367 Uptime: 1h 50m wakeups: 9 Memory: 14.97 GiB used: 5.51 GiB (36.8%) Init: systemd
  v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

User avatar
h3kt0r
Posts: 144
Joined: Fri Oct 08, 2021 6:27 pm

Re: Unable to find the exact reason why computer crash (possibly a hardware problem, not related to MX)

#4 Post by h3kt0r »

Kernel update to Liquorix, perhaps ?
Dell OptiPlex 7010 - i7-3770 (8) @ 3.9GHz - 16Gb RAM - GeForce GT 1030 - MX 21
Panasonic CF MX4 - i5-5300U vPro (4) @ 2.9GHz - 4Gb RAM - HD Graphics 5500 - MX 21
Acer Aspire One ZG5 - Atom (2) @ 1.6GHz - 1.5Gb RAM - HD Gfx 945 - LXLE & XenialPup

User avatar
j2mcgreg
Global Moderator
Posts: 6811
Joined: Tue Oct 23, 2007 12:04 pm

Re: Unable to find the exact reason why computer crash (possibly a hardware problem, not related to MX)

#5 Post by j2mcgreg »

We know that Ryzen based computers just run better with a Liquorix kernel that the stock Debian ones. There are several Liquorix kernels available in MXPI and you may have to experiment a bit to get the best fit. I think that the 6.5.xxx or 6.6.xxx would be a good starting point.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

User avatar
h3kt0r
Posts: 144
Joined: Fri Oct 08, 2021 6:27 pm

Re: Unable to find the exact reason why computer crash (possibly a hardware problem, not related to MX)

#6 Post by h3kt0r »

Otherwise, maybe you could create a new user and try to login into a fresh environment to check if the crash occurs.
Or try to boot from USB into a Mx Live session and see if the problem appears once again...
From there, check if there is any free space left into your "/home" directory or partition...
Dell OptiPlex 7010 - i7-3770 (8) @ 3.9GHz - 16Gb RAM - GeForce GT 1030 - MX 21
Panasonic CF MX4 - i5-5300U vPro (4) @ 2.9GHz - 4Gb RAM - HD Graphics 5500 - MX 21
Acer Aspire One ZG5 - Atom (2) @ 1.6GHz - 1.5Gb RAM - HD Gfx 945 - LXLE & XenialPup

Charlie Brown

Re: Unable to find the exact reason why computer crash (possibly a hardware problem, not related to MX)

#7 Post by Charlie Brown »

Take the rams out, then re-seat.

Yes, take them out no matter they already look tight etc. (This solved such random and unknown freezings etc. so many times (even on new computers) even when mem-test showed everything was fine (therefore I began skipping the mem-test suggestion) ). All you need is a tiny screwdriver.

If still the same: boot with a live usb and observe. ( If it's ok there, then it might be the ssd )

h3kt0r wrote: Tue May 28, 2024 9:48 am... From there, check if there is any free space left into your "/home" directory or partition...
Both are ok:

/ ... used: 237.46 GiB (25.9%)

( and /home is not a separate partition but a directory within / in this case ).

User avatar
crackbarrel
Posts: 75
Joined: Sun Mar 24, 2024 11:11 am

Re: Unable to find the exact reason why computer crash (possibly a hardware problem, not related to MX)

#8 Post by crackbarrel »

I'm gonna try new kernel. I've just had a crash and took more notes:

- IOT instruction (after quitting nvim)
- I've successfully sent a message on an opened app
- Zsh:input/output error: ls (on an opened terminal. I actually couldn't open new terminal)
- I get these kind of error when I exit awsomewm and press power button: Ext4-fs error (device nvme0n1p2): ext4_find_entry: 1682: inode #xxx: comm acpid: reading directory lblock 0

Charlie Brown

Re: Unable to find the exact reason why computer crash (possibly a hardware problem, not related to MX)

#9 Post by Charlie Brown »

crackbarrel wrote: Tue May 28, 2024 10:24 am ... when I exit awsomewm and press power button: Ext4-fs error ...
Live Session: GParted: Right-click on nvme0n1p2 : "Check".

(Also login with any other WM (including the default Xfwm) and try.)

User avatar
crackbarrel
Posts: 75
Joined: Sun Mar 24, 2024 11:11 am

Re: Unable to find the exact reason why computer crash (possibly a hardware problem, not related to MX)

#10 Post by crackbarrel »

So it seems like it was it the kernel. Thanks a lot!

Post Reply

Return to “Hardware /Configuration”