System hangs/crashes/sometimes reboots

Support
1

Hello, back with a problem, this time on a different system. Fresh install of Manjaro XFCE version. I suspect hardware problems. This is a system76 Meekat and it was given to me from my parents. I am trying to use it as nothing more than a Jellyfin media server on my LAN. I do have to use a USB drive for the media files due to the size. The onboard SSD is only for the operation system and application.

Since I’ve installed and set it up I’ve had numerous different variations of what I describe as hang/crash/reboot. I will try to explain best I can. I normally don’t have this system connected to a monitor/keyboard and access it via ssh. I can be in a ssh shell with it and running updates for example and the system will just freeze mid-flight. If I turn on the monitor and local keyboard I will then see the system has rebooted on its own.

Other variations are Jellyfin will stop working or I can just be running a ping to the system and the ping still stop responding, I check and the system has rebooted. I tried testing the system before installing Jellyfin as well to make sure it’s not the problem. I have reinstalled Manjaro from scratch a few times too.

I now have removed XFCE so it’s just CLI only. I thought that might help narrow things by not having a GUI. One other note, the on-board NIC does not appear to work so I am using a USB-to-Eth dongle. Even when I have the USB drive unplugged the system has these issues. I guess I mainly need help figuring out why this is happening. Trying to learn from past threads and commands you guys ask for. Starting here.

journalctl -p3 -b0 - All errors and up, from the current boot.

[will@meerkat ~]$ journalctl -p3 -b0
Oct 05 09:49:32 meerkat kernel: x86/cpu: SGX disabled by BIOS.
Oct 05 09:49:35 meerkat kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02

and sudo inxi --verbosity=8 --filter --width

[will@meerkat ~]$ sudo inxi --verbosity=8 --filter --width
[sudo] password for will: 
System:
  Kernel: 6.6.52-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=6586ff32-3092-4590-9bd7-249708c36828 rw quiet splash
    udev.log_priority=3
  Console: pty pts/1 Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: System76 product: Meerkat v: meer4 serial: <filter>
    Chassis: type: 3 v: meer4 serial: N/A
  Mobo: Intel model: NUC8BEB v: J72693-303 serial: <filter>
    part-nu: BOXNUC8i3BEK uuid: 8fc77b9f-b1d6-828d-6361-94c691a5dc70 UEFI: Intel
    v: BECFL357.86A.0048.2018.0919.2013 date: 09/19/2018
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 4 GiB available: 3.7 GiB used: 649.6 MiB (17.2%)
    igpu: 64 MiB
  Array-1: capacity: 32 GiB slots: 2 modules: 1 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: SODIMM1 type: DDR4 detail: synchronous size: 4 GiB
    speed: 2400 MT/s volts: curr: 1.2 min: 1.2 max: 1.2 width (bits): data: 64
    total: 64 manufacturer: Crucial part-no: CT4G4SFS824A.C8FF serial: <filter>
  Device-2: SODIMM2 type: no module installed
PCI Slots:
  Slot: 0 type: PCIe status: in use info: J6B2 length: long volts: 3.3
    bus-ID: 00:01.0
  Slot: 1 type: PCIe status: in use info: J6B1 length: short volts: 3.3
    bus-ID: 00:1c.3
  Slot: 2 type: PCIe status: in use info: J6D1 length: short volts: 3.3
    bus-ID: 00:1c.4
  Slot: 3 type: PCIe status: in use info: J7B1 length: short volts: 3.3
    bus-ID: 00:1c.5
  Slot: 4 type: PCIe status: in use info: J8B4 length: short volts: 3.3
    bus-ID: 00:1c.6
