CPU fan goes full throttle triggered by waking up from suspend on Lenovo X1 Carbon (4th Gen., 2016)

Bug #1711951 reported by Michael Stucki
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned
Zesty
Expired
Medium
Unassigned

Bug Description

This is a copy of a very similar bug report which is currently marked as triaged and where my comment is ignored maybe because of that.

Please see my additional remarks at the end of this report.

---
Thinkpad X1 Carbon 5th generation ultrabook with i7 Kabylake CPU running Ubuntu 17.04 has its fan go full steam if the laptop is woken up from sleep/suspend. Without any sleep/suspend the laptop's fan is basically "off" or silent, even for hours.

The bug has been fixed upstream, see

6625914 ACPI / EC: Drop EC noirq hooks to fix a regression
9c40f95 Revert "ACPI / EC: Enable event freeze mode..." to fix a regression

and/or https://bugzilla.kernel.org/show_bug.cgi?id=196129
(with duplicate https://bugzilla.kernel.org/show_bug.cgi?id=191181)

and I hope this fix will make its way into a near-future kernel update to ubuntu :)

Many thanks!
---

Source: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709616

Additional remarks:

- Like mentioned in https://bugzilla.kernel.org/show_bug.cgi?id=191181, the bug happens in other Lenovo models as well. It's not limited to the X1 Carbon 5th Gen.
- The bug was fixed in kernel 4.13 but not in 4.10. This means that users who run the HWE kernel on Ubuntu 16.04 LTS will have this problem too!

I can reproduce it on my local system which has "linux-image-generic-hwe-16.04" installed (4.10.0.32.34).

Reading through the comments, it's not exactly clear to me which of the commits has fixed this problem, but I guess that the following two changes have made the difference:

https://patchwork.kernel.org/patch/9835823/
https://patchwork.kernel.org/patch/9835825/

I am reporting this as a new issue because the fixes from 4.13 need to be backported to 4.10 for users of the Ubuntu 16.04 HWE kernel.

Many thanks!

Michael Stucki (mstucki)
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

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 1711951

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Michael Stucki (mstucki) wrote :

Since this is almost entirely a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709616, I am not adding any more logs. I guess it won't help since only a backport of an existing fix is needed.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.17/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key zesty
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Michael Stucki (mstucki) wrote :

I installed this kernel and booted it. Fan was running normal unless I suspended & resumed. After it, the same problem happens again. So no, the issue is not fixed in the mainline kernel.

I also checked the Git repository at git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack. The tag v4.10.17 does not include the two commits mentioned above.

tags: added: kernel-bug-exists-upstream
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

@Joseph,

Looks like these two commits are not being pulled into Zesty master-next.
Should we manually backport it?

commit 662591461c4b9a1e3b9b159dbf37648a585ebaae
Author: Lv Zheng <email address hidden>
Date: Wed Jul 12 11:09:09 2017 +0800

    ACPI / EC: Drop EC noirq hooks to fix a regression

commit 9c40f956ce9b331493347d1b3cb7e384f7dc0581
Author: Lv Zheng <email address hidden>
Date: Wed Jul 12 11:09:17 2017 +0800

    Revert "ACPI / EC: Enable event freeze mode..." to fix a regression

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I built a Zesty test kernel with commits 662591461 and 9c40f956. The kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1711951/

Can you test this kernel and see if it resolves this bug?

Changed in linux (Ubuntu):
assignee: nobody → Joseph Salisbury (jsalisbury)
status: Incomplete → In Progress
Changed in linux (Ubuntu Zesty):
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Joseph Salisbury (jsalisbury)
Revision history for this message
Michael Stucki (mstucki) wrote :

Thanks Joseph! Unfortunately the error persists after suspend (like before).

If I want to test this myself, how can I build a kernel from git://kernel.ubuntu.com/ubuntu/ubuntu-xenial.git, branch "hwe"? I tried to follow https://wiki.ubuntu.com/KernelTeam/GitKernelBuild and https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel but didn't succeed. Where do I take the "debian/" folder from? Should I use the folder which is included in the Git repo? But then, what's debian.hwe/ used for?

I know it's offtopic but it would help me to identify the needed patches for this problem on my own... Thanks for any pointers.

Revision history for this message
Michael Stucki (mstucki) wrote :

Status: Right now I'm on linux-image-generic-hwe-16.04 version 4.10.0.33.35 and it looks like the situation has improved a lot. The last few days I was able to suspend and resume and the fan remained silent. I only remember one time when the fan was loud and only a reboot helped.

Therefore I'd like to keep this issue open for a few more days, just to see if it happens again...

Besides this, I would still be happy if anyone can answer my questions from above...

Revision history for this message
Michael Stucki (mstucki) wrote :

The problem just happened again on this kernel (4.10.0.33.35), so the issue still needs to be solved.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Can you test the latest mainline kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13

Revision history for this message
Michael Stucki (mstucki) wrote :

@jsalisbury Will do and report back...

Still would like to try this out on my own, but I fail to find out how to build the hwe kernel on my own. See my questions above. As it looks to me, the official documentation is outdated or incomplete. Can you (or anyone else) please help?

Revision history for this message
Dag Blakstad (dag-blakstad) wrote :

This issue started to occur on my 4th gen X1 Carbon after I patched the BIOS to v1.33. Might be an coincidence but wanted to provide this information.

Changed in linux (Ubuntu Zesty):
status: In Progress → Incomplete
Changed in linux (Ubuntu):
status: In Progress → Incomplete
assignee: Joseph Salisbury (jsalisbury) → nobody
Changed in linux (Ubuntu Zesty):
assignee: Joseph Salisbury (jsalisbury) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu Zesty) because there has been no activity for 60 days.]

Changed in linux (Ubuntu Zesty):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.