From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 215610] New: eth0 not working after upgrade from 5.16.8 to 5.16.9
Date: Tue, 15 Feb 2022 15:22:33 -0800 [thread overview]
Message-ID: <20220215152233.2c15de26@hermes.local> (raw)
Begin forwarded message:
Date: Tue, 15 Feb 2022 16:24:06 +0000
From: bugzilla-daemon@kernel.org
To: stephen@networkplumber.org
Subject: [Bug 215610] New: eth0 not working after upgrade from 5.16.8 to 5.16.9
https://bugzilla.kernel.org/show_bug.cgi?id=215610
Bug ID: 215610
Summary: eth0 not working after upgrade from 5.16.8 to 5.16.9
Product: Networking
Version: 2.5
Kernel Version: 5.16.9
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: joerg.sigle@jsigle.com
Regression: No
After rebooting with kernel 5.16.9, the eth0 connection did not work any more.
The interface is shown in ifconfig, but ping or other services don't reach any
machines in the LAN or in the internet.
I've not done much research but went back to 5.16.8 which works well again.
In 5.16.8, lspci shows:
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev
04)
Subsystem: Lenovo Ethernet Connection I217-LM
Flags: bus master, fast devsel, latency 0, IRQ 33
Memory at b4a00000 (32-bit, non-prefetchable) [size=128K]
Memory at b4a3e000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 5080 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] PCI Advanced Features
Kernel driver in use: e1000e
Kind regards, js
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-02-15 23:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 23:22 Stephen Hemminger [this message]
2022-02-16 0:35 ` [Bug 215610] New: eth0 not working after upgrade from 5.16.8 to 5.16.9 Jakub Kicinski
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=20220215152233.2c15de26@hermes.local \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).