Bug 211313 - Fans blowing at max after standby - Thinkpad
Summary: Fans blowing at max after standby - Thinkpad
Status: RESOLVED DOCUMENTED
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Thermal (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Zhang Rui
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-21 16:30 UTC by permaer
Modified: 2022-05-18 19:23 UTC (History)
28 users (show)

See Also:
Kernel Version: 5.10.7
Tree: Mainline
Regression: No


Attachments
acpidump (560.03 KB, text/plain)
2021-03-25 13:05 UTC, Davide Corrado
Details
acpidump (558.92 KB, text/plain)
2021-03-27 11:24 UTC, permaer
Details
debug patch to show failure reason (2.25 KB, patch)
2021-07-05 07:40 UTC, Zhang Rui
Details | Diff
ec0 dump with bug triggered (1.24 KB, text/plain)
2021-09-18 11:36 UTC, Ilya
Details
ec0 dump without a bug (1.24 KB, text/plain)
2021-09-18 11:49 UTC, Ilya
Details
acpidump when things are normal (832.16 KB, text/plain)
2021-10-04 21:57 UTC, cfr
Details
acpidump with bug active (832.16 KB, text/plain)
2021-10-04 21:57 UTC, cfr
Details
attachment-3962-0.html (1.42 KB, text/html)
2021-12-29 13:10 UTC, Davide Corrado
Details

Description permaer 2021-01-21 16:30:24 UTC
Device: Lenovo Thinkpad X1 Carbon, 4th gen.

After resuming the laptop from standby, around 1/3 (33%) of the time the fans start running at max and don't auto correct. I need to put the system in standby for the problem to reset (sometimes I need multiple tries). acpitz-acpi-0 gets stuck at 48 degrees C after resuming and fan keeps blowing as a result. I'm running kernel 5.10.7 (Manjaro).

This bug seems to be a duplicate of bug #191181, which seems to have been fixed for many Thinkpad hardware configs, but apparently not for mine. Another user there also reports the problem still persists on a Thinkpad T470s, hopefully they can drop their experience in this bug report as well.
Comment 1 Ilya 2021-01-22 14:39:48 UTC
Can confirm the bug. Still present in Ubuntu kernel 5.4.0-60-generic #67-Ubuntu SMP.

I didnt mess the values. But same bug as https://bugzilla.kernel.org/show_bug.cgi?id=191181

The latter one was unfortunately closed, meanwhile present in actual kernels.

hatdware - Thinkpad T470s with nvm2e ssd
Comment 2 Ilya 2021-01-22 14:41:41 UTC
The bug triggers in ca. 10% of cases.
Comment 3 Jonas 2021-01-31 19:41:09 UTC
Can also confirm this on my T460 on 5.4.94-1-lts #1 SMP and also on 5.10.11-zen2-1-zen #1 ZEN SMP using newest BIOS (r06uj69d), although this problem occurs like 70-90% of the time for me. Hibernation rarely ever works without this thermal/fan issue (sensor stuck at reading 48°C, thus Fan running).
I can still control the fan manually via:
 
echo level 0 > /proc/acpi/ibm/fan
for no fan activity or

echo level 7 > /proc/acpi/ibm/fan
for full fan activity and every level inbetween.

Only a full poweroff fixes it.
Comment 4 Omar 2021-03-02 10:24:02 UTC
I can also confirm this bug. Running T460 on the latest 1.43 BIOS, Manjaro KDE 5.21 Plasma version, kernel version 5.11.2. The problem occurs 100% times since the latest Manjaro and kernel update.
Comment 5 Zhang Rui 2021-03-04 06:25:24 UTC
please define "resume from standby".

I have a T470s on hand and let me check if I can reproduce the problem or not.
Comment 6 Omar 2021-03-04 07:51:12 UTC
(In reply to Zhang Rui from comment #5)
> please define "resume from standby".
> 
> I have a T470s on hand and let me check if I can reproduce the problem or
> not.

It means to put the laptop in sleep mode, then wake up and continue to use it. I don't think you can reproduce this T470s, as it has been resolved for T470/s in the latest BIOS update (1.43) AFAIK.
Comment 7 permaer 2021-03-04 11:00:44 UTC
Yes, resuming is closing the laptop so it goes in sleep mode and then opening it again. I can confirm that after the latest kernel update, Manjaro 5.11.2, it also occurs 100% of the times here on my Thinkpad X1 Carbon 4th gen.
Comment 8 Zhang Rui 2021-03-04 13:44:50 UTC
please check if you can reproduce the problem with the following commands
1. rtcwake -m freeze -s 15
2. rtcwake -m mem -s 15

Given that the problem is fixed by BIOS upgrade for other models, I suspect how much we can do in Linux kernel for this issue.
Comment 9 permaer 2021-03-04 14:36:04 UTC
Yes, I am able to reproduce the issue by executing command no. 2 (rtcwake -m mem -s 15), I don't need to use both commands to reproduce, only command 2 by itself triggers the issue. Command no. 1 does not trigger it. After executing the 2nd command, sensor acpitz-acpi-0 jumps to 48 and the fans start blowing at max.
Comment 10 Omar 2021-03-06 19:56:56 UTC
Okay, I've got some news on this bug. I've reinstalled my Manjaro installation, and fresh installation comes with kernel 5.9.16-1, and this bug didn't occur few times while testing. After that I've installed latest kernel version available which is 5.11.1-1, and error occurred 100% times. Reinstalled 5.9.16-1 and I am yet to experience the bug, will keep you updated.
Comment 11 permaer 2021-03-06 22:57:49 UTC
I use Manjaro as well, and after trying kernel 5.9.16 as Omar suggests, I can confirm that this changes the behaviour somewhat. It doesn't fix the bug however; I tried running 'rtcwake -m mem -s 15' again, and with this kernel version the bug is triggered only roughly 1 in 4 times (25%), and not every time (100%) like with kernel version 5.11.2.
Comment 12 cfr 2021-03-11 05:41:03 UTC
I'm seeing this problem for the first time on X270 with linux 5.11.4.arch1-1
. The problem is reproducible 100% of the time. However many resumes/reboots I do, it persists until poweroff. The issue does not occur with Arch's 5.10.21-1-lts kernel. The issue did not occur with Arch's 5.10.16.arch1-1 or earlier kernels.

The issue is the not-read thermal sensor reading. I posted more details in the comments on the bug report https://bugzilla.kernel.org/show_bug.cgi?id=210457 before I found this one. 

The fan spins up and stays up because the thermal sensor isn't read after waking.

The thermal sensors were read properly with every earlier kernel I've run on this machine over the last 3.5 years. They are read properly now with an older kernel.

What can I do to help diagnose this?
Comment 13 Davide Corrado 2021-03-20 09:51:00 UTC
I confirm the issue is still happening:

thinkpad x1 carbon 4gen (20FB).

fan goes to max speed, comes back to normal after a poweroff. a reboot in linux does not help, a reboot in the diagnostic helps, but after you exit from it.
Comment 14 Davide Corrado 2021-03-20 15:41:52 UTC
I Think I have a pattern:

on battery: if the fan is spinning, closing the lid make the issue happens. On resume fan spins @ max speed. Powering off fixes the issue; reboot does not.
on battery: if the fan is not spinning, the issues does not happen.

on AC power: the issue does not seem to happen to me.
Comment 15 Zhang Rui 2021-03-21 16:14:54 UTC
My first question is that, is the fan spinning and acpitz temperature stucks the same problem? say, do they always happen altogether?
If yes, it seems that the fan spin just because we got a bogus temperature.

And please attach the output of "grep . /sys/class/thermal/*/*" both with and without the fan spinning problem.
Comment 16 Zhang Rui 2021-03-21 16:16:26 UTC
https://bugzilla.kernel.org/show_bug.cgi?id=210457 is a good clue, the Fan is not controlled via ACPI, so the ACPI thermal zome temperature does not matter actually.
Not sure if this applies to other reporters in the thread or not.
Comment 17 Davide Corrado 2021-03-22 07:48:11 UTC
(In reply to Zhang Rui from comment #15)
> My first question is that, is the fan spinning and acpitz temperature stucks
> the same problem? say, do they always happen altogether?
> If yes, it seems that the fan spin just because we got a bogus temperature.
> 
> And please attach the output of "grep . /sys/class/thermal/*/*" both with
> and without the fan spinning problem.

I don't see the temperature stuck. It drops.

here you go:

normal behavior:

/sys/class/thermal/cooling_device0/cur_state:0
/sys/class/thermal/cooling_device0/max_state:10
/sys/class/thermal/cooling_device0/type:Processor
/sys/class/thermal/cooling_device1/cur_state:0
/sys/class/thermal/cooling_device1/max_state:10
/sys/class/thermal/cooling_device1/type:Processor
/sys/class/thermal/cooling_device2/cur_state:0
/sys/class/thermal/cooling_device2/max_state:10
/sys/class/thermal/cooling_device2/type:Processor
/sys/class/thermal/cooling_device3/cur_state:0
/sys/class/thermal/cooling_device3/max_state:10
/sys/class/thermal/cooling_device3/type:Processor
/sys/class/thermal/cooling_device4/cur_state:-1
/sys/class/thermal/cooling_device4/max_state:50
/sys/class/thermal/cooling_device4/type:intel_powerclamp
/sys/class/thermal/cooling_device5/cur_state:0
/sys/class/thermal/cooling_device5/max_state:20
/sys/class/thermal/cooling_device5/type:iwlwifi
/sys/class/thermal/thermal_zone0/available_policies:user_space step_wise bang_bang fair_share 
/sys/class/thermal/thermal_zone0/mode:enabled
/sys/class/thermal/thermal_zone0/passive:0
/sys/class/thermal/thermal_zone0/policy:step_wise
/sys/class/thermal/thermal_zone0/temp:49000
/sys/class/thermal/thermal_zone0/trip_point_0_temp:128000
/sys/class/thermal/thermal_zone0/trip_point_0_type:critical
/sys/class/thermal/thermal_zone0/type:acpitz
/sys/class/thermal/thermal_zone1/available_policies:user_space step_wise bang_bang fair_share 
/sys/class/thermal/thermal_zone1/mode:enabled
/sys/class/thermal/thermal_zone1/passive:0
/sys/class/thermal/thermal_zone1/policy:step_wise
/sys/class/thermal/thermal_zone1/temp:37500
/sys/class/thermal/thermal_zone1/trip_point_0_temp:115000
/sys/class/thermal/thermal_zone1/trip_point_0_type:critical
/sys/class/thermal/thermal_zone1/type:pch_skylake
/sys/class/thermal/thermal_zone2/available_policies:user_space step_wise bang_bang fair_share 
/sys/class/thermal/thermal_zone2/integral_cutoff:0
/sys/class/thermal/thermal_zone2/k_d:0
/sys/class/thermal/thermal_zone2/k_i:0
/sys/class/thermal/thermal_zone2/k_po:0
/sys/class/thermal/thermal_zone2/k_pu:0
/sys/class/thermal/thermal_zone2/mode:enabled
/sys/class/thermal/thermal_zone2/offset:0
/sys/class/thermal/thermal_zone2/policy:step_wise
/sys/class/thermal/thermal_zone2/slope:0
/sys/class/thermal/thermal_zone2/sustainable_power:0
/sys/class/thermal/thermal_zone2/temp:41000
/sys/class/thermal/thermal_zone2/trip_point_0_temp:0
/sys/class/thermal/thermal_zone2/trip_point_0_type:passive
/sys/class/thermal/thermal_zone2/trip_point_1_temp:0
/sys/class/thermal/thermal_zone2/trip_point_1_type:passive
/sys/class/thermal/thermal_zone2/type:x86_pkg_temp
/sys/class/thermal/thermal_zone3/available_policies:user_space step_wise bang_bang fair_share 
/sys/class/thermal/thermal_zone3/mode:enabled
/sys/class/thermal/thermal_zone3/policy:step_wise
/sys/class/thermal/thermal_zone3/temp:22000
/sys/class/thermal/thermal_zone3/trip_point_0_temp:-32768000
/sys/class/thermal/thermal_zone3/trip_point_0_type:passive
/sys/class/thermal/thermal_zone3/trip_point_1_temp:-32768000
/sys/class/thermal/thermal_zone3/trip_point_1_type:passive
/sys/class/thermal/thermal_zone3/trip_point_2_temp:-32768000
/sys/class/thermal/thermal_zone3/trip_point_2_type:passive
/sys/class/thermal/thermal_zone3/trip_point_3_temp:-32768000
/sys/class/thermal/thermal_zone3/trip_point_3_type:passive
/sys/class/thermal/thermal_zone3/trip_point_4_temp:-32768000
/sys/class/thermal/thermal_zone3/trip_point_4_type:passive
/sys/class/thermal/thermal_zone3/trip_point_5_temp:-32768000
/sys/class/thermal/thermal_zone3/trip_point_5_type:passive
/sys/class/thermal/thermal_zone3/trip_point_6_temp:-32768000
/sys/class/thermal/thermal_zone3/trip_point_6_type:passive
/sys/class/thermal/thermal_zone3/trip_point_7_temp:-32768000
/sys/class/thermal/thermal_zone3/trip_point_7_type:passive
/sys/class/thermal/thermal_zone3/type:iwlwifi_1


maxed fan with no redemption:
/sys/class/thermal/cooling_device0/cur_state:0
/sys/class/thermal/cooling_device0/max_state:10
/sys/class/thermal/cooling_device0/type:Processor
/sys/class/thermal/cooling_device1/cur_state:0
/sys/class/thermal/cooling_device1/max_state:10
/sys/class/thermal/cooling_device1/type:Processor
/sys/class/thermal/cooling_device2/cur_state:0
/sys/class/thermal/cooling_device2/max_state:10
/sys/class/thermal/cooling_device2/type:Processor
/sys/class/thermal/cooling_device3/cur_state:0
/sys/class/thermal/cooling_device3/max_state:10
/sys/class/thermal/cooling_device3/type:Processor
/sys/class/thermal/cooling_device4/cur_state:-1
/sys/class/thermal/cooling_device4/max_state:50
/sys/class/thermal/cooling_device4/type:intel_powerclamp
/sys/class/thermal/cooling_device5/cur_state:0
/sys/class/thermal/cooling_device5/max_state:20
/sys/class/thermal/cooling_device5/type:iwlwifi
/sys/class/thermal/thermal_zone0/available_policies:user_space step_wise bang_bang fair_share 
/sys/class/thermal/thermal_zone0/mode:enabled
/sys/class/thermal/thermal_zone0/passive:0
/sys/class/thermal/thermal_zone0/policy:step_wise
/sys/class/thermal/thermal_zone0/temp:48000
/sys/class/thermal/thermal_zone0/trip_point_0_temp:128000
/sys/class/thermal/thermal_zone0/trip_point_0_type:critical
/sys/class/thermal/thermal_zone0/type:acpitz
/sys/class/thermal/thermal_zone1/available_policies:user_space step_wise bang_bang fair_share 
/sys/class/thermal/thermal_zone1/mode:enabled
/sys/class/thermal/thermal_zone1/passive:0
/sys/class/thermal/thermal_zone1/policy:step_wise
/sys/class/thermal/thermal_zone1/temp:31000
/sys/class/thermal/thermal_zone1/trip_point_0_temp:115000
/sys/class/thermal/thermal_zone1/trip_point_0_type:critical
/sys/class/thermal/thermal_zone1/type:pch_skylake
/sys/class/thermal/thermal_zone2/available_policies:user_space step_wise bang_bang fair_share 
/sys/class/thermal/thermal_zone2/integral_cutoff:0
/sys/class/thermal/thermal_zone2/k_d:0
/sys/class/thermal/thermal_zone2/k_i:0
/sys/class/thermal/thermal_zone2/k_po:0
/sys/class/thermal/thermal_zone2/k_pu:0
/sys/class/thermal/thermal_zone2/mode:enabled
/sys/class/thermal/thermal_zone2/offset:0
/sys/class/thermal/thermal_zone2/policy:step_wise
/sys/class/thermal/thermal_zone2/slope:0
/sys/class/thermal/thermal_zone2/sustainable_power:0
/sys/class/thermal/thermal_zone2/temp:30000
/sys/class/thermal/thermal_zone2/trip_point_0_temp:0
/sys/class/thermal/thermal_zone2/trip_point_0_type:passive
/sys/class/thermal/thermal_zone2/trip_point_1_temp:0
/sys/class/thermal/thermal_zone2/trip_point_1_type:passive
/sys/class/thermal/thermal_zone2/type:x86_pkg_temp
/sys/class/thermal/thermal_zone3/available_policies:user_space step_wise bang_bang fair_share 
/sys/class/thermal/thermal_zone3/mode:enabled
/sys/class/thermal/thermal_zone3/policy:step_wise
/sys/class/thermal/thermal_zone3/temp:21000
/sys/class/thermal/thermal_zone3/trip_point_0_temp:-32768000
/sys/class/thermal/thermal_zone3/trip_point_0_type:passive
/sys/class/thermal/thermal_zone3/trip_point_1_temp:-32768000
/sys/class/thermal/thermal_zone3/trip_point_1_type:passive
/sys/class/thermal/thermal_zone3/trip_point_2_temp:-32768000
/sys/class/thermal/thermal_zone3/trip_point_2_type:passive
/sys/class/thermal/thermal_zone3/trip_point_3_temp:-32768000
/sys/class/thermal/thermal_zone3/trip_point_3_type:passive
/sys/class/thermal/thermal_zone3/trip_point_4_temp:-32768000
/sys/class/thermal/thermal_zone3/trip_point_4_type:passive
/sys/class/thermal/thermal_zone3/trip_point_5_temp:-32768000
/sys/class/thermal/thermal_zone3/trip_point_5_type:passive
/sys/class/thermal/thermal_zone3/trip_point_6_temp:-32768000
/sys/class/thermal/thermal_zone3/trip_point_6_type:passive
/sys/class/thermal/thermal_zone3/trip_point_7_temp:-32768000
/sys/class/thermal/thermal_zone3/trip_point_7_type:passive
/sys/class/thermal/thermal_zone3/type:iwlwifi_1


diff between normal and when the issue occurs:
23c23
< /sys/class/thermal/thermal_zone0/temp:49000
---
> /sys/class/thermal/thermal_zone0/temp:48000
31c31
< /sys/class/thermal/thermal_zone1/temp:37500
---
> /sys/class/thermal/thermal_zone1/temp:31000
46c46
< /sys/class/thermal/thermal_zone2/temp:41000
---
> /sys/class/thermal/thermal_zone2/temp:30000
55c55
< /sys/class/thermal/thermal_zone3/temp:22000
---
> /sys/class/thermal/thermal_zone3/temp:21000


I'm quite sure it didn't happen in the past. I just do not use stadby so much
Comment 18 permaer 2021-03-22 11:33:11 UTC
@Davide Corrado: yes, in your case the temperatures seem to "drop" (the values are lower), but, at least here, when the problem occurs there is one sensor that seems to have always the same value, /sys/class/thermal/thermal_zone0/temp. When the issue occurs, this sensor always seems to have jumped to 48000 and stays stuck there (the same as the acpitz sensor). I have tried it multiple times and the result is always the same. Also in your output this sensor reads the same value when the problem occurs.

@Zhang Rui: So yes, the problem of the sensor stuck at 48000 and the fan spinning always occur together.

See also the attached output of "grep . /sys/class/thermal/*/*", which illustrates this as well:

NORMAL
/sys/class/thermal/cooling_device0/cur_state:0
/sys/class/thermal/cooling_device0/max_state:10
/sys/class/thermal/cooling_device0/type:Processor
/sys/class/thermal/cooling_device1/cur_state:0
/sys/class/thermal/cooling_device1/max_state:10
/sys/class/thermal/cooling_device1/type:Processor
/sys/class/thermal/cooling_device2/cur_state:0
/sys/class/thermal/cooling_device2/max_state:10
/sys/class/thermal/cooling_device2/type:Processor
/sys/class/thermal/cooling_device3/cur_state:0
/sys/class/thermal/cooling_device3/max_state:10
/sys/class/thermal/cooling_device3/type:Processor
/sys/class/thermal/cooling_device4/cur_state:0
/sys/class/thermal/cooling_device4/max_state:20
/sys/class/thermal/cooling_device4/type:iwlwifi
/sys/class/thermal/cooling_device5/cur_state:-1
/sys/class/thermal/cooling_device5/max_state:50
/sys/class/thermal/cooling_device5/type:intel_powerclamp
/sys/class/thermal/thermal_zone0/available_policies:power_allocator user_space step_wise bang_bang fair_share 
/sys/class/thermal/thermal_zone0/mode:enabled
/sys/class/thermal/thermal_zone0/passive:0
/sys/class/thermal/thermal_zone0/policy:step_wise
/sys/class/thermal/thermal_zone0/temp:40000
/sys/class/thermal/thermal_zone0/trip_point_0_temp:128000
/sys/class/thermal/thermal_zone0/trip_point_0_type:critical
/sys/class/thermal/thermal_zone0/type:acpitz
/sys/class/thermal/thermal_zone1/available_policies:power_allocator user_space step_wise bang_bang fair_share 
/sys/class/thermal/thermal_zone1/mode:enabled
/sys/class/thermal/thermal_zone1/passive:0
/sys/class/thermal/thermal_zone1/policy:step_wise
/sys/class/thermal/thermal_zone1/temp:35000
/sys/class/thermal/thermal_zone1/trip_point_0_temp:115000
/sys/class/thermal/thermal_zone1/trip_point_0_type:critical
/sys/class/thermal/thermal_zone1/type:pch_skylake
/sys/class/thermal/thermal_zone2/available_policies:power_allocator user_space step_wise bang_bang fair_share 
/sys/class/thermal/thermal_zone2/mode:enabled
/sys/class/thermal/thermal_zone2/policy:step_wise
/sys/class/thermal/thermal_zone2/temp:37000
/sys/class/thermal/thermal_zone2/trip_point_0_temp:-32768000
/sys/class/thermal/thermal_zone2/trip_point_0_type:passive
/sys/class/thermal/thermal_zone2/trip_point_1_temp:-32768000
/sys/class/thermal/thermal_zone2/trip_point_1_type:passive
/sys/class/thermal/thermal_zone2/trip_point_2_temp:-32768000
/sys/class/thermal/thermal_zone2/trip_point_2_type:passive
/sys/class/thermal/thermal_zone2/trip_point_3_temp:-32768000
/sys/class/thermal/thermal_zone2/trip_point_3_type:passive
/sys/class/thermal/thermal_zone2/trip_point_4_temp:-32768000
/sys/class/thermal/thermal_zone2/trip_point_4_type:passive
/sys/class/thermal/thermal_zone2/trip_point_5_temp:-32768000
/sys/class/thermal/thermal_zone2/trip_point_5_type:passive
/sys/class/thermal/thermal_zone2/trip_point_6_temp:-32768000
/sys/class/thermal/thermal_zone2/trip_point_6_type:passive
/sys/class/thermal/thermal_zone2/trip_point_7_temp:-32768000
/sys/class/thermal/thermal_zone2/trip_point_7_type:passive
/sys/class/thermal/thermal_zone2/type:iwlwifi_1
/sys/class/thermal/thermal_zone3/available_policies:power_allocator user_space step_wise bang_bang fair_share 
/sys/class/thermal/thermal_zone3/integral_cutoff:0
/sys/class/thermal/thermal_zone3/k_d:0
/sys/class/thermal/thermal_zone3/k_i:0
/sys/class/thermal/thermal_zone3/k_po:0
/sys/class/thermal/thermal_zone3/k_pu:0
/sys/class/thermal/thermal_zone3/mode:enabled
/sys/class/thermal/thermal_zone3/offset:0
/sys/class/thermal/thermal_zone3/policy:step_wise
/sys/class/thermal/thermal_zone3/slope:0
/sys/class/thermal/thermal_zone3/sustainable_power:0
/sys/class/thermal/thermal_zone3/temp:40000
/sys/class/thermal/thermal_zone3/trip_point_0_temp:0
/sys/class/thermal/thermal_zone3/trip_point_0_type:passive
/sys/class/thermal/thermal_zone3/trip_point_1_temp:0
/sys/class/thermal/thermal_zone3/trip_point_1_type:passive
/sys/class/thermal/thermal_zone3/type:x86_pkg_temp

WITH ISSUE
/sys/class/thermal/cooling_device0/cur_state:0
/sys/class/thermal/cooling_device0/max_state:10
/sys/class/thermal/cooling_device0/type:Processor
/sys/class/thermal/cooling_device1/cur_state:0
/sys/class/thermal/cooling_device1/max_state:10
/sys/class/thermal/cooling_device1/type:Processor
/sys/class/thermal/cooling_device2/cur_state:0
/sys/class/thermal/cooling_device2/max_state:10
/sys/class/thermal/cooling_device2/type:Processor
/sys/class/thermal/cooling_device3/cur_state:0
/sys/class/thermal/cooling_device3/max_state:10
/sys/class/thermal/cooling_device3/type:Processor
/sys/class/thermal/cooling_device4/cur_state:0
/sys/class/thermal/cooling_device4/max_state:20
/sys/class/thermal/cooling_device4/type:iwlwifi
/sys/class/thermal/cooling_device5/cur_state:-1
/sys/class/thermal/cooling_device5/max_state:50
/sys/class/thermal/cooling_device5/type:intel_powerclamp
/sys/class/thermal/thermal_zone0/available_policies:power_allocator user_space step_wise bang_bang fair_share 
/sys/class/thermal/thermal_zone0/mode:enabled
/sys/class/thermal/thermal_zone0/passive:0
/sys/class/thermal/thermal_zone0/policy:step_wise
/sys/class/thermal/thermal_zone0/temp:48000
/sys/class/thermal/thermal_zone0/trip_point_0_temp:128000
/sys/class/thermal/thermal_zone0/trip_point_0_type:critical
/sys/class/thermal/thermal_zone0/type:acpitz
/sys/class/thermal/thermal_zone1/available_policies:power_allocator user_space step_wise bang_bang fair_share 
/sys/class/thermal/thermal_zone1/mode:enabled
/sys/class/thermal/thermal_zone1/passive:0
/sys/class/thermal/thermal_zone1/policy:step_wise
/sys/class/thermal/thermal_zone1/temp:31000
/sys/class/thermal/thermal_zone1/trip_point_0_temp:115000
/sys/class/thermal/thermal_zone1/trip_point_0_type:critical
/sys/class/thermal/thermal_zone1/type:pch_skylake
/sys/class/thermal/thermal_zone2/available_policies:power_allocator user_space step_wise bang_bang fair_share 
/sys/class/thermal/thermal_zone2/mode:enabled
/sys/class/thermal/thermal_zone2/policy:step_wise
/sys/class/thermal/thermal_zone2/temp:37000
/sys/class/thermal/thermal_zone2/trip_point_0_temp:-32768000
/sys/class/thermal/thermal_zone2/trip_point_0_type:passive
/sys/class/thermal/thermal_zone2/trip_point_1_temp:-32768000
/sys/class/thermal/thermal_zone2/trip_point_1_type:passive
/sys/class/thermal/thermal_zone2/trip_point_2_temp:-32768000
/sys/class/thermal/thermal_zone2/trip_point_2_type:passive
/sys/class/thermal/thermal_zone2/trip_point_3_temp:-32768000
/sys/class/thermal/thermal_zone2/trip_point_3_type:passive
/sys/class/thermal/thermal_zone2/trip_point_4_temp:-32768000
/sys/class/thermal/thermal_zone2/trip_point_4_type:passive
/sys/class/thermal/thermal_zone2/trip_point_5_temp:-32768000
/sys/class/thermal/thermal_zone2/trip_point_5_type:passive
/sys/class/thermal/thermal_zone2/trip_point_6_temp:-32768000
/sys/class/thermal/thermal_zone2/trip_point_6_type:passive
/sys/class/thermal/thermal_zone2/trip_point_7_temp:-32768000
/sys/class/thermal/thermal_zone2/trip_point_7_type:passive
/sys/class/thermal/thermal_zone2/type:iwlwifi_1
/sys/class/thermal/thermal_zone3/available_policies:power_allocator user_space step_wise bang_bang fair_share 
/sys/class/thermal/thermal_zone3/integral_cutoff:0
/sys/class/thermal/thermal_zone3/k_d:0
/sys/class/thermal/thermal_zone3/k_i:0
/sys/class/thermal/thermal_zone3/k_po:0
/sys/class/thermal/thermal_zone3/k_pu:0
/sys/class/thermal/thermal_zone3/mode:enabled
/sys/class/thermal/thermal_zone3/offset:0
/sys/class/thermal/thermal_zone3/policy:step_wise
/sys/class/thermal/thermal_zone3/slope:0
/sys/class/thermal/thermal_zone3/sustainable_power:0
/sys/class/thermal/thermal_zone3/temp:34000
/sys/class/thermal/thermal_zone3/trip_point_0_temp:0
/sys/class/thermal/thermal_zone3/trip_point_0_type:passive
/sys/class/thermal/thermal_zone3/trip_point_1_temp:0
/sys/class/thermal/thermal_zone3/trip_point_1_type:passive
/sys/class/thermal/thermal_zone3/type:x86_pkg_temp

DIFF (NORMAL VS ISSUE)
23c23
< /sys/class/thermal/thermal_zone0/temp:40000
---
> /sys/class/thermal/thermal_zone0/temp:48000

31c31
< /sys/class/thermal/thermal_zone1/temp:35000
---
> /sys/class/thermal/thermal_zone1/temp:31000

67c67
< /sys/class/thermal/thermal_zone3/temp:40000
---
> /sys/class/thermal/thermal_zone3/temp:34000
Comment 19 Zhang Rui 2021-03-22 12:42:03 UTC
So there are two problems here.
1. ACPI thermal zone temperature stucks. Please attach the acpidump output.
2. the fan blows. This is unrelated with ACPI thermal control. Let's see if the fan is controlled by thinkpad_acpi or not, please attach the output of "grep . /sys/class/hwmon/hwmon*/*"
Comment 20 Davide Corrado 2021-03-22 15:06:47 UTC
here you go:

1) acpidump:

https://mega.nz/file/DL4DQSwD#jbhrEdY6D9eqpAr5tv7mOMef9U6WlLo0PW5785i8CTI

2) here you go
/sys/class/hwmon/hwmon0/name:AC
/sys/class/hwmon/hwmon1/name:acpitz
/sys/class/hwmon/hwmon1/temp1_crit:128000
/sys/class/hwmon/hwmon1/temp1_input:35000
/sys/class/hwmon/hwmon2/in0_input:15081
/sys/class/hwmon/hwmon2/name:BAT0
/sys/class/hwmon/hwmon3/name:pch_skylake
/sys/class/hwmon/hwmon3/temp1_input:35500
/sys/class/hwmon/hwmon4/fan1_input:0
/sys/class/hwmon/hwmon4/name:thinkpad
/sys/class/hwmon/hwmon4/pwm1:255
/sys/class/hwmon/hwmon4/pwm1_enable:2
/sys/class/hwmon/hwmon4/temp10_input:1000
/sys/class/hwmon/hwmon4/temp11_input:0
/sys/class/hwmon/hwmon4/temp12_input:0
/sys/class/hwmon/hwmon4/temp13_input:0
/sys/class/hwmon/hwmon4/temp14_input:0
/sys/class/hwmon/hwmon4/temp15_input:0
/sys/class/hwmon/hwmon4/temp16_input:0
/sys/class/hwmon/hwmon4/temp1_input:35000
/sys/class/hwmon/hwmon4/temp3_input:0
/sys/class/hwmon/hwmon4/temp4_input:0
/sys/class/hwmon/hwmon4/temp5_input:0
/sys/class/hwmon/hwmon4/temp6_input:0
/sys/class/hwmon/hwmon4/temp7_input:0
/sys/class/hwmon/hwmon4/temp8_input:0
/sys/class/hwmon/hwmon4/temp9_input:0
/sys/class/hwmon/hwmon5/name:coretemp
/sys/class/hwmon/hwmon5/temp1_crit:100000
/sys/class/hwmon/hwmon5/temp1_crit_alarm:0
/sys/class/hwmon/hwmon5/temp1_input:38000
/sys/class/hwmon/hwmon5/temp1_label:Package id 0
/sys/class/hwmon/hwmon5/temp1_max:100000
/sys/class/hwmon/hwmon5/temp2_crit:100000
/sys/class/hwmon/hwmon5/temp2_crit_alarm:0
/sys/class/hwmon/hwmon5/temp2_input:35000
/sys/class/hwmon/hwmon5/temp2_label:Core 0
/sys/class/hwmon/hwmon5/temp2_max:100000
/sys/class/hwmon/hwmon5/temp3_crit:100000
/sys/class/hwmon/hwmon5/temp3_crit_alarm:0
/sys/class/hwmon/hwmon5/temp3_input:38000
/sys/class/hwmon/hwmon5/temp3_label:Core 1
/sys/class/hwmon/hwmon5/temp3_max:100000
/sys/class/hwmon/hwmon6/name:iwlwifi_1
/sys/class/hwmon/hwmon6/temp1_input:28000


please note: I have noticed that temp1 is N/A when the fan it the ludicrous speed; I am not the only one who reported it

normal:
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +28.0°C  

thinkpad-isa-0000
Adapter: ISA adapter
fan1:           0 RPM
temp1:        +42.0°C   <=== NORMAL  
temp2:            N/A  
temp3:         +0.0°C  
temp4:         +0.0°C  
temp5:         +0.0°C  
temp6:         +0.0°C  
temp7:         +0.0°C  
temp8:         +0.0°C  
temp9:         +0.0°C  
temp10:        +1.0°C  
temp11:        +0.0°C  
temp12:        +0.0°C  
temp13:        +0.0°C  
temp14:        +0.0°C  
temp15:        +0.0°C  
temp16:        +0.0°C  

BAT0-acpi-0
Adapter: ACPI interface
in0:          14.47 V  

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +49.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +49.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +49.0°C  (high = +100.0°C, crit = +100.0°C)

pch_skylake-virtual-0
Adapter: Virtual device
temp1:        +37.0°C  

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +42.0°C  (crit = +128.0°C)



ludicrous speed:
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +30.0°C  

thinkpad-isa-0000
Adapter: ISA adapter
fan1:        6993 RPM
temp1:            N/A  <==== MAX SPEED
temp2:            N/A  
temp3:         +0.0°C  
temp4:         +0.0°C  
temp5:         +0.0°C  
temp6:         +0.0°C  
temp7:         +0.0°C  
temp8:         +0.0°C  
temp9:         +0.0°C  
temp10:        +1.0°C  
temp11:        +0.0°C  
temp12:        +0.0°C  
temp13:        +0.0°C  
temp14:        +0.0°C  
temp15:        +0.0°C  
temp16:        +0.0°C  

BAT0-acpi-0
Adapter: ACPI interface
in0:          14.97 V  

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +40.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +39.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +40.0°C  (high = +100.0°C, crit = +100.0°C)

pch_skylake-virtual-0
Adapter: Virtual device
temp1:        +39.5°C  

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +48.0°C  (crit = +128.0°C)
Comment 21 Davide Corrado 2021-03-25 13:05:25 UTC
Created attachment 296059 [details]
acpidump
Comment 22 permaer 2021-03-27 11:24:15 UTC
Created attachment 296089 [details]
acpidump

@Zhang Rui: hereby the requested information.

1) acpidump -> see attachment

