From: Willy Tarreau <w@1wt.eu>
To: Kyle Sanderson <kyle.leet@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, jslaby@suse.cz
Subject: Re: [REGRESSION] - BROKEN NETWORKING Re: Linux 6.16.3
Date: Sun, 24 Aug 2025 20:55:26 +0200 [thread overview]
Message-ID: <20250824185526.GA958@1wt.eu> (raw)
In-Reply-To: <cfd4d3bd-cd0e-45dc-af9b-b478a56f8942@gmail.com>
Hello,
On Sun, Aug 24, 2025 at 11:31:01AM -0700, Kyle Sanderson wrote:
> Thanks for maintaining these as always. For the first time in a long time, I
> booted the latest stable (6.15.x -> 6.16.3) and somehow lost my networking.
> It looks like there is a patch from Intel (reported by AMD) that did not
> make it into stable 6.16.
>
> e67a0bc3ed4fd8ee1697cb6d937e2b294ec13b5e - ixgbe
> https://lore.kernel.org/all/94d7d5c0bb4fc171154ccff36e85261a9f186923.1755661118.git.calvin@wbinvd.org/
> - i40e
Your description is very confusing. First you indicate in the subject
that there is a regression in 6.16.3 (implying from 6.16.2 then), and
you describe a 6.15.x to 6.16.x upgrade, which then has nothing to do
with 6.16.x alone but much more likely with 6.15 to 6.16. Or did a
previous 6.16 work fine ? Also the patch you pointed above is neither
in 6.15 nor in 6.16, so it's not just "missing from 6.16".
Based on your links and descriptions above I suspect that instead it's a
6.15 to 6.16 regression that was brought by a0285236ab93 and that commit
e67a0bc3ed4fd above fixed it in 6.17-rc2, is that it ? If so, can you
apply that patch to confirm that it works and is desired in 6.16.x ?
Regards,
Willy
next prev parent reply other threads:[~2025-08-24 18:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-23 14:51 Linux 6.16.3 Greg Kroah-Hartman
2025-08-23 14:51 ` Greg Kroah-Hartman
2025-08-24 18:31 ` [REGRESSION] - BROKEN NETWORKING " Kyle Sanderson
2025-08-24 18:55 ` Willy Tarreau [this message]
2025-08-24 19:29 ` Calvin Owens
2025-08-24 19:51 ` Kyle Sanderson
2025-08-25 7:00 ` Greg Kroah-Hartman
2025-08-25 7:29 ` Greg Kroah-Hartman
2025-08-25 7:30 ` Greg Kroah-Hartman
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=20250824185526.GA958@1wt.eu \
--to=w@1wt.eu \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=kyle.leet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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