### System details

Lenovo ThinkPad X1 Carbon Gen 11 Machine type: 21HNS65E00 CPU: Intel Core i7-1370P RAM: 32 GB GPU: Intel Raptor Lake-P Iris Xe GPU PCI ID: 8086:a7a0 NVMe: KIOXIA KXG8AZNV1T02 1 TB Wi-Fi: Intel AX211 Thunderbolt 4

### What's wrong?

## Summary

I am experiencing repeated **sudden hard reboots** on Omarchy on a Lenovo ThinkPad X1 Carbon Gen 11.

The machine does not freeze for a long time, show a kernel panic, or perform a normal shutdown. It simply resets/reboots.

The important part is that after extensive testing:

- the issue happens with multiple Linux kernels on Omarchy
- BIOS/UEFI hardware diagnostics pass
- SSD SMART data is clean
- firmware/BIOS/Intel ME are fully updated
- the issue happens with and without external monitors / USB-C adapter
- disabling Chrome hardware acceleration does not help
- the issue can happen during trivial terminal operations
- **Ubuntu installed on the same machine is stable and does not reboot**

This strongly suggests an Omarchy / Arch configuration / Hyprland / power-management / graphics-stack interaction rather than a hardware failure.

---

## Hardware

Laptop:

```text
Lenovo ThinkPad X1 Carbon Gen 11
Machine type: 21HNS65E00
CPU: Intel Core i7-1370P
RAM: 32 GB
GPU: Intel Raptor Lake-P Iris Xe
GPU PCI ID: 8086:a7a0
NVMe: KIOXIA KXG8AZNV1T02 1 TB
Wi-Fi: Intel AX211
Thunderbolt 4
```

GPU:

```text
00:02.0 VGA compatible controller:
Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a0] (rev 04)

Kernel driver in use: i915
Kernel modules: i915, xe
```

---

## Firmware

The laptop firmware was initially outdated, so I updated everything before continuing debugging.

Current versions:

```text
System Firmware / BIOS:
N3XET67W (1.42)
07/15/2026

Intel Management Engine:
1.42.2872

KIOXIA NVMe firmware:
5108APLA
```

`fwupdmgr get-updates` now reports:

```text
Devices with the latest available firmware version:
 • Intel Management Engine
 • KXG8AZNV1T02 LA KIOXIA
 • System Firmware
 • Prometheus
 • UEFI dbx

No updates available
```

Therefore the crashes continue even with current Lenovo firmware.

---

## Omarchy software stack

I tested both:

```text
linux 7.1.8.arch1-3
```

and:

```text
linux-lts 6.18.45-1-lts
```

The hard reboot occurred on **both kernels**.

Relevant Intel packages were current:

```text
linux 7.1.8.arch1-3
linux-firmware 20260810-2
linux-firmware-intel 20260810-2
intel-ucode 20260812-1
mesa 1:26.1.8-1
vulkan-intel 1:26.1.8-1
intel-media-driver 26.2.4-1
```

VA-API was also functioning correctly using Intel's `iHD` driver.

---

## Boot configuration

Omarchy builds the UKI with several Omarchy-specific configurations:

```text
Using drop-in configuration file: 'omarchy_hooks.conf'
Using drop-in configuration file: 'omarchy_resume.conf'
Using drop-in configuration file: 'thunderbolt_module.conf'
```

Example:

```text
Building UKI for linux (7.1.8-arch1-3)

==> Using drop-in configuration file: 'omarchy_hooks.conf'
==> Using drop-in configuration file: 'omarchy_resume.conf'
==> Using drop-in configuration file: 'thunderbolt_module.conf'

...
==> Unified kernel image generation successful
Updated: /boot/limine.conf
```

This might be relevant because Ubuntu does not use these Omarchy-specific initramfs / resume / Thunderbolt settings.

---

# Actual crash behavior

`last -x` confirms that these are not normal reboots.

Example on the normal kernel:

```text
ssuleym* tty1   Sat Aug 22 20:30 - crash  (00:43)
reboot system boot 7.1.8-arch1-3 Sat Aug 22 20:30
```

