> > > 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
>
> Thanks for pointing that out -- it is a great example
> of how powerful mis-information can be.
>
> The fact that the trip-points are writable has obscured,
> rather than clarified, the actual causes of the failures.
> No less than 4 people in that bug report declared that
> cleaning the dust out of their fan fixed the root cause.
> A bunch more said that the issues went away when they
> stopped using ubuntu's user-space power save daemon.
>
> There are a couple more with broken active fan control --
> which also gets obscured rather than clarified by
> over-riding trip points.
>
> And finally, there are probably some with clean fans
> that are working properly, but are thermally challenged
> systems. I'll venture that Windows is NOT modifying or disabling
> the critical trip point to work around this issue.
> I'll venture that their thermal throttling is working
> and ours may not be.
>
> perhaps it was the recently fixed mod_timer() bug in thermal.c,
> or perhaps it is one that we don't know about yet...
>
> > It's also convenient to e.g. lower passive trip point to avoid fan
> > noise.
>
> nope, the OS can't reliably override the processor passive trip point.
> That is what _SCP and cooling_mode are for.
