Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1767441AbXEDWtn (ORCPT ); Fri, 4 May 2007 18:49:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1767461AbXEDWtn (ORCPT ); Fri, 4 May 2007 18:49:43 -0400 Received: from e31.co.us.ibm.com ([32.97.110.149]:38502 "EHLO e31.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1767441AbXEDWtm (ORCPT ); Fri, 4 May 2007 18:49:42 -0400 Subject: Re: cpufreq longhaul locks up From: john stultz To: Jan Engelhardt Cc: davej@codemonkey.org.uk, Linux Kernel Mailing List , cpufreq@lists.linux.org.uk In-Reply-To: References: <1178311052.6094.0.camel@localhost.localdomain> Content-Type: text/plain Date: Fri, 04 May 2007 15:49:38 -0700 Message-Id: <1178318978.6094.29.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1701 Lines: 42 On Fri, 2007-05-04 at 23:02 +0200, Jan Engelhardt wrote: > On May 4 2007 13:37, john stultz wrote: > >> > >> I found that setting the cpufreq governor to ondemand making the box > >> lock up solid in 2.6.20.2 and 2.6.21 after a few seconds. Sysrq > >> does not work anymore, and the last messages are: > >> > >> May 3 19:16:58 cn kernel: longhaul: VIA C3 'Nehemiah C' [C5P] CPU > >> detected. Powersaver supported. > >> May 3 19:16:58 cn kernel: longhaul: Using northbridge support. > >> May 3 19:17:22 cn kernel: Time: acpi_pm clocksource has been installed. > >> May 3 19:17:22 cn kernel: Clocksource tsc unstable (delta = -136422685 > >> ns) > > > >What happens if you boot wihtout the ondemand governor but w/ > >clocksource=acpi_pm ? > > I always let it boot with the default gov (performance), then > use cpufreq-set to change it. > > acpi_pm+performance behaves like tsc+performance, which works > > When switching from tsc+performance to (tsc+)ondemand, acpi_pm gets > used because of the unstable tsc (of course, since we changed > frequency and the cpu does NOT have constant_tsc), so it's > becoming acpi_pm+ondemand naturally. Ok. I just wanted to make sure it wasn't the ACPI PM that was broken and when the system switched to it it was causing the hang. > Switching from acpi_pm+performance to acpi_pm+ondemand also > locks up after a few minutes. Yep. Sounds like an ondemand issue. Thanks for verifying this for me. -john - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/