Crash after dup to 20250727

I did yesterday a zypper dup from the runlevel 3. Everything went fine. Rebooted: no problem.

Shutdown and a few hours later turned on the laptop.

Grub comes up and select the 6.12.40-longterm. Then it got stuck on:

loading initial ramdisk

and that’s it. It’s stuck there. After 3 minutes (actual time) I had to press the power button for 4 sec to shut it down.

I restarted and it worked properly, so I immediately checked the journalctl and absolutely nothing of the failed boot. There was no entry for that boot, but there was for the subsequent one and it was normal. Nothing out of the ordinary entry in the journalctl.

This has already happened twice and only on cold boots.

$ inxi -Fxxx
System:
  Host: dodoite Kernel: 6.12.40-1-longterm arch: x86_64 bits: 64 compiler: gcc
    v: 15.1.1 clocksource: tsc
  Desktop: Xfce v: 4.20.1 tk: Gtk v: 3.24.48 wm: xfwm4 v: 4.20.0
    with: xfce4-panel tools: xfce4-screensaver vt: 7 dm: LightDM v: 1.32.0
    Distro: openSUSE Tumbleweed 20250727
Machine:
  Type: Laptop System: Alienware product: Alienware m16 R2 v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Alienware model: 0MNHT9 v: A01 serial: <superuser required>
    part-nu: 0C91 uuid: <superuser required> UEFI: Alienware v: 1.12.0
    date: 03/27/2025
Battery:
  ID-1: BAT0 charge: 43.4 Wh (53.0%) condition: 81.9/88.2 Wh (92.9%)
    volts: 10.9 min: 11.7 model: SMP DELL M9DG052E type: Li-poly serial: 421
    status: not charging cycles: 5
CPU:
  Info: 16-core (6-mt/10-st) model: Intel Core Ultra 9 185H bits: 64
    type: MST AMCP smt: enabled arch: Meteor Lake rev: 4 cache: L1: 1.6 MiB
    L2: 18 MiB L3: 24 MiB
  Speed (MHz): avg: 1834 min/max: 400/4800:5100:3800:2500 cores: 1: 1834
    2: 1834 3: 1834 4: 1834 5: 1834 6: 1834 7: 1834 8: 1834 9: 1834 10: 1834
    11: 1834 12: 1834 13: 1834 14: 1834 15: 1834 16: 1834 17: 1834 18: 1834
    19: 1834 20: 1834 21: 1834 22: 1834 bogomips: 135168
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Meteor Lake-P [Intel Arc Graphics] vendor: Dell driver: N/A
    arch: Xe-LPG bus-ID: 00:02.0 chip-ID: 8086:7d55 class-ID: 0300
  Device-2: NVIDIA AD107M [GeForce RTX 4060 Max-Q / Mobile] vendor: Dell
    driver: nvidia v: 570.172.08 arch: Lovelace pcie: speed: 2.5 GT/s lanes: 8
    ports: active: none off: HDMI-A-1,eDP-1 empty: DP-1 bus-ID: 01:00.0
    chip-ID: 10de:28e0 class-ID: 0300
  Device-3: Realtek Integrated_Webcam_FHD driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-9:7 chip-ID: 0bda:557c
    class-ID: fe01 serial: 200901010001
  Display: x11 server: X.org v: 1.21.1.15 compositor: xfwm4 v: 4.20.0
    driver: X: loaded: nvidia unloaded: modesetting,vesa
    alternate: fbdev,nouveau,nv gpu: nvidia,nvidia-nvswitch display-ID: :0.0
    screens: 1
  Screen-1: 0 s-res: 2560x1440 s-size: <missing: xdpyinfo>
  Monitor-1: not-matched mapped: DP-2 size-res: N/A modes: N/A
  Monitor-2: not-matched mapped: HDMI-0 pos: primary res: mode: 2560x1440
    hz: 60 scale: 100% (1) dpi: 109 size: 597x336mm (23.5x13.23")
    diag: 685mm (26.97") modes: N/A
  API: OpenGL v: 4.6.0 vendor: nvidia v: 570.172.08 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce RTX 4060 Laptop GPU/PCIe/SSE2
  Info: Tools: api: glxinfo de: xfce4-display-settings
    gpu: nvidia-settings,nvidia-smi x11: xprop,xrandr
Audio:
  Device-1: Intel Meteor Lake-P HD Audio vendor: Dell
    driver: sof-audio-pci-intel-mtl bus-ID: 00:1f.3 chip-ID: 8086:7e28
    class-ID: 0401
  Device-2: NVIDIA AD107 High Definition Audio vendor: Dell
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 8
    bus-ID: 01:00.1 chip-ID: 10de:22be class-ID: 0403
  API: ALSA v: k6.12.40-1-longterm status: kernel-api with: aoss
    type: oss-emulator
  Server-1: PipeWire v: 1.4.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Realtek Killer E3000 2.5GbE vendor: Dell driver: r8169 v: kernel
    pcie: speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 2e:00.0 chip-ID: 10ec:3000
    class-ID: 0200
  IF: enp46s0 state: down mac: e8:cf:83:0b:51:56
  Device-2: Intel Wi-Fi 7 AX1775 /AX1790 /BE20 /BE401/BE1750 2x2
    driver: iwlwifi v: kernel pcie: speed: 16 GT/s lanes: 1 bus-ID: 2f:00.0
    chip-ID: 8086:272b class-ID: 0280
  IF: wlp47s0f0 state: up mac: 44:38:e8:c3:f2:b7
  IF-ID-1: bridge0 state: down mac: 22:b0:3a:55:80:cc
Drives:
  Local Storage: total: 953.87 GiB used: 117.34 GiB (12.3%)
  ID-1: /dev/nvme0n1 vendor: Micron model: 2550 1024GB size: 953.87 GiB
    speed: 63.2 Gb/s lanes: 4 tech: SSD serial: 24374C02C7B4 fw-rev: 25500201
    temp: 34.9 C scheme: GPT
Partition:
  ID-1: / size: 123.31 GiB used: 16.8 GiB (13.6%) fs: ext4 dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 511 MiB used: 25 MiB (4.9%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: /home size: 782.51 GiB used: 100.52 GiB (12.8%) fs: ext4
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: partition size: 31.45 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p4
Sensors:
  System Temperatures: cpu: 52.0 C mobo: 51.0 C gpu: nvidia temp: 44 C
  Fan Speeds (rpm): cpu: 0 fan-2: 0
Info:
  Memory: total: 32 GiB note: est. available: 30.86 GiB used: 2.05 GiB (6.6%)
  Processes: 389 Power: uptime: 0h 17m states: freeze,mem,disk
    suspend: s2idle wakeups: 0 hibernate: platform Init: systemd v: 257
    default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm Compilers: gcc: 15.1.1 alt: 14
    Shell: Bash v: 5.2.37 running-in: xfce4-terminal inxi: 3.3.37

and here’s my grub start line:

nomodeset fbdev=1 ipv6.disable=1 rd.driver.blacklist=nouveau resume=/dev/disk/by-uuid/a8ea6820-4ab1-4bab-8468-d310d5626a16 quiet security=selinux selinux=1 sysrq_always_enabled=1 

This just happened after upgrading to 20250727 with 6.12.40-1-longterm.

What should I look for to try to investigate?

Thanks

As always - boot with plymouth.enable=0 and without quiet kernel parameters. It may show some more information.

Just did a full shutdown then restarted and it booted properly!

Thanks, I’ll have to watch what’s happening over time.

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