linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bert Karwatzki <spasswolf@web.de>
To: "Mario Limonciello (AMD) (kernel.org)" <superm1@kernel.org>,
	"Christian König" <christian.koenig@amd.com>,
	linux-kernel@vger.kernel.org
Cc: linux-next@vger.kernel.org, regressions@lists.linux.dev,
	 linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
	spasswolf@web.de
Subject: Re: [REGRESSION 00/04] Crash during resume of pcie bridge
Date: Fri, 07 Nov 2025 14:09:17 +0100	[thread overview]
Message-ID: <0cb75fae3a9cdb8dd82ca82348f4df919d34844d.camel@web.de> (raw)
In-Reply-To: <3772b8f5-6d1a-403e-ad27-99a711e78902@kernel.org>

Am Mittwoch, dem 05.11.2025 um 15:31 -0600 schrieb Mario Limonciello (AMD) (kernel.org):
> 
> Once you're done with your bisect I'd be really interested if you can 
> still reproduce the splats and NULL pointer on the recovery path using 
> amd-staging-drm-next.
> > 

There are good news and bad news on this:

The good news: I found out that one can generate a large number of ACPI GPP0 events
and resumes by scrolling through a large pdf (1305 pages - Gravitation by Wheeler, Misner and Thorne)
using the arrow keys. This can generate these crashes quite fast.

The bad news: Using the method above I could generate these crashes in v6.13 and v6.14,
so all the previous bisecting was completely useless.

Version v6.12 has not (yet, ...) crashed so I might be able to bisect between v6.12 and v6.13.

Here's a short log of the recent tests and time to crash (with number of GPP0 wakeup events and GPU resumes)

Retest:
6.14.0-stable		booted 18:11:24, 6.11.2025, crashed 18:45:30 (~34min, 588 GPP0 events, 210 resumes)

Retest:
6.14.11-stable		booted 19:09:33, 6.11.2025, crashed 19:17:42 (~8min (new record!), 122 GPP0 events, 44 resumes)

Testing (this was tested by the old method of starting evolution by script):		
v6.13			booted 23:46:21, 6.11.2025, GPU lost 4:38, 7.11.2025 (~5h, 760 GPP0 events, 807 resumes) no crash

Retest:
v6.13			booted 9:12, 7.11.2025 crashed 11:25, 7.11.2025 (~1.25h, 351 GPP0 events, 330 resumes)

Testing:
v6.12.52		booted 11:27, 7.11.2025 no crash after 1h, 735 GPP0 events, 301 resumes

Testing:
v6.12			booted 13:00, 7.11.2025 no crash after 1h, 890 GPP0 events, 287 resumes


Bert Karwatzki

  reply	other threads:[~2025-11-07 13:09 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-06 12:09 [REGRESSION 00/04] Crash during resume of pcie bridge Bert Karwatzki
2025-10-06 12:09 ` [REGRESSION 01/04] " Bert Karwatzki
2025-10-06 12:09 ` [REGRESSION 02/04] " Bert Karwatzki
2025-10-06 12:09 ` [REGRESSION 03/04] " Bert Karwatzki
2025-10-06 12:09 ` [REGRESSION 04/04] " Bert Karwatzki
2025-10-06 12:39 ` [REGRESSION 00/04] " Christian König
2025-10-06 16:22   ` Bert Karwatzki
2025-10-07  6:50     ` Bert Karwatzki
2025-10-07 21:33 ` Mario Limonciello
2025-10-13 16:29   ` Bert Karwatzki
2025-10-13 18:51     ` Mario Limonciello
2025-10-14 10:50       ` Christian König
     [not found]         ` <1853e2af7f70cf726df278137b6d2d89d9d9dc82.camel@web.de>
2025-10-31 13:38           ` Bert Karwatzki
2025-10-31 13:47             ` Bert Karwatzki
2025-10-31 18:35               ` Bert Karwatzki
2025-11-05 11:44                 ` Bert Karwatzki
2025-11-05 21:31                   ` Mario Limonciello (AMD) (kernel.org)
2025-11-07 13:09                     ` Bert Karwatzki [this message]
2025-11-07 17:09                       ` Bert Karwatzki
2025-11-10 13:33                         ` Christian König
2025-11-16 21:08                           ` Crash during resume of pcie bridge due to infinite loop in ACPICA Bert Karwatzki
2025-11-17 16:40                             ` Rafael J. Wysocki
2025-11-24 22:34                               ` Bert Karwatzki
2025-11-25 19:46                                 ` Rafael J. Wysocki
2025-11-27  0:08                                   ` Bert Karwatzki
2025-11-27 13:02                                     ` Rafael J. Wysocki
2025-11-28 20:47                                       ` Bert Karwatzki
2025-12-02 18:59                                         ` Rafael J. Wysocki
2025-12-02 19:53                                           ` Bert Karwatzki
2025-12-02 20:01                                             ` Rafael J. Wysocki
2025-12-05 10:05                                               ` Crash during resume of pcie bridge due to incorrect error handling Bert Karwatzki

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=0cb75fae3a9cdb8dd82ca82348f4df919d34844d.camel@web.de \
    --to=spasswolf@web.de \
    --cc=christian.koenig@amd.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=superm1@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 NNTP newsgroup(s).