All of lore.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: [6.13.6 stable regression?] Nouveau reboot failure in r535_gsp_msg_recv()
Date: Tue, 8 Apr 2025 16:46:27 +0000	[thread overview]
Message-ID: <42b856605c340547d5e27df99db57f7b6e61e6a8.camel@nvidia.com> (raw)
In-Reply-To: <22fbb2813a38c5848b457b7f08a3058a1a0ebb3e.camel@infradead.org>

On Tue, 2025-04-08 at 17:42 +0100, David Woodhouse wrote:
> ISTR you said that if the proprietary driver does manage to use that
> port, then we could at least look at why nouveau doesn't?

Yes, but that is beyond my knowledge of Nouveau and GPU drivers.

> Could it even already be fixed in the r570-based update to nouveau?

I doubt it.  Let me look at the logs, and if I don't see anything, I'll give
you instructions on how to beta test r570.

  reply	other threads:[~2025-04-08 16:46 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
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 [this message]
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=42b856605c340547d5e27df99db57f7b6e61e6a8.camel@nvidia.com \
    --to=ttabi@nvidia.com \
    --cc=bskeggs@nvidia.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=dwmw2@infradead.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.