https://bugzilla.novell.com/show_bug.cgi?id=409064 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=409064#c2 --- Comment #2 from Thomas Renninger 2008-07-14 15:40:57 MDT --- Have of the bugs -> half of the bugs -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Also tell me if I am risking my system by running with ACPI but not letting the thermal module run. On an HP, I'd say yes. There should always be HW switching off if it gets too hot, but HP laptops do their thermal management through ACPI only. So it could be that you constantly run at 90C, which might not destroy your HW, but shorten

https://bugzilla.novell.com/show_bug.cgi?id=409064 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=409064#c4 --- Comment #4 from Thomas Renninger 2008-07-15 02:40:41 MDT --- the lifetime, especially of your disk data...

I will check for a BIOS update I will wait a bit. If there really is a new BIOS, please tell me if you still see this and then upload acpidump of the new BIOS. It does not make sense to work on old code.

Hm, this is probably another problem than the I/O APIC problem I forwared you some info. But it could be related in a way that on both systems the ACPI code is going wrong paths (on the HP nx6325 showing wrong trip points, all 16C, here returning wrong temperature). If you can see the negative temperature value in dmesg (then we could calc back for what we are searching in the DSDT) or paste some output of related lines, this could also help. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=409064 User joachim.deguara@amd.com added comment https://bugzilla.novell.com/show_bug.cgi?id=409064#c6 --- Comment #6 from Joachim Deguara 2008-07-15 10:30:03 MDT --- The BIOS currently installed is the latest. I disassembled the ACPI but I don't know how to read the therm trip stuff. Can we read it all out of the acpi dump I attached or do I need to do other diagnostics? Unfortunately I can't see the therm trip points (which I assume are bad) without the laptop shutting down immediately. I don't think this is related to polling frequency as it polls regularly and that is why it know/thinks it is overheating. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

The same problem (shutting down immediately on boot) happens with SLED10 SP2 also Thanks a lot for trying that! I thought this came in because the new ACPI

https://bugzilla.novell.com/show_bug.cgi?id=409064 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=409064#c8 --- Comment #8 from Thomas Renninger 2008-07-15 11:42:15 MDT --- This is the thermal zone stuff, I already cut out most parts. My comments start with # Jean: There is one interesting line for you marked with "Jean" :) Scope (_TZ) { Name (TPC, 0x69) Name (TPTM, 0x4B) Name (TPAS, 0x5F) ThermalZone (THRM) { # Temperature method Method (_TMP, 0, NotSerialized) { If (ECON) { # Read out from Embedded controller Store (\_SB.PCI0.LPC0.EC0.RTMP, Local0) Return (Add (0x0AAC, Multiply (Local0, 0x0A))) } Else { Return (Add (0x0AAC, Multiply (TPTM, 0x0A))) } } # Critical temperature Method (_CRT, 0, Serialized) { # If Windows is earlier than Windows Vista (cmp. with OSTP func) # return 0x69 (TPC + 273 Kelvin) * 10, or here: (TPC * 10) + 2732 If (LLess (TPOS, 0x40)) { Return (Add (0x0AAC, Multiply (TPC, 0x0A))) } # IF OSI RETURNS TRUE FOR WINDOWS VISTA (or VISTA SP1) OR LINUX (cmp.OSTP func) # then zero is returned. I EXPECT THE ERROR IS HERE (see kernel code snipet at the end) Else { Return (Zero) } } # Jean: They seem to provide a name for the thermal zone. Can/should we pass # this to hwmon? Name (REGN, "Processor Thermal Zone") .. } } In drivers/acpi/thermal.c: /* Critical Shutdown (required) */ if (flag & ACPI_TRIPS_CRITICAL) { status = acpi_evaluate_integer(tz->device->handle, "_CRT", NULL, &tz->trips.critical.temperature); /* * Treat freezing temperatures as invalid as well; some * BIOSes return really low values and cause reboots at startup. * Below zero (Celcius) values clearly aren't right for sure.. * ... so lets discard those as invalid. */ if (ACPI_FAILURE(status) || tz->trips.critical.temperature <= 2732) { tz->trips.critical.flags.valid = 0; ACPI_EXCEPTION((AE_INFO, status, "No or invalid critical threshold")); ---- Because zero is returned and the kernel is calculating the Kelvin*10 value back or better comparing it with (Kelvin*10) temperature values you get a negativ Celsius value. Ohh, it looks like the above code is in linux-next only? This should be the commit fixing it: commit a39a2d7c72b358c6253a2ec28e17b023b7f6f41c Author: Arjan van de Ven Date: Mon May 19 15:55:15 2008 -0700 ACPI: Reject below-freezing temperatures as invalid critical temperatures My laptop thinks that it's a good idea to give -73C as the critical CPU temperature.... which isn't the best thing since it causes a shutdown right at bootup. Temperatures below freezing are clearly invalid critical thresholds so just reject these as such. Signed-off-by: Arjan van de Ven Acked-by: Zhang Rui Signed-off-by: Len Brown This is something that must pop up in stable kernels... Increasing severity, I will take care about this tomorrow. thermal patches, but this shows how bad it is that we return OSI=Windows. They break SLES10 SP2 certification by adding Vista hotfixes. Linux must not return true for OSI=Windows... (A fight I lost with Intel, they want to let machines break, so that we stay close to Windows ACPI implementation and by that fix other machines..., but this give me new material...). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=409064 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=409064#c10 --- Comment #10 from Thomas Renninger 2008-07-15 15:24:38 MDT ---

and sure enough found that critical threshold is set to -273 whereas hot is set to 105 C This is strange. The hot trip point is returned in the same way..., ohhh you are right: for the _HOT method it is LEqual, means only for Vista, but not for Linux zero is returned.

Method (_HOT, 0, Serialized) { !!! If (LEqual (TPOS, 0x40)) { Return (Add (0x0AAC, Multiply (TPC, 0x0A))) } Else { Return (Zero) } } Method (_CRT, 0, Serialized) { !!! If (LLess (TPOS, 0x40)) { Return (Add (0x0AAC, Multiply (TPC, 0x0A))) } Else { Return (Zero) } } -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=409064 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=409064#c12 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|joachim.deguara@amd.com | Resolution| |FIXED --- Comment #12 from Thomas Renninger 2008-07-29 02:22:42 MDT --- I added a patch to 11.0 a while ago. Now this should also work for SLE10-SP2: Tue Jul 29 10:20:11 CEST 2008 - trenn@suse.de - patches.arch/acpi_thermal_check_critical_temp.patch: ACPI: Reject below-freezing temperatures as invalid critical temperatures (bnc#409064). Thanks for reporting. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.