| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20130427102346.GA30588@amd.pavel.ucw.cz> Date: Sat, 27 Apr 2013 12:23:47 +0200 From: Pavel Machek <pavel@....cz> To: Zhang Rui <rui.zhang@...el.com> Cc: linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org, linux-acpi@...r.kernel.org, rjw@...k.pl, lenb@...nel.org, eduardo.valentin@...com Subject: Re: [PATCH] ACPI thermal: do not always return THERMAL_TREND_RAISING for active trip points Hi! > Commit 4ae46befb49d4173122e0afa995c4e93d01948a2 > introduces a regression that the fan is always on > even if the system is in idle state. > > My original idea in that commit is that: > when the current temperature is above the trip point, > keep the fan on, even if the temperature is dropping. > when the current temperature is below the trip point, > turn on the fan when the temperature is raising, > turn off the fan when the temperature is dropping. Is that even right algoritm? Assume I'm running at very cold room, lets say -10C. Assume idle CPU will hover around 30C with no fan, or hover around 10C with fan running, trip point being 50C. You _could_ leave fan off until 50C, having silent, passively cooled system. What it will do instead is annoyingly pulse fan at 10C. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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