This bug was fixed in the package linux - 6.17.0-3.3
---------------
linux (6.17.0-3.3) questing; urgency=medium
* questing/linux: 6.17.0-3.3 -proposed tracker (LP: #2121512)
* Enable Xilinx PS UART configs (LP: #2121337)
- [Config] Enable Xilinx PS UART configs
* Packaging resync (LP: #1786013)
- [Packaging] update variants
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
(main/d2025.08.25)
* Plucky/Questing fails to boot on (older) Macs (LP: #2105402)
- SAUCE: hack: efi/libstub: enable t14s boot failure hack only on arm64
* Miscellaneous Ubuntu changes
- [Packaging] Fix linux-modules Description, add dependency on wireless-
regdb from old -extra
- [Packaging] Fix arch list for bpftool build-dep
-- Timo Aaltonen <[email protected]> Thu, 28 Aug 2025
10:37:03 +0300
** Changed in: linux (Ubuntu Questing)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.14 in Ubuntu.
https://bugs.launchpad.net/bugs/2115393
Title:
No IP Address assigned after hot-plugging Ethernet cable on HP
Platform
Status in HWE Next:
Triaged
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Committed
Status in linux-oem-6.11 source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux source package in Plucky:
Fix Committed
Status in linux-oem-6.11 source package in Plucky:
Invalid
Status in linux-oem-6.14 source package in Plucky:
Invalid
Status in linux source package in Questing:
Fix Released
Status in linux-oem-6.11 source package in Questing:
Invalid
Status in linux-oem-6.14 source package in Questing:
Invalid
Bug description:
[ Impact ]
On HP platform, a system equipped with Intel 8086:57a0 Ethernet
exhibits a symptom: after hot plugging the Ethernet cable, the network
interface can't get an IP address from DHCP server. This is caused by
a packet loss problem introduced by the commit from stable update:
96d4a384ccc2edfe5 e1000e: change k1 configuration on MTP and later
platforms
The packet loss problem reproduces with the 100% rate, when no packet
can be sent and received by the Ethernet controller, eventually block
the DCHP process.
Although there is an RFC patch [1] from upstream mailing list, it
simply introduces a module parameter which can turn the k1
configuration off. That being said, turning off the k1 configuration
would increase the system's power consumption.
[ Fix ]
For the temporary solution, we revert the following patch:
96d4a384ccc2edfe5 e1000e: change k1 configuration on MTP and later
platforms
[ Test Plan ]
1. Boot into Ubuntu kernel with Ethernet cable unplugged
2. Plug the Ethernet cable into the machine
3. Check if the system can get IP address from a DHCP server
[ Where problems could occur ]
Reverting the commit might cause minor packet loss on some platform,
said by the Intel Ethernet maintainer. That being said, we have not
observed it on our certified machines.
[ Additional Information ]
[1]
https://lore.kernel.org/netdev/[email protected]/
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2115393/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
