It's a regression introduced in mutter 42.9 by Intel:
https://gitlab.gnome.org/GNOME/mutter/-/commit/1fd96e30f5f8a61d70d51f9012112e01818161a7
Although they would probably argue it's not a regression so long as you
have a new enough kernel. Since we don't always have a new enough kernel
in jammy we probably need to revert that commit.
** Changed in: mutter (Ubuntu)
Importance: Undecided => High
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-intel-iotg (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux-intel-iotg (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: Fix Released
** Also affects: mutter (Ubuntu Mantic)
Importance: High
Assignee: Daniel van Vugt (vanvugt)
Status: Confirmed
** Also affects: linux-intel-iotg (Ubuntu Mantic)
Importance: Medium
Status: Confirmed
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux-intel-iotg (Ubuntu Lunar)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Jammy)
** No longer affects: linux (Ubuntu Kinetic)
** No longer affects: linux (Ubuntu Lunar)
** No longer affects: linux (Ubuntu Mantic)
** No longer affects: linux-intel-iotg (Ubuntu Jammy)
** No longer affects: linux-intel-iotg (Ubuntu Kinetic)
** No longer affects: linux-intel-iotg (Ubuntu Lunar)
** No longer affects: linux-intel-iotg (Ubuntu Mantic)
** Changed in: mutter (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: mutter (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: mutter (Ubuntu Jammy)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: mutter (Ubuntu Lunar)
Status: New => Invalid
** Changed in: mutter (Ubuntu Mantic)
Status: Confirmed => Invalid
** Changed in: mutter (Ubuntu Mantic)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
** Changed in: mutter (Ubuntu Mantic)
Importance: High => Undecided
** Changed in: mutter (Ubuntu Jammy)
Status: Confirmed => In Progress
** Summary changed:
- [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 kernels
(Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers
failed: Invalid argument)
+ gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running
5.15 kernels (Failed to lock front buffer on /dev/dri/cardN:
drmModeAddFB2WithModifiers failed: Invalid argument)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2026887
Title:
gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake
running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN:
drmModeAddFB2WithModifiers failed: Invalid argument)
Status in linux package in Ubuntu:
Fix Released
Status in linux-intel-iotg package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Invalid
Status in mutter source package in Jammy:
In Progress
Status in mutter source package in Kinetic:
Invalid
Status in mutter source package in Lunar:
Invalid
Status in mutter source package in Mantic:
Invalid
Bug description:
Hi Ubuntu Team,
MY ISSUE:
I installed today my PC with Ubuntu IOT Desktop(22.04.2 LTS (Jammy
Jellyfish)).
But with updated for all packages and with reboot PC, i have error with
starting gdm and access to /dev/dri/card0.
ERROR:
iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]:
GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL'
failed
iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]:
GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL'
failed
iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL:
g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL:
g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
iul 11 19:00:11 MY-PC gnome-session-binary[1022]: Entering running state
root@MY-PC:/home/tester# journalctl -b --no-pager | grep gnome-
iul 11 19:00:09 MY-PC systemd[1]: Mounting Mount unit for gnome-3-38-2004,
revision 119...
iul 11 19:00:09 MY-PC systemd[1]: Mounted Mount unit for gnome-3-38-2004,
revision 119.
iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]:
GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL'
failed
iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]:
GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL'
failed
iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL:
g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL:
g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
iul 11 19:00:10 MY-PC gnome-shell[1040]: Running GNOME Shell (using mutter
42.9) as a Wayland display server
iul 11 19:00:10 MY-PC gnome-shell[1040]: Device '/dev/dri/card0' prefers
shadow buffer
iul 11 19:00:10 MY-PC gnome-shell[1040]: Added device '/dev/dri/card0' (i915)
using atomic mode setting.
iul 11 19:00:10 MY-PC gnome-shell[1040]: Created gbm renderer for
'/dev/dri/card0'
iul 11 19:00:10 MY-PC gnome-shell[1040]: Boot VGA GPU /dev/dri/card0 selected
as primary
iul 11 19:00:10 MY-PC /usr/libexec/gdm-wayland-session[1021]:
dbus-daemon[1021]: [session uid=128 pid=1021] Activating service
name='org.a11y.Bus' requested by ':1.4' (uid=128 pid=1040
comm="/usr/bin/gnome-shell " label="unconfined")
iul 11 19:00:10 MY-PC gnome-shell[1040]: Using public X11 display :1024,
(using :1025 for managed services)
iul 11 19:00:10 MY-PC gnome-shell[1040]: Using Wayland display name
'wayland-0'
iul 11 19:00:11 MY-PC gnome-shell[1040]: Unset XDG_SESSION_ID,
getCurrentSessionProxy() called outside a user session. Asking logind directly.
iul 11 19:00:11 MY-PC gnome-shell[1040]: Will monitor session c1
iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd:
service name='org.freedesktop.locale1'
unit='dbus-org.freedesktop.locale1.service' requested by ':1.34' (uid=128
pid=1040 comm="/usr/bin/gnome-shell " label="unconfined")
iul 11 19:00:11 MY-PC /usr/libexec/gdm-wayland-session[1021]:
dbus-daemon[1021]: [session uid=128 pid=1021] Activating service
name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=128
pid=1040 comm="/usr/bin/gnome-shell " label="unconfined")
iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd:
service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by
':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined")
iul 11 19:00:11 MY-PC polkitd(authority=local)[725]: Registered
Authentication Agent for unix-session:c1 (system bus name :1.34
[/usr/bin/gnome-shell], object path
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd:
service name='org.freedesktop.PackageKit' unit='packagekit.service' requested
by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined")
iul 11 19:00:11 MY-PC gnome-shell[1040]: Extension [email protected]
already installed in /usr/share/gnome-shell/extensions/[email protected].
/usr/share/gnome-shell/extensions/[email protected] will not be loaded
iul 11 19:00:11 MY-PC gnome-shell[1040]: Extension
[email protected] already installed in
/usr/share/gnome-shell/extensions/[email protected].
/usr/share/gnome-shell/extensions/[email protected] will not be
loaded
iul 11 19:00:11 MY-PC gnome-shell[1040]: Extension [email protected]
already installed in /usr/share/gnome-shell/extensions/[email protected].
/usr/share/gnome-shell/extensions/[email protected] will not be loaded
iul 11 19:00:11 MY-PC /usr/libexec/gdm-wayland-session[1021]:
dbus-daemon[1021]: [session uid=128 pid=1021] Activating service
name='org.gnome.Shell.Notifications' requested by ':1.3' (uid=128 pid=1040
comm="/usr/bin/gnome-shell " label="unconfined")
iul 11 19:00:11 MY-PC /usr/libexec/gdm-wayland-session[1135]:
dbus-daemon[1135]: Activating service name='org.a11y.atspi.Registry' requested
by ':1.0' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined")
iul 11 19:00:11 MY-PC gnome-shell[1040]: JS ERROR: TypeError:
this._managerProxy is undefined
iul 11 19:00:11 MY-PC gnome-shell[1040]: Error looking up permission:
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd:
service name='net.reactivated.Fprint' unit='fprintd.service' requested by
':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined")
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: ATK Bridge is disabled but a11y has
already been enabled.
iul 11 19:00:11 MY-PC gnome-session-binary[1022]: Entering running state
iul 11 19:00:11 MY-PC gnome-shell[1040]: JS ERROR: Failed to initialize
fprintd service: Gio.IOErrorEnum:
GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Registering session with GDM
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:12 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:13 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:13 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:22 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:22 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:22 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
iul 11 19:00:22 MY-PC gnome-shell[1040]: Failed to lock front buffer on
/dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
LIBMUTTER VERSION:
dpkg -l | grep libmutter
ii libmutter-10-0:amd64 42.9-0ubuntu1
amd64 window manager library from the Mutter window manager
GNOME SHELL VERSION:
dpkg -l | grep gnome-shell
ii gnome-shell 42.9-0ubuntu2
amd64 graphical shell for the GNOME desktop
WORKAROUND:
I use workaround to have gdm completely started.
cat /etc/environment
MUTTER_DEBUG_USE_KMS_MODIFIERS=0
OS VERSION:
cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.2 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
KERNEL VERSION:
uname -a
Linux MY-PC 5.15.0-1034-intel-iotg #39-Ubuntu SMP Thu Jun 22 20:56:05 UTC
2023 x86_64 x86_64 x86_64 GNU/Linux
CPU:
12th Gen Intel(R) Core(TM) i7-1260P
SYSTEM:
lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:4621] (rev 02)
00:02.0 VGA compatible controller [0300]: Intel Corporation Alder Lake-P
Integrated Graphics Controller [8086:46a6] (rev 0c)
00:06.0 PCI bridge [0604]: Intel Corporation 12th Gen Core Processor PCI
Express x4 Controller #0 [8086:464d] (rev 02)
00:07.0 PCI bridge [0604]: Intel Corporation Alder Lake-P Thunderbolt 4 PCI
Express Root Port #0 [8086:466e] (rev 02)
00:07.2 PCI bridge [0604]: Intel Corporation Alder Lake-P Thunderbolt 4 PCI
Express Root Port #2 [8086:462f] (rev 02)
00:08.0 System peripheral [0880]: Intel Corporation 12th Gen Core Processor
Gaussian & Neural Accelerator [8086:464f] (rev 02)
00:0a.0 Signal processing controller [1180]: Intel Corporation Platform
Monitoring Technology [8086:467d] (rev 01)
00:0d.0 USB controller [0c03]: Intel Corporation Alder Lake-P Thunderbolt 4
USB Controller [8086:461e] (rev 02)
00:0d.2 USB controller [0c03]: Intel Corporation Alder Lake-P Thunderbolt 4
NHI #0 [8086:463e] (rev 02)
00:0d.3 USB controller [0c03]: Intel Corporation Alder Lake-P Thunderbolt 4
NHI #1 [8086:466d] (rev 02)
00:14.0 USB controller [0c03]: Intel Corporation Alder Lake PCH USB 3.2 xHCI
Host Controller [8086:51ed] (rev 01)
00:14.2 RAM memory [0500]: Intel Corporation Alder Lake PCH Shared SRAM
[8086:51ef] (rev 01)
00:14.3 Network controller [0280]: Intel Corporation Alder Lake-P PCH CNVi
WiFi [8086:51f0] (rev 01)
00:15.0 Serial bus controller [0c80]: Intel Corporation Alder Lake PCH Serial
IO I2C Controller #0 [8086:51e8] (rev 01)
00:15.1 Serial bus controller [0c80]: Intel Corporation Alder Lake PCH Serial
IO I2C Controller #1 [8086:51e9] (rev 01)
00:16.0 Communication controller [0780]: Intel Corporation Alder Lake PCH
HECI Controller [8086:51e0] (rev 01)
00:17.0 SATA controller [0106]: Intel Corporation Alder Lake-P SATA AHCI
Controller [8086:51d3] (rev 01)
00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:51b0] (rev 01)
00:1f.0 ISA bridge [0601]: Intel Corporation Alder Lake PCH eSPI Controller
[8086:5182] (rev 01)
00:1f.3 Multimedia audio controller [0401]: Intel Corporation Alder Lake
PCH-P High Definition Audio Controller [8086:51c8] (rev 01)
00:1f.4 SMBus [0c05]: Intel Corporation Alder Lake PCH-P SMBus Host
Controller [8086:51a3] (rev 01)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Alder Lake-P PCH SPI
Controller [8086:51a4] (rev 01)
01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd
NVMe SSD Controller PM9A1/PM9A3/980PRO [144d:a80a]
56:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller
I225-V [8086:15f3] (rev 03)
SEVERITY BUG:
MEDIUM TO CRITICAL
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp