From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Suspend to RAM regression tracked down Date: Sun, 02 Jul 2006 23:02:36 -0700 Message-ID: <44A8B2FC.6080806@goop.org> References: <1151837268.5358.10.camel@idefix.homelinux.org> <44A80B20.1090702@goop.org> <1151880764.5358.32.camel@idefix.homelinux.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1151880764.5358.32.camel@idefix.homelinux.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: cpufreq-bounces@lists.linux.org.uk Errors-To: cpufreq-bounces+glkc-cpufreq=m.gmane.org+glkc-cpufreq=m.gmane.org@lists.linux.org.uk Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Jean-Marc Valin Cc: cpufreq@lists.linux.org.uk, Linux Kernel Jean-Marc Valin wrote: > Any link to the patch and the thread about the problem (if any)? Also, > was the race introduced in 2.6.12-rc5-git6? If not, it's a completely > different problem because my machine worked fine with 2.6.12-rc5-git5. > It's in the thread on the cpufreq list titled "ondemand vs suspend"; Venkatesh Pallipadi posted the patch. J