| Summary: | Shutdown due to overheating after resuming from S3 on coreboot | ||
|---|---|---|---|
| Product: | Base System | Reporter: | moe |
| Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | New --- | ||
| Severity: | Affects Some People | CC: | yzrh |
| Priority: | --- | ||
| Version: | 12.0-RELEASE | ||
| Hardware: | amd64 | ||
| OS: | Any | ||
|
Description
moe
2018-12-18 11:56:52 UTC
I can't reproduce this bug on OpenBSD and FreeBSD Sorry, I meant Linux and OpenBSD (In reply to moe from comment #0) First thing I would check is whether there is a real overheat issue or if the temperature gets misreported. (In reply to Andriy Gapon from comment #3) I'm not sure how to do that. I've tried to run sysctl -a | grep temperature in a loop while trying to suspend and resume, and I got thrown out of X.org into the console which displayed a message "WARNING: current temperature [128°C] is unsafe" or something like that, after that my PC halted. I'm pretty sure that if my CPU went up to 128°C it would either shut down automatically by BIOS, or I wouldn't be writing this right now. Increase hw.acpi.thermal.polling_rate to something like 20 should `fix' the problem. |