While my problem is not exactly the same, i feel that it's so closely related as to not warrant a separate bug.
I have a thinkpad x1 extreme gen3. Whenever i suspend, upon waking up, it shuts down:
thermal thermal_zone3: critical temperature reached (128 C), shutting down
almost always zone3, sometimes zone4.
This is on my focal install, but i tried on a pristine focal live cd, as well as a groovy daily live cd (from sept 26th), with the exact same result. Groovy has thermald 2.3.
I *know* my laptop is not in overheat at that point. I can do this from a cold laptop, on battery or on power at 100%, doing fine with temperatures way low (~40 degC), suspend and wake up 10 seconds later _and i still have that behavior. Whatever that sensor is reading did not go from 40 to 128 in 10 seconds of suspend. I suspect a single bad reading when it wakes up trips everything up.
I've tried thermal.nocrt, or thermal.crt=150, as kernel command lines (and checked when booted that they were applied). That seems to only impact the acpitz-acpi-0 zone, nothing else, and it still powers off when waking up.
removing module int3403_thermal removes thermal_zone[1-8] in /sys/class/thermal
(interestingly, sensors still returns the same set, so either those zones aren't to do with the cpu or anything else sensors returns, or sensors goes through something else to get its values?)
and suspend now works fine.
happy to do some more digging, i'd obviously prefer to un-blacklist this module but now at least i can suspend
While my problem is not exactly the same, i feel that it's so closely related as to not warrant a separate bug.
I have a thinkpad x1 extreme gen3. Whenever i suspend, upon waking up, it shuts down:
thermal thermal_zone3: critical temperature reached (128 C), shutting down
almost always zone3, sometimes zone4.
This is on my focal install, but i tried on a pristine focal live cd, as well as a groovy daily live cd (from sept 26th), with the exact same result. Groovy has thermald 2.3.
I *know* my laptop is not in overheat at that point. I can do this from a cold laptop, on battery or on power at 100%, doing fine with temperatures way low (~40 degC), suspend and wake up 10 seconds later _and i still have that behavior. Whatever that sensor is reading did not go from 40 to 128 in 10 seconds of suspend. I suspect a single bad reading when it wakes up trips everything up.
I've tried thermal.nocrt, or thermal.crt=150, as kernel command lines (and checked when booted that they were applied). That seems to only impact the acpitz-acpi-0 zone, nothing else, and it still powers off when waking up.
removing module int3403_thermal removes thermal_zone[1-8] in /sys/class/thermal
(interestingly, sensors still returns the same set, so either those zones aren't to do with the cpu or anything else sensors returns, or sensors goes through something else to get its values?)
and suspend now works fine.
happy to do some more digging, i'd obviously prefer to un-blacklist this module but now at least i can suspend