All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Moulding <dan@danm.net>
To: fw@strlen.de
Cc: dan@danm.net, netfilter-devel@vger.kernel.org,
	pablo@netfilter.org, regressions@lists.linux.dev
Subject: Re: [REGRESSION] v6.16 system hangs (bisected to nf_conntrack fix)
Date: Thu, 31 Jul 2025 13:49:01 -0600	[thread overview]
Message-ID: <20250731194901.7156-1-dan@danm.net> (raw)
In-Reply-To: <aIuQoUQQnFMyvJJs@strlen.de>

Florian Westphal <fw@strlen.de> wrote:
> > Strange.  Can you completely revert 2d72afb340657f03f7261e9243b44457a9228ac7
> > and then apply this patch instead?
> 
> Any news?

For some reason, I can no longer reproduce the problem in new kernels
that I build. I can still reproduce it in the kernels that I built
last week. But if I build a new one, from the same commit as I was
able to reproduce it from before, the new kernel build can't reproduce
it. I didn't change anything (like compiler version) since. So I'm
stumped.

I'm not sure what this means, other than that I can't test any new
patches because any new build I do doesn't exhibit the problem. I
guess at this point I can't rule out some kind of hardware failure on
my end (though that would seem very strange that it would consistently
point to a specific commit, and the problem went away after reverting,
if it was a hardware problem).

So maybe we can ignore this for now and see if it comes up again with
anyone else.

Cheers,

-- Dan

  reply	other threads:[~2025-07-31 19:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 23:25 [REGRESSION] v6.16 system hangs (bisected to nf_conntrack fix) Dan Moulding
2025-07-28 23:47 ` Florian Westphal
2025-07-29  0:25   ` Florian Westphal
2025-07-29 17:02   ` Dan Moulding
2025-07-29 17:38     ` Florian Westphal
2025-07-31 15:49       ` Florian Westphal
2025-07-31 19:49         ` Dan Moulding [this message]
2025-08-30  3:48           ` Dan Moulding

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=20250731194901.7156-1-dan@danm.net \
    --to=dan@danm.net \
    --cc=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=regressions@lists.linux.dev \
    /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.