2) Output of "grep . /sys/class/hwmon/hwmon*/*":

/sys/class/hwmon/hwmon0/name:acpitz
/sys/class/hwmon/hwmon0/temp1_crit:128000
/sys/class/hwmon/hwmon0/temp1_input:48000
/sys/class/hwmon/hwmon1/name:AC
/sys/class/hwmon/hwmon2/name:pch_skylake
/sys/class/hwmon/hwmon2/temp1_input:31000
/sys/class/hwmon/hwmon3/in0_input:17122
/sys/class/hwmon/hwmon3/name:BAT0
/sys/class/hwmon/hwmon4/fan1_input:6928
/sys/class/hwmon/hwmon4/name:thinkpad
/sys/class/hwmon/hwmon4/pwm1:255
/sys/class/hwmon/hwmon4/pwm1_enable:2
/sys/class/hwmon/hwmon4/temp10_input:1000
/sys/class/hwmon/hwmon4/temp11_input:0
/sys/class/hwmon/hwmon4/temp12_input:0
/sys/class/hwmon/hwmon4/temp13_input:0
/sys/class/hwmon/hwmon4/temp14_input:0
/sys/class/hwmon/hwmon4/temp15_input:0
/sys/class/hwmon/hwmon4/temp16_input:0
/sys/class/hwmon/hwmon4/temp3_input:0
/sys/class/hwmon/hwmon4/temp4_input:0
/sys/class/hwmon/hwmon4/temp5_input:0
/sys/class/hwmon/hwmon4/temp6_input:0
/sys/class/hwmon/hwmon4/temp7_input:0
/sys/class/hwmon/hwmon4/temp8_input:0
/sys/class/hwmon/hwmon4/temp9_input:0
/sys/class/hwmon/hwmon5/name:coretemp
/sys/class/hwmon/hwmon5/temp1_crit:100000
/sys/class/hwmon/hwmon5/temp1_crit_alarm:0
/sys/class/hwmon/hwmon5/temp1_input:33000
/sys/class/hwmon/hwmon5/temp1_label:Package id 0
/sys/class/hwmon/hwmon5/temp1_max:100000
/sys/class/hwmon/hwmon5/temp2_crit:100000
/sys/class/hwmon/hwmon5/temp2_crit_alarm:0
/sys/class/hwmon/hwmon5/temp2_input:32000
/sys/class/hwmon/hwmon5/temp2_label:Core 0
/sys/class/hwmon/hwmon5/temp2_max:100000
/sys/class/hwmon/hwmon5/temp3_crit:100000
/sys/class/hwmon/hwmon5/temp3_crit_alarm:0
/sys/class/hwmon/hwmon5/temp3_input:32000
/sys/class/hwmon/hwmon5/temp3_label:Core 1
/sys/class/hwmon/hwmon5/temp3_max:100000
/sys/class/hwmon/hwmon6/name:iwlwifi_1
/sys/class/hwmon/hwmon6/temp1_input:33000
Comment 23 cfr 2021-03-29 03:04:42 UTC
On my machine (X270), a firmware update seems to have resolved the issue. That is, the thermal sensor is no longer gets stuck and the fan behaves much as it always did. This is even with the 5.11.* kernels after sleep. So, in my case, the kernels seem to have triggered an underlying firmware bug which didn't cause any symptoms with earlier kernels (3+ years' worth).

