suspend only works once on ThinkPad X1 Carbon gen 7
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| linux (Ubuntu) |
High
|
Kai-Heng Feng | ||
| Bionic |
Undecided
|
Unassigned | ||
| Eoan |
Undecided
|
Unassigned | ||
| Focal |
High
|
Kai-Heng Feng | ||
| linux-oem-osp1 (Ubuntu) |
Undecided
|
Unassigned | ||
| Bionic |
Undecided
|
Unassigned | ||
| Eoan |
Undecided
|
Unassigned | ||
| Focal |
Undecided
|
Unassigned |
Bug Description
=== SRU Justification Fix===
[Impact]
Some ThinkPads failed to suspend to s2idle when ethernet disconnected.
[Fix]
I219 chip of some platforms is controlled by ME, which needs more time
when setting ULP mode. Wait for ME to finish setting ULP mode.
[Test]
Verified on hw, and user reported s2idle works.
[Regression Potential]
Low, Increase timeout and breaks with condition,
no impacts for who don't need this long wait.
Bionic doesn't introduce the commit f15bb6dde738cc8fa0, no need for
this.
=== SRU Justification ===
[Impact]
Lenovo X1 Carbon 7th can only susped (s2idle) once, subsquent suspends
are blocked by failed e1000e resume routine.
[Fix]
It's not root caused yet by Intel, so disable the s0ix flow on X1 Carbon
7th as a temporary workaround.
[Test]
After applying the DMI quirk patch, e1000e keeps working, so it doesn't
block s2idle anymore.
User also confimred the workaround works.
[Regression Potential]
Low. It limits to a specific model, and I can confirm s0ix can still be
reached withouth this feature.
=== Original Bug Report ===
5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only once* after boot. On subsequent attempts, when the lid it closed, backlight and wifi are turned off, but system does not suspend.
First successful suspend:
[ 147.413295] PM: suspend entry (s2idle)
[ 147.416601] Filesystems sync: 0.003 seconds
[ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 147.421210] OOM killer disabled.
[ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug)
[ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 147.527810] e1000e: EEE TX LPI TIMER: 00000011
[ 150.246317] ACPI: EC: interrupt blocked
[ 881.134544] ACPI: EC: interrupt unblocked
[ 883.933255] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
[ 884.047802] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
[ 884.112730] iwlwifi 0000:00:14.3: FW already configured (0) - re-configuring
[ 886.815475] e1000e 0000:00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet
[ 887.485832] e1000e 0000:00:1f.6 enp0s31f6: Hardware Error
[ 888.016931] OOM killer enabled.
[ 888.016932] Restarting tasks ... done.
[ 888.060613] PM: suspend exit
Second unsuccessful suspend:
[ 907.584802] PM: suspend entry (s2idle)
[ 907.589779] Filesystems sync: 0.004 seconds
[ 907.591416] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 907.593518] OOM killer disabled.
[ 907.593518] Freezing remaining freezable tasks ... (elapsed 0.328 seconds) done.
[ 907.921560] printk: Suspending console(s) (use no_console_suspend to debug)
[ 907.922127] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 908.024438] e1000e: EEE TX LPI TIMER: 00000011
[ 909.916364] PM: pci_pm_suspend(): e1000e_
[ 909.916367] PM: dpm_run_callback(): pci_pm_
[ 909.916369] PM: Device 0000:00:1f.6 failed to suspend async: error -2
[ 911.183052] PM: Some devices failed to suspend, or early wake event detected
[ 911.197091] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
[ 911.314903] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
[ 911.382438] iwlwifi 0000:00:14.3: FW already configured (0) - re-configuring
[ 911.413624] OOM killer enabled.
[ 911.413625] Restarting tasks ... done.
[ 911.462021] PM: suspend exit
It looks like Ethernet driver prevents suspend. Ethernet is not connected (I do not have the adaptor).
CVE References
Eugene Crosser (crosser) wrote : | #1 |
summary: |
- suspend only works once on ThnkPad X1 Carbon gen 7 + suspend only works once on ThinkPad X1 Carbon gen 7 |
affects: | linux-5.4 (Ubuntu) → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
status: | New → Incomplete |
Hui Wang (hui.wang) wrote : | #3 |
Looks like it is an issue on the e1000e driver
[ 909.916364] PM: pci_pm_suspend(): e1000e_
[ 909.916367] PM: dpm_run_callback(): pci_pm_
[ 909.916369] PM: Device 0000:00:1f.6 failed to suspend async: error -2
[ 911.183052] PM: Some devices failed to suspend, or early wake event detected
Kai-Heng Feng (kaihengfeng) wrote : | #4 |
Please test latest mainline kernel:
https:/
Eugene Crosser (crosser) wrote : | #5 |
5.6.0-050600rc4
Same behaviour:
First time works:
[ 122.113542] PM: suspend entry (s2idle)
[ 122.118823] Filesystems sync: 0.005 seconds
[ 122.120954] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 122.123333] OOM killer disabled.
[ 122.123334] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 122.124606] printk: Suspending console(s) (use no_console_suspend to debug)
[ 122.125072] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 122.230038] e1000e: EEE TX LPI TIMER: 00000011
[ 122.345108] ACPI: EC: interrupt blocked
[ 138.117673] ACPI: EC: interrupt unblocked
[ 140.917449] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
[ 141.031854] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
[ 141.096775] iwlwifi 0000:00:14.3: FW already configured (0) - re-configuring
[ 143.796468] e1000e 0000:00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet
[ 144.466557] e1000e 0000:00:1f.6 enp0s31f6: Hardware Error
[ 145.195597] OOM killer enabled.
[ 145.195597] Restarting tasks ... done.
[ 145.213016] mei_hdcp 0000:00:
[ 145.239043] PM: suspend exit
Second time fails to suspend:
[ 169.696561] PM: suspend entry (s2idle)
[ 169.734111] Filesystems sync: 0.037 seconds
[ 169.734688] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 169.736790] OOM killer disabled.
[ 169.736791] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 169.738032] printk: Suspending console(s) (use no_console_suspend to debug)
[ 169.738318] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 169.839564] e1000e: EEE TX LPI TIMER: 00000011
[ 171.730682] PM: pci_pm_suspend(): e1000e_
[ 171.730685] PM: dpm_run_callback(): pci_pm_
[ 171.730687] PM: Device 0000:00:1f.6 failed to suspend async: error -2
[ 172.997917] PM: Some devices failed to suspend, or early wake event detected
[ 173.010160] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
[ 173.126554] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
[ 173.193691] iwlwifi 0000:00:14.3: FW already configured (0) - re-configuring
[ 173.222986] OOM killer enabled.
[ 173.222987] Restarting tasks ...
[ 173.235209] mei_hdcp 0000:00:
[ 173.235267] done.
[ 173.266890] PM: suspend exit
Suspend works with eoan's 5.3.0-18-generic (same system, just booted into the old kernel):
First time successful:
[ 66.725822] PM: suspend entry (s2idle)
[ 66.731748] Filesystems sync: 0.005 seconds
[ 66.732769] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 66.735102] OOM killer disabled.
[ 66.735103] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 66.736358] printk: Suspending console(s) (use no_console_suspend to debug)
[ 66.737562] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 ...
Eugene Crosser (crosser) wrote : | #6 |
Could the culprit be enabled "wake on LAN" functionality of e1000e, that was not enabled in 5.3?
Kai-Heng Feng (kaihengfeng) wrote : | #7 |
Would it be possible for you to do a kernel bisection?
First, find the last -rc kernel works and the first -rc kernel doesn’t work from http://
Then,
$ sudo apt build-dep linux
$ git clone git://git.
$ cd linux
$ git bisect start
$ git bisect good $(the working version you found)
$ git bisect bad $(the non-working version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If it still have the same issue,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the offending commit.
Eugene Crosser (crosser) wrote : | #8 |
@kaihengfeng, unfortunately that does not work.
I could not find time to do git bisect (each kernel build takes a long time), but it would not help if I did. I did a "bisect" over the packages in https:/
5.4.24-
5.5.0-050500rc1
5.5.0-050500rc4
5.5.0-050500rc5
5.5.0-050500rc6
5.5.0-050500rc7
Alex Hung (alexhung) wrote : | #9 |
Some system does not work well with s2idle, but they might work with regular suspend (s3).
Please try "echo deep | sudo tee /sys/power/
AaronMa (mapengyu) wrote : | #10 |
5.4.0-16/17 are abandoned for issues of s2idle, please ignore it.
And for e1000e errors, not reproduced on my X1 Carbon 7.
Please update the kernel.
If you still reproduce this issue, lease test the latest e1000e driver from intel:
https:/
Please file a bug in bugzilla.kernel.org too if driver above failed too.
And for mainline kernel suspend hang that is because of it lacks of audio sof supports.
Eugene Crosser (crosser) wrote : | #11 |
> 5.4.0-16/17 are abandoned for issues of s2idle, please ignore it.
I do not understand that.
With the current "official" kernel, the problem still exists:
5.4.0-17-generic suspend works only the first time
The only kernel that works for me is 5.4.24-
AaronMa (mapengyu) wrote : | #12 |
@crosser,
5.4.0-17 is a Ubuntu kernel version.
5.4.24 is mainline stable kernel version.
If 5.4.24 is good, that means it is a regression of Ubuntu kernel 5.4.0-17 who is from proposed kernel not a official release in updates channel.
Now Ubuntu kernel 5.4.0-18 has replaced 5.4.0-17 in proposed channel.
You can try it first.
AaronMa (mapengyu) wrote : | #13 |
May blame to this patch:
https:/
Eugene Crosser (crosser) wrote : | #14 |
JFYI, with the current "proposed" kernel behaviour is the same (problematic):
5.4.0-18-generic suspend works only the first time
Eugene Crosser (crosser) wrote : | #15 |
To check the theory from comment #13, I built kernel from mainline at tag v5.6-rc5. Out of the box, it behaves the same way as all recent kernels: suspend works only the first time. I could not revert commit f15bb6d (there were later changes), instead I commented out the calls to e1000e_
diff --git a/drivers/
index db4ea58bac82.
--- a/drivers/
+++ b/drivers/
@@ -6860,8 +6860,8 @@ static int e1000e_
e1000e_
/* Introduce S0ix implementation */
- if (hw->mac.type >= e1000_pch_cnp)
- e1000e_
+ /*if (hw->mac.type >= e1000_pch_cnp)
+ e1000e_
return rc;
}
@@ -6875,8 +6875,8 @@ static int e1000e_
int rc;
/* Introduce S0ix implementation */
- if (hw->mac.type >= e1000_pch_cnp)
- e1000e_
+ /* if (hw->mac.type >= e1000_pch_cnp)
+ e1000e_
rc = __e1000_
if (rc)
And voila, suspend works normally every time now!
Apparently S0ix implementation is indeed the culprit.
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
status: | Incomplete → Triaged |
assignee: | nobody → Kai-Heng Feng (kaihengfeng) |
Kai-Heng Feng (kaihengfeng) wrote : | #16 |
A test kernel can be found here:
https:/
Eugene Crosser (crosser) wrote : | #17 |
I can confirm that suspend works normally with the kernel from comment #16
Thank you!
roland (roland-micite) wrote : | #19 |
Thank you for going the extra mile in resolving this issue.
Changed in linux (Ubuntu Bionic): | |
status: | New → Won't Fix |
Changed in linux-oem-osp1 (Ubuntu Eoan): | |
status: | New → Won't Fix |
Changed in linux-oem-osp1 (Ubuntu Focal): | |
status: | New → Won't Fix |
description: | updated |
This bug is awaiting verification that the 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-
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:/
tags: | added: verification-needed-focal |
AaronMa (mapengyu) wrote : | #21 |
Hi
Please verify the issue with this patch:
https://<email address hidden>/
Eugene Crosser (crosser) wrote : | #22 |
@mapengyu, I've rebuilt e1000e.ko with your patch applied to 5.6.0-rc5 tree, and suspend works normally for me:
Linux journex 5.6.0-rc5+ #2 SMP Sun Mar 15 00:09:19 CET 2020 x86_64 x86_64 x86_64 GNU/Linux
First suspend:
[ 66.578525] PM: suspend entry (s2idle)
[ 66.582870] Filesystems sync: 0.004 seconds
[ 66.583640] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 66.585841] OOM killer disabled.
[ 66.585842] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 66.587085] printk: Suspending console(s) (use no_console_suspend to debug)
[ 66.587375] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 66.691969] e1000e: EEE TX LPI TIMER: 00000011
[ 69.395364] ACPI: EC: interrupt blocked
[ 79.252679] ACPI: EC: interrupt unblocked
[ 82.053040] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
[ 82.169363] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
[ 82.234288] iwlwifi 0000:00:14.3: FW already configured (0) - re-configuring
[ 85.251055] OOM killer enabled.
[ 85.251056] Restarting tasks ... done.
[ 85.260141] mei_hdcp 0000:00:
[ 85.293929] PM: suspend exit
[ 85.391753] e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down
[ 85.627128] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
...
Second suspend:
[ 140.523471] PM: suspend entry (s2idle)
[ 140.554018] Filesystems sync: 0.030 seconds
[ 140.554655] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 140.556773] OOM killer disabled.
[ 140.556773] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 140.558014] printk: Suspending console(s) (use no_console_suspend to debug)
[ 140.558275] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 140.659976] e1000e: EEE TX LPI TIMER: 00000011
[ 143.380606] ACPI: EC: interrupt blocked
[ 158.716081] ACPI: EC: interrupt unblocked
[ 161.516454] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
[ 161.866014] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
[ 161.933414] iwlwifi 0000:00:14.3: FW already configured (0) - re-configuring
[ 164.586442] OOM killer enabled.
[ 164.586443] Restarting tasks ...
[ 164.592488] mei_hdcp 0000:00:
[ 164.592743] done.
[ 164.637623] PM: suspend exit
[ 164.735062] e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down
[ 164.999601] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
...
roland (roland-micite) wrote : | #23 |
I've just tested on Eoan with the proposed branch.
It didn't resolve my issue. I'll give it some time today to see if the new kernel
gets released.
This is the kernel I'm running after an apt update/upgrade cycle this morning
Linux MiX 5.3.0-43-generic #36-Ubuntu SMP Mon Mar 16 13:29:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Eugene Crosser (crosser) wrote : | #24 |
Using the kernel package from -proposed makes suspend work normally as well.
Linux journex 5.4.0-20-generic #24-Ubuntu SMP Mon Mar 23 20:55:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Though I guess that 5.4.0-20 uses the "workaround", and it may be better to apply the "proper fix" from comment 21?
In any case, I am marking it "verification-done" because it does indeed work.
tags: |
added: verification-done-focal removed: verification-needed-focal |
roland (roland-micite) wrote : | #25 |
About comment #23 It's won't work. I'm on Eoan, the proposed kernel is for focal.
Kai-Heng Feng (kaihengfeng) wrote : | #26 |
It'll be in Eoan kernel when it's "Fix committed".
Launchpad Janitor (janitor) wrote : | #27 |
This bug was fixed in the package linux - 5.4.0-21.25
---------------
linux (5.4.0-21.25) focal; urgency=medium
* CVE-2020-8835
- SAUCE: bpf: undo incorrect __reg_bound_
-- Thadeu Lima de Souza Cascardo <email address hidden> Thu, 26 Mar 2020 17:51:28 -0300
Changed in linux (Ubuntu Focal): | |
status: | Triaged → Fix Released |
description: | updated |
Changed in linux (Ubuntu Eoan): | |
status: | New → Fix Committed |
This bug is awaiting verification that the 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-
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:/
tags: | added: verification-needed-eoan |
Launchpad Janitor (janitor) wrote : | #29 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in linux-oem-osp1 (Ubuntu Bionic): | |
status: | New → Confirmed |
Changed in linux-oem-osp1 (Ubuntu): | |
status: | New → Confirmed |
roland (roland-micite) wrote : | #31 |
I've updated the tag to verification-
I was able to suspend three times in a row.
Specs:
ThinkPad X1C7 ubuntu 19.10 eoan
tags: |
added: verification-done-eoan removed: verification-needed-eoan |
Changed in linux-oem-osp1 (Ubuntu Bionic): | |
status: | Confirmed → Fix Committed |
Launchpad Janitor (janitor) wrote : | #32 |
This bug was fixed in the package linux - 5.3.0-51.44
---------------
linux (5.3.0-51.44) eoan; urgency=medium
* CVE-2020-11884
- SAUCE: s390/mm: fix page table upgrade vs 2ndary address mode accesses
-- Thadeu Lima de Souza Cascardo <email address hidden> Wed, 22 Apr 2020 17:35:41 -0300
Changed in linux (Ubuntu Eoan): | |
status: | Fix Committed → Fix Released |
Launchpad Janitor (janitor) wrote : | #33 |
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1050.55
---------------
linux-oem-osp1 (5.0.0-1050.55) bionic; urgency=medium
* bionic/
* alsa/sof: external mic can't be deteced on Lenovo and HP laptops
(LP: #1872569)
- SAUCE: ASoC: intel/skl/hda - set autosuspend timeout for hda codecs
-- Chia-Lin Kao (AceLan) <email address hidden> Fri, 24 Apr 2020 18:25:45 +0800
Changed in linux-oem-osp1 (Ubuntu Bionic): | |
status: | Fix Committed → Fix Released |
Bin Li (binli) wrote : | #34 |
Tried on ThinkPad X13 Yoga with 5.0.0-1050.55 kernel on bionic, this issue is not fixed.
Kai-Heng Feng (kaihengfeng) wrote : | #35 |
Bin, can you please file a separate bug? I plan to pull Aaron's more generic fix.
Launchpad Janitor (janitor) wrote : | #36 |
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1059.64
---------------
linux-oem-osp1 (5.0.0-1059.64) bionic; urgency=medium
[ Ubuntu: 5.0.0-52.56 ]
* CVE-2020-0543
- SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id
- SAUCE: x86/cpu: Add 'table' argument to cpu_matches()
- SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS)
mitigation
- SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation
- SAUCE: x86/speculation: Add Ivy Bridge to affected list
linux-oem-osp1 (5.0.0-1054.59) bionic; urgency=medium
* bionic/
* Speed up the process of s3 resume (LP: #1876844)
- PCI/PM: Adjust pcie_wait_
- PCI/PM: Assume ports without DLL Link Active train links in 100 ms
linux-oem-osp1 (5.0.0-1053.58) bionic; urgency=medium
* bionic/
* rtl8723bu wifi issue after being turned off (LP: #1878296)
- rtl8xxxu: Improve TX performance of RTL8723BU on rtl8xxxu driver
- rtl8xxxu: add bluetooth co-existence support for single antenna
- rtl8xxxu: remove set but not used variable 'rate_mask'
- rtl8xxxu: Remove set but not used variable 'vif', 'dev', 'len'
* Fix Pericom USB controller OHCI/EHCI PME# defect (LP: #1879321)
- serial: 8250_pci: Move Pericom IDs to pci_ids.h
- PCI: Avoid Pericom USB controller OHCI/EHCI PME# defect
* Don't register platform::micmute if the related tokens don't exist
(LP: #1877275)
- SAUCE: platform/x86: dell-laptop: don't register platform::micmute if the
related tokens don't exist
[ Ubuntu: 5.0.0-49.53 ]
* disco/linux: 5.0.0-49.53 -proposed tracker (LP: #1878826)
* Disco update: upstream stable patchset 2020-05-14 (LP: #1878681)
- remoteproc: Fix wrong rvring index computation
- mtd: cfi: fix deadloop in cfi_cmdset_0002.c do_write_buffer
- binder: take read mode of mmap_sem in binder_
- usb: dwc3: gadget: Do link recovery for SS and SSP
- usb: gadget: udc: bdc: Remove unnecessary NULL checks in bdc_req_complete
- iio:ad7797: Use correct attribute_group
- ASoC: q6dsp6: q6afe-dai: add missing channels to MI2S DAIs
- ASoC: tas571x: disable regulators on failed probe
- ASoC: wm8960: Fix wrong clock after suspend & resume
- nfsd: memory corruption in nfsd4_lock()
- i2c: altera: use proper variable to hold errno
- rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket
- net/cxgb4: Check the return from t4_query_params properly
- xfs: acquire superblock freeze protection on eofblocks scans
- svcrdma: Fix trace point use-after-free race
- svcrdma: Fix leak of svc_rdma_recv_ctxt objects
- PCI: Avoid ASMedia XHCI USB PME# from D0 defect
- PCI: Move Apex Edge TPU class quirk to fix BAR assignment
- ARM: dts: bcm283x: Disable dsi0 node
- cpumap: Avoid warning when CONFIG_
- net/mlx5: Fix failing fw tracer allocation on s390
- perf/core: fix parent pid/tid in task exit events
- bpf, x86_3...
Changed in linux-oem-osp1 (Ubuntu Eoan): | |
status: | Won't Fix → Fix Released |
This bug is awaiting verification that the 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-
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:/
tags: | added: verification-needed-groovy |
Eugene Crosser (crosser) wrote : | #38 |
I understand that it's fixed in the mainline quite a while ago, no?
Don't get it why is "verification-
tags: | removed: verification-needed-groovy |
This bug is awaiting verification that the 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-
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:/
tags: | added: verification-needed-groovy |
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 1865570
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.