Example on the LTS kernel:

```text
ssuleym* tty1   Sat Aug 22 19:53 - crash  (00:20)
reboot system boot 6.18.45-1-lts Sat Aug 22 19:53
```

So this is reproducible with both the normal and LTS kernels.

---

## Journal behavior

The previous boot journal normally just **stops abruptly**.

There is no clean shutdown sequence before the reset.

For example, close to one crash the last messages were ordinary network messages:

```text
Aug 22 21:11:52 kernel: [UFW BLOCK] ...
Aug 22 21:12:29 kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x703
Aug 22 21:12:29 kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x703
```

Then nothing.

The system simply rebooted.

Another crash similarly ended with regular UFW/network activity.

There was no preceding:

```text
kernel panic
MCE / Machine Check
Hardware Error
watchdog lockup
thermal shutdown
NVMe fatal error
OOM shutdown
normal systemd shutdown
```

`/sys/fs/pstore` was also empty after the crashes.

---

## One graphics-related error observed

During one earlier Omarchy boot I also observed:

```text
i915 ... *ERROR* Atomic update failure on pipe A
```

However this was not present immediately before every crash, so I cannot say that it is the direct cause.

The machine uses:

```text
Intel Iris Xe
i915
GuC submission
HuC authentication
SLPC
```

Typical initialization:

```text
i915 0000:00:02.0: [drm] Found alderlake_p/raptorlake_p
i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adlp_dmc.bin (v2.20)
i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.49.4
i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
```

---

# Things tested and ruled out / made significantly less likely

## 1. Hardware diagnostics

I ran Lenovo's BIOS/UEFI hardware diagnostics.

All tests passed.

This included the available hardware tests from Lenovo BIOS.

---

## 2. NVMe

SMART data is clean:

```text
SMART overall-health self-assessment test result: PASSED

Critical Warning:                0x00
Temperature:                     ~40 C
Available Spare:                 100%
Percentage Used:                 0%
Media and Data Integrity Errors: 0
Error Information Log Entries:   0
```

The drive reports no errors.

There are multiple `Unsafe Shutdowns`, but those appear to be the result of these hard resets:

```text
Unsafe Shutdowns: 28
```

---

## 3. Battery

Battery appears healthy:

```text
energy-full:        57 Wh
energy-full-design: 57 Wh
capacity:           100%
charge-cycles:      3
warning-level:      none
```

---

## 4. Kernel version

Initially I suspected Linux 7.1.x.

I therefore installed:

```text
linux-lts 6.18.45-1-lts
```

But the machine also hard-rebooted on LTS:

```text
tty1 ... - crash
```

Therefore this does not appear to be exclusively a Linux 7.1 regression.

---

## 5. External monitor / USB-C / Thunderbolt

I normally use external screens through USB-C/Thunderbolt.

There were some suspicious events such as:

```text
usb 3-1: USB disconnect
usb 3-1: new low-speed USB device
Product: USB Type-C Digital AV Adapter
No LPM exit latency info found, disabling LPM
```

I therefore disconnected:

- external monitor
- USB-C Digital AV adapter
- USB-C power path / display accessories

The laptop still hard-rebooted.

Therefore the external monitor / adapter alone is not the root cause.

---

## 6. Chrome / browser hardware acceleration

Several early crashes happened while watching YouTube, so I initially suspected Chrome GPU acceleration / VA-API.

I disabled graphics acceleration in Chrome.

The machine still rebooted.

The machine also rebooted during completely unrelated terminal activity.

For example, one reboot occurred around running a simple configuration search:

```bash
grep -RniE 'nvidia|nvidia_uvm' \
    /etc/modules-load.d \
    /etc/modprobe.d \
    /etc/mkinitcpio.conf \
    /etc/mkinitcpio.conf.d
```

Another reboot occurred while running:

```bash
sudo pacman -S firefox
```

So Chrome itself does not appear to be the cause.

---

## 7. Intel graphics userspace packages

