Manjaro freezes, REISUB does not help, journal is empty

Support
1

My distro keeps freezing up, randomly, with different time intervals between several hours to several days. Doesn’t react to keyboard, or mouse. REISUB does not work (albeit I enabled and tested it). I disconnected and reconnected keyboard - keyboard did light up its RGB. I disconnected and reconnected monitor, and it said “No Signal”. Reviewing journalctl output, I get nothing - no crashes, nothing besides some bluetooth bs.

I have exhausted ideas I’ve been able to find. Did anyone encounter something exactly like this?

Here is my inxi --admin --verbosity=7 --filter --no-host --width output:

System:
  Kernel: 6.18.12-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.18-x86_64
    root=UUID=c8acbe4d-40dc-46d7-a39b-ccefa7cacd5b rw rootflags=subvol=@ quiet
    splash udev.log_priority=3 pcie_aspm=off
  Desktop: KDE Plasma v: 6.5.5 tk: Qt v: N/A info: frameworks v: 6.23.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: B850 GAMING X WIFI6E v: -CF-WCP
    serial: <superuser required>
  Mobo: Gigabyte model: B850 GAMING X WIFI6E v: x.x
    serial: <superuser required> uuid: <superuser required> Firmware: UEFI
    vendor: American Megatrends LLC. v: F1 date: 09/24/2024
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 64 GiB available: 60.44 GiB used: 6.11 GiB (10.1%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB slots: 4 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Channel-A DIMM 0 type: no module installed
  Device-2: Channel-A DIMM 1 type: DDR5 detail: synchronous unbuffered
    (unregistered) size: 32 GiB speed: 6400 MT/s volts: note: check curr: 1
    min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: Corsair
    part-no: CMK64GX5M2B6400C32 serial: N/A
  Device-3: Channel-B DIMM 0 type: no module installed
  Device-4: Channel-B DIMM 1 type: DDR5 detail: synchronous unbuffered
    (unregistered) size: 32 GiB speed: 6400 MT/s volts: note: check curr: 1
    min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: Corsair
    part-no: CMK64GX5M2B6400C32 serial: N/A
CPU:
  Info: model: AMD Ryzen 7 9700X bits: 64 type: MT MCP arch: Zen 5 gen: 5
    level: v4 note: check built: 2024+ process: TSMC n4 (4nm) family: 0x1A (26)
    model-id: 0x44 (68) stepping: 0 microcode: 0xB40401C
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
    smt: enabled cache: L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 8 MiB
    desc: 8x1024 KiB L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 2993 min/max: 605/5582 boost: enabled scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 2993 2: 2993 3: 2993
    4: 2993 5: 2993 6: 2993 7: 2993 8: 2993 9: 2993 10: 2993 11: 2993 12: 2993
    13: 2993 14: 2993 15: 2993 16: 2993 bogomips: 121383
  Flags: 3dnowprefetch abm adx aes amd_lbr_pmc_freeze amd_lbr_v2 aperfmperf
    apic arat avx avx2 avx512_bf16 avx512_bitalg avx512_vbmi2 avx512_vnni
    avx512_vp2intersect avx512_vpopcntdq avx512bw avx512cd avx512dq avx512f
    avx512ifma avx512vbmi avx512vl avx_vnni bmi1 bmi2 bpext bus_lock_detect
    cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy constant_tsc
    cpb cppc cpuid cpuid_fault cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists erms extapic
    extd_apicid f16c flush_l1d flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt
    gfni ht hw_pstate ibpb ibrs ibrs_enhanced ibs invpcid irperf lahf_lm lbrv
    lm mba mca mce misalignsse mmx mmxext monitor movbe movdir64b movdiri msr
    mtrr mwaitx nonstop_tsc nopl npt nrip_save nx ospke osvw overflow_recov
    pae pat pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb
    perfmon_v2 pfthreshold pge pku pni popcnt pse pse36 rapl rdpid rdpru
    rdrand rdt_a rdtscp rep_good sep sha_ni skinit smap smca smep ssbd sse
    sse2 sse4_1 sse4_2 sse4a ssse3 stibp succor svm svm_lock syscall tce
    topoext tsc tsc_adjust tsc_scale umip user_shstk v_spec_ctrl
    v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall vnmi vpclmulqdq wbnoinvd
    wdt xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves xtopology
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: IBPB on VMEXIT only
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB: conditional;
    STIBP: always-on; 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 on VMEXIT
Graphics:
  Device-1: NVIDIA GB205 [GeForce RTX 5070] vendor: Gigabyte driver: nvidia
    v: 590.48.01 alternate: nouveau,nova_core,nvidia_drm non-free: 550-580.xx+
    status: current (as of 2025-11) arch: Lovelace code: AD1xx
    process: TSMC n4 (5nm) built: 2022+ pcie: gen: 5 speed: 32 GT/s lanes: 16
    ports: active: none off: HDMI-A-2 empty: DP-4,DP-5,DP-6 bus-ID: 01:00.0
    chip-ID: 10de:2f04 class-ID: 0300
  Device-2: Advanced Micro Devices [AMD/ATI] Granite Ridge [Radeon Graphics]
    vendor: Gigabyte driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
    process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16
    ports: active: none empty: DP-1, DP-2, DP-3, HDMI-A-1, Writeback-1
    bus-ID: 11:00.0 chip-ID: 1002:13c0 class-ID: 0300 temp: 34.0 C
  Display: x11 server: X.Org v: 21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_x11 driver: X: loaded: amdgpu,nvidia
    unloaded: modesetting,nouveau alternate: fbdev,nv,vesa dri: radeonsi
    gpu: nv_platform,nvidia,nvidia-nvswitch display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 108 s-size: 602x342mm (23.70x13.46")
    s-diag: 692mm (27.26")
  Monitor-1: HDMI-A-2 mapped: HDMI-0 note: disabled
    model: LG (GoldStar) ULTRAGEAR serial: <filter> built: 2024 res:
    mode: 2560x1440 hz: 144 scale: 100% (1) dpi: 109 gamma: 1.2
    size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9 modes:
    max: 2560x1440 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia drv: amd radeonsi platforms: device: 0
    drv: nvidia device: 2 drv: radeonsi device: 3 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 590.48.01
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 5070/PCIe/SSE2
    memory: 11.66 GiB
  API: Vulkan v: 1.4.341 layers: 4 device: 0 type: discrete-gpu
    name: NVIDIA GeForce RTX 5070 driver: nvidia v: 590.48.01
    device-ID: 10de:2f04 surfaces: N/A device: 1 type: integrated-gpu name: AMD
    Ryzen 7 9700X 8-Core Processor (RADV RAPHAEL_MENDOCINO) driver: mesa radv
    v: 25.3.5-arch1.1 device-ID: 1002:13c0 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: NVIDIA GB205 High Definition Audio driver: snd_hda_intel v: kernel
    pcie: gen: 5 speed: 32 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:2f80
    class-ID: 0403
  Device-2: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 11:00.1 chip-ID: 1002:1640 class-ID: 0403
  Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 11:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.18.12-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.4.10 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8852CE PCIe 802.11ax Wireless Network
    driver: rtw89_8852ce v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: d000
    bus-ID: 07:00.0 chip-ID: 10ec:c852 class-ID: 0280
  IF: wlp7s0 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: c000 bus-ID: 08:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp8s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-9:4 chip-ID: 0bda:0852
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 4.55 TiB used: 94.62 GiB (2.0%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: Samsung model: SSD 990 EVO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 126 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 0B2QKXJ7 temp: 46.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:7 vendor: Samsung
    model: SSD 990 EVO Plus 1TB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QKXG7 temp: 44.9 C scheme: GPT
  ID-3: /dev/nvme2n1 maj-min: 259:0 vendor: Samsung model: SSD 990 PRO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 4B2QJXD7 temp: 43.9 C
    scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 860.45 GiB size: 860.45 GiB (100.00%)
    used: 94.62 GiB (11.0%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:9
    label: N/A uuid: c8acbe4d-40dc-46d7-a39b-ccefa7cacd5b
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 668 KiB (0.2%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:8 label: N/A
    uuid: 3D1A-E16F
  ID-3: /home raw-size: 860.45 GiB size: 860.45 GiB (100.00%)
    used: 94.62 GiB (11.0%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:9
    label: N/A uuid: c8acbe4d-40dc-46d7-a39b-ccefa7cacd5b
  ID-4: /var/cache raw-size: 860.45 GiB size: 860.45 GiB (100.00%)
    used: 94.62 GiB (11.0%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:9
    label: N/A uuid: c8acbe4d-40dc-46d7-a39b-ccefa7cacd5b
  ID-5: /var/log raw-size: 860.45 GiB size: 860.45 GiB (100.00%)
    used: 94.62 GiB (11.0%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:9
    label: N/A uuid: c8acbe4d-40dc-46d7-a39b-ccefa7cacd5b
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 70.77 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme1n1p3 maj-min: 259:10 label: N/A
    uuid: 84f258dd-bfd5-443f-8d2f-4898813c3f5a
Unmounted:
  ID-1: /dev/nvme0n1p1 maj-min: 259:3 size: 200 MiB fs: vfat label: N/A
    uuid: 0016-866E
  ID-2: /dev/nvme0n1p2 maj-min: 259:4 size: 16 MiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-3: /dev/nvme0n1p3 maj-min: 259:5 size: 1.82 TiB fs: ntfs label: N/A
    uuid: 06B416D2B416C459
  ID-4: /dev/nvme0n1p4 maj-min: 259:6 size: 735 MiB fs: ntfs label: N/A
    uuid: 0058704B58704188
  ID-5: /dev/nvme2n1p1 maj-min: 259:1 size: 1.82 TiB fs: ntfs label: N/A
    uuid: C8D8D72ED8D71A10
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-5:2 info: Razer USA Basilisk V3 Pro 35K type: mouse,keyboard
    driver: razermouse,usbhid interfaces: 4 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 1532:00cc class-ID: 0301
    serial: <filter>
  Device-2: 1-6:3 info: Integrated Express GIGABYTE Device type: HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 048d:5711 class-ID: 0300
  Device-3: 1-9:4 info: Realtek Bluetooth Radio type: bluetooth driver: btusb
    interfaces: 2 rev: 1.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 500mA chip-ID: 0bda:0852 class-ID: e001 serial: <filter>
  Hub-2: 2-0:1 info: super-speed hub ports: 5 rev: 3.1
    speed: 20 Gb/s (2.33 GiB/s) lanes: 2 mode: 3.2 gen-2x2 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-4: 4-0:1 info: super-speed hub ports: 2 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
  Hub-5: 5-0:1 info: hi-speed hub with single TT ports: 2 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: 5-1:2 info: Razer USA Basilisk V3 Pro 35K type: mouse,keyboard
    driver: razermouse,usbhid interfaces: 5 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 1532:00cd class-ID: 0300
    serial: <filter>
  Hub-6: 6-0:1 info: super-speed hub ports: 2 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
  Hub-7: 7-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-8: 7-1:2 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Device-1: 7-1.2:3 info: Razer USA BlackWidow V4 75%
    type: keyboard,mouse,HID driver: razerkbd,usbhid interfaces: 5 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 500mA
    chip-ID: 1532:02a5 class-ID: 0300
Sensors:
  System Temperatures: cpu: 41.0 C mobo: 32.0 C
  Fan Speeds (rpm): N/A
  GPU: device: nvidia screen: :0.0 temp: 44 C fan: 0% device: amdgpu
    temp: 35.0 C
Info:
  Processes: 491 Power: uptime: 2m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 24.11 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 259 default: graphical
    tool: systemctl
  Packages: pm: pacman pkgs: 1439 libs: 371 tools: pamac,yay pm: flatpak
    pkgs: 0 Compilers: gcc: 15.2.1 Shell: Bash v: 5.3.9 default: Zsh v: 5.9
    running-in: konsole inxi: 3.3.40
2

Hi @g00dm0us3 ,

Welcome to the forum. :confetti_ball:

Your board is on F1 (Firmware 1) — the launch BIOS from September 2024.

vendor: American Megatrends LLC. v: F1 date: 09/24/2024

The latest is F9.

For a brand new platform like B850 + Zen 5 + DDR5-6400, early BIOS revisions almost always get stability fixes that the OS simply can’t compensate for.

Worth updating before digging deeper.

https://www.gigabyte.com/Motherboard/B850-GAMING-X-WIFI6E-rev-1x/support#Support-Bios

Be aware:

After firmware update, BIOS goes to default settings.

7 Likes
3

What were(are) you doing, which applications is running at the point of freeze? Not that I think it makes much difference but it could give you a direction.

If the system

  • does not react - at all
  • the direct kernel commands fail
  • nothing in the journal

I am thinking low level - really low level - hardware issue - the kind of issue that never reaches the kernel - like direct kernel commands and journal.

This can be anything - I am guessing

  • undervolting
  • firmware

I any case - as suggested by @musdus - update the firmware - but also check the general firmware setup - especially if the firmware provides voltage and timing adjustment for CPU and RAM.

Apply the firmware defaults and reboot - search for more details on your specific board revision.

1 Like
4

You can try another LTS Kernel, switch to 6.12 LTS for example.

  1. Was your system stable in the past with Manjaro?
  2. Since when exactly did this instability happening?
  3. Did you made any manually changes since then?

I also can’t see in your Grub Parameter’s that you had REISUB successfull activated.

Updating might be a good idea, specially a F1 Bios.

But im not sure if it made sense now… without finding the culprit first for this instabilitys.

If his system was running stable in the past or not… which is unclear yet. Based on the lag of information what we got here at this moment, it was never a good decision to made multiple changes to a system.

I recently saw a info from a AMD 9800X3D user complaint that he can’t boot into Linux and that he can’t even reinstall it anymore with the newest Motherboard Firmware.

He told me in discord, that he had to disable ACPI to use Linux again, till the vendor fixes the firmware for linux.

5

Thank you, will update, and see if it helps :crossed_fingers:

6
  • Was your system stable in the past with Manjaro?
  • Since when exactly did this instability happening?
  • Did you made any manually changes since then?
  1. No, it was doing this right from the start.
  2. Since install. Not much new there.
  3. I removed a bunch of apps I installed via snapd. Stopped using Chrome.

About REISUB, so this command cat /proc/sys/kernel/sysrq gives me 1, and when I tap on system rq, and type the thing, PC reloads. I followed these intructions , is these anything else I need to do?

Will look into the ACPI thing, don’t even know what is.

7
8

Add (NOT overwrite anything) this in your /etc/default/grub:

sysrq_always_enabled=1

after you added this, execute:

sudo update-grub

Since you new to Manjaro, its maybe also worth to ask, if you new to Linux?

Maybe you did some mistakes while installing?

Manjaro is a rolling distro and required the latest ISO… you run into problem if you install a ISO which might be several month old. Because you shouldn’t skip release updates between.

You should also be aware that a Stable System under Windows, isn’t a stable system under Linux.

I found out after i switched from Windows to Linux, that i have to reduce my OC from my CPU. My system was running stable with Prime95 and massive gaming with 4,7Ghz OC under Windows, but for Linux i had to reduce to it by 200Mhz to 4,5Ghz.

As long this install is fresh, i would also ask myself if you really want to use BTRFS instead EXT4.
Are you aware about the additional maintaining that BTRFS required and that EXT4 is more userfriendly?

EDIT: Probably Off-Topic:
TBH, since i don’t know much, how BTRFS is behaving when going into copywrite mode, how does it look?
Is there a clear output in journal? Does our System freeze like from OP? I don’t know..

9

What exactly do you mean by that? :thinking:

10

When you using BTRFS and the checksum check from BTRFS identify a data loss/file corruption. From my understanding the filesystem is locking up, it went into copywrite protection mode.

Im wondering how the desktop behaves, what the journal is saying?
Does your system freezing because it can’t modify any system file’s?

And how can you identify the difference to a SSD, who is going to die… which can also go into copywrite protection mode then.

BTW. i think this conversation is going a little bid off-topic, since the chances are not high enough that BTRFS is the culprit here, i guess.

11

You mean read-only mode. Well, no, btrfs is self-healing. It stores the metadata in duplicate, and it can use this and the journal to repair file damage.

Filesystem damage is another thing, and is very rare on btrfs — much rarer than on ext4.

The error messages would be similar, except for those aspects of the filesystem that are distinct from ext4, of course, because btrfs is not only a filesystem but also a volume manager.

System files are normally never written to during normal operation. About half of my many btrfs subvolumes are mounted read-only anyway. But btrfs will upon mounting the subvolume always inspect the filesystem journal and play it back if needed for its self-healing, even on filesystems or subvolumes that are normally mounted read-only.

That’s a different kind of error messages. In that case, it’s not the filesystem that errors, but the hardware. So you’d be getting S.M.A.R.T.-related errors in the system log and in dmesg.

Indeed. The problem sits elsewhere. ACPI could be a clue — some BIOS or UEFI firmwares have a buggy implementation of it.

1 Like
12

Please do not forget to check your RAM for errors. (This may take some time)
:footprints:

1 Like
13

Yeah, I am pretty new to Linux. While installing, I basically just downloaded the latest ISO for KDE, and chose as I remember proprietary drivers for GPU and something called Wayland which I later changed to X11 in an effort to fix my problem.

I don’t have my CPU overclocked, but I do have XMP enabled in BIOS, maybe that’s can also be trouble? In any case I updated BIOS. Now, while loading I no longer get “RSEED bit is broken” or something of the sort. I am pretty sure it was innocuous, but I am still glad it’s gone)

Sad but true (c) as I realize now.

I am not aware of the BTRFS situation, last time I touched Linux (fifteen years ago), it was all EXT. In any case, I am interested to look into it.

Btw, thank you for your answer.

14

Wayland, like X11, is a display server protocol, but it works differently. KDE Plasma now defaults to Wayland, and as of Plasma 6.8, all X11 support in Plasma will be dropped completely.

The problem child in the classroom is of course Nvidia. Only their newest proprietary drivers work properly with Wayland.

Absolutely!

I’m afraid @Kobold has either expressed himself badly — he’s not a native English speaker — or he’s wrong.

The thing is that Microsoft Windows isn’t particularly picky on whether the hardware properly functions or not. The Linux kernel on the other hand is.

The following thread — see the link below — may serve as an introduction, but it’s only the tip of the iceberg. btrfs is a very advanced filesystem, and contrary to what some of our more conservative members believe, it is far more robust than ext4. :backhand_index_pointing_down:

2 Likes
15

There you’ll find everything that’s different about btrfs.
:footprints:

1 Like
19

It’s been a couple of days w/o freezes. I updated BIOS and left XMP enabled. This seems to have done the trick. Thx!

1 Like
20

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.