From: Jason Gunthorpe <jgg@nvidia.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "Longia, Amandeep Kaur" <amandeepkaur.longia@amd.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Vasant Hegde <vasant.hegde@amd.com>
Subject: Re: linux-next: Tree for Nov 6
Date: Thu, 6 Nov 2025 16:05:41 -0400 [thread overview]
Message-ID: <20251106200541.GG1732817@nvidia.com> (raw)
In-Reply-To: <b47cc630-b27a-4d62-83c2-c81463b53bee@infradead.org>
On Thu, Nov 06, 2025 at 11:42:36AM -0800, Randy Dunlap wrote:
> > Currently, I am bisecting between kernel tags 'next-20251106' and 'next-20251105' to identify the culprit commit causing this issue.
>
> Pretty sure that your beginning "good" should be Linux v6.18-rc4 and
> not linux-next. "bad" should be next-20251106.
Thorsten pointed this out in the morning:
https://lore.kernel.org/r/20251106185814.GA1708009@nvidia.com
Alot of bots and people have used this series before it was merged so
I'm not sure what the special condition is to trigger this.. Does the
above fix it?
Jason
next prev parent reply other threads:[~2025-11-06 20:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 4:32 linux-next: Tree for Nov 6 Stephen Rothwell
2025-11-06 19:02 ` Longia, Amandeep Kaur
2025-11-06 19:42 ` Randy Dunlap
2025-11-06 20:05 ` Jason Gunthorpe [this message]
2025-11-09 8:58 ` Longia, Amandeep Kaur
-- strict thread matches above, loose matches on Subject: below --
2024-11-06 6:50 Stephen Rothwell
2023-11-06 0:47 Stephen Rothwell
2021-11-06 2:58 Stephen Rothwell
2020-11-06 6:18 Stephen Rothwell
2019-11-06 8:03 Stephen Rothwell
2018-11-06 3:14 Stephen Rothwell
2017-11-06 7:30 Stephen Rothwell
2015-11-06 3:24 Stephen Rothwell
2015-11-06 12:45 ` Christian Borntraeger
2015-11-09 21:31 ` Stephen Rothwell
2014-11-06 8:43 Stephen Rothwell
2013-11-06 9:28 Stephen Rothwell
2012-11-06 5:48 Stephen Rothwell
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=20251106200541.GG1732817@nvidia.com \
--to=jgg@nvidia.com \
--cc=amandeepkaur.longia@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=vasant.hegde@amd.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