On Tue Feb 3, 2026 at 3:38 PM CET, Greg KH wrote: > On Sun, Feb 01, 2026 at 11:14:51PM +0100, Bruno Prémont wrote: >> Bisect completed. >> >> The offending patch is: >> commit 448a2071a843831fe5fa71545cbfa7e15ee8966d (HEAD) >> Author: Lyude Paul <[email protected]> >> Date: Wed Jan 21 14:13:10 2026 -0500 >> >> drm/nouveau/disp: Set drm_mode_config_funcs.atomic_(check|commit) >> >> commit 604826acb3f53c6648a7ee99a3914ead680ab7fb upstream. >> >> Apparently we never actually filled these in, despite the fact that we do >> in fact technically support atomic modesetting. >> >> Since not having these filled in causes us to potentially forget to >> disable >> fbdev and friends during suspend/resume, let's fix it. >> >> Signed-off-by: Lyude Paul <[email protected]> >> Cc: [email protected] >> Reviewed-by: Dave Airlie <[email protected]> >> Link: https://patch.msgid.link/[email protected] >> Signed-off-by: Greg Kroah-Hartman <[email protected]> >> >> drivers/gpu/drm/nouveau/nouveau_display.c | 2 ++ >> 1 file changed, 2 insertions(+) >> >> >> It landed in 6.18.8. Seems like not all chip generations are ready for >> atomic modesetting. > > Is this also a problem in 6.19-rc?
I did not test it, but a different mail [1] suggests that John did reproduce this in 6.19-rc7 too. I've already picked up a revert [2], which should be in linux-next and should soon be in Linus' tree as well. [1] https://lore.kernel.org/all/[email protected]/ [2] https://patch.msgid.link/[email protected]
