Fix incorrect speed/duplex when I210 device is runtime suspended
Bug #1880656 reported by
Kai-Heng Feng
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Medium
|
Unassigned | ||
linux-oem-5.6 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Won't Fix
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
linux-oem-osp1 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
[Impact]
When I210 device is runtime suspended, trying to read speed or duplex from sysfs causes an error:
[ 385.991957] igb 0000:03:00.0 enp3s0: PCIe link lost
[Fix]
Only try to read the device register when it's not runtime suspended.
[Test]
Without the fix:
$ cat /sys/class/
1000
With the fix:
$ cat /sys/class/
-1
-1 means "unknown speed", which is the correct status when device is runtime suspend.
[Regression Potential]
Low. It's a trivial fix which limits to one driver.
CVE References
Changed in linux-oem-5.6 (Ubuntu Bionic): | |
status: | New → Won't Fix |
Changed in linux-oem-osp1 (Ubuntu Focal): | |
status: | New → Won't Fix |
Changed in linux (Ubuntu Bionic): | |
status: | New → Won't Fix |
tags: | added: oem-priority originate-from-1857680 somerville |
Changed in linux (Ubuntu Bionic): | |
status: | Won't Fix → Invalid |
Changed in linux (Ubuntu Focal): | |
importance: | Undecided → Medium |
status: | Incomplete → Triaged |
Changed in linux (Ubuntu Focal): | |
status: | Triaged → Fix Committed |
Changed in linux-oem-osp1 (Ubuntu Bionic): | |
status: | New → Fix Committed |
Changed in linux-oem-5.6 (Ubuntu Focal): | |
status: | New → Fix Committed |
Changed in hwe-next: | |
status: | New → Fix Released |
To post a comment you must log in.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1880656
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.