http://bugzilla.kernel.org/show_bug.cgi?id=8884


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO




------- Comment #18 from [EMAIL PROTECTED]  2007-08-14 11:22 -------
> Machine is stable if I simulate fan failure, load the cpu and rmmod
> thermal and rmmod powernow_k7. I guess 300MHz cpu is not hot enough to
> reach any interesting temperature. Inserting powernow_k7 kills the
> machine in minute-or-so.

If you boot without powernow_k7, the machine comes up and
runs at constant 300MHz and does not fail under load --
even if you disconnect the fan?  How hot is it getting?
Can you load thermal here and verify that you are not
exceeding 83C?

Is it possible to run the same experiment, but at peak MHz?
I'd like to see powernow not loaded, if possible, or at least
not running -- say, by using the performance governor.

> Fan seems to have a mind of its own. It comes into live at ~60
> celsius, and turns itself off at ~55. Nothing I do can control it.

Apparently ACPI fan control on this system is a facade with nothing
behind it.  Certainly with no _TZP and no thermal events, Windows
will simply ignore it.  Linux should just ignore it too.   This
can be done in a pretty way in 2.6.23-rc3 via "thermal.act=-1"

But the fact that thermal events don't work suggests that Windows
will also not notice the passive trip point at 83C -- and it should
run into the same hardware malfunction that Linux runs into.

It would be useful if you can verify that Windows causes this unit to
malfunction the same way Linux does, or if Windows behaves differently.

Does more than one of these machines exist?
If so, do they all fail the same way?

The fact that the fan kicks in starting at 60C but the system
continues to heat up to 83C suggests that the thermal solution
is simply broken on this unit.

But the fact that the malfunction occurs at 83C, which happens to
be the passive trip point is either a very large coincidence
(possible, since you get a failure also with acpi=off,
though unclear at what temperature)
or throttling may actually be involved provoke the failure.

What do you see if you boot 2.6.23-rc3 with "thermal.psv=70" and
heat up the system.  Does it continue to function
while keeping the temperature down to 70?  Note that since
there seem to be no thermal events on this box, you'll also
need thermal.tzp=5 or use what SuSE uses to enable polling from proc.


-- 
Configure bugmail: http://bugzilla.kernel.org/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: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to