I don't know if this is helpful. If you still want any data from me, let me know. I'm assuming not since I'm not seeing the issue any longer..
Comment 24 Omar 2021-03-29 15:56:08 UTC
(In reply to cfr from comment #23)
> On my machine (X270), a firmware update seems to have resolved the issue.
> That is, the thermal sensor is no longer gets stuck and the fan behaves much
> as it always did. This is even with the 5.11.* kernels after sleep. So, in
> my case, the kernels seem to have triggered an underlying firmware bug which
> didn't cause any symptoms with earlier kernels (3+ years' worth).
> 
> I don't know if this is helpful. If you still want any data from me, let me
> know. I'm assuming not since I'm not seeing the issue any longer..


May I ask what firmware are you referring to? Is it the BIOS or something else?
Comment 25 Daniel 2021-03-31 19:43:54 UTC
I can confirm this bug (or a variation thereof) for the Thinkpad X1 Yoga, 4th Generation, for kernel versions 5.10.26 and 5.11.10. Sometimes (not only after standby-wakeup, also after a regular boot) the fan blows full speed, and sometimes you can hear it spin up for a very short time. It is definitely not a hardware defect.
Comment 26 Denis L. 2021-04-12 17:04:01 UTC
I can confirm, this problem still exist on 5.11.11 kernel.
Problem exist only when system waking up from sleep mode (not hibernate). Reboot system not resolve this problem, only full halt system helpful.
My Machine Lenovo X1 Carbon 4th GEN.
Comment 27 Denis L. 2021-04-28 06:51:02 UTC
Im assume thats a hardware/bios bug...

Listen, when this issue appear im found that sensors showing me constantly same temperature
acpitz-acpi-0
Adapter: ACPI interface
temp1:        +48.0°C  (crit = +128.0°C)

