[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200708031435.25416.lenb@kernel.org>
Date: Fri, 3 Aug 2007 14:35:25 -0400
From: Len Brown <lenb@...nel.org>
To: "Renato S. Yamane" <renatoyamane@...dic.com.br>
Cc: Knut Petersen <Knut_Petersen@...nline.de>,
linux-kernel@...r.kernel.org, Andrew Morton <akpm@...l.org>,
trenn@...e.de, pavel@....cz, mjg59@...f.ucam.org,
linux-acpi@...r.kernel.org
Subject: Re: 2.6.22 regression: thermal trip points
On Friday 03 August 2007 07:43, Renato S. Yamane wrote:
> Len Brown escreveu:
> > On Thursday 02 August 2007 04:40, Knut Petersen wrote:
> >> mainboard: AOpen i915GMm-hfs, AWARD BIOS
> >> cpu: Pentium-M 750 (0.8 to 1.86 MHz)
> >> openSuSE 10.2 with kernel 2.6.22.1
> >>
> >> The cpu fan can not be controled by linux kernel.
> >> The BIOS will switch on the cpu fan a bit above 50 deg. Celsius.
> >> The active and passive trip points both are set to 50 deg. Celsius.
> >> Temperature of the idle cpu at 800 Mhz: 34 to 42 deg. C.
> >> The BIOS never changes the trip points.
> >> Cpufreq does work perfectly.
>
> On my Toshiba M45-S355 (Toshiba Bios, Pentium M 750 - 0.8 at 1.86GHz,
> Debian Etch) I see the same using Kernel 2.6.21.6
>
> >> Previously there was the possibility to add something like
> >>
> >> echo "100:0:65:70:0" > /proc/acpi/thermal_zone/THRM/trip_points
> >> echo 2 > /proc/acpi/thermal_zone/THRM/polling_frequency
> >> echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
>
> I never do that, but see below (Kernel 2.6.21.6):
>
> cat /proc/acpi/thermal_zone/TZCL/trip_points
> critical (S5): 105 C
>
> cat /proc/acpi/thermal_zone/TZCL/polling_frequency
> polling frequency: 2 seconds
>
> cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
> ondemand
>
Renato,
I don't understand how your Toshiba is similar to Knut's Aopen.
You've got a single critical trip point at 105C, but no active or passive
trip points.
Are you reporting some kind of failure?
The only thing wrong with your system is that polling_frequency != 0 --
but that is probably a distro configuration issue rather than
a kernel issue.
thanks,
-Len
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists