Date: Tue, 26 Mar 2024 04:41:08 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 277969] coretemp returns erroneous temps when resuming from S3 acpi state Message-ID: <bug-277969-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277969 Bug ID: 277969 Summary: coretemp returns erroneous temps when resuming from S3 acpi state Product: Base System Version: 13.3-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: tom+fbsdbugzilla@nuegia.net The coretemp drivers reports 182 degrees C when resuming from S3 acpi power state causing the system to trigger an emergency shut down. My CPU is most definitely not 182C, I don't even think that is possible. This happens about every 1 of 5 resumes. Removing coretemp from the loaded kernel modules allows system to resume from S3 reliably, but prevents tempature monitoring. platform: Lenovo Thinkpad T430 hw.machine: amd64 hw.model: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz ACPI APIC Table: <COREv4 COREBOOT> acpi0: <COREv4 COREBOOT> % uname -v FreeBSD 14.0-RELEASE-p5 #0: Tue Feb 13 23:37:36 UTC 2024 root@amd64-builder.daemonology.net:/usr/obj/usr/src/amd64.amd64/sys/GENERIC Perhaps coretemp should be changed to not initiate a critical temp shutdown except when the last 3 readings have been overtemp. This would prevent noise from triggering emergency actions. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-277969-227>