The appropriate Intel stack was installed:

```text
mesa
vulkan-intel
intel-media-driver
linux-firmware-intel
intel-ucode
```

`vainfo` worked correctly with the Intel `iHD` driver.

---

# Important comparison: Ubuntu is stable

I finally removed Omarchy and installed Ubuntu on exactly the same laptop.

Ubuntu has now been running normally without the spontaneous reboots.

Ubuntu kernel:

```text
7.0.0-30-generic
```

Ubuntu uses the **same i915 driver**:

```text
00:02.0 VGA compatible controller:
Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a0]

Kernel driver in use: i915
Kernel modules: i915, xe
```

Loaded modules:

```text
i915
xe
```

`i915` is the active GPU driver.

Ubuntu also loads the same firmware versions:

```text
DMC firmware: adlp_dmc.bin v2.20
GuC firmware: 70.49.4
HuC firmware: 7.9.3

HuC authenticated
GuC submission enabled
GuC SLPC enabled
GuC RC enabled
```

Ubuntu kernel command line is very simple:

```text
BOOT_IMAGE=/vmlinuz-7.0.0-30-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv
ro quiet splash
crashkernel=...
```

There have been no sudden resets so far.

This is important because it suggests that:

- the physical Intel GPU is probably fine
- `i915` itself can operate stably on this hardware
- GuC/HuC/DMC firmware works
- CPU/RAM/system board passed Lenovo diagnostics
- the NVMe is healthy

The failure appears to be connected to something specific to the Omarchy/Arch environment.

---

# Possible areas worth investigating

At this point I suspect one of the following combinations rather than a single hardware component:

1. Omarchy + Hyprland + i915/DRM
2. Hyprland DPMS/display power management
3. Mesa / Hyprland / i915 interaction
4. Omarchy resume / suspend configuration
5. Omarchy's `thunderbolt_module.conf`
6. Omarchy's UKI/initramfs configuration
7. Arch-specific kernel configuration compared with Ubuntu's generic kernel
8. some Omarchy power-management service/configuration

I cannot currently prove which one is responsible.

---

# Additional warnings seen on Omarchy

These appeared but do not seem directly related to the reset:

```text
i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
```

and:

```text
spi-nor spi0.0: unrecognized JEDEC id bytes: f7 f0 30 09 03 00
```

There were also:

```text
iwlwifi 0000:00:14.3: Unhandled alg: 0x703
```

However none of these consistently occurred exactly at the point of every crash.

mkinitcpio also reported:

```text
Possibly missing firmware for module: xhci_pci_renesas
Possibly missing firmware for module: qat_6xxx
```

but `lspci` confirms that this laptop uses Intel xHCI/Thunderbolt hardware, not Renesas or QAT devices, so those warnings appear unrelated.

---

# Expected behavior

Omarchy should remain running normally on this hardware, as Ubuntu does.

---

# Actual behavior

Omarchy randomly performs a hard reset.

Frequency varied from a few minutes to tens of minutes.

There is generally no useful final kernel error because the journal simply stops.

---

# Why I am opening this issue

The difficult part of this problem is that it initially looks like hardware failure because there is no kernel panic.

However:

```text
Lenovo BIOS diagnostics  -> PASS
NVMe SMART               -> PASS
Current BIOS / ME        -> PASS
linux 7.1                -> CRASH
linux-lts 6.18           -> CRASH
without external display -> CRASH
Chrome GPU disabled      -> CRASH
Ubuntu + same hardware   -> STABLE
Ubuntu + i915            -> STABLE
```

So I am reporting this in case other Omarchy users with Intel Raptor Lake / ThinkPad hardware encounter the same unexplained hard reboots.

It would be especially useful to know whether there are known issues involving:

- Hyprland / DPMS
- i915 on Raptor Lake-P
- Omarchy resume/hibernate configuration
- early-loaded Thunderbolt module
- Omarchy UKI / mkinitcpio hooks
- Intel power-management configuration

I am happy to provide additional logs/configuration if there is a specific comparison that would help isolate the issue.