From: Timur Tabi <ttabi@nvidia.com>
To: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
Ben Skeggs <bskeggs@nvidia.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: Re: [6.13.6 stable regression?] Nouveau reboot failure in r535_gsp_msg_recv()
Date: Mon, 7 Apr 2025 18:30:56 +0000 [thread overview]
Message-ID: <7acb91aac7e7e720e735b5271e4938f866a476ac.camel@nvidia.com> (raw)
In-Reply-To: <9890af80b576c61bd503134c13ee866a105a89fa.camel@nvidia.com>
On Mon, 2025-04-07 at 17:14 +0000, Timur Tabi wrote:
> What I need now are the GSP-RM logs. In your /etc/modprobe.d, see if
> there
> is a file with "options nouveau". If there isn't, create one, and then
> add
> the "keep-gsp-logging=1" parameter, so it looks something like this:
>
> options nouveau keep-gsp-logging=1
>
> Reboot and then tell me if you see anything like this:
Ugh, I just noticed that this feature is probably not in 6.13. It was added
in 6.14, so unless you're willing to upgrade to 6.14, this might be a dead
end. Sorry.
next prev parent reply other threads:[~2025-04-07 18:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 15:28 [6.13.6 stable regression?] Nouveau reboot failure in r535_gsp_msg_recv() David Woodhouse
2025-04-07 16:28 ` Timur Tabi
2025-04-07 17:01 ` David Woodhouse
2025-04-07 17:14 ` Timur Tabi
2025-04-07 18:30 ` Timur Tabi [this message]
2025-04-07 18:39 ` David Woodhouse
2025-04-07 18:47 ` Timur Tabi
2025-04-07 19:12 ` David Woodhouse
2025-04-07 19:41 ` David Woodhouse
2025-04-07 19:51 ` Timur Tabi
2025-04-07 20:09 ` David Woodhouse
2025-04-08 15:59 ` Timur Tabi
2025-04-08 16:21 ` David Woodhouse
2025-04-08 16:30 ` Timur Tabi
2025-04-08 16:42 ` David Woodhouse
2025-04-08 16:46 ` Timur Tabi
2025-04-08 18:19 ` David Woodhouse
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=7acb91aac7e7e720e735b5271e4938f866a476ac.camel@nvidia.com \
--to=ttabi@nvidia.com \
--cc=bskeggs@nvidia.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=nouveau@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.