CPU:
  Info: model: Intel Core i3-8109U socket: BGA1528 (U3E1) note: check bits: 64
    type: MT MCP arch: Coffee Lake gen: core 8 level: v3 note: check built: 2017
    process: Intel 14nm family: 6 model-id: 0x8E (142) stepping: 0xA (10)
    microcode: 0xF6
  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: 400 min/max: 400/3600 base/boost: 2300/3500 scaling:
    driver: intel_pstate governor: powersave volts: 0.8 V ext-clock: 100 MHz
    cores: 1: 400 2: 400 3: 400 4: 400 bogomips: 24008
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
    fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida
    intel_pt invpcid lahf_lm lm mca mce md_clear mmx monitor movbe mpx msr
    mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge
    pln pni popcnt pse pse36 pti pts rdrand rdseed rdtscp rep_good sdbg sep
    smap smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2
    tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic
    xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  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 mitigation: Clear CPU buffers; SMT vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  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: IBRS; IBPB: conditional; STIBP: conditional;
    RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel CoffeeLake-U GT3e [Iris Plus Graphics 655] driver: i915
    v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports:
    active: DP-1 empty: DP-2,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:3ea5
    class-ID: 0300
  Display: server: X.org v: 1.21.1.13 driver: X: loaded: modesetting
    alternate: fbdev,vesa dri: iris gpu: i915 tty: 190x42
  Monitor-1: DP-1 model: TLX-01511C serial: <filter> built: 2008
    res: 1280x800 dpi: 99 gamma: 1.37 chroma: red: x: 0.600 y: 0.345 green:
    x: 0.294 y: 0.537 blue: x: 0.137 y: 0.169 white: x: 0.306 y: 0.357
    size: 332x207mm (13.07x8.15") diag: 386mm (15.2") ratio: 16:10
    modes: 1280x800, 1280x720, 1024x768, 832x624, 800x600, 720x576, 720x480,
    640x480, 720x400
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris
    inactive: wayland,x11
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 24.2.2-arch1.1
    note: console (EGL sourced) renderer: Mesa Intel Iris Plus Graphics 655 (CFL
    GT3), llvmpipe (LLVM 18.1.8 256 bits)
