[Bug 210457] Fan sporadically maxed on wake-up due to unavailable sensor temperature

[Bug 210457] Fan sporadically maxed on wake-up due to unavailable sensor temperature

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=210457

cfr (reescf@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |reescf@gmail.com

--- Comment #1 from cfr (reescf@gmail.com) ---
Lenovo ThinkPad X720 is also affected by this, but it is not sporadic, as far
as I can tell. Not once since installing my current kernel have I seen normal
behaviour following sleep.

The problem persists if the machine is rebooted. Only powering off and
restarting restores the expected behaviour.

The bug seems to be a regression. See
https://bugzilla.kernel.org/show_bug.cgi?id=196129. My machine was not affected
by the original bug, but the problem looks to be the same.

Following sleep:

cat /sys/devices/platform/thinkpad_hwmon/hwmon/hwmon7/temp*
0
1000
0
0
0
0
0
cat: /sys/devices/platform/thinkpad_hwmon/hwmon/hwmon7/temp1_input: No such
device or address
cat: /sys/devices/platform/thinkpad_hwmon/hwmon/hwmon7/temp2_input: No such
device or address
0
0
0
0
0
0
0

and

cat /proc/acpi/ibm/thermal 
temperatures:   -128 -128 0 0 0 0 0 0 0 0 1 0 0 0 0 0

Prior to sleep, only the second sensor is missing and acpitz-acpi-0 gives a
sane reading. Following, the first goes AWOL and acpitz-acpi-0 is stuck at 48.

Removing and reloading thinkpad_acpi makes no difference and, for me,
re-sleeping and rewaking makes no difference either.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 210457] Fan sporadically maxed on wake-up due to unavailable sensor temperature

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=210457

--- Comment #2 from cfr (reescf@gmail.com) ---
I should have looked at the date of this report. The problem I'm seeing is new.
I installed a new kernel this week and the problem started then.

ArchLinux kernel package version is 5.11.4-arch1-1. I did NOT see this bug with
5.10.16.arch1-1.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 210457] Fan sporadically maxed on wake-up due to unavailable sensor temperature

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=210457

--- Comment #3 from cfr (reescf@gmail.com) ---
I tried adding 

acpi.ec_freeze_events=Y acpi.ec_suspend_yield=Y

to my kernel command line and rebooting, but I never got past the screen
displaying the command. The machine froze and I had to poweroff. 

Is there a newer invocation I could try here?

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 210457] Fan sporadically maxed on wake-up due to unavailable sensor temperature

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=210457

--- Comment #4 from cfr (reescf@gmail.com) ---
The bug does NOT manifest if I boot linux-lts 5.10.21-1. Following sleep:

cat /sys/devices/platform/thinkpad_hwmon/hwmon/hwmon6/temp*
0
1000
0
0
0
0
0
38000
cat: /sys/devices/platform/thinkpad_hwmon/hwmon/hwmon6/temp2_input: No such
device or address
0
0
0
0
0
0
0

and the fan is at 0RPM, while acpitz-acpi-0 and thinkpad-isa-0000 temp1 are
both +38.0°C.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 210457] Fan sporadically maxed on wake-up due to unavailable sensor temperature

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=210457

Thorsten (s-cvhajmmblfsofmpsh@thorsten-wissmann.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |s-cvhajmmblfsofmpsh@thorste
                   |                            |n-wissmann.de

--- Comment #5 from Thorsten (s-cvhajmmblfsofmpsh@thorsten-wissmann.de) ---
I have the same issue on X1 Carbon 5th generation (i.e. lacking of temp1 makes
the fan run in max speed) and the bug still exists in 5.11.7.arch1-1. Going
back to the lts-kernel (5.10.24-1) makes temp1 appear.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 210457] Fan sporadically maxed on wake-up due to unavailable sensor temperature

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=210457

--- Comment #7 from Thorsten (s-cvhajmmblfsofmpsh@thorsten-wissmann.de) ---
Probably it's the same issue. However, here we know that the main issue is that
the first entry of /proc/acpi/ibm/thermal is erronously -128 some (or most) of
the time (so the fan is just a symptom, not the issue).

temperatures:   -128 -128 0 0 0 0 0 0 0 0 1 0 0 0 0 0

Iirc, the first entry is
/sys/devices/platform/thinkpad_hwmon/hwmon/hwmon*/temp1_input

(By the way, the second entry being -128 is fine)

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 210457] Fan sporadically maxed on wake-up due to unavailable sensor temperature

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=210457

Hans de Goede (jwrdegoede@fedoraproject.org) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jwrdegoede@fedoraproject.or
                   |                            |g

--- Comment #9 from Hans de Goede (jwrdegoede@fedoraproject.org) ---
(In reply to cfr from comment #8)
> On my machine, the issue seems to have been caused by a firmware bug, which
> only manifested in symptoms with the kernel update. That is, the firmware
> was the same for 3+ years with no issue, the new kernel triggered the bug,
> but a firmware update seems to have resolved it.

Thank you.

Can the other reporters of this bug please also see if the latest BIOS resolves
this? ThinkPad BIOS updates are available on lvfs, so they can be done under
Linux through fwupdmgr.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 210457] Fan sporadically maxed on wake-up due to unavailable sensor temperature

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=210457

--- Comment #10 from Daniel T. (pterion@gmail.com) ---
(In reply to Hans de Goede from comment #9)
> (In reply to cfr from comment #8)
> > On my machine, the issue seems to have been caused by a firmware bug, which
> > only manifested in symptoms with the kernel update. That is, the firmware
> > was the same for 3+ years with no issue, the new kernel triggered the bug,
> > but a firmware update seems to have resolved it.
> 
> Thank you.
> 
> Can the other reporters of this bug please also see if the latest BIOS
> resolves this? ThinkPad BIOS updates are available on lvfs, so they can be
> done under Linux through fwupdmgr.

The situation is NOT resolved / the same for me after the recent firmware /
BIOS update.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 210457] Fan sporadically maxed on wake-up due to unavailable sensor temperature

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=210457

--- Comment #12 from Thorsten (s-cvhajmmblfsofmpsh@thorsten-wissmann.de) ---
After updating to kernel 5.12.12(-arch1-1), the issue still existed, but only
after multiple suspend/resume-cycles (I couldn't find a deterministic way to
reproduce it). After a BIOS update I wasn't able to reproduce it anymore. The
BIOS now reports: UEFI BIOS Version: N1MET65W (1.50), Embedded Controller
Version: N1MHT31W (1.20), Machine Type Model: 20HQS3KG00. However, I do not
own/hold the laptop anymore, so I can't tell whether the issue returns after
running the laptop for a longer time (days, or so).

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.