Bug 2431159 - The xe KMD driver needs CONFIG_DEVICE_PRIVATE on linux 6.18
Summary: The xe KMD driver needs CONFIG_DEVICE_PRIVATE on linux 6.18
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 43
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Justin M. Forbes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-01-20 09:29 UTC by Thomas Hellström
Modified: 2026-01-29 01:10 UTC (History)
14 users (show)

Fixed In Version: kernel-6.18.7-200.fc43 kernel-6.18.7-100.fc42
Clone Of:
Environment:
Last Closed: 2026-01-29 00:55:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Thomas Hellström 2026-01-20 09:29:34 UTC
1. Please describe the problem:

Without CONFIG_DEVICE_PRIVATE, the xe driver won't work properly since starting with
version 6.18 it's required for xe userptr. -> kernel regression.

xe developers is working to automatically select it when needed, meanwhile could you please include it in the fedora kernel configuration?

2. What is the Version-Release number of the kernel:
6.18+

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

Previous kernels work.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Run for example the igt test xe-exec-compute-mode on 6.18+

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

Unknown

6. Are you running any modules that not shipped with directly Fedora's kernel?:

No.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Reproducible: Always

Comment 1 Thomas Hellström 2026-01-20 11:40:30 UTC
xe driver permanent fix patch series.

https://patchwork.freedesktop.org/series/160350/

Comment 2 Fedora Update System 2026-01-23 20:28:58 UTC
FEDORA-2026-c24ec82023 (kernel-6.18.7-200.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-c24ec82023

Comment 3 Fedora Update System 2026-01-23 20:29:02 UTC
FEDORA-2026-eb2a61ce38 (kernel-6.18.7-100.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-eb2a61ce38

Comment 4 Fedora Update System 2026-01-24 01:25:19 UTC
FEDORA-2026-c24ec82023 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-c24ec82023`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-c24ec82023

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2026-01-24 02:04:17 UTC
FEDORA-2026-eb2a61ce38 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-eb2a61ce38`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-eb2a61ce38

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2026-01-29 00:55:53 UTC
FEDORA-2026-c24ec82023 (kernel-6.18.7-200.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2026-01-29 01:10:51 UTC
FEDORA-2026-eb2a61ce38 (kernel-6.18.7-100.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.