Well, the title says it all, after my T460 wakes from sleep, fan(s) ramp up to the max, and they stay that way until “cold” reboot, rebooting from the OS itself doesn’t do anything and fans keep on spinning. Google didn’t help at all.
Try the Arch Laptops wiki, even if it doesn’t list your specific model some share almost identical hardware architecture, so you could always find something helpful there regarding yours.
https://wiki.archlinux.org/index.php/Laptop/Lenovo#IBM/Lenovo
/edit:
example: clicked randomly on model T470, it states:
suspend-resume results in the fan holding at 100% without ever spinning down. This is being tracked on the kernel bugtracker. The issue seems to be resolved by BIOS 1.43.
Thanks for the reply, I have also found this information, but this doesn’t seem to resolve a problem on T460 model, since I’m already running the latest version of BIOS (1.43) and the problem still occurs regularly.
Maybe i will not reply accurately, but, i have the same issue after suspend.
This is an extract from Arch wiki :
Fancontrol stops working after suspend–wake cycles
Unfortunately, fancontrol does not work after suspending. As per the filed bug, you will have to restart fancontrol after suspending. This can be achieved automatically by a systemd hook.
I do not know is you use Fancontrol though.
Hi,
I have the same problem with my laptop. Even if I restart fancontrol it’s not working 
[david@MrRobot ~]$ systemctl start fancontrol.service
[david@MrRobot ~]$ systemctl status fancontrol.service
● fancontrol.service - Start fan control, if configured
Loaded: loaded (/usr/lib/systemd/system/fancontrol.service; enabled; vendor preset: disabled)
Active: inactive (dead)
Condition: start condition failed at Fri 2021-03-12 09:49:07 CET; 7s ago
└─ ConditionFileNotEmpty=/etc/fancontrol was not met
mar 12 09:18:02 MrRobot systemd[1]: Condition check resulted in Start fan control, if configured being skipped.
mar 12 09:18:50 MrRobot systemd[1]: Condition check resulted in Start fan control, if configured being skipped.
mar 12 09:25:52 MrRobot systemd[1]: Condition check resulted in Start fan control, if configured being skipped.
mar 12 09:26:39 MrRobot systemd[1]: Condition check resulted in Start fan control, if configured being skipped.
mar 12 09:28:38 MrRobot systemd[1]: Condition check resulted in Start fan control, if configured being skipped.
mar 12 09:49:07 MrRobot systemd[1]: Condition check resulted in Start fan control, if configured being skipped.
Didn’t found a solution yet…