From: Andreas Wild <andiwild@gmail.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: "Maciej W. Rozycki" <macro@orcam.me.uk>,
Bjorn Helgaas <helgaas@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev,
M M <restafvalendergelijke@outlook.com>,
blaat windows <blaaaat@hotmail.com>,
edwardmalik95@icloud.com
Subject: Re: [PATCH v3] PCI: Skip Target Speed quirk on clamped ports with no link
Date: Tue, 29 Sep 2026 09:59:16 +0200 [thread overview]
Message-ID: <20260929080109.53944-1-andiwild@gmail.com> (raw)
In-Reply-To: <87c93553-d74d-4588-bd54-0ccb2728f327@leemhuis.info>
On Tue, 29 Sep 2026, Thorsten Leemhuis wrote:
> No reason given, just a link to a diagnostic file that from a very quick
> look showed an Oops from the Nvidia driver:
> https://paste.cachyos.org/p/49a2487.log
>
> So maybe it's a problem in that OOT driver, maybe not. [...]
I had a look at that log, and I don't think it points at the patch.
It covers two boots, both on the same 7.2.2-1-cachyos build, which
carries the patch. The second one, from which the report was taken,
came up normally.
In the failing boot the NVIDIA driver fails to initialise the GPU
("RmInitAdapter failed! (0x24:0x72:1281)"), and about a second later
modprobe takes a general protection fault in __refill_objects_node(),
reached from mas_preallocate(): an object still on the maple_node free
list had a zeroed free pointer, as if it had been allocated or written
to while still free. The journal ends a second after that, so this is
presumably the hang the revert mentions.
That looks like slab corruption, which usually shows up in a victim
rather than the culprit, so the lack of NVIDIA frames in the trace
doesn't clear the driver: its failed-init teardown reported leaked
objects just before. Another candidate is 4a724bcf5d70 ("mm/slab: take
n->list_lock in __slab_try_return_freelist() to avoid race"), which only
reached stable in 7.2.7.
Nothing in the log implicates the patch, but it can't clear it either:
the patch's early return is silent, and the report only has warnings
and errors from the failing boot. One unexplained difference between
the boots: the r8169 NIC is at 33:00.0 in the failing one and at
30:00.0 in the good one.
Best regards,
Andreas
next prev parent reply other threads:[~2026-09-29 8:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 20:11 Andreas Wild
2026-08-03 5:39 ` Thorsten Leemhuis
2026-08-03 22:07 ` Maciej W. Rozycki
2026-08-04 5:32 ` Thorsten Leemhuis
2026-08-07 19:59 ` Aoxtj
2026-08-08 6:31 ` Andreas Wild
2026-08-11 3:43 ` Aoxtj
2026-08-11 6:42 ` Andreas Wild
2026-08-24 14:26 ` Thorsten Leemhuis
2026-08-25 7:05 ` Andreas Wild
2026-08-25 10:18 ` Maciej W. Rozycki
2026-09-02 15:48 ` Thorsten Leemhuis
2026-09-07 12:33 ` Maciej W. Rozycki
2026-09-17 23:33 ` Bjorn Helgaas
2026-09-18 5:39 ` Thorsten Leemhuis
2026-09-18 10:39 ` Maciej W. Rozycki
2026-09-18 11:00 ` Thorsten Leemhuis
2026-09-18 12:18 ` Maciej W. Rozycki
2026-09-18 12:50 ` Thorsten Leemhuis
2026-09-21 10:33 ` Thorsten Leemhuis
2026-09-29 5:45 ` Thorsten Leemhuis
2026-09-29 7:59 ` Andreas Wild [this message]
2026-09-20 8:15 blaat windows
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=20260929080109.53944-1-andiwild@gmail.com \
--to=andiwild@gmail.com \
--cc=bhelgaas@google.com \
--cc=blaaaat@hotmail.com \
--cc=edwardmalik95@icloud.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=restafvalendergelijke@outlook.com \
/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
all inboxes | Powered by JetHome®