Audio:
  Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel
    v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
    chip-ID: 8086:9dc8 class-ID: 0403
  API: ALSA v: k6.6.52-1-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.2.3 status: off with: 1: pipewire-pulse status: off
    2: wireplumber status: off 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Cannon Point-LP CNVi [Wireless-AC] driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:9df0 class-ID: 0280
  IF: wlp0s20f3 state: down mac: <filter>
  Device-2: Intel Ethernet I219-V driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:15be class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-3: ASIX AX88179 Gigabit Ethernet driver: ax88179_178a type: USB
    rev: 3.0 speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 2-3:2
    chip-ID: 0b95:1790 class-ID: ff00 serial: <filter>
  IF: enp0s20f0u3 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager, sshd, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) driver: btusb v: 0.8
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-10:3
    chip-ID: 8087:0aaa class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 7.5 TiB used: 649.57 GiB (8.5%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 1B2QEXE7 temp: 26.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: Expansion HDD
    size: 7.28 TiB block-size: physical: 4096 B logical: 512 B type: USB rev: 3.2
    spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
    fw-rev: 0003 scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 232.59 GiB size: 227.88 GiB (97.98%) used: 9.7 GiB (4.3%)
    fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2 label: N/A
    uuid: 6586ff32-3092-4590-9bd7-249708c36828
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 296 KiB (0.1%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
    maj-min: 259:1 label: N/A uuid: 2C06-B364
  ID-3: /mnt raw-size: 7.28 TiB size: 7.28 TiB (100.00%)
    used: 639.87 GiB (8.6%) fs: ntfs block-size: 4096 B dev: /dev/sda1
    maj-min: 8:1 label: Vault-1 uuid: 96B428EBB428CF93
Swap:
  Alert: No swap data was found.
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-1:2 info: Shenzhen Riitek Wireless Receiver
    type: mouse,keyboard driver: hid-generic,usbhid interfaces: 2 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 50mA
    chip-ID: 1997:2466 class-ID: 0301
  Device-2: 1-10:3 info: Intel Bluetooth 9460/9560 Jefferson Peak (JfP)
    type: bluetooth driver: btusb interfaces: 2 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 8087:0aaa class-ID: e001
  Hub-2: 2-0:1 info: super-speed hub ports: 6 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Device-1: 2-3:2 info: ASIX AX88179 Gigabit Ethernet type: Network
    driver: ax88179_178a interfaces: 1 rev: 3.0 speed: 5 Gb/s (596.0 MiB/s)
    lanes: 1 mode: 3.2 gen-1x1 power: 496mA chip-ID: 0b95:1790 class-ID: ff00
    serial: <filter>
  Device-2: 2-4:3 info: Seagate RSS LLC Expansion HDD type: mass storage
    driver: uas interfaces: 1 rev: 3.2 speed: 5 Gb/s (596.0 MiB/s) lanes: 1
    mode: 3.2 gen-1x1 chip-ID: 0bc2:2032 class-ID: 0806 serial: <filter>
Sensors:
  System Temperatures: cpu: 33.0 C pch: 37.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: pacman pkgs: 897 libs: 292 tools: pamac
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: http://manjaro.mirror.ac.za/stable/$repo/$arch
    2: https://manjaro.mirror.liquidtelecom.com/stable/$repo/$arch
    3: https://manjarolinux-mirror.cloud.mu/stable/$repo/$arch
    4: http://mirror.is.co.za/mirrors/manjaro.org/stable/$repo/$arch
Processes:
  CPU top: 5 of 135
  1: cpu: 1.2% command: jellyfin pid: 464 mem: 328.7 MiB (8.6%)
  2: cpu: 0.2% command: sudo pid: 768 mem: 7.25 MiB (0.1%)
  3: cpu: 0.0% command: init pid: 1 mem: 12.3 MiB (0.3%)
  4: cpu: 0.0% command: [kthreadd] pid: 2 mem: 0.00 MiB (0.0%)
  5: cpu: 0.0% command: [pool_workqueue_release] pid: 3 mem: 0.00 MiB (0.0%)
  Memory top: 5 of 135
  1: mem: 328.7 MiB (8.6%) command: jellyfin pid: 464 cpu: 1.2%
  2: mem: 23.8 MiB (0.6%) command: NetworkManager pid: 461 cpu: 0.0%
  3: mem: 17.2 MiB (0.4%) command: systemd-journald pid: 286 cpu: 0.0%
  4: mem: 12.3 MiB (0.3%) command: init pid: 1 cpu: 0.0%
  5: mem: 11.1 MiB (0.2%) command: ModemManager pid: 507 cpu: 0.0%
Info:
  Processes: 135 Power: uptime: 25m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 1.47 GiB Init: systemd v: 256
    default: multi-user tool: systemctl
  Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: Sudo (sudo) v: 1.9.15p5
    default: Bash v: 5.2.32 running-in: pty pts/1 (SSH) inxi: 3.3.36
[will@meerkat ~]$

and

[will@meerkat ~]$ mhwd-kernel -li
Currently running: 6.6.52-1-MANJARO (linux66)
The following kernels are installed in your system:
   * linux66

and one log level up since last boot

[will@meerkat ~]$ journalctl -p4 -b -1
Oct 03 01:38:50 meerkat kernel: x86/cpu: SGX disabled by BIOS.
Oct 03 01:38:50 meerkat kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Oct 03 01:38:50 meerkat kernel: MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_stale_data.html>
Oct 03 01:38:50 meerkat kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 03 01:38:50 meerkat kernel: hpet_acpi_add: no address or irqs in _CRS
Oct 03 01:38:50 meerkat kernel: nvme nvme0: missing or invalid SUBNQN field.
Oct 03 01:38:50 meerkat kernel: i915 0000:00:02.0: [drm] *ERROR* DPLL0 not locked
Oct 03 01:38:50 meerkat kernel: ------------[ cut here ]------------
Oct 03 01:38:50 meerkat kernel: i915 0000:00:02.0: drm_WARN_ON((val & (1 << 30)) == 0)
Oct 03 01:38:50 meerkat kernel: WARNING: CPU: 0 PID: 140 at drivers/gpu/drm/i915/display/intel_cdclk.c:889 skl_get_cdclk+0x24c/0x2a0 [i915]
Oct 03 01:38:50 meerkat kernel: Modules linked in: usbhid(+) i915(+) rtsx_pci_sdmmc mmc_core nvme nvme_core i2c_algo_bit drm_buddy crc32c_intel ttm nvme_common intel_gtt rtsx_pci drm_displa>
Oct 03 01:38:50 meerkat kernel: CPU: 0 PID: 140 Comm: (udev-worker) Not tainted 6.6.52-1-MANJARO #1 7fd24cb19f2dc7edce5825af0acb3586c0f026f9
Oct 03 01:38:50 meerkat kernel: Hardware name: System76 Meerkat/NUC8BEB, BIOS BECFL357.86A.0048.2018.0919.2013 09/19/2018
Oct 03 01:38:50 meerkat kernel: RIP: 0010:skl_get_cdclk+0x24c/0x2a0 [i915]
Oct 03 01:38:50 meerkat kernel: Code: 8b 7d 08 4c 8b 6f 50 4d 85 ed 74 36 e8 6d dd c6 ea 48 c7 c1 98 96 72 c0 4c 89 ea 48 c7 c7 5c 94 75 c0 48 89 c6 e8 34 d6 3d ea <0f> 0b 8b 53 04 e9 be fe>
Oct 03 01:38:50 meerkat kernel: RSP: 0018:ffffc9000029b6c0 EFLAGS: 00010286
Oct 03 01:38:50 meerkat kernel: RAX: 0000000000000000 RBX: ffff8881075588c0 RCX: 0000000000000003
Oct 03 01:38:50 meerkat kernel: RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000001
Oct 03 01:38:50 meerkat kernel: RBP: ffff888107558000 R08: 0000000000000000 R09: ffffc9000029b530
Oct 03 01:38:50 meerkat kernel: R10: ffffffffac8b23e8 R11: 0000000000000003 R12: ffff888107559d00
Oct 03 01:38:50 meerkat kernel: R13: ffff888101629400 R14: ffff8881015880c0 R15: ffff888101588000
Oct 03 01:38:50 meerkat kernel: FS:  00007f3e3e391880(0000) GS:ffff888179c00000(0000) knlGS:0000000000000000
Oct 03 01:38:50 meerkat kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 03 01:38:50 meerkat kernel: CR2: 00007f3e3ecaccdc CR3: 0000000105d88006 CR4: 00000000003706f0
Oct 03 01:38:50 meerkat kernel: Call Trace:
Oct 03 01:38:50 meerkat kernel:  <TASK>
Oct 03 01:38:50 meerkat kernel:  ? skl_get_cdclk+0x24c/0x2a0 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  ? __warn+0x81/0x130
Oct 03 01:38:50 meerkat kernel:  ? skl_get_cdclk+0x24c/0x2a0 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  ? report_bug+0x16f/0x1a0
Oct 03 01:38:50 meerkat kernel:  ? handle_bug+0x3c/0x80
Oct 03 01:38:50 meerkat kernel:  ? exc_invalid_op+0x17/0x70
Oct 03 01:38:50 meerkat kernel:  ? asm_exc_invalid_op+0x1a/0x20
Oct 03 01:38:50 meerkat kernel:  ? skl_get_cdclk+0x24c/0x2a0 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  intel_update_cdclk+0x20/0x70 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  intel_cdclk_init_hw+0x288/0x570 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  intel_power_domains_init_hw+0x3ef/0x630 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  intel_display_driver_probe_noirq+0x7f/0x270 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  i915_driver_probe+0x67e/0xb70 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  local_pci_probe+0x42/0xa0
Oct 03 01:38:50 meerkat kernel:  pci_device_probe+0xbd/0x2a0
Oct 03 01:38:50 meerkat kernel:  ? sysfs_do_create_link_sd+0x6e/0xe0
Oct 03 01:38:50 meerkat kernel:  really_probe+0x19b/0x3e0
Oct 03 01:38:50 meerkat kernel:  ? __pfx___driver_attach+0x10/0x10
Oct 03 01:38:50 meerkat kernel:  __driver_probe_device+0x78/0x160
Oct 03 01:38:50 meerkat kernel:  driver_probe_device+0x1f/0xa0
Oct 03 01:38:50 meerkat kernel:  __driver_attach+0xba/0x1c0
Oct 03 01:38:50 meerkat kernel:  bus_for_each_dev+0x8c/0xe0
Oct 03 01:38:50 meerkat kernel:  bus_add_driver+0x112/0x240
Oct 03 01:38:50 meerkat kernel:  driver_register+0x5c/0x100
Oct 03 01:38:50 meerkat kernel:  i915_init+0x22/0xc0 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  ? __pfx_i915_init+0x10/0x10 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  do_one_initcall+0x5a/0x320
Oct 03 01:38:50 meerkat kernel:  do_init_module+0x60/0x240
Oct 03 01:38:50 meerkat kernel:  init_module_from_file+0x89/0xe0
Oct 03 01:38:50 meerkat kernel:  idempotent_init_module+0x121/0x320
Oct 03 01:38:50 meerkat kernel:  __x64_sys_finit_module+0x5e/0xb0
Oct 03 01:38:50 meerkat kernel:  do_syscall_64+0x5a/0x80
Oct 03 01:38:50 meerkat kernel:  ? ksys_read+0x6d/0xf0
Oct 03 01:38:50 meerkat kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Oct 03 01:38:50 meerkat kernel:  ? do_syscall_64+0x66/0x80
Oct 03 01:38:50 meerkat kernel:  ? vfs_fstatat+0x94/0xb0
Oct 03 01:38:50 meerkat kernel:  ? __do_sys_newfstatat+0x3c/0x80
Oct 03 01:38:50 meerkat kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Oct 03 01:38:50 meerkat kernel:  ? do_syscall_64+0x66/0x80
Oct 03 01:38:50 meerkat kernel:  ? __rseq_handle_notify_resume+0xa9/0x4e0
Oct 03 01:38:50 meerkat kernel:  ? __call_rcu_common+0xf4/0x720
Oct 03 01:38:50 meerkat kernel:  ? exit_to_user_mode_prepare+0x17d/0x1f0
Oct 03 01:38:50 meerkat kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Oct 03 01:38:50 meerkat kernel:  ? do_syscall_64+0x66/0x80
Oct 03 01:38:50 meerkat kernel:  ? do_syscall_64+0x66/0x80
Oct 03 01:38:50 meerkat kernel:  ? exit_to_user_mode_prepare+0x17d/0x1f0
Oct 03 01:38:50 meerkat kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Oct 03 01:38:50 meerkat kernel:  ? do_syscall_64+0x66/0x80
Oct 03 01:38:50 meerkat kernel:  ? do_syscall_64+0x66/0x80
Oct 03 01:38:50 meerkat kernel:  entry_SYSCALL_64_after_hwframe+0x78/0xe2
Oct 03 01:38:50 meerkat kernel: RIP: 0033:0x7f3e3eb6b1fd
Oct 03 01:38:50 meerkat kernel: Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01>
Oct 03 01:38:50 meerkat kernel: RSP: 002b:00007ffc706bd8b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Oct 03 01:38:50 meerkat kernel: RAX: ffffffffffffffda RBX: 00005558f5e0d520 RCX: 00007f3e3eb6b1fd
Oct 03 01:38:50 meerkat kernel: RDX: 0000000000000004 RSI: 00007f3e3e38b05d RDI: 000000000000001f
Oct 03 01:38:50 meerkat kernel: RBP: 00007ffc706bd970 R08: 0000000000000001 R09: 00007ffc706bd900
Oct 03 01:38:50 meerkat kernel: R10: 0000000000000040 R11: 0000000000000246 R12: 00007f3e3e38b05d
Oct 03 01:38:50 meerkat kernel: R13: 0000000000020000 R14: 00005558f5e04c10 R15: 00005558f5e0f250
Oct 03 01:38:50 meerkat kernel:  </TASK>
Oct 03 01:38:50 meerkat kernel: ---[ end trace 0000000000000000 ]---
Oct 03 01:38:50 meerkat kernel: ------------[ cut here ]------------
Oct 03 01:38:50 meerkat kernel: i915 0000:00:02.0: drm_WARN_ON(intel_cdclk_needs_modeset(&dev_priv->display.cdclk.hw, &cdclk_config))
Oct 03 01:38:50 meerkat kernel: WARNING: CPU: 0 PID: 140 at drivers/gpu/drm/i915/display/intel_display_power_well.c:981 gen9_disable_dc_states+0x278/0x2c0 [i915]
Oct 03 01:38:50 meerkat kernel: Modules linked in: usbhid(+) i915(+) rtsx_pci_sdmmc mmc_core nvme nvme_core i2c_algo_bit drm_buddy crc32c_intel ttm nvme_common intel_gtt rtsx_pci drm_displa>
Oct 03 01:38:50 meerkat kernel: CPU: 0 PID: 140 Comm: (udev-worker) Tainted: G        W          6.6.52-1-MANJARO #1 7fd24cb19f2dc7edce5825af0acb3586c0f026f9
Oct 03 01:38:50 meerkat kernel: Hardware name: System76 Meerkat/NUC8BEB, BIOS BECFL357.86A.0048.2018.0919.2013 09/19/2018
Oct 03 01:38:50 meerkat kernel: RIP: 0010:gen9_disable_dc_states+0x278/0x2c0 [i915]
Oct 03 01:38:50 meerkat kernel: Code: 48 8b 6f 50 48 85 ed 75 03 48 8b 2f e8 c1 a3 c3 ea 48 c7 c1 68 01 73 c0 48 89 ea 48 c7 c7 08 b0 75 c0 48 89 c6 e8 88 9c 3a ea <0f> 0b e9 1a fe ff ff 48>
Oct 03 01:38:50 meerkat kernel: RSP: 0018:ffffc9000029b6c8 EFLAGS: 00010282
Oct 03 01:38:50 meerkat kernel: RAX: 0000000000000000 RBX: ffff888107558000 RCX: 0000000000000003
Oct 03 01:38:50 meerkat kernel: RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000001
Oct 03 01:38:50 meerkat kernel: RBP: ffff888101629400 R08: 0000000000000000 R09: ffffc9000029b538
Oct 03 01:38:50 meerkat kernel: R10: ffffffffac8b23e8 R11: 0000000000000003 R12: 000000000000004c
Oct 03 01:38:50 meerkat kernel: R13: ffff88810755a358 R14: ffff8881015880c0 R15: ffff888101588000
Oct 03 01:38:50 meerkat kernel: FS:  00007f3e3e391880(0000) GS:ffff888179c00000(0000) knlGS:0000000000000000
Oct 03 01:38:50 meerkat kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 03 01:38:50 meerkat kernel: CR2: 00007f3e3ecaccdc CR3: 0000000105d88006 CR4: 00000000003706f0
Oct 03 01:38:50 meerkat kernel: Call Trace:
Oct 03 01:38:50 meerkat kernel:  <TASK>
Oct 03 01:38:50 meerkat kernel:  ? gen9_disable_dc_states+0x278/0x2c0 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  ? __warn+0x81/0x130
Oct 03 01:38:50 meerkat kernel:  ? gen9_disable_dc_states+0x278/0x2c0 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  ? report_bug+0x16f/0x1a0
Oct 03 01:38:50 meerkat kernel:  ? handle_bug+0x3c/0x80
Oct 03 01:38:50 meerkat kernel:  ? exc_invalid_op+0x17/0x70
Oct 03 01:38:50 meerkat kernel:  ? asm_exc_invalid_op+0x1a/0x20
Oct 03 01:38:50 meerkat kernel:  ? gen9_disable_dc_states+0x278/0x2c0 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  ? gen9_disable_dc_states+0x278/0x2c0 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  intel_power_well_enable+0x5b/0x70 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  __intel_display_power_get_domain.part.0+0x52/0x70 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  intel_power_domains_init_hw+0x93/0x630 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  intel_display_driver_probe_noirq+0x7f/0x270 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  i915_driver_probe+0x67e/0xb70 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  local_pci_probe+0x42/0xa0
Oct 03 01:38:50 meerkat kernel:  pci_device_probe+0xbd/0x2a0
Oct 03 01:38:50 meerkat kernel:  ? sysfs_do_create_link_sd+0x6e/0xe0
Oct 03 01:38:50 meerkat kernel:  really_probe+0x19b/0x3e0
Oct 03 01:38:50 meerkat kernel:  ? __pfx___driver_attach+0x10/0x10
Oct 03 01:38:50 meerkat kernel:  __driver_probe_device+0x78/0x160
Oct 03 01:38:50 meerkat kernel:  driver_probe_device+0x1f/0xa0
Oct 03 01:38:50 meerkat kernel:  __driver_attach+0xba/0x1c0
Oct 03 01:38:50 meerkat kernel:  bus_for_each_dev+0x8c/0xe0
Oct 03 01:38:50 meerkat kernel:  bus_add_driver+0x112/0x240
Oct 03 01:38:50 meerkat kernel:  driver_register+0x5c/0x100
Oct 03 01:38:50 meerkat kernel:  i915_init+0x22/0xc0 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  ? __pfx_i915_init+0x10/0x10 [i915 8dd93fd37cc6bb9befa8c8290392785c763516f3]
Oct 03 01:38:50 meerkat kernel:  do_one_initcall+0x5a/0x320
Oct 03 01:38:50 meerkat kernel:  do_init_module+0x60/0x240
Oct 03 01:38:50 meerkat kernel:  init_module_from_file+0x89/0xe0
Oct 03 01:38:50 meerkat kernel:  idempotent_init_module+0x121/0x320
Oct 03 01:38:50 meerkat kernel:  __x64_sys_finit_module+0x5e/0xb0
Oct 03 01:38:50 meerkat kernel:  do_syscall_64+0x5a/0x80
Oct 03 01:38:50 meerkat kernel:  ? ksys_read+0x6d/0xf0
Oct 03 01:38:50 meerkat kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Oct 03 01:38:50 meerkat kernel:  ? do_syscall_64+0x66/0x80
Oct 03 01:38:50 meerkat kernel:  ? vfs_fstatat+0x94/0xb0
Oct 03 01:38:50 meerkat kernel:  ? __do_sys_newfstatat+0x3c/0x80
Oct 03 01:38:50 meerkat kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Oct 03 01:38:50 meerkat kernel:  ? do_syscall_64+0x66/0x80
Oct 03 01:38:50 meerkat kernel:  ? __rseq_handle_notify_resume+0xa9/0x4e0
Oct 03 01:38:50 meerkat kernel:  ? __call_rcu_common+0xf4/0x720
Oct 03 01:38:50 meerkat kernel:  ? exit_to_user_mode_prepare+0x17d/0x1f0
Oct 03 01:38:50 meerkat kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Oct 03 01:38:50 meerkat kernel:  ? do_syscall_64+0x66/0x80
Oct 03 01:38:50 meerkat kernel:  ? do_syscall_64+0x66/0x80
Oct 03 01:38:50 meerkat kernel:  ? exit_to_user_mode_prepare+0x17d/0x1f0
Oct 03 01:38:50 meerkat kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Oct 03 01:38:50 meerkat kernel:  ? do_syscall_64+0x66/0x80
Oct 03 01:38:50 meerkat kernel:  ? do_syscall_64+0x66/0x80
Oct 03 01:38:50 meerkat kernel:  entry_SYSCALL_64_after_hwframe+0x78/0xe2
Oct 03 01:38:50 meerkat kernel: RIP: 0033:0x7f3e3eb6b1fd
Oct 03 01:38:50 meerkat kernel: Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01>
Oct 03 01:38:50 meerkat kernel: RSP: 002b:00007ffc706bd8b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Oct 03 01:38:50 meerkat kernel: RAX: ffffffffffffffda RBX: 00005558f5e0d520 RCX: 00007f3e3eb6b1fd
Oct 03 01:38:50 meerkat kernel: RDX: 0000000000000004 RSI: 00007f3e3e38b05d RDI: 000000000000001f
Oct 03 01:38:50 meerkat kernel: RBP: 00007ffc706bd970 R08: 0000000000000001 R09: 00007ffc706bd900
Oct 03 01:38:50 meerkat kernel: R10: 0000000000000040 R11: 0000000000000246 R12: 00007f3e3e38b05d
Oct 03 01:38:50 meerkat kernel: R13: 0000000000020000 R14: 00005558f5e04c10 R15: 00005558f5e0f250
Oct 03 01:38:50 meerkat kernel:  </TASK>
Oct 03 01:38:50 meerkat kernel: ---[ end trace 0000000000000000 ]---
Oct 03 01:38:50 meerkat kernel: sd 3:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
Oct 03 01:38:50 meerkat kernel: systemd[1]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
lines 128-168/168 (END)

I’ve captured this output a couple of times and compared/looked for issues and it’s not always the same.

2

You may need more RAM, or at least some swap :wink:
:footprints:

I would suggest 12GB swap partition at least.

4 Likes
3

Since I’ve opened a thread now. I will do a fresh install now and ensure I add swap. I’ll leave Jellyfin off. Just a default install of Manajro right now. It just crashed and rebooted again in the time since I made this post 5 minutes ago. :smiley: Sometimes I can watch a movie on Jellyfin and it not crash. But most often it happens within an hour of trying this system. Rarely does it happen when I actually am trying to reproduce the issue. :wink:

4

I’m rusty using the manual partition option in the GUI. Can’t figure out how to get it where it will let me click next. When I use Erase disk and add Swap (no hibernate) it allocates 8.15Gib. I guess ill start with that. Can’t we re-size it afterwards?

5

If it is a swap file - yes.
Otherwise you’d need to shrink one partition to grow the other.

But:
this amount of swap should be enough - your inxi system info shows your RAM only lightly / partially used
I have had zero problems running all variants of Manjaro in a VM with only 4 GB allocated to it and without any swap -
on a host that has got 8 GB RAM and the same amount of swap
so, the host is running on 4 GB only as well while the VM is running.

6

I got the install done. Haven’t even run updates yet. Stepped away from the computer for 5 minutes and it already rebooted. Wow.

Partition:
  ID-1: / raw-size: 224.45 GiB size: 219.87 GiB (97.96%) used: 6.11 GiB (2.8%)
    fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2 label: N/A
    uuid: cfff1955-8fd2-45b3-b3a9-343a3b4ebe85
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 296 KiB (0.1%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
    maj-min: 259:1 label: N/A uuid: F778-35A1
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 8.14 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p3 maj-min: 259:3 label: swap
    uuid: a5aadaec-b59f-4157-9f9e-3c9c9711a266
7

I would try a memory test or even more simple… wait in Bios for a reset.

If both are running stable, i would go next and wait in a live boot for a crash/freeze/reset.

Since you not using a dedicated GPU… and your CPU looks extremly good cooled. Im guessing it could be something around your RAM, but its to early to judge here.

1 Like
8

Good ideas. Will do and report back. I’m running updates and will try those next.

sudo pacman-mirrors --continent && sudo pacman -Syu

9

BIOS ran a good 20+ hours, watched the clock count up. Memorytest86+ passed.

10

All right, this sounds good.

Next step i would let your system idle in the newest iso Live boot.

Did you installed something special? The last time where your system froze after the fresh install.

1 Like
11

Correct, freezes even after a fresh install. All I’ve done this go around is run updates pacman -Syu and install openssh so I can access from my other computer.

Yesterday after the memory test I simply rebooted it and left it at the XFCE login screen. Turned monitor off, came back this morning, and I can’t even get the monitor to output (keyboard not waking it up). I had to hold power button down. :frowning:

Booted into live USB session now. Ill leave it like this for a couple hours.

12

This isn’t a Laptop right? So you have a Num LED on your Keyboard and still can be turned on/off correct?

When Num/Capslock/Scroll LED not flashing and can be manual turned on/off, that is a good sign.

Probably switching Kernels 6.1 LTS or the newest 6.10/6.11 Kernels to evade issues.

With activated Swap, you can also look in your logs after a reboot.

journalctl -p err -b -1

Reisub, could also help to revive your system:

Another ways to rive your system by pressing:
crlt+alt+backspace
crlt+alt+F1-F5 Keys switching to TTY and back to desktop.

1 Like
13

5 hours running off live image, with a GUI terminal open (left a ping running). It’s not a laptop, it’s like a mini-pc or nuc. I will try the other kernels.

14

That sounds pretty good, are you using the newest ISO there? So its Kernel 6.10 in this live boot?

15

I dont think its that kernel. Let me check. I let it run another 24 hours on the live usb no issues. Apologies, may take me bit longer to respond during the middle of the week vs weekend.

16

Thats okay, let your time… im fine with it.

I’m additional asked about the Kernel because the newest Live Iso is using 6.10 Kernel but changing Kernel could help… you never know.

17

6.6.52 is the kernel that’s been on it from the install (not the live usb iso). Will try 6.1 and the newer ones 6.10/11 and report back.

18

Alright, good luck.

19

Ran on 6.11.0 kernel, left it on the desktop before bed pinging 127.0.0.1. Just giving it something to do. This morning it had rebooted with an uptime of 15 minutes. I wonder how many times it rebooted overnight.

20

If your system is this unstable, why you let it run overnight anyways?

I really don’t understand why a live boot is running stable but a install won’t.
:thinking:

Since your Live Boot was 6.10, right? maybe 6.10 Kernel works better for you :man_shrugging: