Public bug reported:

I'm running Ubuntu 24.10 Oracular on a Lenovo X1 G6 Yoga with an Intel
iGPU.

Under normal desktop usage (e.g. Chrome, GIMP, PyCharm), the system
becomes unresponsive, eventually forcing me to "Force Quit" all windows.
SSH remains available.

>From the logs, the crash appears to be in the Xe DRM kernel driver:

BUG: kernel NULL pointer dereference, address: 0000000000000014
RIP: 0010:xe_pt_check_kill+0x79/0xf0 [xe]

The crash is triggered by the Xwayland process. Additional graphics-
related logs show transient GPU context failures.

The issue appears related to memory access in the `xe` kernel module.

I am guessing I have seen this issue every few weeks. In at least one
instance, it seemed to be easily repeated with the same window dialogue
actions, but I no longer have details from that incident.

**System Information:**

- Ubuntu 24.10 (Oracular)
- Kernel: Linux imac-X1-Yoga 6.11.0-21-generic #21-Ubuntu SMP PREEMPT_DYNAMIC 
Wed Feb 19 16:50:40 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
- Xe DRM driver active
- GNOME 45, Wayland session
- Intel GPU 00:02.0 VGA compatible controller: Intel Corporation TigerLake GT2 
[Iris Xe Graphics] (rev 01)

**Steps to reproduce**:
- Boot normally into Wayland session
- Launch Chrome and maybe some other tools (Slack, GIMP, PyCharm in this case) 
- After some use, overnight sleeps, UI crashes with system logs showing Xe 
driver errors

**Attachments**:
Pulled these via scp from my other laptop before restarting it this time. 
os-release.txt                                100%  397    44.3KB/s   00:00    
gpu-lspci.txt                                 100%  204     8.3KB/s   00:00    
dmesg.txt                                     100%  260KB   3.4MB/s   00:00    
uname.txt                                     100%  128    18.9KB/s   00:00    
journalctl-full.txt                           100% 2368KB  11.3MB/s   00:00    
journalctl-errors.txt                         100% 1821   130.4KB/s   00:00    
lsmod.txt                                     100%  507    58.4KB/s   00:00    
gnome-shell.log                               100%   70KB   4.3MB/s   00:00 

dmesg > ~/bugreport-xe-crash/dmesg.txt
journalctl -b > ~/bugreport-xe-crash/journalctl-full.txt
journalctl -b -p 0..3 > ~/bugreport-xe-crash/journalctl-errors.txt
journalctl -xe _COMM=gnome-shell > ~/bugreport-xe-crash/gnome-shell.log
lspci -nnk | grep -A3 VGA > ~/bugreport-xe-crash/gpu-lspci.txt
lsmod | grep xe > ~/bugreport-xe-crash/lsmod.txt
uname -a > ~/bugreport-xe-crash/uname.txt
cat /etc/os-release > ~/bugreport-xe-crash/os-release.txt

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

** Attachment added: "tar file with debug files described above"
   
https://bugs.launchpad.net/bugs/2106628/+attachment/5870494/+files/xe-bugreport.tar

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2106628

Title:
  Kernel NULL pointer dereference in xe_pt_check_kill with Xe DRM driver
  (Ubuntu 24.10)

Status in linux package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 24.10 Oracular on a Lenovo X1 G6 Yoga with an Intel
  iGPU.

  Under normal desktop usage (e.g. Chrome, GIMP, PyCharm), the system
  becomes unresponsive, eventually forcing me to "Force Quit" all
  windows. SSH remains available.

  From the logs, the crash appears to be in the Xe DRM kernel driver:

  BUG: kernel NULL pointer dereference, address: 0000000000000014
  RIP: 0010:xe_pt_check_kill+0x79/0xf0 [xe]

  The crash is triggered by the Xwayland process. Additional graphics-
  related logs show transient GPU context failures.

  The issue appears related to memory access in the `xe` kernel module.

  I am guessing I have seen this issue every few weeks. In at least one
  instance, it seemed to be easily repeated with the same window
  dialogue actions, but I no longer have details from that incident.

  **System Information:**

  - Ubuntu 24.10 (Oracular)
  - Kernel: Linux imac-X1-Yoga 6.11.0-21-generic #21-Ubuntu SMP PREEMPT_DYNAMIC 
Wed Feb 19 16:50:40 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
  - Xe DRM driver active
  - GNOME 45, Wayland session
  - Intel GPU 00:02.0 VGA compatible controller: Intel Corporation TigerLake 
GT2 [Iris Xe Graphics] (rev 01)

  **Steps to reproduce**:
  - Boot normally into Wayland session
  - Launch Chrome and maybe some other tools (Slack, GIMP, PyCharm in this 
case) 
  - After some use, overnight sleeps, UI crashes with system logs showing Xe 
driver errors

  **Attachments**:
  Pulled these via scp from my other laptop before restarting it this time. 
  os-release.txt                                100%  397    44.3KB/s   00:00   
 
  gpu-lspci.txt                                 100%  204     8.3KB/s   00:00   
 
  dmesg.txt                                     100%  260KB   3.4MB/s   00:00   
 
  uname.txt                                     100%  128    18.9KB/s   00:00   
 
  journalctl-full.txt                           100% 2368KB  11.3MB/s   00:00   
 
  journalctl-errors.txt                         100% 1821   130.4KB/s   00:00   
 
  lsmod.txt                                     100%  507    58.4KB/s   00:00   
 
  gnome-shell.log                               100%   70KB   4.3MB/s   00:00 

  dmesg > ~/bugreport-xe-crash/dmesg.txt
  journalctl -b > ~/bugreport-xe-crash/journalctl-full.txt
  journalctl -b -p 0..3 > ~/bugreport-xe-crash/journalctl-errors.txt
  journalctl -xe _COMM=gnome-shell > ~/bugreport-xe-crash/gnome-shell.log
  lspci -nnk | grep -A3 VGA > ~/bugreport-xe-crash/gpu-lspci.txt
  lsmod | grep xe > ~/bugreport-xe-crash/lsmod.txt
  uname -a > ~/bugreport-xe-crash/uname.txt
  cat /etc/os-release > ~/bugreport-xe-crash/os-release.txt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106628/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to