Fix non-working e1000e device after resume
Bug #1951861 reported by
Kai-Heng Feng
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
OEM Priority Project |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Focal |
Won't Fix
|
Undecided
|
Unassigned | ||
Impish |
Fix Released
|
High
|
Unassigned | ||
linux-oem-5.13 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
High
|
Unassigned | ||
Impish |
Invalid
|
Undecided
|
Unassigned | ||
linux-oem-5.14 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
High
|
Unassigned | ||
Impish |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
e1000e devices stop working after s2idle resume.
[Fix]
Revert the offending patch series, which is to bring some minor power
saving.
[Test]
Vendor did extensive tests and didn't find any regression, and the power
consumption remains the same.
[Where problems could occur]
Maybe on some system the series can save some energy, so reverting will
cause some power consumption increase.
CVE References
Changed in linux (Ubuntu Focal): | |
status: | New → Won't Fix |
Changed in linux (Ubuntu Impish): | |
status: | New → Confirmed |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in linux (Ubuntu Impish): | |
importance: | Undecided → High |
Changed in linux-oem-5.13 (Ubuntu): | |
status: | New → Invalid |
Changed in linux-oem-5.13 (Ubuntu Impish): | |
status: | New → Confirmed |
Changed in linux-oem-5.13 (Ubuntu Focal): | |
status: | New → Confirmed |
Changed in linux-oem-5.13 (Ubuntu Impish): | |
status: | Confirmed → Invalid |
Changed in linux-oem-5.14 (Ubuntu): | |
status: | New → Invalid |
Changed in linux-oem-5.14 (Ubuntu Impish): | |
status: | New → Invalid |
Changed in linux-oem-5.14 (Ubuntu Focal): | |
status: | New → Confirmed |
Changed in linux-oem-5.13 (Ubuntu Focal): | |
importance: | Undecided → High |
Changed in linux-oem-5.14 (Ubuntu Focal): | |
importance: | Undecided → High |
tags: | added: oem-priority originate-from-1938506 somerville |
tags: | added: originate-from-1948738 sutton |
tags: | added: originate-from-1947661 |
tags: | added: originate-from-1947678 |
Changed in linux (Ubuntu Impish): | |
status: | Confirmed → Fix Committed |
tags: |
added: verification-done-impish removed: verification-needed-impish |
Changed in linux-oem-5.13 (Ubuntu Focal): | |
status: | Confirmed → Fix Committed |
Changed in linux-oem-5.14 (Ubuntu Focal): | |
status: | Confirmed → Fix Committed |
tags: |
added: verification-done-focal removed: verification-needed-focal |
Changed in oem-priority: | |
status: | New → Fix Released |
Changed in hwe-next: | |
status: | New → Fix Released |
To post a comment you must log in.
This bug is awaiting verification that the linux/5.13.0-23.23 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- impish' to 'verification- done-impish' . If the problem still exists, change the tag 'verification- needed- impish' to 'verification- failed- impish' .
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!