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>
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 17:14:35 +0000	[thread overview]
Message-ID: <9890af80b576c61bd503134c13ee866a105a89fa.camel@nvidia.com> (raw)
In-Reply-To: <5a0a20cddbc13d3f9eb96067491034a22830620e.camel@infradead.org>

On Mon, 2025-04-07 at 18:01 +0100, David Woodhouse wrote:

> > 
> 
> Not exactly the same build (I'm on 6.14 now) but:
> 
> (gdb) list *(r535_gsp_msgq_wait+0x1c4)
> 0xd24 is in r535_gsp_msgq_wait
> (drivers/gpu/drm/nouveau/nvkm/subdev/gsp/r535.c:117).
> 112				break;
> 113	
> 114			usleep_range(1, 2);
> 115		} while (--(*ptime));
> 116	
> 117		if (WARN_ON(!*ptime))
> 118			return ERR_PTR(-ETIMEDOUT);

This tells me that GSP-RM has crashed, which explains a lot of the behavior
you're seeing.

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:

# ls -lR /sys/kernel/debug/nouveau/                                        
/sys/kernel/debug/nouveau/:                                                
total 0                                                                    
drwxr-xr-x 2 root root 0 Apr  7 12:06 0000:65:00.0                         
                                                                                                                                                                                                                                                                                                            
'/sys/kernel/debug/nouveau/0000:65:00.0':                                  
total 0                                                                    
-r--r--r-- 1 root root 65536 Apr  7 12:06 loginit                          
-r--r--r-- 1 root root 65536 Apr  7 12:06 logintr                          
-r--r--r-- 1 root root  4096 Apr  7 12:06 logpmu                           
-r--r--r-- 1 root root 65536 Apr  7 12:06 logrm                            

If you do, I need the contents of these files.  So e.g.:

cp /sys/kernel/debug/nouveau/0000:65:00.0/loginit loginit
cp /sys/kernel/debug/nouveau/0000:65:00.0/logrm logrm
cp /sys/kernel/debug/nouveau/0000:65:00.0/logpmu logpmu
cp /sys/kernel/debug/nouveau/0000:65:00.0/logintr logintr

You may only see some of these files, that's okay.

Zip them up and email them to me.


> Any clues on how to debug the USB-C output, and where to report that? 

No, I can't help with that.



  reply	other threads:[~2025-04-07 17:14 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 [this message]
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
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=9890af80b576c61bd503134c13ee866a105a89fa.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.