http://bugzilla.kernel.org/show_bug.cgi?id=12826 ------- Comment #20 from trenn@xxxxxxx 2009-03-07 08:33 ------- On Saturday 07 March 2009 04:00:16 pm Matthew Garrett wrote: > On Sat, Mar 07, 2009 at 12:09:29PM +0100, Maciej Piechotka wrote: > > # cat /proc/acpi/thermal_zone/THM0/trip_points > > critical (S5): 99 C > > passive: 95 C: tc1=5 tc2=4 tsp=600 devices= CPU > > > > The problem is that it seems that the system halts at about 95 C - in > > moment when cooling should be applied. This might be an ACPI/ibm_acpi > > bug. > > Halts as in shuts down, or halts as in stops running? The R51e seems to > have the 32/64-bit ACPI address issue - can you try booting with > acpi=rsdt as a kernel argument and see whether it behaves any better? Yes it has. I posted patches to fix this about three times, first time probably more than a year ago, last one should be these (on the acpi list, easy to google): [PATCH 1/3] ACPICA: Add acpi_gbl_force_rsdt variable [PATCH 2/3] Introduce acpi_root_table=rsdt boot param and dmi list to force rsdt [PATCH 3/3] Remove R40e c-state blacklist wrong the last time I sent them was on 19th of Oct. 2008: [RESEND] [PATCH 0/3] Blacklist broken ThinkPads to use 32 bit FADT addresses [RESEND] [PATCH 1/3] ACPICA: Add acpi_gbl_force_rsdt variable [RESEND] [PATCH 2/3] Introduce acpi_root_table=rsdt boot param and dmi list to force rsdt [RESEND] [PATCH 3/3] Remove R40e c-state blacklist No we have: - SUSE and mainline kernels are out of sync with boot params, acpi_root_table=rsdt vs acpi=rsdt - R51e and R40e are broken in mainline for years, even we know why and they still are While I agree with Len that we should try to find the root cause, such issues should get blacklisted first until the root cause has been found or we start debugging the same issues over and over again and loose an overview about which machines/BIOSes are broken. Thomas -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
