Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	regressions@lists.linux.dev
Cc: Sasha Levin <sashal@kernel.org>, Lyude Paul <lyude@redhat.com>,
	Danilo Krummrich <dakr@kernel.org>,
	Dave Airlie <airlied@redhat.com>,
	Ilia Mirkin <imirkin@alum.mit.edu>,
	stable@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"R. V. Lobato" <vieira.lobato@gmail.com>
Subject: Re: [REGRESSION] nouveau: GM108 hangs at boot since "drm/nouveau/devinit/gf100-: try to avoid double-running vbios scripts" (6.18.64)
Date: Sat, 21 Nov 2026 22:38:45 -0500	[thread overview]
Message-ID: <2026-11-21-2-daily-reply-0002@kernel.org> (raw)
In-Reply-To: <20261121101350.bab69dff11a2@gmail.com>

> The 6.18.64 backport 15465d681517 ("drm/nouveau/devinit/gf100-: try
> to avoid double-running vbios scripts", upstream 2139cb633d48, review
> patch 426/686 <20261113153835.372076643@linuxfoundation.org>) breaks
> nouveau on my GM108 laptop GPU. The machine hangs during boot.

[...]

> The guard expects nvkm_devinit_disable() to return a mask of disabled
> engines. In 6.18.64 it calls the void ->disable() hook, which disables
> subdevs with nvkm_subdev_disable(), and then always returns 0. So the
> guard is always true, also on boards without a display engine.

Thanks for the analysis, that matches what I see: nvkm_devinit_disable()
has returned 0 since da2b1a0a40d8 ("drm/nouveau/devinit: Convert function
disable() to be void").

I've reverted it for the next 7.3, 6.18 and 6.12 releases and dropped it
from the 6.6, 6.1, 5.15 and 5.10 queues. Mainline has the same bug and
still needs a fix.

-- 
Thanks,
Sasha

      reply	other threads:[~2026-11-22  3:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-21 13:13 [REGRESSION] nouveau: GM108 hangs at boot since "drm/nouveau/devinit/gf100-: try to avoid double-running vbios scripts" (6.18.64) R. V. Lobato
2026-11-22  3:38 ` Sasha Levin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2026-11-21-2-daily-reply-0002@kernel.org \
    --to=sashal@kernel.org \
    --cc=airlied@redhat.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=imirkin@alum.mit.edu \
    --cc=lyude@redhat.com \
    --cc=nouveau@lists.freedesktop.org \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=vieira.lobato@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox