Manjaro freezing unexpectedly on Dell Latitude 7480

Hi all, i’m fairly new to linux and brand new to Manjaro. A friend was getting rid of a Dell Latitude 7480 which won’t support Windows 11, so i figured i’d try to get Manjaro up and running on it.

Overall, the install seems to have worked, but i have an issue: random freezes. It has happened 5-6 times today over several hours of use. The first few times were soon after boot, with only Firefox running. Then it happened several times while using the “Add/Remove Software” tool (once while downloading/building a package, another time while just searching). It also happened from the lock/login screen.

During the install, a message appeared saying something about the sytem not meeting minimum requirements for Manjaro, but i pushed through it because, as far as i can tell, the hardware meets the system recommendations listed in the Manjaro documentation.

When frozen, the system will not accept any keyboard input (including REISUB) and the only thing i’ve found to do is a full system reboot by holding down the power button. Mostly the pointer has disappeared but on the last one, it remained visible and moveable although clicking was not responsive.

Here are the system parameters from inxi

CPU: dual core Intel Core i7-7600U (-MT MCP-) speed/min/max: 400/400/3900 MHz
Kernel: 6.12.39-1-MANJARO x86_64 Up: 3m Mem: 1.17/15.5 GiB (7.5%)
Storage: 476.94 GiB (1.5% used) Procs: 203 Shell: Zsh inxi: 3.3.38

I have seen several similar threads on here but it seems like each has a different solution (downgrade the bios, stop memory bleed by deleting/modifying certain files, etc.)

Again, being fairly new to linux, does anyone have any recommendations for how to proceed with figuring out what’s going on and debugging?

Thanks!

It sounds very much like your BIOS (firmware) is not cooperating with Linux’s aggressive power saving settings. This means that Linux switches to a high C-state to save power, but this is too low to keep the processor/gpu alive and it freezes.

I would recommend adding:

# Create the directory:
sudo mkdir /etc/default/grub.d/
# Create the file:
echo "GRUB_CMDLINE_LINUX_DEFAULT+=\" intel_idle.max_cstate=1 \"" | sudo tee -a /etc/default/grub.d/00-overwrite.cfg
# Update grub:
sudo grub-mkconfig -o /boot/grub/grub.cfg

Now reboot. The config restricts the CPU to use only C0 - C1. If that helps, then you can try to go higher and see when it happens again.

However, I would strongly recommend updating the BIOS/UEFI if possible.

You can also add:

i915.enable_dc=0 i915.enable_fbc=0 i915.enable_psr=0

to the kernel parameter like above. That will disable some power saving features of the gpu, which can produce problems on older devices.

1 Like

Please provide system information as described (below).

Regards.


Welcome to the Manjaro community

As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit:


Update Announcements

The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.

System Information

While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly; :eyes:

Output of the inxi command with appropriate parameters will achieve this (naturally, formatted according to forum guidelines) and will generally be more useful for those wishing to help:

inxi --filter --verbosity=8

or the short form:

inxi -zv8

Be prepared to provide output from other commands whenever asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.

Highly Recommended
Technical Resources
Required Reading

1 Like

@megavolt, thanks for your quick reply! I just tried the commands that you suggested to limit the CPU cores used. It froze within 2 min of reboot (Firefox, again).

I then added the i915.enable statements and it seems ok so far, but need to keep playing with it to be sure.

@soundofthunder hte inxi output is very large, do you need all of it? Here is what seems likely to be relevant to me, but i’m not sure!

System:
  Kernel: 6.12.39-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.12-x86_64
    root=UUID=38fce4db-8a9a-442a-8c5f-4896aa52ba21 rw rootflags=subvol=@
    quiet
    cryptdevice=UUID=52642e83-a600-4617-8fe3-179221716096:luks-52642e83-a600-4617-8fe3-179221716096
    root=/dev/mapper/luks-52642e83-a600-4617-8fe3-179221716096 splash
    udev.log_priority=3 intel_idle.max_cstate=1 i915.enable_dc=0
    i915.enable_fbc=0 i915.enable_psr=0
  Desktop: KDE Plasma v: 6.3.6 tk: Qt v: N/A info: frameworks v: 6.16.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: Dell product: Latitude 7480 v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Dell model: 00F6D3 v: A00 serial: <superuser required> part-nu: 07A0
    uuid: <superuser required> UEFI: Dell v: 1.4.6 date: 05/18/2017
Memory:
  System RAM: total: 16 GiB available: 15.5 GiB used: 1.8 GiB (11.6%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 32 GiB slots: 2 modules: 2 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: DIMM A type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: spec: 2400 MT/s actual: 2133 MT/s volts: note: check
    curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
    manufacturer: 80AD000080AD part-no: HMA81GS6AFR8N-UH serial: <filter>
  Device-2: DIMM B type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: spec: 2400 MT/s actual: 2133 MT/s volts: note: check
    curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
    manufacturer: 80AD000080AD part-no: HMA81GS6AFR8N-UH serial: <filter>
CPU:
  Info: model: Intel Core i7-7600U bits: 64 type: MT MCP arch: Amber/Kaby Lake
    note: check gen: core 7 level: v3 note: check built: 2017
    process: Intel 14nm family: 6 model-id: 0x8E (142) stepping: 9
    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: 800 min/max: 400/3900 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 23209
  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 smx 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
Graphics:
  Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel
    arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1
    empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5916
    class-ID: 0300
  Device-2: Sunplus Innovation Integrated_Webcam_HD driver: uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:2
    chip-ID: 1bcf:2b96 class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_x11 driver: X: loaded: modesetting alternate: fbdev,vesa
    dri: iris gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93") monitors: <missing: xrandr>
  Monitor-1: eDP-1 model: AU Optronics 0x333d built: 2016 res: 1920x1080
    dpi: 158 gamma: 1.2 chroma: red: x: 0.631 y: 0.337 green: x: 0.322 y: 0.616
    blue: x: 0.157 y: 0.039 white: x: 0.314 y: 0.329
    size: 309x174mm (12.17x6.85") diag: 355mm (14") ratio: 16:9
    modes: 1920x1080
  EDID-Warnings: 1: parse_edid: unknown flag 0
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
    inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.1.6-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 620 (KBL GT2)
    device-ID: 8086:5916 memory: 15.14 GiB unified: yes
  API: Vulkan v: 1.4.321 layers: N/A device: 0 type: integrated-gpu
    name: Intel HD Graphics 620 (KBL GT2) driver: mesa intel v: 25.1.6-arch1.1
    device-ID: 8086:5916 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo,xprop
Info:
  Processes: 216 Power: uptime: 5m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.18 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Compilers: clang: 20.1.8 gcc: 15.1.1 Shell: Zsh v: 5.9 running-in: konsole
    inxi: 3.3.38

Does that get you what you need? Thanks for all of both of your support!

Please provide the full inxi -zv8 output, as requested by @soundofthunder

The edited output you provided is lacking some vital information (2 of the first 3 things I usually look at when a system is randomly crashing).

Also, I see that you are still using Plasma with X11. Does switching to Plasma on Wayland make any difference?

You can change your Plasma session from X11 to Wayland by selecting the session type at the login screen (Wayland is now KDE’s default for Plasma).

If you have set up autologin to skip the password screen, you can change to a Wayland session by opening System Settings → Colors & Themes → Login Screen (SDDM) → Behavior.

Topic closed as seems to be abandoned. @roonsta if you wish to revisit this, let us know.