Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report.
Summary: ACPI: Critical temperature reached (65 C), shutting down. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=155496 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Flag| |needinfo?([EMAIL PROTECTED] | |et) ------- Additional Comments From [EMAIL PROTECTED] 2007-07-20 12:13 EST ------- > # ~misc/files/source/inb_outb > 55 > 55 > 65 Assuming this is the case with 65 critical and 55 passive, this confirms that Linux/ACPI/AML are correctly reading and acting on the underlying memory locations where the BIOS is storing these trip points > Yes, I can choose from "disabled, 70 C, 80 C and 90 C". > 90 C maps to 65 C critical, 55 C passive > 80 C maps to 60 C critical, 50 C passive If you request 70 I assume you get a critical shutdown during boot? What if you request 70, boot "acpi=off" and run inb_outb? Let me guess, we get 55 critical and 45 passive? What do you see if you request "disabled"? What is the default setting for this parameter if you globally reset the BIOS to SETUP defaults? What do you see if you modify inb_outb to do this: # outb 0xF0 0x72 # outb 0x73 0x55 // set TMIN to 85C = 0x55 # outb 0xF0 0x72 # inb 0x73 // this should give us TMIN # outb 0xF1 0x72 # outb 0x73 0x55 // set TMAX to 86 = 0x56 # outb 0xF1 0x72 # inb 0x73 // this should give us TMAX # outb 0xF2 0x72 # outb 0x73 0x5A // set TCRT to 90 = 0x5A # outb 0xF2 0x72 # inb 0x73 // this should give us TCRT you might need a temperature event to coax Linux/ACPI to re-evaluate these trip-points, which should re-read them from memory. possibly setting /proc/acpi/thermal_zone/.../polling_frequency to a non-zero value for a bit would be enough to make this happen. However, the real question is where the EC/temperature-sensors on this box are going to trip. Are they tripping at the BIOS SETUP points, the points in TMIN, TCRT, or some other values that we don't see? You should be able to determine this by disabling the critical shutdown: # mv /sbin/poweroff /sbin/poweroff.orig and enabling monitoring of ACPI events: kill acpid # cat /proc/acpi/event then poll the temperature in /proc/acpi/thermal_zone run something to heat up the system, and see if an ACPI critical trip point event actually occur at the trip point specified or not. It is possible that your original critical shutdown issue was not actually triggered by a critical shutdown event, but a mundane temperature change event that caused Linux to compare current temperature vs the (bogus) critical shutdown point. The other mystery, of course, is what Windows does. It looks like Linux/ACPI are reading the hardware properly, so it might be that Windows has a platform-specific workaround that applies to this chipset or this BIOS. I wonder if Windows has a mechanism where they display the trip points -- if so, it would be interesting to see what they display for each of the BIOS SETUP selections... -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
