[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200708031430.26789.lenb@kernel.org>
Date: Fri, 3 Aug 2007 14:30:26 -0400
From: Len Brown <lenb@...nel.org>
To: Knut Petersen <Knut_Petersen@...nline.de>
Cc: 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 08:53, Knut Petersen wrote:
> Len Brown :
> >
> >
> > Thanks for the sighting, Knut!
> > This regression is dramatic when put in the terms of 50% performance hit!
> > I guess the good news is that thermal throttling is doing the job
> > we are asking it to:-)
> >
> >
> >
> Thermal management by cpufreq is working really fine ;-)
Unfortunately, I a lot of people don't understand that the ";-)"
after this statement and they really think that cpufreq is a
solution for thermal management. It isn't. Systems still
need to be thermally sane when they are fully utilized and
cpufreq helps not.
> My problems are definitely not related to a linux bug. All trip_points
> are fixed, hardcoded in the system BIOS at address 0x000FF810.
>
> Yes, I could hack and flash a custom BIOS.
>
> After reading a lot I think I even could fix the DSDT.
No, you should never have to override your BIOS --
except for debugging.
If Windows works out-of-the-box on this system,
then Linux should too - even if we have to use a DMI-based
workaround for a BIOS bug.
I'm looking forward to seeing the bug report that you are
going to file. Please include the dmidecode output in addition
to the acpidump output.
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