From: David Airlie <airlied@redhat.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: lyude@redhat.com, kherbst@redhat.com, dakr@redhat.com,
stable@vger.kernel.org, Dan Moulding <dan@danm.net>,
nouveau@lists.freedesktop.org
Subject: Re: [REGRESSION] v6.9-rc7: nouveau: init failed, no display output from kernel; successfully bisected
Date: Fri, 10 May 2024 07:11:39 +1000 [thread overview]
Message-ID: <CAMwc25pJqmNwpRvD3-Ahf66_XB9yFMxhSvU=M4vBMdhVSYS3PQ@mail.gmail.com> (raw)
In-Reply-To: <ba0bc464-a06a-4c54-945a-202dca2c4e49@leemhuis.info>
On Thu, May 9, 2024 at 8:31 PM Linux regression tracking (Thorsten
Leemhuis) <regressions@leemhuis.info> wrote:
>
> On 06.05.24 20:23, Dan Moulding wrote:
> > After upgrading to rc7 from rc6 on a system with NVIDIA GP104 using
> > the nouveau driver, I get no display output from the kernel (only the
> > output from GRUB shows on the primary display). Nonetheless, I was
> > able to SSH to the system and get the kernel log from dmesg. I found
> > errors from nouveau in it. Grepping it for nouveau gives me this:
> >
> > [ 0.367379] nouveau 0000:01:00.0: NVIDIA GP104 (134000a1)
> > [ 0.474499] nouveau 0000:01:00.0: bios: version 86.04.50.80.13
> > [ 0.474620] nouveau 0000:01:00.0: pmu: firmware unavailable
> > [ 0.474977] nouveau 0000:01:00.0: fb: 8192 MiB GDDR5
> > [ 0.484371] nouveau 0000:01:00.0: sec2(acr): mbox 00000001 00000000
> > [ 0.484377] nouveau 0000:01:00.0: sec2(acr):load: boot failed: -5
> > [ 0.484379] nouveau 0000:01:00.0: acr: init failed, -5
> > [ 0.484466] nouveau 0000:01:00.0: init failed with -5
> > [ 0.484468] nouveau: DRM-master:00000000:00000080: init failed with -5
> > [ 0.484470] nouveau 0000:01:00.0: DRM-master: Device allocation failed: -5
> > [ 0.485078] nouveau 0000:01:00.0: probe with driver nouveau failed with error -50
> >
> > I bisected between v6.9-rc6 and v6.9-rc7 and that identified commit
> > 52a6947bf576 ("drm/nouveau/firmware: Fix SG_DEBUG error with
> > nvkm_firmware_ctor()") as the first bad commit.
>
> Lyude, that's a commit of yours.
>
> Given that 6.9 is due a quick question: I assume there is no easy fix
> for this in sight? Or is a quick revert something that might be
> appropriate to prevent this from entering 6.9?
I'll take a look today and see if I can reproduce it and revert it if needed.
Dave.
prev parent reply other threads:[~2024-05-09 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 18:23 [REGRESSION] v6.9-rc7: nouveau: init failed, no display output from kernel; successfully bisected Dan Moulding
2024-05-06 18:59 ` Dan Moulding
2024-05-09 10:31 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-09 21:11 ` David Airlie [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='CAMwc25pJqmNwpRvD3-Ahf66_XB9yFMxhSvU=M4vBMdhVSYS3PQ@mail.gmail.com' \
--to=airlied@redhat.com \
--cc=dakr@redhat.com \
--cc=dan@danm.net \
--cc=kherbst@redhat.com \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).