Then i shutdown laptop and then immediately turned on him, then i call sensors and found strange issue, temperature will be higher berfore turning off and then temperature started to decline

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +64.0°C  (crit = +128.0°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +51.0°C  (crit = +128.0°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +50.0°C  (crit = +128.0°C)


acpitz-acpi-0
Adapter: ACPI interface
temp1:        +49.0°C  (crit = +128.0°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +48.0°C  (crit = +128.0°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +47.0°C  (crit = +128.0°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +46.0°C  (crit = +128.0°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +45.0°C  (crit = +128.0°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +44.0°C  (crit = +128.0°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +43.0°C  (crit = +128.0°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +39.0°C  (crit = +128.0°C)
Comment 28 Nghia T 2021-05-04 21:47:25 UTC
I can confirm the problem existed on Thinkpad X1 Carbon Gen 4 running 5.4.0-58-generic (Mint 20.1). BIOS is latest (1.48).  acpitz-acpi-0 showed 48 deg when the fan went screaming without any cpu load.
Comment 29 Nghia T 2021-05-05 21:02:38 UTC
(In reply to Zhang Rui from comment #8)
> please check if you can reproduce the problem with the following commands
> 1. rtcwake -m freeze -s 15
> 2. rtcwake -m mem -s 15
> 
> Given that the problem is fixed by BIOS upgrade for other models, I suspect
> how much we can do in Linux kernel for this issue.

Once I ran the 2nd command above, the fan stopped and temp1 went back to 29 deg C. So something was configured to run when the laptop resumes from suspend??

I went checking /usr/lib/systemd/system-sleep and there are x2 scripts: hdparm and tlp. They were installed part of the tlp package. Since the thinkpad X1 has SSD, I've remove the packages hdparm and tlp as an experiment to see if things will improve or not.
Comment 30 Denis L. 2021-05-06 15:21:04 UTC
(In reply to Zhang Rui from comment #8)
> please check if you can reproduce the problem with the following commands
> 1. rtcwake -m freeze -s 15
> 2. rtcwake -m mem -s 15
> 
> Given that the problem is fixed by BIOS upgrade for other models, I suspect
> how much we can do in Linux kernel for this issue.

Thats not helped for me :(
Comment 31 Denis L. 2021-05-19 06:25:11 UTC
Im found next bug, kernel 5.11.19-300.fc34.x86_64 after suspend fan constantly changes from decreasing to higher speed and vice versa.
After upgrade kernel to 5.11.20-300.fc34.x86_64 after suspend fan constantly working at full power.
Comment 32 Luke 2021-06-27 11:08:49 UTC
Same here. CPU fan at 100% regardless of load.

Thinkpad x260, Fedora 34, kernel: 5.12.12-300.fc34.x86_64
Comment 33 Davide Corrado 2021-06-27 18:41:42 UTC
the latest firmware update fixed the issue on x1 carbon 4th gen!

this version: 1.49 released on: 15 Jun 2021
Comment 34 Denis L. 2021-06-28 05:24:57 UTC
I cannot approve this fix on

Handle 0x000C, DMI type 1, 27 bytes
System Information
	Manufacturer: LENOVO
	Product Name: 20FB002RUS
	Version: ThinkPad X1 Carbon 4th


Handle 0x000B, DMI type 0, 24 bytes
BIOS Information
	Vendor: LENOVO
	Version: N1FET75W (1.49 )
	Release Date: 05/25/2021
	Address: 0xE0000
	Runtime Size: 128 kB
	ROM Size: 16 MB


Problem exists, what kernel you are using?
Comment 35 Davide Corrado 2021-06-28 07:50:53 UTC
(In reply to Denis L. from comment #34)
> I cannot approve this fix on
> 
> Handle 0x000C, DMI type 1, 27 bytes
> System Information
>       Manufacturer: LENOVO
>       Product Name: 20FB002RUS
>       Version: ThinkPad X1 Carbon 4th
> 
> 
> Handle 0x000B, DMI type 0, 24 bytes
> BIOS Information
>       Vendor: LENOVO
>       Version: N1FET75W (1.49 )
>       Release Date: 05/25/2021
>       Address: 0xE0000
>       Runtime Size: 128 kB
>       ROM Size: 16 MB
> 
> 
> Problem exists, what kernel you are using?

try the latest firmware. it fixed on mine. read my previous post
Comment 36 Davide Corrado 2021-06-28 07:51:29 UTC
oh, I see you are running on latest one. sorry
Comment 37 Luke 2021-06-28 22:34:58 UTC
BIOS Information
        Vendor: LENOVO
        Version: R02ET71W (1.44 )
        Release Date: 05/08/2019
        Address: 0xE0000
        Runtime Size: 128 kB
        ROM Size: 16 MB
        [...]
        BIOS Revision: 1.44
        Firmware Revision: 1.15

Handle 0x000C, DMI type 1, 27 bytes
System Information
        Manufacturer: LENOVO
        Product Name: 20F5S31G00
        Version: ThinkPad X260


I thought I'm up-to-date with the firmware via fwupd (LVFS) but it looks like there's a newer firmware on Lenovo website. I'll flash it in my free time.
Comment 38 permaer 2021-06-30 20:12:55 UTC
I can confirm the observation made by Denis L., that upgrading the Lenovo ThinkPad X1 Carbon 4th gen to BIOS firmware 1.49 does NOT solve the problem (kernel version 5.12.9 on Manjaro).

So I will use kernel version 5.4.124, which does not contain this bug. Would be great if someone could track it down and squash it, because it is a very annoying bug.
Comment 39 Denis L. 2021-06-30 20:32:29 UTC
@permaer same here on 5.12.12-300.fc34.x86_64. NOT FIXED
Comment 40 Denis L. 2021-06-30 20:39:29 UTC
So, im using legacy BIOS
Comment 41 Denis L. 2021-06-30 20:44:14 UTC
Any clue, im using LTE modem, may be this bug, im not tested...
Comment 42 Zhang Rui 2021-07-01 01:42:32 UTC
can all of you in this thread confirm this pattern?

thinkpad-isa-0000
Adapter: ISA adapter
fan1:        6993 RPM
temp1:            N/A  <==== MAX SPEED
temp2:            N/A 

please attach the output both with and without the problem occurred.

To be honest,
1. I'm not sure if you're seeing exactly the same problem or not, as we got conflict information on different models/firmware versions/kernel versions.
2. I'm not sure how much we can do from kernel' perspective of view because this is very likely to be firmware related. we can only try to narrow down the problem. for example, if the above pattern is correct, the thinkpad-acpi driver may give some clue of the rootcause of the problem.
Comment 43 Denis L. 2021-07-01 06:11:43 UTC
>can all of you in this thread confirm this pattern?

thinkpad-isa-0000
Adapter: ISA adapter
fan1:        7894 RPM
temp1:            N/A  
temp2:            N/A  
temp3:         +0.0°C  
temp4:         +0.0°C  
temp5:         +0.0°C  
temp6:         +0.0°C  
temp7:         +0.0°C  
temp8:         +0.0°C
Comment 44 Zhang Rui 2021-07-01 06:34:32 UTC
sorry that I was not clear enough,

Can we confirm the above pattern exists only when the Fan is blowing erroneously?
Comment 45 Denis L. 2021-07-01 06:37:32 UTC
>Can we confirm the above pattern exists only when the Fan is blowing
>erroneously?

after full shutdown i have this data
thinkpad-isa-0000
Adapter: ISA adapter
fan1:        5199 RPM
temp1:        +63.0°C  
temp2:            N/A  
temp3:         +0.0°C  
temp4:         +0.0°C  
temp5:         +0.0°C  
temp6:         +0.0°C  
temp7:         +0.0°C  
temp8:         +0.0°C
Comment 46 Davide Corrado 2021-07-01 08:26:02 UTC
well, I tried two times on battery: running mprime -t to make the fan spin, then stop it and close the lid. the fan does not spin as hell, it works as expected. this is what I noticed when I joined the discussion and it works now. what do I miss then?

I'm on this kernel right now

5.12.13-300.fc34.x86_64

latest firmware applied to x1 carbon 4gen
Comment 47 Denis L. 2021-07-01 08:27:55 UTC
# uname -r
5.12.12-300.fc34.x86_64
# rpm -qa|grep linux-firmware
linux-firmware-whence-20210511-120.fc34.noarch
linux-firmware-20210511-120.fc34.noarch
Comment 48 Zhang Rui 2021-07-01 08:44:41 UTC
(In reply to Denis L. from comment #45)
> >Can we confirm the above pattern exists only when the Fan is blowing
> >erroneously?
> 
> after full shutdown i have this data
> thinkpad-isa-0000
> Adapter: ISA adapter
> fan1:        5199 RPM
> temp1:        +63.0°C  
> temp2:            N/A  

tmp2 N/A is okay.
what do you see when the problem is reproduced?
Comment 49 Zhang Rui 2021-07-01 08:45:32 UTC
(In reply to Davide Corrado from comment #46)
> well, I tried two times on battery: running mprime -t to make the fan spin,
> then stop it and close the lid. the fan does not spin as hell, it works as
> expected. this is what I noticed when I joined the discussion and it works
> now. what do I miss then?
> 
> I'm on this kernel right now
> 
> 5.12.13-300.fc34.x86_64
> 
> latest firmware applied to x1 carbon 4gen

So the problem is gone on your system, right?

what is the output about thinkpad-isa-0000?
Comment 50 Denis L. 2021-07-01 08:50:25 UTC
(In reply to Zhang Rui from comment #48)
> (In reply to Denis L. from comment #45)
> > >Can we confirm the above pattern exists only when the Fan is blowing
> > >erroneously?
> > 
> > after full shutdown i have this data
> > thinkpad-isa-0000
> > Adapter: ISA adapter
> > fan1:        5199 RPM
> > temp1:        +63.0°C  
> > temp2:            N/A  
> 
> tmp2 N/A is okay.
> what do you see when the problem is reproduced?

After sleep my fan always in an eternal start/stop loop
# sensors
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +44.0°C  

thinkpad-isa-0000
Adapter: ISA adapter
fan1:        6928 RPM
temp1:            N/A  
temp2:            N/A  
temp3:         +0.0°C  
temp4:         +0.0°C  
temp5:         +0.0°C  
temp6:         +0.0°C  
temp7:         +0.0°C  
temp8:         +0.0°C  

BAT0-acpi-0
Adapter: ACPI interface
in0:          16.68 V  

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +45.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +42.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +41.0°C  (high = +100.0°C, crit = +100.0°C)

pch_skylake-virtual-0
Adapter: Virtual device
temp1:        +42.0°C  

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +48.0°C  (crit = +128.0°C)
Comment 51 Denis L. 2021-07-01 08:51:47 UTC
(In reply to Davide Corrado from comment #46)
> well, I tried two times on battery: running mprime -t to make the fan spin,
> then stop it and close the lid. the fan does not spin as hell, it works as
> expected. this is what I noticed when I joined the discussion and it works
> now. what do I miss then?
> 
> I'm on this kernel right now
> 
> 5.12.13-300.fc34.x86_64
> 
> latest firmware applied to x1 carbon 4gen

Can you confirm that you are using exactly SLEEP mode, no HIBERNATE?
Comment 52 Davide Corrado 2021-07-01 09:29:42 UTC
I will do all the tests required. I, in the first place, do not close the lid and the power adapter is always plugged in. so this could have been unnoticed. But once I was working on the road, on battery. I had to move from a table to another one and I closed the lid, on battery, for moving. Then I opened the lid and noticed the fan was running like hell. so in my case I noticed this wrong behaviour on battery. Please tell me what I have to test. does this occur also when you are connected to the power adapter? I'm quite sure I am using sleep and not hybernate, but I cannot check it right now. will do asap
Comment 53 Denis L. 2021-07-01 11:36:26 UTC
(In reply to Davide Corrado from comment #52)
> I will do all the tests required. I, in the first place, do not close the
> lid and the power adapter is always plugged in. so this could have been
> unnoticed. But once I was working on the road, on battery. I had to move
> from a table to another one and I closed the lid, on battery, for moving.
> Then I opened the lid and noticed the fan was running like hell. so in my
> case I noticed this wrong behaviour on battery. Please tell me what I have
> to test. does this occur also when you are connected to the power adapter?
> I'm quite sure I am using sleep and not hybernate, but I cannot check it
> right now. will do asap

In my case i have a problem in both modes - on AC adapter and on a battery.
Comment 54 Davide Corrado 2021-07-01 16:24:15 UTC
the problem is not gone :-(

I think I have been just lucky in my previous tests. In my case it happens on battery. It happened a moment ago, with the latest efi firmware from x1c 4gen
Comment 55 Ilya 2021-07-02 09:22:11 UTC
Still present in Ubuntu kernel 5.4.0-70-generic #78-Ubuntu SMP.

The latter one was unfortunately closed, meanwhile present in actual kernels.

hatdware - Thinkpad T470s with nvm2e ssd

BIOS Version: N1WET41W (1.20 )

Steps:

1. sleep to mem when connected to  Poweradapter+HDMI Monitor+USB KEyboard/mouse
2. then disconnect
3. power up on battery without peripherals

output of sensors:


coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +29.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +27.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +27.0°C  (high = +100.0°C, crit = +100.0°C)

pch_skylake-virtual-0
Adapter: Virtual device
temp1:        +26.5°C  

BAT0-acpi-0
Adapter: ACPI interface
in0:          11.38 V  

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +28.0°C  

thinkpad-isa-0000
Adapter: ISA adapter
fan1:        4418 RPM
temp1:            N/A  
temp2:            N/A  
temp3:         +0.0°C  
temp4:         +0.0°C  
temp5:         +0.0°C  
temp6:         +0.0°C  
temp7:         +0.0°C  
temp8:         +0.0°C  

BAT1-acpi-0
Adapter: ACPI interface
in0:          11.46 V  

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +48.0°C  (crit = +128.0°C)
Comment 56 Zhang Rui 2021-07-05 01:15:35 UTC
when this happens,
temp1:            N/A  
temp2:            N/A 

It actually means the hwmon temp1_input and temp2_input sysfs attributes are gone?

just like what permaer attached previously,

(In reply to permaer from comment #22)
> 2) Output of "grep . /sys/class/hwmon/hwmon*/*":
> 
> /sys/class/hwmon/hwmon4/fan1_input:6928
> /sys/class/hwmon/hwmon4/name:thinkpad
> /sys/class/hwmon/hwmon4/pwm1:255
> /sys/class/hwmon/hwmon4/pwm1_enable:2
> /sys/class/hwmon/hwmon4/temp10_input:1000
> /sys/class/hwmon/hwmon4/temp11_input:0
> /sys/class/hwmon/hwmon4/temp12_input:0
> /sys/class/hwmon/hwmon4/temp13_input:0
> /sys/class/hwmon/hwmon4/temp14_input:0
> /sys/class/hwmon/hwmon4/temp15_input:0
> /sys/class/hwmon/hwmon4/temp16_input:0
> /sys/class/hwmon/hwmon4/temp3_input:0
> /sys/class/hwmon/hwmon4/temp4_input:0
> /sys/class/hwmon/hwmon4/temp5_input:0
> /sys/class/hwmon/hwmon4/temp6_input:0
> /sys/class/hwmon/hwmon4/temp7_input:0
> /sys/class/hwmon/hwmon4/temp8_input:0
> /sys/class/hwmon/hwmon4/temp9_input:0

Or maybe permaer just filter out the stderr messages.

So, when this happens,
temp1:            N/A  
temp2:            N/A 
please check check your hwmon sysfs I/F and see if the temp1_input/temp2_input attributes are gone, or they return error code.
Comment 57 Denis L. 2021-07-05 05:29:48 UTC
(In reply to Zhang Rui from comment #56)
> when this happens,
> temp1:            N/A  
> temp2:            N/A 
> 
> It actually means the hwmon temp1_input and temp2_input sysfs attributes are
> gone?
> 
> just like what permaer attached previously,
> 
> (In reply to permaer from comment #22)
> > 2) Output of "grep . /sys/class/hwmon/hwmon*/*":
> > 
> > /sys/class/hwmon/hwmon4/fan1_input:6928
> > /sys/class/hwmon/hwmon4/name:thinkpad
> > /sys/class/hwmon/hwmon4/pwm1:255
> > /sys/class/hwmon/hwmon4/pwm1_enable:2
> > /sys/class/hwmon/hwmon4/temp10_input:1000
> > /sys/class/hwmon/hwmon4/temp11_input:0
> > /sys/class/hwmon/hwmon4/temp12_input:0
> > /sys/class/hwmon/hwmon4/temp13_input:0
> > /sys/class/hwmon/hwmon4/temp14_input:0
> > /sys/class/hwmon/hwmon4/temp15_input:0
> > /sys/class/hwmon/hwmon4/temp16_input:0
> > /sys/class/hwmon/hwmon4/temp3_input:0
> > /sys/class/hwmon/hwmon4/temp4_input:0
> > /sys/class/hwmon/hwmon4/temp5_input:0
> > /sys/class/hwmon/hwmon4/temp6_input:0
> > /sys/class/hwmon/hwmon4/temp7_input:0
> > /sys/class/hwmon/hwmon4/temp8_input:0
> > /sys/class/hwmon/hwmon4/temp9_input:0
> 
> Or maybe permaer just filter out the stderr messages.
> 
> So, when this happens,
> temp1:            N/A  
> temp2:            N/A 
> please check check your hwmon sysfs I/F and see if the
> temp1_input/temp2_input attributes are gone, or they return error code.

Hi Zhang! This data when i have a bug

# LC_ALL=en_US grep . /sys/class/hwmon/hwmon*/*
grep: /sys/class/hwmon/hwmon0/device: Is a directory
/sys/class/hwmon/hwmon0/name:AC
grep: /sys/class/hwmon/hwmon0/power: Is a directory
grep: /sys/class/hwmon/hwmon0/subsystem: Is a directory
grep: /sys/class/hwmon/hwmon1/device: Is a directory
/sys/class/hwmon/hwmon1/name:acpitz
grep: /sys/class/hwmon/hwmon1/power: Is a directory
grep: /sys/class/hwmon/hwmon1/subsystem: Is a directory
/sys/class/hwmon/hwmon1/temp1_crit:128000
/sys/class/hwmon/hwmon1/temp1_input:48000
grep: /sys/class/hwmon/hwmon2/device: Is a directory
/sys/class/hwmon/hwmon2/in0_input:16105
/sys/class/hwmon/hwmon2/name:BAT0
grep: /sys/class/hwmon/hwmon2/power: Is a directory
grep: /sys/class/hwmon/hwmon2/subsystem: Is a directory
grep: /sys/class/hwmon/hwmon3/device: Is a directory
/sys/class/hwmon/hwmon3/name:pch_skylake
grep: /sys/class/hwmon/hwmon3/power: Is a directory
grep: /sys/class/hwmon/hwmon3/subsystem: Is a directory
/sys/class/hwmon/hwmon3/temp1_input:28000
grep: /sys/class/hwmon/hwmon4/device: Is a directory
/sys/class/hwmon/hwmon4/fan1_input:6932
/sys/class/hwmon/hwmon4/name:thinkpad
grep: /sys/class/hwmon/hwmon4/power: Is a directory
/sys/class/hwmon/hwmon4/pwm1:255
/sys/class/hwmon/hwmon4/pwm1_enable:2
grep: /sys/class/hwmon/hwmon4/subsystem: Is a directory
grep: /sys/class/hwmon/hwmon4/temp1_input: No such device or address
grep: /sys/class/hwmon/hwmon4/temp2_input: No such device or address
/sys/class/hwmon/hwmon4/temp3_input:0
/sys/class/hwmon/hwmon4/temp4_input:0
/sys/class/hwmon/hwmon4/temp5_input:0
/sys/class/hwmon/hwmon4/temp6_input:0
/sys/class/hwmon/hwmon4/temp7_input:0
/sys/class/hwmon/hwmon4/temp8_input:0
grep: /sys/class/hwmon/hwmon5/device: Is a directory
/sys/class/hwmon/hwmon5/name:coretemp
grep: /sys/class/hwmon/hwmon5/power: Is a directory
grep: /sys/class/hwmon/hwmon5/subsystem: Is a directory
/sys/class/hwmon/hwmon5/temp1_crit:100000
/sys/class/hwmon/hwmon5/temp1_crit_alarm:0
/sys/class/hwmon/hwmon5/temp1_input:31000
/sys/class/hwmon/hwmon5/temp1_label:Package id 0
/sys/class/hwmon/hwmon5/temp1_max:100000
/sys/class/hwmon/hwmon5/temp2_crit:100000
/sys/class/hwmon/hwmon5/temp2_crit_alarm:0
/sys/class/hwmon/hwmon5/temp2_input:29000
/sys/class/hwmon/hwmon5/temp2_label:Core 0
/sys/class/hwmon/hwmon5/temp2_max:100000
/sys/class/hwmon/hwmon5/temp3_crit:100000
/sys/class/hwmon/hwmon5/temp3_crit_alarm:0
/sys/class/hwmon/hwmon5/temp3_input:29000
/sys/class/hwmon/hwmon5/temp3_label:Core 1
/sys/class/hwmon/hwmon5/temp3_max:100000
grep: /sys/class/hwmon/hwmon6/device: Is a directory
/sys/class/hwmon/hwmon6/name:iwlwifi_1
grep: /sys/class/hwmon/hwmon6/power: Is a directory
grep: /sys/class/hwmon/hwmon6/subsystem: Is a directory
/sys/class/hwmon/hwmon6/temp1_input:28000

# sensors
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +28.0°C  

thinkpad-isa-0000
Adapter: ISA adapter
fan1:        6928 RPM
temp1:            N/A  
temp2:            N/A  
temp3:         +0.0°C  
temp4:         +0.0°C  
temp5:         +0.0°C  
temp6:         +0.0°C  
temp7:         +0.0°C  
temp8:         +0.0°C
Comment 58 Zhang Rui 2021-07-05 07:40:15 UTC
Created attachment 297753 [details]
debug patch to show failure reason

Hopefully the thinkpad_acpi driver can give more clue about this issue.
Please apply this patch on top of latest upstream kernel, and when the problem is reproduced, attach the dmesg output after running this command "grep . /sys/class/hwmon/hwmon4/temp*_input"
Comment 59 Denis L. 2021-07-05 08:42:59 UTC
(In reply to Zhang Rui from comment #58)
> Created attachment 297753 [details]
> debug patch to show failure reason
> 
> Hopefully the thinkpad_acpi driver can give more clue about this issue.
> Please apply this patch on top of latest upstream kernel, and when the
> problem is reproduced, attach the dmesg output after running this command
> "grep . /sys/class/hwmon/hwmon4/temp*_input"

Done
[69077.107348] ACPI: battery: extension unregistered: ThinkPad Battery Extension
[69086.420806] thinkpad_acpi: ThinkPad ACPI Extras v0.26
[69086.420814] thinkpad_acpi: http://ibm-acpi.sf.net/
[69086.420816] thinkpad_acpi: ThinkPad BIOS N1FET75W (1.49 ), EC N1FHT35W
[69086.420819] thinkpad_acpi: Lenovo ThinkPad X1 Carbon 4th, model 20FB002RUS
[69086.424947] thinkpad_acpi: radio switch found; radios are enabled
[69086.425754] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver
[69086.425760] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default...
[69086.436543] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
[69086.440165] thinkpad_acpi: rfkill switch tpacpi_wwan_sw: radio is unblocked
[69086.471131] thinkpad_acpi: battery 1 registered (start 0, stop 100)
[69086.471157] ACPI: battery: new extension: ThinkPad Battery Extension
[69086.478317] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input17
[69150.435218] thinkpad_acpi: thermal_get_sensor: idx 0, thermal_read_mode 3
[69150.435492] acpi_ec_read succeeded, tmp -128
[69150.435495] return -ENXIO because value is TPACPI_THERMAL_SENSOR_NA
[69150.435683] thinkpad_acpi: thermal_get_sensor: idx 1, thermal_read_mode 3
[69150.435982] acpi_ec_read succeeded, tmp -128
[69150.435984] return -ENXIO because value is TPACPI_THERMAL_SENSOR_NA
[69150.436030] thinkpad_acpi: thermal_get_sensor: idx 2, thermal_read_mode 3
[69150.436327] acpi_ec_read succeeded, tmp 0
[69150.436406] thinkpad_acpi: thermal_get_sensor: idx 3, thermal_read_mode 3
[69150.436665] acpi_ec_read succeeded, tmp 0
[69150.436705] thinkpad_acpi: thermal_get_sensor: idx 4, thermal_read_mode 3
[69150.436964] acpi_ec_read succeeded, tmp 0
[69150.436996] thinkpad_acpi: thermal_get_sensor: idx 5, thermal_read_mode 3
[69150.437261] acpi_ec_read succeeded, tmp 0
[69150.437291] thinkpad_acpi: thermal_get_sensor: idx 6, thermal_read_mode 3
[69150.437563] acpi_ec_read succeeded, tmp 0
[69150.437604] thinkpad_acpi: thermal_get_sensor: idx 7, thermal_read_mode 3
[69150.437860] acpi_ec_read succeeded, tmp 0
Comment 60 Zhang Rui 2021-07-06 00:52:09 UTC
CC Hans and Mark, who are the thinkpad_acpi driver experts.

Hi, Hans and Mark,

this problem is reported on a series of lenovo laptops, and at least as some of the reporters have already confirmed, the thinkpad_acpi sensors is not reading temperature correctly when the problem happens (In thermal_get_sensor(), the acpi_ec_read() returns -128.)

Do you know what doe it mean in this case? This does not sounds like a software bug to me, do you have any ideas for next steps?
Comment 61 Mark Pearson 2021-07-07 17:43:18 UTC
Hi Zhang,

I'd not come across this issue before but sounds like I need to raise it to the FW team. I don't know what the -128 means I'm afraid.

This is all referencing somewhat older platforms (from before I joined the Lenovo PC team) so I don't have any of them on hand to test against. I'll see if any of my colleagues have access to one

I saw above some people referencing FW fixes being applied to (for instance) the X270. If anybody knows exactly which FW version it was fixed with (on any platform) that would be helpful. I then can track down the release notes and maybe short cut the firmware team to the solution.

I can't promise a solution for these older platforms as they were I believe before the Linux certification program. Getting firmware updates done is always somewhat tricky and I have a fewer levers to pull...but I will see what I can do

Mark
Comment 62 Denis L. 2021-07-07 17:48:34 UTC
(In reply to Mark Pearson from comment #61)
> Hi Zhang,
> 
> I'd not come across this issue before but sounds like I need to raise it to
> the FW team. I don't know what the -128 means I'm afraid.
> 
> This is all referencing somewhat older platforms (from before I joined the
> Lenovo PC team) so I don't have any of them on hand to test against. I'll
> see if any of my colleagues have access to one
> 
> I saw above some people referencing FW fixes being applied to (for instance)
> the X270. If anybody knows exactly which FW version it was fixed with (on
> any platform) that would be helpful. I then can track down the release notes
> and maybe short cut the firmware team to the solution.
> 
> I can't promise a solution for these older platforms as they were I believe
> before the Linux certification program. Getting firmware updates done is
> always somewhat tricky and I have a fewer levers to pull...but I will see
> what I can do
> 
> Mark

Thank you Mark! Im assume, that all X1 Carbon 4th Gen has this issue, but i can assume, that MS Win hasnt this issue
Comment 63 Mark Pearson 2021-07-07 17:51:44 UTC
I would assume that's the case too. I have a feeling Windows gets the temp sensors via a different mechanism so might not be affected - but I'm guessing a lot.

<Just for my cross-reference purposes: Raised internal ticket LO-1296>
Comment 64 Denis L. 2021-07-12 12:16:47 UTC
(In reply to Mark Pearson from comment #63)
> I would assume that's the case too. I have a feeling Windows gets the temp
> sensors via a different mechanism so might not be affected - but I'm
> guessing a lot.
> 
> <Just for my cross-reference purposes: Raised internal ticket LO-1296>

Hi Mark! Are there any updates on ticket?
Comment 65 Mark Pearson 2021-07-12 12:49:04 UTC
Could someone seeing this issue please collect the output from

hexdump -C /sys/kernel/debug/ec/ec0/io

(may need to load the ec_sys module depending on distro)

And just to repost the Q from above: If anybody has a reference to when there was a FW released on a platform that fixed the issue please let me know so I hav that detail as a reference.

Thanks
Mark
Comment 66 Denis L. 2021-07-12 13:01:20 UTC
(In reply to Mark Pearson from comment #65)
> Could someone seeing this issue please collect the output from
> 
> hexdump -C /sys/kernel/debug/ec/ec0/io
> 
> (may need to load the ec_sys module depending on distro)
> 
> And just to repost the Q from above: If anybody has a reference to when
> there was a FW released on a platform that fixed the issue please let me
> know so I hav that detail as a reference.
> 
> Thanks
> Mark

Im sorry, but ec_sys module not found on Fedora 34 distro :(
Comment 67 Denis L. 2021-07-13 07:43:06 UTC
(In reply to Mark Pearson from comment #65)
> Could someone seeing this issue please collect the output from
> 
> hexdump -C /sys/kernel/debug/ec/ec0/io
> 
> (may need to load the ec_sys module depending on distro)
> 
> And just to repost the Q from above: If anybody has a reference to when
> there was a FW released on a platform that fixed the issue please let me
> know so I hav that detail as a reference.
> 
> Thanks
> Mark

Hi Mark! Im install ec_sys module and output is

# hexdump -C /sys/kernel/debug/ec/ec0/io
00000000  a6 05 a0 c2 00 86 05 00  00 08 47 00 00 09 80 00  |..........G.....|
00000010  00 00 ff ff d0 7c 00 01  7b ff 00 00 ff ff 1d 01  |.....|..{.......|
00000020  00 00 00 00 00 00 00 5b  00 00 00 00 77 00 00 80  |.......[....w...|
00000030  00 40 02 00 70 04 04 00  84 00 70 18 00 5f 00 00  |.@..p.....p.._..|
00000040  00 00 00 00 00 00 14 46  40 0c 00 00 00 00 04 00  |.......F@.......|
00000050  00 80 02 19 e5 07 07 0c  05 13 23 07 00 00 00 00  |..........#.....|
00000060  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000070  00 00 00 00 00 00 00 00  80 80 00 00 00 00 00 00  |................|
00000080  00 00 05 06 87 19 02 00  00 00 00 00 00 00 2b 00  |..............+.|
00000090  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000a0  4e 09 4e 09 ff ff 64 00  00 00 16 41 ff ff e0 00  |N.N...d....A....|
000000b0  00 00 00 00 00 00 00 00  00 00 2d 05 00 96 01 00  |..........-.....|
000000c0  00 01 00 00 00 00 00 00  01 5a 00 00 00 c6 00 00  |.........Z......|
000000d0  17 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000e0  00 00 00 00 00 00 00 00  11 80 ee 21 e4 ae 44 03  |...........!..D.|
000000f0  4e 31 46 48 54 33 35 57  1e ff 62 d1 00 00 00 00  |N1FHT35W..b.....|
00000100
Comment 68 Mark Pearson 2021-07-13 17:26:52 UTC
Perfect - thanks! I've forwarded to the FW team
Comment 69 Davide Corrado 2021-07-13 17:49:32 UTC
I'm quite sure that in the past it worked as expected, I say this because I have been owning my carbon since late 2016... I would have noticed even if I don't suspend it so much. But, since then, FW has been updated and the kernel has evolved, so it would be useful to know when this happened for the 1st time
Comment 70 Denis L. 2021-07-14 06:24:47 UTC
(In reply to Davide Corrado from comment #69)
> I'm quite sure that in the past it worked as expected, I say this because I
> have been owning my carbon since late 2016... I would have noticed even if I
> don't suspend it so much. But, since then, FW has been updated and the
> kernel has evolved, so it would be useful to know when this happened for the
> 1st time

hope the guys from Lenovo investigate this problem and solve it, otherwise my cooler will burn out :)
Comment 71 Denis L. 2021-07-19 05:25:21 UTC
(In reply to Mark Pearson from comment #68)
> Perfect - thanks! I've forwarded to the FW team

Hi Mark! Any updates?
Comment 72 Ilya 2021-08-25 11:50:26 UTC
I can reproduce this bug in nearly all of cases:

Close the lid, connect HDMI monitor, USB-Keyboard und mouse to the laptop. Start the laptop. Close the lid (needs to be closed meanwhile operating). Then send it to standby, then disconnect the equipment. Then start the laptop from standby.
Comment 73 Mark Pearson 2021-08-25 14:10:27 UTC
I've sent a nudge to the Firmware engineer who was reviewing the ec logs. I don't have any updates I'm afraid.

Mark
Comment 74 Mark Pearson 2021-09-07 16:05:33 UTC
Hi - I got an update.

Would it be possible to collect some more debug information from the EC logs please?
Same as above but need to edit offset 0x81 to be 0x60. I've done this previously using hexedit. This displays some extra registers (for a short amount of time - the register self clears)

As a note - they're a but puzzled as the fan speed from sensors doesn't match what they expected (full speed is 6950rpm). The logs will help clarify which state the system is in.

Mark
Comment 75 Denis L. 2021-09-07 16:16:40 UTC
(In reply to Mark Pearson from comment #74)
> Hi - I got an update.
> 
> Would it be possible to collect some more debug information from the EC logs
> please?
> Same as above but need to edit offset 0x81 to be 0x60. I've done this
> previously using hexedit. This displays some extra registers (for a short
> amount of time - the register self clears)
> 
> As a note - they're a but puzzled as the fan speed from sensors doesn't
> match what they expected (full speed is 6950rpm). The logs will help clarify
> which state the system is in.
> 
> Mark

Splendid! But I do not have enough skills to do this, if you show an example how to do it, I will try to do
Comment 76 Denis L. 2021-09-08 06:06:23 UTC
(In reply to Mark Pearson from comment #74)
> Hi - I got an update.
> 
> Would it be possible to collect some more debug information from the EC logs
> please?
> Same as above but need to edit offset 0x81 to be 0x60. I've done this
> previously using hexedit. This displays some extra registers (for a short
> amount of time - the register self clears)
> 
> As a note - they're a but puzzled as the fan speed from sensors doesn't
> match what they expected (full speed is 6950rpm). The logs will help clarify
> which state the system is in.
> 
> Mark

Sorry for the misunderstanding where should i change the offset?
file /sys/kernel/debug/ec/ec0/io is read-only
Comment 77 Mark Pearson 2021-09-08 12:26:49 UTC
Ah - apologies - useful instructions are important :)

When loading the ec_sys module you need to add 'write_support=1' as an argument to enable writing.

command history for my system:
   modprobe ec_sys write_support=1
   hexdump -C /sys/kernel/debug/ec/ec0/io
   hexedit -s /sys/kernel/debug/ec/ec0/io
   hexdump -C /sys/kernel/debug/ec/ec0/io

and an example dump showing offset 0x81 set

# hexdump -C /sys/kernel/debug/ec/ec0/io
00000000  e6 05 38 c6 00 86 00 00  00 08 47 00 00 03 80 00  |..8.......G.....|
00000010  00 00 ff ff d0 fd 00 19  7b ff 00 00 ff ff 1f 07  |........{.......|
00000020  10 00 00 00 00 00 00 31  00 00 00 01 26 00 00 80  |.......1....&...|
00000030  00 40 00 00 70 04 00 00  84 00 60 18 00 5f 00 00  |.@..p.....`.._..|
00000040  00 00 00 00 00 00 54 46  60 14 00 00 00 00 00 00  |......TF`.......|
00000050  00 80 02 03 00 00 00 20  2c b1 04 13 01 00 00 00  |....... ,.......|
00000060  2c b1 04 00 00 00 00 00  00 00 00 00 00 00 00 00  |,...............|
00000070  00 00 00 00 04 00 00 00  39 80 00 00 00 00 00 80  |........9.......|
00000080  00 60 05 06 ae 19 02 00  40 00 00 00 00 00 2b 00  |.`......@.....+.|
00000090  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000a0  39 80 3d 80 23 80 21 80  35 2e 39 80 37 22 80 80  |9.=.#.!.5.9.7"..|
000000b0  00 00 00 00 00 00 01 26  00 00 2d 05 00 00 00 00  |.......&..-.....|
000000c0  00 01 42 00 01 82 00 02  01 41 00 01 08 00 00 00  |..B......A......|
000000d0  1a c0 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000e0  00 00 00 00 00 00 00 00  12 20 68 24 e4 ae 44 03  |......... h$..D.|
000000f0  4e 33 32 48 54 34 32 57  2a 4a 55 12 00 00 00 00  |N32HT42W*JU.....|

Thanks!
Mark
Comment 78 Denis L. 2021-09-08 12:41:32 UTC
(In reply to Mark Pearson from comment #77)
> Ah - apologies - useful instructions are important :)
> 
> When loading the ec_sys module you need to add 'write_support=1' as an
> argument to enable writing.
> 
> command history for my system:
>    modprobe ec_sys write_support=1
>    hexdump -C /sys/kernel/debug/ec/ec0/io
>    hexedit -s /sys/kernel/debug/ec/ec0/io
>    hexdump -C /sys/kernel/debug/ec/ec0/io
> 
> and an example dump showing offset 0x81 set
> 
> # hexdump -C /sys/kernel/debug/ec/ec0/io
> 00000000  e6 05 38 c6 00 86 00 00  00 08 47 00 00 03 80 00 
> |..8.......G.....|
> 00000010  00 00 ff ff d0 fd 00 19  7b ff 00 00 ff ff 1f 07 
> |........{.......|
> 00000020  10 00 00 00 00 00 00 31  00 00 00 01 26 00 00 80 
> |.......1....&...|
> 00000030  00 40 00 00 70 04 00 00  84 00 60 18 00 5f 00 00 
> |.@..p.....`.._..|
> 00000040  00 00 00 00 00 00 54 46  60 14 00 00 00 00 00 00 
> |......TF`.......|
> 00000050  00 80 02 03 00 00 00 20  2c b1 04 13 01 00 00 00  |.......
> ,.......|
> 00000060  2c b1 04 00 00 00 00 00  00 00 00 00 00 00 00 00 
> |,...............|
> 00000070  00 00 00 00 04 00 00 00  39 80 00 00 00 00 00 80 
> |........9.......|
> 00000080  00 60 05 06 ae 19 02 00  40 00 00 00 00 00 2b 00 
> |.`......@.....+.|
> 00000090  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 
> |................|
> 000000a0  39 80 3d 80 23 80 21 80  35 2e 39 80 37 22 80 80 
> |9.=.#.!.5.9.7"..|
> 000000b0  00 00 00 00 00 00 01 26  00 00 2d 05 00 00 00 00 
> |.......&..-.....|
> 000000c0  00 01 42 00 01 82 00 02  01 41 00 01 08 00 00 00 
> |..B......A......|
> 000000d0  1a c0 00 00 00 00 00 00  00 00 00 00 00 00 00 00 
> |................|
> 000000e0  00 00 00 00 00 00 00 00  12 20 68 24 e4 ae 44 03  |.........
> h$..D.|
> 000000f0  4e 33 32 48 54 34 32 57  2a 4a 55 12 00 00 00 00 
> |N32HT42W*JU.....|
> 
> Thanks!
> Mark

Thank you, Mark!
Done
Before
# hexdump -C /sys/kernel/debug/ec/ec0/io
00000000  a6 05 a0 c2 00 86 05 00  00 08 47 00 00 09 80 00  |..........G.....|
00000010  00 00 ff ff d0 7c 00 01  7b ff 00 00 ff ff 1d 01  |.....|..{.......|
00000020  00 00 00 00 00 00 00 9a  00 00 00 00 41 00 00 80  |............A...|
00000030  00 40 02 00 70 04 00 00  84 00 70 18 00 5f 00 00  |.@..p.....p.._..|
00000040  00 00 00 00 00 00 14 46  40 04 00 00 00 00 00 00  |.......F@.......|
00000050  00 80 02 19 e5 07 09 01  07 24 3a 07 00 00 00 00  |.........$:.....|
00000060  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000070  00 00 00 00 00 00 00 00  80 80 00 00 00 00 00 00  |................|
00000080  00 00 05 06 29 18 02 00  00 00 00 00 00 00 2b 00  |....).........+.|
00000090  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000a0  1b 05 1b 05 ff ff 64 00  00 00 2d 41 ff ff e0 00  |......d...-A....|
000000b0  00 00 00 00 00 00 00 00  00 00 2d 05 00 96 01 00  |..........-.....|
000000c0  00 01 00 00 00 00 00 00  01 5a 00 00 00 89 00 00  |.........Z......|
000000d0  17 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000e0  00 00 00 00 00 00 00 00  11 80 ee 21 e4 ae 44 03  |...........!..D.|
000000f0  4e 31 46 48 54 33 35 57  1e ff 62 d1 00 00 00 00  |N1FHT35W..b.....|
00000100
# hexedit -s /sys/kernel/debug/ec/ec0/io
After
# hexdump -C /sys/kernel/debug/ec/ec0/io
00000000  a6 05 a0 c2 00 86 05 00  00 08 47 00 00 09 80 00  |..........G.....|
00000010  00 00 ff ff d0 7c 00 01  7b ff 00 00 ff ff 1d 01  |.....|..{.......|
00000020  00 00 00 00 00 00 00 16  00 00 00 00 41 00 00 80  |............A...|
00000030  00 40 02 00 70 04 00 00  84 00 70 18 00 5f 00 00  |.@..p.....p.._..|
00000040  00 00 00 00 00 00 14 46  40 04 00 00 00 00 00 00  |.......F@.......|
00000050  00 80 02 19 e5 07 09 01  07 24 3a 07 00 00 00 00  |.........$:.....|
00000060  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000070  00 00 00 00 00 00 00 00  80 80 00 00 00 00 00 00  |................|
00000080  00 60 05 06 36 18 02 00  00 00 00 00 00 00 2b 00  |.`..6.........+.|
00000090  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000a0  80 1d 21 80 1d 80 1c 80  1e 1f 1c 20 1e 1f 80 80  |..!........ ....|
000000b0  00 00 00 00 00 00 00 00  00 00 2d 05 00 96 01 00  |..........-.....|
000000c0  00 01 00 00 00 00 00 00  01 5a 00 00 00 73 00 00  |.........Z...s..|
000000d0  17 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000e0  00 00 00 00 00 00 00 00  11 80 ee 21 e4 ae 44 03  |...........!..D.|
000000f0  4e 31 46 48 54 33 35 57  1e ff 62 d1 00 00 00 00  |N1FHT35W..b.....|
00000100
Comment 79 Mark Pearson 2021-09-08 18:14:42 UTC
Perfect - thanks!
Comment 80 Mark Pearson 2021-09-09 12:26:33 UTC
Sorry - another log request from the firmware team. Can I also get an ec dump when the issue isn't happening (fans are normal). They would like it for comparison.
It seems like the issue may be related to incorrect temperature reporting

Thanks!
Mark
Comment 81 Denis L. 2021-09-09 12:48:53 UTC
(In reply to Mark Pearson from comment #80)
> Sorry - another log request from the firmware team. Can I also get an ec
> dump when the issue isn't happening (fans are normal). They would like it
> for comparison.
> It seems like the issue may be related to incorrect temperature reporting
> 
> Thanks!
> Mark

Hi Mark!
After full power down i have this
# hexdump -C /sys/kernel/debug/ec/ec0/io
00000000  a6 05 a0 c2 00 86 00 00  00 08 47 00 00 09 80 00  |..........G.....|
00000010  00 00 ff ff d0 7c 00 01  7b ff 00 00 ff ff 1d 01  |.....|..{.......|
00000020  00 00 00 00 00 00 00 00  00 00 00 00 41 00 00 80  |............A...|
00000030  00 40 00 00 70 04 00 00  84 00 70 18 00 5f 00 00  |.@..p.....p.._..|
00000040  00 00 00 00 00 00 14 46  40 14 00 00 00 00 00 00  |.......F@.......|
00000050  00 80 02 19 e5 07 09 09  0c 2b 16 07 00 00 00 00  |.........+......|
00000060  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000070  00 00 00 00 00 00 00 00  2b 80 00 00 00 00 00 00  |........+.......|
00000080  00 00 05 06 69 0c 02 00  00 00 00 00 00 00 2b 00  |....i.........+.|
00000090  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000a0  19 05 19 05 ff ff 64 00  00 00 30 41 ff ff e0 00  |......d...0A....|
000000b0  00 00 00 00 00 00 00 00  00 00 2d 05 00 96 01 00  |..........-.....|
000000c0  00 01 00 00 00 00 00 00  01 5a 00 00 00 70 00 00  |.........Z...p..|
000000d0  17 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000e0  00 00 00 00 00 00 00 00  11 80 ee 21 e4 ae 44 03  |...........!..D.|
000000f0  4e 31 46 48 54 33 35 57  1e ff 62 d1 00 00 00 00  |N1FHT35W..b.....|
00000100

change offset
# hexedit -s /sys/kernel/debug/ec/ec0/io

after
# hexdump -C /sys/kernel/debug/ec/ec0/io
00000000  a6 05 a0 c2 00 86 00 00  00 08 47 00 00 09 80 00  |..........G.....|
00000010  00 00 ff ff d0 7c 00 01  7b ff 00 00 ff ff 1d 01  |.....|..{.......|
00000020  00 00 00 00 00 00 00 ee  00 00 00 00 41 00 00 80  |............A...|
00000030  00 40 00 00 70 04 00 00  84 00 70 18 00 5f 00 00  |.@..p.....p.._..|
00000040  00 00 00 00 00 00 14 46  40 14 00 00 00 00 00 00  |.......F@.......|
00000050  00 80 02 19 e5 07 09 09  0c 2b 16 07 00 00 00 00  |.........+......|
00000060  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000070  00 00 00 00 00 00 00 00  25 80 00 00 00 00 00 00  |........%.......|
00000080  00 60 05 06 00 00 02 00  00 00 00 00 00 00 2b 00  |.`............+.|
00000090  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000a0  25 1d 22 80 1b 80 1b 80  20 21 1d 22 20 20 80 80  |%."..... !."  ..|
000000b0  00 00 00 00 00 00 00 00  00 00 2d 05 00 96 01 00  |..........-.....|
000000c0  00 01 00 00 00 00 00 00  01 5a 00 00 00 68 00 00  |.........Z...h..|
000000d0  17 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000e0  00 00 00 00 00 00 00 00  11 80 ee 21 e4 ae 44 03  |...........!..D.|
000000f0  4e 31 46 48 54 33 35 57  1e ff 62 d1 00 00 00 00  |N1FHT35W..b.....|
00000100
Comment 82 Mark Pearson 2021-09-17 14:50:08 UTC
I think I need a brave guinea-pig :)

I have a test EC firmware to try out, but we're having trouble tracking down an X1C4 to test on, and even if we do find it I'd like to confirm the details on a system that someone is seeing the problem on (and has experience seeing the problem).

If someone is interested - please email me (markpearson at lenovo.com) and I'll share details. I can't post the trial firmware publicly.

The exercise will involve installing the EC firmware from a USB key, reproducing the issue, and then setting some EC registers (which I believe we can do via the ec_sys kernel module) to confirm the problem can be cleared.

I am going to see if we can borrow a system from the Windows team and run the steps ourselves first as a sanity check - but if anybody reads this and thinks "hell yeah that sounds like fun" then (after seeking medical attention) let me know.

Mark
Comment 83 Ilya 2021-09-18 11:36:07 UTC
Created attachment 298871 [details]
ec0 dump with bug triggered
Comment 84 Ilya 2021-09-18 11:49:19 UTC
Created attachment 298873 [details]
ec0 dump without a bug
Comment 85 Ilya 2021-09-18 11:56:12 UTC
I have the same bug on T470s, dumps are above
Comment 86 Ilya 2021-09-18 14:49:31 UTC
Because I changed kernel a little time ago, Im not sure about dumps, if they are from the same kernel. Just now the bug ocurred again. So, two dumps: one with fan at full speed:

00000000  a6 05 a0 c4 00 86 05 00  00 08 47 00 00 41 80 00  |..........G..A..|
00000010  00 00 ff ff f0 bc 00 09  7b ff 00 00 ff ff 5d 01  |........{.....].|
00000020  00 00 00 00 46 46 00 a6  00 00 00 00 67 00 6f 80  |....FF......g.o.|
00000030  00 40 02 00 70 04 04 00  c3 83 20 18 00 5f 00 00  |.@..p..... .._..|
00000040  00 00 00 00 00 00 04 04  40 10 01 00 00 00 04 00  |........@.......|
00000050  00 80 02 03 00 00 00 20  01 00 00 00 00 00 02 01  |....... ........|
00000060  00 02 00 01 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000070  00 00 00 00 04 00 00 00  80 80 00 00 00 00 00 00  |................|
00000080  00 10 05 06 5c 11 02 00  00 00 00 00 00 00 2b 00  |....\.........+.|
00000090  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000a0  02 06 ae 08 b2 00 45 00  00 00 e0 2d ff ff c0 00  |......E....-....|
000000b0  28 46 28 46 00 00 00 00  00 00 2d 05 00 96 01 00  |(F(F......-.....|
000000c0  00 00 00 00 00 00 00 00  00 00 00 08 00 00 80 00  |................|
000000d0  17 c0 c0 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000e0  00 00 00 00 00 00 00 00  11 80 fb 22 e4 ae 44 03  |..........."..D.|
000000f0  4e 31 57 48 54 33 36 57  23 53 82 fa 00 00 00 00  |N1WHT36W#S......|


other: after suspending to ram and resuming. fan speed normal (zero).


00000000  a6 05 a0 c4 00 86 05 00  00 08 47 00 00 01 80 00  |..........G.....|
00000010  00 00 ff ff f0 bc 00 09  7b ff 00 00 ff ff 5d 01  |........{.....].|
00000020  00 00 00 00 46 46 00 7e  00 00 00 00 67 00 6f 80  |....FF.~....g.o.|
00000030  00 40 02 00 70 04 04 00  c3 83 20 18 00 5f 00 00  |.@..p..... .._..|
00000040  00 00 00 00 00 00 04 04  40 00 01 00 00 00 04 00  |........@.......|
00000050  00 80 02 03 00 00 00 20  01 00 00 00 00 00 02 01  |....... ........|
00000060  00 02 00 01 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000070  00 00 00 00 04 00 00 00  1b 80 00 00 00 00 00 00  |................|
00000080  00 10 05 06 00 00 02 00  00 00 00 00 00 00 2b 00  |..............+.|
00000090  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000a0  02 06 ae 08 11 01 45 00  00 00 e0 2d ff ff c0 00  |......E....-....|
000000b0  28 46 28 46 00 00 00 00  00 00 2d 05 00 96 01 00  |(F(F......-.....|
000000c0  00 00 00 00 00 00 00 00  00 00 00 08 00 00 80 00  |................|
000000d0  17 c0 c0 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000e0  00 00 00 00 00 00 00 00  11 80 fb 22 e4 ae 44 03  |..........."..D.|
000000f0  4e 31 57 48 54 33 36 57  23 53 82 fa 00 00 00 00  |N1WHT36W#S......|
Comment 87 Denis L. 2021-09-20 13:01:53 UTC
(In reply to Mark Pearson from comment #82)
> I think I need a brave guinea-pig :)
> 
> I have a test EC firmware to try out, but we're having trouble tracking down
> an X1C4 to test on, and even if we do find it I'd like to confirm the
> details on a system that someone is seeing the problem on (and has
> experience seeing the problem).
> 
> If someone is interested - please email me (markpearson at lenovo.com) and
> I'll share details. I can't post the trial firmware publicly.
> 
> The exercise will involve installing the EC firmware from a USB key,
> reproducing the issue, and then setting some EC registers (which I believe
> we can do via the ec_sys kernel module) to confirm the problem can be
> cleared.
> 
> I am going to see if we can borrow a system from the Windows team and run
> the steps ourselves first as a sanity check - but if anybody reads this and
> thinks "hell yeah that sounds like fun" then (after seeking medical
> attention) let me know.
> 
> Mark

Hi Mark! I send you email, check please :)
Comment 88 cfr 2021-10-04 15:31:59 UTC
This bug has reappeared on X270 with the 5.14 kernel. After updating my firmware, I had no problems until I upgraded my system yesterday, when I changed from a 5.13 kernel to 5.14. It is the same as before: after sleeping (suspending to RAM), the temperature gets stuck at 48, the fan runs continuously at 6000+ RPM and only powering off (as opposed to rebooting) resolves the issue.

Specifically, I'm seeing the issue with the following kernel: 5.14.8-arch1-1 #1 SMP PREEMPT Sun, 26 Sep 2021 19:36:15 +0000 x86_64 GNU/Linux.

I would be happy to help troubleshoot this, but I don't have an X1C4. If there's some way I could help with an X270, though, I'd be very willing (provided it doesn't risk bricking my laptop).
(In reply to Mark Pearson from comment #61)
> Hi Zhang,
> 
> I'd not come across this issue before but sounds like I need to raise it to
> the FW team. I don't know what the -128 means I'm afraid.
> 
> This is all referencing somewhat older platforms (from before I joined the
> Lenovo PC team) so I don't have any of them on hand to test against. I'll
> see if any of my colleagues have access to one
> 
> I saw above some people referencing FW fixes being applied to (for instance)
> the X270. If anybody knows exactly which FW version it was fixed with (on
> any platform) that would be helpful. I then can track down the release notes
> and maybe short cut the firmware team to the solution.
> 
> I can't promise a solution for these older platforms as they were I believe
> before the Linux certification program. Getting firmware updates done is
> always somewhat tricky and I have a fewer levers to pull...but I will see
> what I can do
> 
> Mark

This is the history of firmware updates on my X270. However, note that the bug has now resurfaced with the 5.14 kernel so the firmware updates seem to have provided only a temporary fix for me.

20HNCTO1WW
│
├─Embedded Controller:
│ │   Device ID:          4144f261efb14c45aa79a27b4c4d3bf228f6cdb9
│ │   Previous version:   0.1.12
│ │   Update State:       Success
│ │   Last modified:      2021-03-17 03:56
│ │   GUID:               18dfeb28-b8a4-4cec-97ce-b0599416a13e
│ │   Device Flags:       • Internal device
│ │                       • Updatable
│ │                       • System requires external power source
│ │                       • Supported on remote server
│ │                       • Needs a reboot after installation
│ │                       • Reported to remote server
│ │                       • Device is usable for the duration of the update
│ │ 
│ └─  New version:      0.1.17
│       Remote ID:        lvfs
│       Licence:          Unknown
│     
├─Intel Management Engine:
│ │   Device ID:          fe94af9d9355fcfc0cabeffc6ae8695564bec6f3
│ │   Previous version:   182.29.3287
│ │   Update State:       Success
│ │   Last modified:      2021-03-17 03:56
│ │   GUID:               b7895f97-9624-42b0-8ea4-8600e242e79b
│ │   Device Flags:       • Internal device
│ │                       • Updatable
│ │                       • System requires external power source
│ │                       • Supported on remote server
│ │                       • Needs a reboot after installation
│ │                       • Reported to remote server
│ │                       • Device is usable for the duration of the update
│ │ 
│ └─  New version:      184.77.3664
│       Remote ID:        lvfs
│       Licence:          Unknown
│     
└─System Firmware:
  │   Device ID:          8c997bbd20dfdf9c471aaae577d182d9ae77bca7
  │   Previous version:   0.1.20
  │   Update State:       Success
  │   Last modified:      2021-03-17 03:56
  │   GUID:               14cc970e-c105-4eba-a704-448dde9de64d
  │   Device Flags:       • Internal device
  │                       • Updatable
  │                       • System requires external power source
  │                       • Supported on remote server
  │                       • Needs a reboot after installation
  │                       • Reported to remote server
  │                       • Cryptographic hash verification is available
  │                       • Device is usable for the duration of the update
  │ 
  └─  New version:      0.1.39
        Remote ID:        lvfs
        Licence:          Unknown

Prior to that, the firmware had never been updated on this machine and I have not touched it since. It really seems as if there's some combination of kernel and firmware which triggers the issue on the X270, but I'm sure it is really more complicated than that!
Comment 89 cfr 2021-10-04 15:37:56 UTC
(In reply to Omar from comment #24)
> (In reply to cfr from comment #23)
> > On my machine (X270), a firmware update seems to have resolved the issue.
> > That is, the thermal sensor is no longer gets stuck and the fan behaves
> much
> > as it always did. This is even with the 5.11.* kernels after sleep. So, in
> > my case, the kernels seem to have triggered an underlying firmware bug
> which
> > didn't cause any symptoms with earlier kernels (3+ years' worth).
> > 
> > I don't know if this is helpful. If you still want any data from me, let me
> > know. I'm assuming not since I'm not seeing the issue any longer..
> 
> 
> May I ask what firmware are you referring to? Is it the BIOS or something
> else?

Sorry for the absurdly late response but, in case you still wish to know, yes, I meant the BIOS. However, it doesn't seem to have been a permanent fix.
Comment 90 cfr 2021-10-04 15:58:12 UTC
... but the issue is no longer as consistent for me. I tried to reproduce to get acpidumps, for example, but suspending didn't cause a problem this time. I will get the dump when it happens again. I can also try updating the firmware again, although there's nothing obviously about temperature sensors in the available updates this time.
Comment 91 Mark Pearson 2021-10-04 16:35:47 UTC
Just as a note - we're still trying to track down an X1C4 internally we can play with...surprisingly hard to find. 
I decided I'm not hugely comfortable sharing a test BIOS and instructions without having tried it withour team....I've bricked too many systems that way and it just makes me nervous to put a customer through that. This thread isn't forgotten.
Comment 92 cfr 2021-10-04 21:55:53 UTC
I got acpidump before and after the bug is triggered, though the files appear to be identical (to diff).
Comment 93 cfr 2021-10-04 21:57:15 UTC
Created attachment 299093 [details]
acpidump when things are normal
Comment 94 cfr 2021-10-04 21:57:49 UTC
Created attachment 299095 [details]
acpidump with bug active
Comment 95 kristaps 2021-11-13 18:40:00 UTC
Same problem on X260 with kernel 5.14.16-301.fc35.x86_64, BIOS R02ET73W (1.46)

Would like to add my observation.

The temperature interface /sys/devices/platform/thinkpad_hwmon/hwmon/hwmon4/temp1_input is there, but returns an error:

# cat /sys/devices/platform/thinkpad_hwmon/hwmon/hwmon4/name
thinkpad
# cat /sys/devices/platform/thinkpad_hwmon/hwmon/hwmon4/temp1_label
CPU
# cat /sys/devices/platform/thinkpad_hwmon/hwmon/hwmon4/temp1_input
cat: temp1_input: No such device or address

The node temp1_input is visible with ls, just returns error when reading with cat.

After full shutdown and boot the fans get back to normal and the temperature is readable:

# cat /sys/devices/platform/thinkpad_hwmon/hwmon/hwmon4/temp1_input
43000

Been using this laptop for years, and this wasn't an issue with older kernels.

In my case the issue only happens when the laptop is sleeping without power supply attached, but not always.
Comment 96 Xian Wang 2021-11-17 06:46:48 UTC
(In reply to Mark Pearson from comment #91)
> Just as a note - we're still trying to track down an X1C4 internally we can
> play with...surprisingly hard to find. 
> I decided I'm not hugely comfortable sharing a test BIOS and instructions
> without having tried it withour team....I've bricked too many systems that
> way and it just makes me nervous to put a customer through that. This thread
> isn't forgotten.
Comment 97 Blanche Schaefer 2021-11-26 21:31:25 UTC
I started facing same problem on lenovo yoga since linux 5.15
Comment 98 ChriS 2021-12-04 14:52:55 UTC
I had the same problem on a Thinkpad X1 Carbon (5th gen), kernel 5.15.0-2-amd64 on Debian: the fan was *always* at high speed when resuming from suspend.  I just upgraded¹ the firmware to version 1.53 and, at least, the last 2 suspends (on battery) did not trigger the problem.

¹ https://math.umons.ac.be/anum/X1Carbon/#fan
Comment 99 Tufan 2021-12-05 09:09:00 UTC
I had the same behaviour on Thinkpad X260 with kernel 5.15.6-200.fc35.x86_64 and BIOS R02ET74W (1.46). If I close the lid or suspend the PC, after wake up fans are blowing forever.
Comment 100 Blanche Schaefer 2021-12-28 22:58:17 UTC
I have latest BIOS for my model from October this year so there is nothing to update. The fact it started happening only after kernel upgrade suggests regression on kernel side not faulty BIOS.

It's 100% reproucible after suspend/resume on AC while unplugging cable then suspend/resume fixes it.

acpitz-acpi-0 is stuck at +48.0°C when it occurs.
Comment 101 Blanche Schaefer 2021-12-28 23:31:16 UTC
Booting with "acpi.ec_freeze_events=N acpi.ec_suspend_yield=Y" seems to workaround the problem.
Comment 102 Davide Corrado 2021-12-29 11:56:40 UTC
(In reply to Blanche Schaefer from comment #101)
> Booting with "acpi.ec_freeze_events=N acpi.ec_suspend_yield=Y" seems to
> workaround the problem.

HELL YEAH!
I do confirm that this workaround fan works as expected.

I suspected it was related to a regression in kernel code too, I have been using my laptop since 2017 and I didn't notice it happening in the past.
Comment 103 Denis L. 2021-12-29 12:08:32 UTC
(In reply to Davide Corrado from comment #102)
> (In reply to Blanche Schaefer from comment #101)
> > Booting with "acpi.ec_freeze_events=N acpi.ec_suspend_yield=Y" seems to
> > workaround the problem.
> 
> HELL YEAH!
> I do confirm that this workaround fan works as expected.
> 
> I suspected it was related to a regression in kernel code too, I have been
> using my laptop since 2017 and I didn't notice it happening in the past.

this fix not helped for me on X1C4 BIOS 1.51
Comment 104 Davide Corrado 2021-12-29 13:10:08 UTC
Created attachment 300181 [details]
attachment-3962-0.html

I own the same laptop with the same bios. Are you sure???

Il Mer 29 Dic 2021, 13:08 <bugzilla-daemon@bugzilla.kernel.org> ha scritto:

> https://bugzilla.kernel.org/show_bug.cgi?id=211313
>
> --- Comment #103 from Denis L. (dlotarev@yahoo.com) ---
> (In reply to Davide Corrado from comment #102)
> > (In reply to Blanche Schaefer from comment #101)
> > > Booting with "acpi.ec_freeze_events=N acpi.ec_suspend_yield=Y" seems to
> > > workaround the problem.
> >
> > HELL YEAH!
> > I do confirm that this workaround fan works as expected.
> >
> > I suspected it was related to a regression in kernel code too, I have
> been
> > using my laptop since 2017 and I didn't notice it happening in the past.
>
> this fix not helped for me on X1C4 BIOS 1.51
>
> --
> You may reply to this email to add a comment.
>
> You are receiving this mail because:
> You are on the CC list for the bug.
Comment 105 Blanche Schaefer 2021-12-29 13:24:53 UTC
Looking closer at those parameters it seems that "acpi.ec_freeze_events=N" is the default[1] and "acpi.ec_suspend_yield" parameter was never added to mainline (it was only part of some preliminary patchset[2]).

So my comment above was wrong and the fact problem disappeared for a while was a pure coincidence that could be related to multiple reboots in short period.

Now I'm testing "acpi.ec_freeze_events=Y" which again seem to workaround the problem however I can't be sure.

[1] You may check /sys/module/acpi/parameters/ec_freeze_events for current value.
[2] https://bugzilla.kernel.org/attachment.cgi?id=256927
Comment 106 Davide Corrado 2021-12-29 14:07:10 UTC
i tried 4, 5 times with "acpi.ec_freeze_events=N acpi.ec_suspend_yield=Y" and it seemed to work
Comment 107 Denis L. 2021-12-30 07:33:48 UTC
(In reply to Davide Corrado from comment #106)
> i tried 4, 5 times with "acpi.ec_freeze_events=N acpi.ec_suspend_yield=Y"
> and it seemed to work

im tried twice, and no luck,
kernel params

[    0.000000] Command line: BOOT_IMAGE=(lvmid/dAILBd-Addc-AjZB-307N-8pAr-xd4e-XT38b8/ODteSF-NONj-J7Ao-rPX1-fPN0-hOI5-VydKU1)/vmlinuz-5.15.7-100.fc34.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root 
rd.lvm.lv=fedora/home rd.lvm.lv=fedora/boot rhgb quiet acpi.ec_freeze_events=N acpi.ec_suspend_yield=Y elevator=noop intel_pstate=enable acpi_osi=!Windows 2012

and after sleep sensors showing 
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +40.0°C  

thinkpad-isa-0000
Adapter: ISA adapter
fan1:        6912 RPM
CPU:              N/A  
GPU:              N/A  
temp3:         +0.0°C  
temp4:         +0.0°C  
temp5:         +0.0°C  
temp6:         +0.0°C  
temp7:         +0.0°C  
temp8:         +0.0°C  

BAT0-acpi-0
Adapter: ACPI interface
in0:          16.38 V  

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +41.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +39.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +38.0°C  (high = +100.0°C, crit = +100.0°C)

pch_skylake-virtual-0
Adapter: Virtual device
temp1:        +37.5°C  

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +48.0°C  (crit = +128.0°C)
Comment 108 Denis L. 2021-12-30 07:40:34 UTC
after testing acpi.ec_freeze_events=Y or acpi.ec_freeze_events=N no luck and sensors after sleep showing N/A in CPU

CPU:              N/A
Comment 109 Peter Stein 2022-01-01 17:56:35 UTC
Hi

T460, same behavior, wake up from suspend works on AC, fan blowing on battery

Linux version 5.11.0-43-generic (buildd@lcy02-amd64-036) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #47~20.04.2-Ubuntu SMP Mon Dec 13 11:06:56 UTC 2021

I'm using the current/latest firmware:
UEFI BIOS R06ET69W (1.43), 
UEFI BIOS Date 2020-01-08. 

No improvement with proposed work-around (testing acpi.ec_freeze_events=Y or acpi.ec_freeze_events=N).

I'm provided instructions I'm ready to help (including potentially risky firmware tests).
Comment 110 Mark Pearson 2022-01-07 19:47:09 UTC
Interesting.

We tracked down a X1C4 and reproduced the issue (and confirmed it was fixed by the trial BIOS). But getting them to actually release it is proving challenging

I'll go and chase down what was happening - some folk on my team in China were looking after the details and I lost track of this with the carnage that is December...
Comment 111 Denis L. 2022-01-07 20:36:37 UTC
(In reply to Mark Pearson from comment #110)
> Interesting.
> 
> We tracked down a X1C4 and reproduced the issue (and confirmed it was fixed
> by the trial BIOS). But getting them to actually release it is proving
> challenging
> 
> I'll go and chase down what was happening - some folk on my team in China
> were looking after the details and I lost track of this with the carnage
> that is December...

Amazing! Splendid! Thank you Lenovo DevTeam and Mark! You are the best!
We are waiting for the fix :) and with the coming holidays
Comment 112 Ilya 2022-01-08 11:14:12 UTC
(In reply to Mark Pearson from comment #110)
> Interesting.
> 
> We tracked down a X1C4 and reproduced the issue (and confirmed it was fixed
> by the trial BIOS). But getting them to actually release it is proving
> challenging
> 
> I'll go and chase down what was happening - some folk on my team in China
> were looking after the details and I lost track of this with the carnage
> that is December...

Wow. Will this work for T470s too?

BTW, I have other, perhaps related, bug. Very seldom, but still appearing sometimes. This one is dangerous, because the sensor of a fan reports full speed meanwhile the fan doesnt rotate. So, the temperature of CPU could be raised.

$:~/tmp$ hexdump -C sensors_io.bug 
00000000  a6 05 a0 c4 00 86 05 00  00 08 47 00 00 01 80 40  |..........G....@|
00000010  00 00 ff ff f0 bc 00 09  7b ff 00 00 ff ff 5d 01  |........{.....].|
00000020  00 00 00 00 46 46 00 93  00 00 00 00 68 00 68 80  |....FF......h.h.|
00000030  00 40 02 00 70 14 00 00  c3 83 20 18 00 5f 00 00  |.@..p..... .._..|
00000040  00 00 00 00 00 00 04 04  40 08 01 00 00 00 00 00  |........@.......|
00000050  00 80 02 03 00 00 00 20  01 00 00 00 00 00 02 01  |....... ........|
00000060  00 02 00 01 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000070  00 00 00 00 04 00 00 00  35 80 00 00 00 00 00 00  |........5.......|
00000080  00 10 05 06 ff ff 02 00  00 00 00 00 00 00 2b 00  |..............+.|
00000090  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000a0  ac 05 2a 08 56 00 45 00  00 00 99 2e ff ff c0 00  |..*.V.E.........|
000000b0  28 46 28 46 00 00 00 00  00 00 2d 05 00 96 01 00  |(F(F......-.....|
000000c0  00 00 00 00 00 00 00 00  00 00 00 08 00 00 80 00  |................|
000000d0  17 c0 c0 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000e0  00 00 00 00 00 00 00 00  11 80 fb 22 e4 ae 44 03  |..........."..D.|
000000f0  4e 31 57 48 54 33 36 57  23 53 82 fa 00 00 00 00  |N1WHT36W#S......|
00000100
$:~/tmp$ cat sensors.bug 
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +56.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +56.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +55.0°C  (high = +100.0°C, crit = +100.0°C)

pch_skylake-virtual-0
Adapter: Virtual device
temp1:        +45.5°C  

BAT0-acpi-0
Adapter: ACPI interface
in0:          10.95 V  

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +28.0°C  

thinkpad-isa-0000
Adapter: ISA adapter
fan1:        65535 RPM
temp1:        +51.0°C  
temp2:            N/A  
temp3:         +0.0°C  
temp4:         +0.0°C  
temp5:         +0.0°C  
temp6:         +0.0°C  
temp7:         +0.0°C  
temp8:         +0.0°C  

BAT1-acpi-0
Adapter: ACPI interface
in0:          11.93 V  

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +51.0°C  (crit = +128.0°C)
Comment 113 Blanche Schaefer 2022-01-08 18:45:00 UTC
(In reply to Mark Pearson from comment #110)
> Interesting.
> 
> We tracked down a X1C4 and reproduced the issue (and confirmed it was fixed
> by the trial BIOS). But getting them to actually release it is proving
> challenging
> 
> I'll go and chase down what was happening - some folk on my team in China
> were looking after the details and I lost track of this with the carnage
> that is December...

I would appreciate if similar BIOS update could be made for Yoga 370.
Comment 114 Tufan 2022-01-08 19:02:51 UTC
(In reply to Mark Pearson from comment #110)
> Interesting.
> 
> We tracked down a X1C4 and reproduced the issue (and confirmed it was fixed
> by the trial BIOS). But getting them to actually release it is proving
> challenging
> 
> I'll go and chase down what was happening - some folk on my team in China
> were looking after the details and I lost track of this with the carnage
> that is December...

As I and others mentioned that the same problem is exist on X260 laptops, it would be great to have a BIOS update to fix it.
Comment 115 abrouwers 2022-01-31 16:05:38 UTC
(In reply to Mark Pearson from comment #110)
> Interesting.
> 
> We tracked down a X1C4 and reproduced the issue (and confirmed it was fixed
> by the trial BIOS). But getting them to actually release it is proving
> challenging
> 
> I'll go and chase down what was happening - some folk on my team in China
> were looking after the details and I lost track of this with the carnage
> that is December...

That's great news, coming from an x1c4 user.  Any update on the firmware, or even an unofficial version that can be tested?
Comment 116 Luke 2022-02-01 11:05:48 UTC
> We tracked down a X1C4 and reproduced the issue (and confirmed it was fixed
> by the trial BIOS). But getting them to actually release it is proving
> challenging
>
> I'll go and chase down what was happening - some folk on my team in China
> were looking after the details and I lost track of this with the carnage that
> is December...

Awesome! It seems a lot more models are affected, any chance of getting this fix for other models? I'm personally hit by this on X260. I can do some testing if needed.
Comment 117 Julian Ruess 2022-02-01 13:46:22 UTC
Hi,

I have the same problem with my T460.

Manjaro with Kernel 5.16.2-1 seems to solve the problem.
Comment 118 Jackie Dong 2022-02-08 01:56:37 UTC
(In reply to permaer from comment #0)
> Device: Lenovo Thinkpad X1 Carbon, 4th gen.
> 
> After resuming the laptop from standby, around 1/3 (33%) of the time the
> fans start running at max and don't auto correct. I need to put the system
> in standby for the problem to reset (sometimes I need multiple tries).
> acpitz-acpi-0 gets stuck at 48 degrees C after resuming and fan keeps
> blowing as a result. I'm running kernel 5.10.7 (Manjaro).
> 
> This bug seems to be a duplicate of bug #191181, which seems to have been
> fixed for many Thinkpad hardware configs, but apparently not for mine.
> Another user there also reports the problem still persists on a Thinkpad
> T470s, hopefully they can drop their experience in this bug report as well.

Hi Permaer,
   Lenovo has released new BIOS to fix this issue, you can update it.

BIOS n1fuj45w.zip (include BIOS N1FET78W, EC N1FHT36W) fixed this issue has been released on Lenovo support web.

https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x1-carbon-type-20fb-20fc/downloads/ds111756-bios-update-utility-bootable-cd-for-windows-10-64-bit-81-64-bit-7-64-bit-32-bit-linux-thinkpad-x1-carbon-type-20fb-20fc-x1-yoga-types-20fq-20fr

   Thanks
Comment 119 Denis L. 2022-02-08 06:52:13 UTC
(In reply to Jackie Dong from comment #118)
> (In reply to permaer from comment #0)
> > Device: Lenovo Thinkpad X1 Carbon, 4th gen.
> > 
> > After resuming the laptop from standby, around 1/3 (33%) of the time the
> > fans start running at max and don't auto correct. I need to put the system
> > in standby for the problem to reset (sometimes I need multiple tries).
> > acpitz-acpi-0 gets stuck at 48 degrees C after resuming and fan keeps
> > blowing as a result. I'm running kernel 5.10.7 (Manjaro).
> > 
> > This bug seems to be a duplicate of bug #191181, which seems to have been
> > fixed for many Thinkpad hardware configs, but apparently not for mine.
> > Another user there also reports the problem still persists on a Thinkpad
> > T470s, hopefully they can drop their experience in this bug report as well.
> 
> Hi Permaer,
>    Lenovo has released new BIOS to fix this issue, you can update it.
> 
> BIOS n1fuj45w.zip (include BIOS N1FET78W, EC N1FHT36W) fixed this issue has
> been released on Lenovo support web.
> 
> https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-
> series-laptops/thinkpad-x1-carbon-type-20fb-20fc/downloads/ds111756-bios-
> update-utility-bootable-cd-for-windows-10-64-bit-81-64-bit-7-64-bit-32-bit-
> linux-thinkpad-x1-carbon-type-20fb-20fc-x1-yoga-types-20fq-20fr
> 
>    Thanks

Yes, i can approve this. Problem solved!

Thanks Lenovo Team!
Comment 120 Davide Corrado 2022-02-08 15:07:40 UTC
great work! thank you very much lenovo
Comment 121 Blanche Schaefer 2022-02-08 16:15:08 UTC
(In reply to Jackie Dong from comment #118)
> Hi Permaer,
>    Lenovo has released new BIOS to fix this issue, you can update it.
> 
> BIOS n1fuj45w.zip (include BIOS N1FET78W, EC N1FHT36W) fixed this issue has
> been released on Lenovo support web.
> 
> https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-
> series-laptops/thinkpad-x1-carbon-type-20fb-20fc/downloads/ds111756-bios-
> update-utility-bootable-cd-for-windows-10-64-bit-81-64-bit-7-64-bit-32-bit-
> linux-thinkpad-x1-carbon-type-20fb-20fc-x1-yoga-types-20fq-20fr
> 
>    Thanks

That's great to hear. Is there a chance for similar updates for other models, like Yoga 370?
Comment 122 permaer 2022-02-08 16:21:44 UTC
(In reply to Jackie Dong from comment #118)
> Hi Permaer,
>    Lenovo has released new BIOS to fix this issue, you can update it.
> 
> BIOS n1fuj45w.zip (include BIOS N1FET78W, EC N1FHT36W) fixed this issue has
> been released on Lenovo support web.
> 
> https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-
> series-laptops/thinkpad-x1-carbon-type-20fb-20fc/downloads/ds111756-bios-
> update-utility-bootable-cd-for-windows-10-64-bit-81-64-bit-7-64-bit-32-bit-
> linux-thinkpad-x1-carbon-type-20fb-20fc-x1-yoga-types-20fq-20fr
> 
>    Thanks

Thanks Jackie and Lenovo team, the fix works great! I will mark this as closed. Hopefully a fix can be made for the other Thinkpad models mentioned in this thread as well.
Comment 123 Nghia T 2022-02-08 21:31:56 UTC
I can confirmed the fix worked on Thinkpad X1 Carbon after updating to BIOS v1.52.
Thanks Lenovo team.
Comment 124 Jackie Dong 2022-02-09 07:31:52 UTC
(In reply to Blanche Schaefer from comment #121)
> (In reply to Jackie Dong from comment #118)
> > Hi Permaer,
> >    Lenovo has released new BIOS to fix this issue, you can update it.
> > 
> > BIOS n1fuj45w.zip (include BIOS N1FET78W, EC N1FHT36W) fixed this issue has
> > been released on Lenovo support web.
> > 
> >
> https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-
> > series-laptops/thinkpad-x1-carbon-type-20fb-20fc/downloads/ds111756-bios-
> > update-utility-bootable-cd-for-windows-10-64-bit-81-64-bit-7-64-bit-32-bit-
> > linux-thinkpad-x1-carbon-type-20fb-20fc-x1-yoga-types-20fq-20fr
> > 
> >    Thanks
> 
> That's great to hear. Is there a chance for similar updates for other
> models, like Yoga 370?

For other products, we are evaluating whether there is a suitable solution. 
Suggest you can update the BIOS to latest release, maybe it can fix the issue in future. 

Thank you very much for your kind attention.
Comment 125 Samgarr 2022-03-03 09:19:26 UTC
Hello, any chance to get this update also for x260?
Comment 126 Jackie Dong 2022-03-03 09:30:30 UTC
(In reply to Samgarr from comment #125)
> Hello, any chance to get this update also for x260?

BIOS team is evaluating the solution for x260 now. But I don't get a plan from them.
Comment 127 François Bernier 2022-03-10 22:26:53 UTC
@jac(In reply to Jackie Dong from comment #124)
> (In reply to Blanche Schaefer from comment #121)
> > (In reply to Jackie Dong from comment #118)
> > > Hi Permaer,
> > >    Lenovo has released new BIOS to fix this issue, you can update it.
> > > 
> > > BIOS n1fuj45w.zip (include BIOS N1FET78W, EC N1FHT36W) fixed this issue
> has
> > > been released on Lenovo support web.
> > > 
> > >
> >
> https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-
> > > series-laptops/thinkpad-x1-carbon-type-20fb-20fc/downloads/ds111756-bios-
> > >
> update-utility-bootable-cd-for-windows-10-64-bit-81-64-bit-7-64-bit-32-bit-
> > > linux-thinkpad-x1-carbon-type-20fb-20fc-x1-yoga-types-20fq-20fr
> > > 
> > >    Thanks
> > 
> > That's great to hear. Is there a chance for similar updates for other
> > models, like Yoga 370?
> 
> For other products, we are evaluating whether there is a suitable solution. 
> Suggest you can update the BIOS to latest release, maybe it can fix the
> issue in future. 
> 
> Thank you very much for your kind attention.

Hey,

I am experiencing the same issue on the X1 carbon gen9 on the latest bios (1.51). Is a fix incoming?
Comment 128 Hans de Goede 2022-03-11 09:13:27 UTC
(In reply to François Bernier from comment #127)
> I am experiencing the same issue on the X1 carbon gen9 on the latest bios
> (1.51). Is a fix incoming?

The issue being discussed here is a different issue then the x1c9 issue. There indeed also is an issue with recent kernel on the X1C9, but that is a different issue. The X1C9 issue is being tracked here atm:
https://bugzilla.redhat.com/show_bug.cgi?id=2057909
Comment 129 Luke 2022-05-05 08:24:27 UTC
How come this is "RESOLVED DOCUMENTED" while there's many more affected models?
Comment 130 Luke 2022-05-05 09:45:13 UTC
UPDATE about Thinkpad X260

Newest BIOS (1.49) from March 2022 fixed the issue!


  Package      BIOS  (BIOS ID)   ECP   (ECP ID)      Rev.  Issue Date
  ---------    ----------------  ----------------    ----  ---------------
  1.49         1.49  (R02ET76W)  1.16  (R02HT34W)    01    2022/03/04
  1.47         1.47  (R02ET74W)  1.15  (R02HT33W)    01    2021/01/14

Thank you all, and thank you Lenovo for not abandoning your older laptops. It took a year to release new BIOS but it's finally here. Cheers!
Comment 131 Jackie Dong 2022-05-05 10:14:47 UTC
Update other 3 products fixed the issue with BIOS version, thanks for your support.

ThinkPad T470s
  Package  (ID)     UEFI BIOS  (BIOS ID)  ECP  (ECP ID)       Rev.  Issue Date
  ----------------  --------------------  ----------------    ----  ----------
  1.45  (N1WUJ38W)  1.45  (N1WET66W)      1.22  (N1WHT40W)    01    2022/03/25
  1.43  (N1WUJ36W)  1.43  (N1WET64W)      1.22  (N1WHT40W)    01    2021/11/29
  1.42  (N1WUJ35W)  1.42  (N1WET63W)      1.22  (N1WHT40W)    01    2021/09/28
  1.41  (N1WUJ34W)  1.41  (N1WET62W)      1.21  (N1WHT39W)    01    2021/06/03
  1.40  (N1WUJ33W)  1.40  (N1WET61W)      1.21  (N1WHT39W)    01    2020/11/10
  1.39  (N1WUJ32W)  1.39  (N1WET60W)      1.21  (N1WHT39W)    01    2020/06/25
  1.38  (N1WUJ31W)  1.38  (N1WET59W)      1.21  (N1WHT39W)    01    2020/05/11
  1.37  (N1WUJ30W)  1.37  (N1WET58W)      1.21  (N1WHT39W)    01    2020/03/24
  1.36  (N1WUJ29W)  1.36  (N1WET57W)      1.21  (N1WHT39W)    01    2019/12/23
  1.35  (N1WUJ28W)  1.35  (N1WET56W)      1.20  (N1WHT38W)    01    2019/09/24


ThinkPad X1 Carbon Gen 5 
 Package      (ID)     UEFI BIOS (BIOS ID)  ECP (ECP ID)      Rev.  Issue Date
  --------------------  -------------------  ---------------   ----  ----------
  1.53      (N1MUJ38W)  1.53 (N1MET68W)      1.22 (N1MHT33W)   01    2021/12/02
  1.52      (N1MUJ37W)  1.52 (N1MET67W)      1.22 (N1MHT33W)   01    2021/10/25
  1.51      (N1MUJ36W)  1.51 (N1MET66W)      1.22 (N1MHT33W)   01    2021/08/23
  1.50      (N1MUJ34W)  1.50 (N1MET65W)      1.20 (N1MHT31W)   01    2021/04/28
  1.49      (N1MUJ33W)  1.49 (N1MET64W)      1.20 (N1MHT31W)   01    2020/11/02
  1.48      (N1MUJ32W)  1.48 (N1MET63W)      1.20 (N1MHT31W)   01    2020/06/22
  1.46      (N1MUJ31W)  1.46 (N1MET61W)      1.20 (N1MHT31W)   01    2020/05/11
  1.45      (N1MUJ28W)  1.45 (N1MET60W)      1.20 (N1MHT31W)   01    2020/03/02
  1.44      (N1MUJ27W)  1.44 (N1MET59W)      1.20 (N1MHT31W)   02    2020/01/30
  1.43      (N1MUJ26W)  1.43 (N1MET58W)      1.20 (N1MHT31W)   01    2019/11/14
  1.42      (N1MUJ25W)  1.42 (N1MET57W)      1.19 (N1MHT30W)   01    2019/09/17

ThinkPad X270 
 Package      BIOS  (BIOS ID)   ECP    (ECP ID)      Rev.  Issue Date
  ---------    ----------------  ----------------    ----  ---------------
  1.45         1.45  (R0IET67W)  1.18   (R0IHT36W)    01    2022/03/15
Comment 132 Peter Stein 2022-05-06 10:40:40 UTC
(In reply to Jackie Dong from comment #131)

It would be great if you could make this magic also work for the T460 which is otherwise still a useful Linux machine (there is some hope since there was a security update recently).
Comment 133 Jackie Dong 2022-05-11 06:48:31 UTC
(In reply to Blanche Schaefer from comment #113)
> (In reply to Mark Pearson from comment #110)
> > Interesting.
> > 
> > We tracked down a X1C4 and reproduced the issue (and confirmed it was fixed
> > by the trial BIOS). But getting them to actually release it is proving
> > challenging
> > 
> > I'll go and chase down what was happening - some folk on my team in China
> > were looking after the details and I lost track of this with the carnage
> > that is December...
> 
> I would appreciate if similar BIOS update could be made for Yoga 370.

Hi Blanche,
   For Yoga 370, this issue has been fixed after BIOS version 1.21. 
   Pls update your BIOS version to latest and verify, thanks!

https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-yoga-series-laptops/thinkpad-yoga-370/downloads/ds120869-bios-update-utility-bootable-cd-for-windows-10-64-bit-thinkpad-yoga-370

<1.21>
 UEFI: 1.21 / ECP: 1.12
- (Fix) Fixed fan runs with maximum speed after resume on Linux.

VERSION INFORMATION

  The following versions of UEFI BIOS and ECP (Embedded Controller Program) have
  been released to date. 

   Package  (ID)       BIOS  (BIOS ID)   ECP    (ECP ID)    Rev.   Issue Date
  ----------------    ----------------  ----------------    ----  ---------------
  1.37  (R0HUJ28W)     1.37  (R0HET57W)  1.16   (R0HHT36W)  01     2020/10/28
  1.36  (R0HUJ27W)     1.36  (R0HET56W)  1.15   (R0HHT35W)  01     2020/09/24
  1.35  (R0HUJ26W)     1.35  (R0HET55W)  1.15   (R0HHT35W)  01     2020/02/04
  1.34  (R0HUJ25W)     1.34  (R0HET54W)  1.15   (R0HHT35W)  01     2019/04/29
  1.33  (R0HUJ24W)     1.33  (R0HET53W)  1.15   (R0HHT35W)  01     2019/02/13 
  1.32  (R0HUJ23W)     1.32  (R0HET52W)  1.15   (R0HHT35W)  01     2018/09/29 
  1.31  (R0HUJ22W)     1.31  (R0HET51W)  1.15   (R0HHT35W)  01     2018/07/13 
  1.30  (R0HUJ21W)     1.30  (R0HET50W)  1.15   (R0HHT35W)  01     2018/06/28 
  1.29  (R0HUJ20W)     1.29  (R0HET49W)  1.15   (R0HHT35W)  01     2018/06/15
  1.28  (R0HUJ19W)     1.28  (R0HET48W)  1.15   (R0HHT35W)  01     2018/05/07 
  1.27  (R0HUJ18W)     1.27  (R0HET47W)  1.14   (R0HHT34W)  01     2018/03/22 
  1.26  (R0HUJ17W)     1.26  (R0HET46W)  1.14   (R0HHT34W)  01     2018/03/12 
  1.25  (R0HUJ16W)     1.25  (R0HET45W)  1.13   (R0HHT33W)  01     2018/02/27 
  1.24  (R0HUJ15W)     1.24  (R0HET44W)  1.13   (R0HHT33W)  01     2018/01/24 
  1.21  (R0HUJ12W)     1.21  (R0HET41W)  1.12   (R0HHT32W)  01     2017/11/13
Comment 134 Jackie Dong 2022-05-18 04:14:32 UTC
(In reply to Peter Stein from comment #132)
> (In reply to Jackie Dong from comment #131)
> 
> It would be great if you could make this magic also work for the T460 which
> is otherwise still a useful Linux machine (there is some hope since there
> was a security update recently).

Hi Peter,
    For T460 Laptop (ThinkPad), this issue has been fixed with latest r06uj71w BIOS. 
   Pls update your BIOS version to latest and verify, thanks!

https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-t-series-laptops/thinkpad-t460/downloads/ds112122-bios-update-utility-bootable-cd-for-windows-10-81-7-64-bit-7-32-bit-thinkpad-t460
Comment 135 Peter Stein 2022-05-18 19:06:18 UTC
(In reply to Jackie Dong from comment #134)
> (In reply to Peter Stein from comment #132)
> 
> Hi Peter,
>     For T460 Laptop (ThinkPad), this issue has been fixed with latest
> r06uj71w BIOS. 
>    Pls update your BIOS version to latest and verify, thanks!
> 
> https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-t-
> series-laptops/thinkpad-t460/downloads/ds112122-bios-update-utility-bootable-
> cd-for-windows-10-81-7-64-bit-7-32-bit-thinkpad-t460


Hi Jackie,


I've updated my T460 with the indicated BIOS and did a test - it works!


For reference, I did the following:

> In my case sdX is sdc, a 4GiB USB thumb drive
>  wget https://download.lenovo.com/pccbbs/mobiles/r06uj71d.iso
>  geteltorito -o r06uj71d.img r06uj71d.iso
>  sudo dd if=r06uj71d.img of=/dev/sdX bs=1M status=progress oflag=direct
>
>  # Now the test
>  # power down, power up, press enter, boot options
>  # select boot from USB device
>  # follow the instructions - multiple restarts appear to be normal
>  # boot into Ubuntu 20.04
>  # run from battery
>  # go to "suspend" mode
>  # wait 30s while the T460 is in suspend mode 
>  # resume operation
>  # wait 30s while the T460 is in operating mode - the fan should stay silent
Comment 136 Peter Stein 2022-05-18 19:23:23 UTC
@Jackie - I forgot to say thanks to you and to the team!

Also thanks to all who helped to track down the bug!

Note You need to log in before you can comment on or make changes to this bug.