Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932427AbVJaTpN (ORCPT ); Mon, 31 Oct 2005 14:45:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932493AbVJaTpN (ORCPT ); Mon, 31 Oct 2005 14:45:13 -0500 Received: from anf141.internetdsl.tpnet.pl ([83.17.87.141]:4281 "EHLO anf141.internetdsl.tpnet.pl") by vger.kernel.org with ESMTP id S932427AbVJaTpL (ORCPT ); Mon, 31 Oct 2005 14:45:11 -0500 From: "Rafael J. Wysocki" To: Andrew Morton Subject: Re: 2.6.14-git3: scheduling while atomic from cpufreq on Athlon64 Date: Mon, 31 Oct 2005 20:45:32 +0100 User-Agent: KMail/1.8.2 Cc: linux-kernel@vger.kernel.org, Ashok Raj , Dave Jones , Ingo Molnar References: <200510311606.36615.rjw@sisk.pl> <20051031113413.34a599cd.akpm@osdl.org> In-Reply-To: <20051031113413.34a599cd.akpm@osdl.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510312045.32908.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1797 Lines: 35 On Monday, 31 of October 2005 20:34, Andrew Morton wrote: > "Rafael J. Wysocki" wrote: }-- snip --{ > > scheduling while atomic: swapper/0x00000001/1 > > > > Call Trace:{schedule+122} {cpufreq_frequency_table_target+371} > > {powernowk8_target+1916} {__cpufreq_driver_target+116} > > {sysfs_new_dirent+41} {cpufreq_governor_performance+62} > > {__cpufreq_governor+173} {__cpufreq_set_policy+551} > > {cpufreq_set_policy+79} {cpufreq_add_dev+806} > > {handle_update+0} {sysdev_driver_register+170} > > {cpufreq_register_driver+198} {init+194} > > {child_rip+8} {init+0} > > {child_rip+0} > > Well I can't find it. Ingo, didn't you have a debug patch which would help > us identify where this atomic section started? This is 100% reproducible on my box so I'll try to figure out what's up tomorrow (unless someone else does it earlier ;-)). Now I can only say it did not happen with 2.6.14-rc5-mm1. > > Additionally there are some problems with freezing processes by swsusp. Once the box has not suspended due to a process refusing to freeze, but I was unable to trace the problem at that time. This does not seem to be readily reproducible, however. Greetings, Rafael - 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/