Looks like an iissue with the i915 flaking out, presenting your black screen and taking the Gnome shell with it, or at least causing a crash in Gnome-shell.
Aug 17 13:59:47 kernel: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=221 end=222) time 1173 us, min 2385, max 2399, scanline start 2320, end 25
I’m not a Gnome user, an Nvidia card user nor an i915 user, so this is where I have to stop as it’ll be guesswork on my part for any further prodding.
Thanks for everything up to this point hopefully I’ll get attention from someone who knows what’s going on
I found something similar in the Arch wiki that mentions
“i915 0000:00:02.0: [drm] ERROR Atomic update failure on pipe A”
https://bbs.archlinux.org/viewtopic.php?id=263884
Interesting
For one of the users
Wonderfulyeah | 2021-03-22 10:15:55
I found the reason for my laptop,when i remove the Thermal Monitor Widget,everything all right.
Another user
mikapyon
Finally read on reddit about setting
intel_idle.max_cstate=1
in
GRUB_CMDLINE_LINUX_DEFAULT
and had no freeze in a whole week of uptime with regular use!
Yep - saw that cstate parameter. It limits the amount of powersaving the CPU can perform - means it can’t drop to the lower power level to save battery.
You can certainly try it with the knowledge that it will reduce the amount of time on battery, which you may not care about.
I’ll try it out and observe, because what’s the point of a long lasting battery that doesn’t actually turn on
Agreed. Rather have a usable machine than something which helps itself to a reboot whenever it feels like it.
You can try it as a one-shot boot by hitting e on the grub menu when you’ve selected a kernel and sticking intel_idle.max_cstate=1 on the linux line, alongside rhgb and quiet. It’ll be active for that boot only.
If that remains stable we can use grubby to make it permanent.
Okay let me try it
Your fpaste output shows a crash of KDE’s /app/bin/extension-manager. Did you preserve an older ~/.config? You could have a newly broken (due to age) extension.
No?, I lost all my files and this is a completely fresh install
Also extension manager is this application here
Extension Manager
Could this flatpak be the one causing the system crash? Also doesn’t that mean sunboxxing is broken?
I think it’s rather google chromes extension-manager running as a flatpak?
guessing from the lib paths registered in the trace
/usr/lib/x86_64-linux-gnu/
I’d assume that chrome might be the culprit here, crashing gnome-shel and / or mutter .
Ahhhhhh so gnome has a chrome extension that let’s you install extensions from it’s website.
I’ll also remove this just to see
no I really assumed this is some part of chrome. ignore that.
But have you chrome open and running when the blackouts/reboots happen?
Not always no.
Btw after adding the cststes to the command list in grub my laptop is still on and hasn’t crashed yet.
I’ll try to let it sleep because oddly enough
systemctl suspend
Doesn’t cause it to die but automatically suspending by itself does.
I jinxed it it has now rebooted,
intel_idle.max_cstate=1
Doesn’t seem to solve it
I found a workaround for the constant gnome crashing on i915 intel igpu,
esentially we force mutter to use the stable gpu as the primary gnome-shell render device as per Mutter Multi GPU
My system has been stable for the past 2 hours, with no issues so far though now because i am contantly using my dgpu i am having high power useage but its a stable system so i am happy.
How to
1.Find Your Target GPU’s Vendor & Device IDs
lspci -nn | grep -E "VGA|3D"
Exmaple output:
n3shemmy3 > lspci -nn | grep -E "VGA|3D"
00:02.0 VGA compatible controller [0300]: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05)
01:00.0 3D controller [0302]: NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1)
n3shemmy3 >
From this we only focus on the brackets [10de:2882] for exmaple because my stable gpu is the nvidia one
very ironic that i got wramed about nvidia gpu issues on linux for years only have intel gpu issues instead
- Vendor ID:
10de - Device ID:
2882
2.Create the Udev Rule:
Create a new rule file in /etc/udev/rules.d/61-mutter-preferred-primary-gpu.rules:
sudo nano /etc/udev/rules.d/61-mutter-preferred-primary-gpu.rules`
Add the following content, replacing 0x10de and 0x2882 with your GPU’s vendor and device IDs (keep the 0x prefix):
SUBSYSTEM=="drm", ENV{DEVTYPE}=="drm_minor", ENV{DEVNAME}=="/dev/dri/card[0-9]", SUBSYSTEMS=="pci", ATTRS{vendor}=="0x10de", ATTRS{device}=="0x2882", TAG+="mutter-device-preferred-primary"
You can disble this by adding a
#infront and rebooting btw
3.Reboot and Verify Selection:
systemctl reboot
now if you check your gpu
nvidia-smi
You should see gnome-shell and wayland on there with more than 1mb of memory. Unforturnately if you have low vram it gets even less because all your apps that do anything accelratable will use it up so you cant game with lots of stuff in the background
n3shemmy3 > nvidia-smi
Mon Aug 17 19:16:33 2026
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 610.57.04 KMD Version: 610.57.04 CUDA UMD Version: 13.3 |
+-----------------------------------------+------------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+========================+======================|
| 0 Quadro T2000 with Max-Q ... Off | 00000000:01:00.0 Off | N/A |
| N/A 49C P5 9W / 40W | 889MiB / 4096MiB | 6% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+
+-----------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=========================================================================================|
| 0 N/A N/A 98014 G /usr/bin/gnome-shell 231MiB |
| 0 N/A N/A 100280 G /usr/bin/python3 1MiB |
| 0 N/A N/A 102724 G /usr/bin/Xwayland 2MiB |
| 0 N/A N/A 103097 G ...rack-uuid=3190708988185955192 422MiB |
| 0 N/A N/A 103513 C+G /usr/bin/nautilus 63MiB |
| 0 N/A N/A 109227 C+G /usr/bin/gnome-text-editor 35MiB |
| 0 N/A N/A 109865 C+G /usr/bin/ptyxis 43MiB |
+-----------------------------------------------------------------------------------------+
n3shemmy3 >
Special thanks to everyone in this topic for helping narrow down the exact part on my laptop that is failiing (thankfully not the ram haha, if you are from the future and confused 2026 was the ramagedon)
Idk if keywords work but hopefully this helps me or someone else in the future.
keywords :
“i915 0000:00:02.0: drm ERROR Atomic update failure on pipe A"
“Intel i915”
“i915 Gnome crashing”
“intel igpu crashing”
“intel + Nvidia gnome crashing”
“wayland + intel + nvidia crashing”
“Nvidia T2000 Linux crashing”
“Intel® Core™ i7-10875H crashing Linux”
“Dell XPS 15 9500”
“Dell Precision 5550”