linux-kernel - Re: 6.13-rc1 graphics fail

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c87fa6006f356f999a1d5165ee5e58422f68a3a3.camel@linux.intel.com>
Date: Mon, 02 Dec 2024 20:22:10 +0100
From: Thomas Hellström <thomas.hellstrom@...ux.intel.com>
To: Genes Lists <lists@...ience.com>, linux-kernel@...r.kernel.org, 
	lucas.demarchi@...el.com, rodrigo.vivi@...el.com, airlied@...il.com, 
	tzimmermann@...e.de, dri-devel@...ts.freedesktop.org, 
	intel-xe@...ts.freedesktop.org
Cc: intel-gfx@...ts.freedesktop.org
Subject: Re: 6.13-rc1 graphics fail

Hi,

On Mon, 2024-12-02 at 13:40 -0500, Genes Lists wrote:
> 
> 6.12.1 on same system with same userspace works fine (as did 6.12)
> while 6.13-rc1 boots, but without working graphics using gnome with
> wayland.
> 
> Laptop is raptor lake with Intel XE (lspci attached).
> No kernel errors are logged, but GDM fails, leading to frozen screen
> with some messages logged most notable seems to be quite a few of
> this
> one:
> 
>   Failed to ensure KMS FB ID on /dev/dri/card1
>        drmModeAddFB2WithModifiers failed: Invalid argument
> 
> which does not happen with 6.12.
> 
> I can switch to different VTs but GDM appears hung.
> 
> This is my primary machine so will take some time before I can bisect
> but thought it best to share sooner than later. Maybe this rings a
> bell
> to someone? Or does userspace GDM need to be changed to work with
> 6.13?

Your logs shows the i915 driver loading and not the xe driver. The i915
driver is the correct one for your hardware unless you are
experimenting.

So please file an issue here
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues

And follow up on the intel-gfx list (CC'd)

Thanks,
Thomas


> 
> 
> regards
> 
> gene
> 
> Larger journal attached along with lspci and kernel config.
> Some possibly relevant additional log bits:
> 
> -- journal --
> 
> gnome-shell[1380]: Thread 'KMS thread' will be using high priority
> scheduling
> gnome-shell[1380]: Device '/dev/dri/card1' prefers shadow buffer
> gnome-shell[1380]: Added device '/dev/dri/card1' (i915) using atomic
> mode setting.
> gnome-shell[1380]: Created gbm renderer for '/dev/dri/card1'
> gnome-shell[1380]: GPU /dev/dri/card1 selected primary from builtin
> panel presence
> gnome-shell[1380]: Obtained a high priority EGL context
> gnome-shell[1380]: Running GNOME Shell (using mutter 47.2) as a
> Wayland
> display server
> 
> /usr/lib/gdm-wayland-session[1367]: dbus-daemon[1367]: [session
> uid=120
> pid=1367] Activating service   
> name='org.freedesktop.impl.portal.desktop.gnome' requested by  
> ':1.39'
> (uid=120 pid=1777 comm="/usr>
> 
> gnome-shell[1380]: Failed to ensure KMS FB ID on /dev/dri/card1:   
> drmModeAddFB2WithModifiers failed: Invalid argument
> 
> meta_frame_native_release: assertion '!frame_native->kms_update'
> failed
> 
> -- journal --
>