On Thu, May 17, 2007 at 06:35:48PM -0400, Len Brown wrote:
Yes, SuSE enables polling mode by default, but that is just
distro specific value add that should eventually be fixed.
I will do that for openSUSE FACTORY.
--
Stefan Seyfried
QA / RD Team Mobile Devices| Any
On Tue, May 22, 2007 at 11:06:36AM +0200, Pavel Machek wrote:
We need to ignore trip point updates from BIOS, and we need to poll
thermals when use overrides trip points. That's expected. Plus I've
yet to see platform actually updating the trip points.
Thinkpad 600, whenever a trip point is
On Mon 2007-06-04 11:02:01, Stefan Seyfried wrote:
On Thu, May 17, 2007 at 06:35:48PM -0400, Len Brown wrote:
Yes, SuSE enables polling mode by default, but that is just
distro specific value add that should eventually be fixed.
I will do that for openSUSE FACTORY.
Well, I still
On Thu 2007-05-31 22:46:11, Len Brown wrote:
On Monday 21 May 2007 08:11, Pavel Machek wrote:
On Thu 2007-05-17 18:42:43, Len Brown wrote:
Something similar happened to me on XE3, yes.
(Actual values were different; BIOS specified critical temperature at
cca 95C, but hw killed
On Monday 21 May 2007 08:11, Pavel Machek wrote:
On Thu 2007-05-17 18:42:43, Len Brown wrote:
Something similar happened to me on XE3, yes.
(Actual values were different; BIOS specified critical temperature at
cca 95C, but hw killed the power at cca 83C. Setting critical trip
Hi!
So don't do it badly. The advantage of doing so is that you can make it
work properly, which you can't by putting it in the kernel.
You want stuff like critical shutdowns to work even if userspace is
dead.
I don't think anyone suggested putting the critical shutdown control
On Tue, May 22, 2007 at 11:06:36AM +0200, Pavel Machek wrote:
We need to ignore trip point updates from BIOS, and we need to poll
thermals when use overrides trip points. That's expected. Plus I've
yet to see platform actually updating the trip points.
Try any recent HP bios.
--
Matthew
Le 05/22/2007 11:16 AM, Matthew Garrett a déclaré :
On Tue, May 22, 2007 at 11:06:36AM +0200, Pavel Machek wrote:
We need to ignore trip point updates from BIOS, and we need to poll
thermals when use overrides trip points. That's expected. Plus I've
yet to see platform actually updating the
Matthew Garrett pisze:
.
Try any recent HP bios.
Yes...
hp nx 6310, bios version:
F.06. cpufreq works, MFCG Bios Error in dmesg (PCI: BIOS Bug: MCFG area
at f800 is not E820-reserved)
F.08. like above + cpufreq broken
F.09 Remove this errors, but problem with reboot (too long time -
On Sun, 2007-05-20 at 23:50 -0400, Len Brown wrote:
On Saturday 19 May 2007 15:56, Thomas Renninger wrote:
On Thu, 2007-05-17 at 15:17 -0400, Len Brown wrote:
On Thursday 17 May 2007 05:23, Pavel Machek wrote:
ACPI: thermal trip points are read-only
What was the
Hi!
No, writing trip-points is neither a fix, nor it is reasonable.
It is a workaround at best, and it is a dangerous and mis-leading hack.
Yes it is a workaround for critical ACPI bugs like that or similar:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/22336
On Thu 2007-05-17 18:42:43, Len Brown wrote:
Something similar happened to me on XE3, yes.
(Actual values were different; BIOS specified critical temperature at
cca 95C, but hw killed the power at cca 83C. Setting critical trip
point at 80C made the problem go away.)
Great, please
On Mon, May 21, 2007 at 02:10:48PM +0200, Pavel Machek wrote:
nope, the OS can't reliably override the processor passive trip point.
That is what _SCP and cooling_mode are for.
Yes, it is reliable if you turn on thermal polling.
As Len says, the system can force a reevaluation of the trip
Hi!
For folks with the reverse problem -- active cooling where the
fans kick in early than they'd like, they should just turn off
the fans via /proc/acpi/fan and not mess with the trip points at
all.
No. Manually turning off fans is even worse hack.
It's significantly more
On Mon, May 21, 2007 at 03:29:48PM +0200, Pavel Machek wrote:
No. Manually turning off fans is even worse hack.
It's significantly more correct.
Significantly more correct? It forces you to do all the thermal
management in userspace!
Why's that a problem? Overriding the hardware
On Mon 2007-05-21 14:36:08, Matthew Garrett wrote:
On Mon, May 21, 2007 at 03:29:48PM +0200, Pavel Machek wrote:
No. Manually turning off fans is even worse hack.
It's significantly more correct.
Significantly more correct? It forces you to do all the thermal
management in
On Mon, May 21, 2007 at 03:40:46PM +0200, Pavel Machek wrote:
On Mon 2007-05-21 14:36:08, Matthew Garrett wrote:
On Mon, May 21, 2007 at 03:29:48PM +0200, Pavel Machek wrote:
Significantly more correct? It forces you to do all the thermal
management in userspace!
Why's that a
On Tue, May 22, 2007 at 12:42:00AM +0200, Pavel Machek wrote:
On Mon 2007-05-21 14:45:53, Matthew Garrett wrote:
So don't do it badly. The advantage of doing so is that you can make it
work properly, which you can't by putting it in the kernel.
You want stuff like critical shutdowns to
On Saturday 19 May 2007 15:56, Thomas Renninger wrote:
On Thu, 2007-05-17 at 15:17 -0400, Len Brown wrote:
On Thursday 17 May 2007 05:23, Pavel Machek wrote:
ACPI: thermal trip points are read-only
What was the rationale? Can we get this one reverted?
Some machines (HP
On Thu, 2007-05-17 at 15:17 -0400, Len Brown wrote:
On Thursday 17 May 2007 05:23, Pavel Machek wrote:
ACPI: thermal trip points are read-only
What was the rationale? Can we get this one reverted?
Some machines (HP omnibook xe3) have broken trip points -- too high --
so
Hi!
In 2.6.20.9 I can change trippoints:
echo 105:100:100:78:70:40:30 /proc/acpi/thermal_zone/TZ0/trip_points
echo 10 /proc/acpi/thermal_zone/TZ0/polling_frequency
Then I got:
cat /proc/acpi/thermal_zone/TZ0/*
...
Its bug or feature?
Committed to mainline May 10:
Pavel Machek pisze:
What was the rationale? Can we get this one reverted?
Some machines (HP omnibook xe3) have broken trip points -- too high --
so machine will overheat and trigger hw shutdown before starting
passive cooling.
That's really broken, and write to trip points is reasonable
On Thursday 17 May 2007 09:36, Maciej Rutecki wrote:
Many people need change trippoints, for example I have:
cat /proc/acpi/thermal_zone/TZ0/trip_points | grep critical
critical (S5): 256 C
I _must_ change it to below 105 C, or edit DSDT table (too difficult to
me). I cannot
On Thursday 17 May 2007 05:23, Pavel Machek wrote:
ACPI: thermal trip points are read-only
What was the rationale? Can we get this one reverted?
Some machines (HP omnibook xe3) have broken trip points -- too high --
so machine will overheat and trigger hw shutdown before starting
Len Brown pisze:
What bad things happen if you leave the critical trip point at 256?
Do you find that you can drive the temperature over 105 and
the system fails to shut down?
-Len
It isn't problem in this case (nx6310). But on hp nc nc6220 first trip
point is at 30 *C, so fan is
Added to bugzilla (Bug 8496)
http://bugzilla.kernel.org/show_bug.cgi?id=8496
--
Maciej Rutecki
http://www.maciek.unixy.pl
smime.p7s
Description: S/MIME Cryptographic Signature
Hi!
ACPI: thermal trip points are read-only
What was the rationale? Can we get this one reverted?
Some machines (HP omnibook xe3) have broken trip points -- too high --
so machine will overheat and trigger hw shutdown before starting
passive cooling.
That's really
On Thu 2007-05-17 15:08:39, Len Brown wrote:
On Thursday 17 May 2007 09:36, Maciej Rutecki wrote:
Many people need change trippoints, for example I have:
cat /proc/acpi/thermal_zone/TZ0/trip_points | grep critical
critical (S5): 256 C
I _must_ change it to below 105 C,
No, writing trip-points is neither a fix, nor it is reasonable.
It is a workaround at best, and it is a dangerous and mis-leading hack.
The OS has no capability to actually change the ACPI trip points
that are used by the BIOS. Changing the OS copy of them
to make the user think that
Something similar happened to me on XE3, yes.
(Actual values were different; BIOS specified critical temperature at
cca 95C, but hw killed the power at cca 83C. Setting critical trip
point at 80C made the problem go away.)
Great, please file a bug and include the acpidump from the XE3
and
In 2.6.20.9 I can change trippoints:
echo 105:100:100:78:70:40:30 /proc/acpi/thermal_zone/TZ0/trip_points
echo 10 /proc/acpi/thermal_zone/TZ0/polling_frequency
Then I got:
cat /proc/acpi/thermal_zone/TZ0/*
setting not supported
cooling mode: active
polling frequency: 10 seconds
state:
Maciej Rutecki wrote:
In 2.6.20.9 I can change trippoints:
echo 105:100:100:78:70:40:30 /proc/acpi/thermal_zone/TZ0/trip_points
echo 10 /proc/acpi/thermal_zone/TZ0/polling_frequency
Then I got:
cat /proc/acpi/thermal_zone/TZ0/*
setting not supported
cooling mode: active
polling
Le 05/16/2007 07:47 PM, Chuck Ebbert a déclaré :
Gitweb:
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=11ccc0f249cb01a129f54760b8ff087f242935d4
Commit: 11ccc0f249cb01a129f54760b8ff087f242935d4
Parent: de46c33745f5e2ad594c72f2cf5f490861b16ce1
33 matches
Mail list logo
