From: Kyle Sanderson <kyle.leet@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org
Cc: lwn@lwn.net, jslaby@suse.cz
Subject: [REGRESSION] - BROKEN NETWORKING Re: Linux 6.16.3
Date: Sun, 24 Aug 2025 11:31:01 -0700 [thread overview]
Message-ID: <cfd4d3bd-cd0e-45dc-af9b-b478a56f8942@gmail.com> (raw)
In-Reply-To: <2025082354-halogen-retaliate-a8ba@gregkh>
On 8/23/2025 7:51 AM, Greg Kroah-Hartman wrote:
> I'm announcing the release of the 6.16.3 kernel.
>
> All users of the 6.16 kernel series that use the ext4 filesystem should
> upgrade.
>
> The updated 6.16.y git tree can be found at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-6.16.y
> and can be browsed at the normal kernel.org git web browser:
> https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
>
> thanks,
>
> greg k-h
Hi Greg,
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
This asset is a quad-port embedded Intel NIC, previously eno1..4, now
eno1np0, eno2np1, eno3np0, eno4np1.
Seems like there's a bit of a debate right now over should this get
carried in the tree (this 1/4 state stuff is no good). Anyway, upgrading
the kernel broke my networking, and because this is carried in 6.17-rc3
for ixgbe it will break again. I honestly don't care if it's some
ridiculous systemd thing or the kernel that fixes this, just that
there's a note on how to migrate for the common man (and that there is a
material change to how interfaces are exposed).
Kyle.
next prev parent reply other threads:[~2025-08-24 18:31 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 ` Kyle Sanderson [this message]
2025-08-24 18:55 ` [REGRESSION] - BROKEN NETWORKING " Willy Tarreau
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=cfd4d3bd-cd0e-45dc-af9b-b478a56f8942@gmail.com \
--to=kyle.leet@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--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