RTL8111EPP: Fix the network lost after resume with DASH
Bug #2043786 reported by
AaronMa
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
AaronMa | ||
linux (Ubuntu) |
In Progress
|
Undecided
|
Unassigned | ||
Jammy |
Won't Fix
|
Undecided
|
Unassigned | ||
Lunar |
Won't Fix
|
Medium
|
Unassigned | ||
Mantic |
Fix Released
|
Medium
|
Unassigned | ||
linux-oem-6.1 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Lunar |
Invalid
|
Undecided
|
Unassigned | ||
Mantic |
Invalid
|
Undecided
|
Unassigned | ||
linux-oem-6.5 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Lunar |
Invalid
|
Undecided
|
Unassigned | ||
Mantic |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
On the system installed RTL8111EPP with DASH, unable to get the network back upon system resume
[Fix]
handle DASH during system suspend and resume.
[Test]
Vendor tested on hardware, the ethernet is OK after resume.
[Where problems could occur]
It may break r8169 driver.
No SRU for Jammy 5.15 kernel due to too many commits are needed to
backport to support DASH.
tags: | added: oem-priority originate-from-2042997 sutton |
Changed in hwe-next: | |
assignee: | nobody → AaronMa (mapengyu) |
status: | New → In Progress |
Changed in linux (Ubuntu Jammy): | |
status: | New → Invalid |
Changed in linux (Ubuntu Lunar): | |
status: | New → In Progress |
Changed in linux (Ubuntu Mantic): | |
status: | New → In Progress |
Changed in linux-oem-6.1 (Ubuntu Lunar): | |
status: | New → Invalid |
Changed in linux-oem-6.1 (Ubuntu Mantic): | |
status: | New → Invalid |
Changed in linux-oem-6.1 (Ubuntu Jammy): | |
status: | New → In Progress |
Changed in linux-oem-6.5 (Ubuntu Jammy): | |
status: | New → In Progress |
Changed in linux-oem-6.5 (Ubuntu): | |
status: | New → In Progress |
Changed in linux-oem-6.5 (Ubuntu Lunar): | |
status: | New → Invalid |
Changed in linux-oem-6.5 (Ubuntu Mantic): | |
status: | New → Invalid |
Changed in linux-oem-6.1 (Ubuntu): | |
status: | New → In Progress |
Changed in linux (Ubuntu): | |
status: | New → In Progress |
Changed in linux (Ubuntu Jammy): | |
status: | Invalid → Won't Fix |
description: | updated |
Changed in linux-oem-6.1 (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
Changed in linux-oem-6.5 (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
Changed in linux-oem-6.1 (Ubuntu): | |
status: | In Progress → Invalid |
Changed in linux-oem-6.5 (Ubuntu): | |
status: | In Progress → Invalid |
Changed in linux (Ubuntu Lunar): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Mantic): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Mantic): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Lunar): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-lunar-linux verification-done-mantic-linux removed: verification-needed-lunar-linux verification-needed-mantic-linux |
Changed in hwe-next: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
This bug is awaiting verification that the linux-oem- 6.1/6.1. 0-1027. 27 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- jammy-linux- oem-6.1' to 'verification- done-jammy- linux-oem- 6.1'. If the problem still exists, change the tag 'verification- needed- jammy-linux- oem-6.1' to 'verification- failed- jammy-linux- oem-6.1' .
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!