Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750917AbVJaPGN (ORCPT ); Mon, 31 Oct 2005 10:06:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750991AbVJaPGN (ORCPT ); Mon, 31 Oct 2005 10:06:13 -0500 Received: from anf141.internetdsl.tpnet.pl ([83.17.87.141]:7096 "EHLO anf141.internetdsl.tpnet.pl") by vger.kernel.org with ESMTP id S1750917AbVJaPGM (ORCPT ); Mon, 31 Oct 2005 10:06:12 -0500 From: "Rafael J. Wysocki" To: LKML Subject: 2.6.14-git3: scheduling while atomic from cpufreq on Athlon64 Date: Mon, 31 Oct 2005 16:06:36 +0100 User-Agent: KMail/1.8.2 Cc: Andrew Morton MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510311606.36615.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4319 Lines: 71 Hi, I'm getting some "scheduling while atomic" messages from 2.6.14-git3 on boot and on suspend/resume, eg.: NET: Registered protocol family 1 powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.50.4) powernow-k8: 0 : fid 0x0 (800 MHz), vid 0x12 (1100 mV) powernow-k8: 1 : fid 0x8 (1600 MHz), vid 0x6 (1400 mV) powernow-k8: 2 : fid 0xa (1800 MHz), vid 0x2 (1500 mV) cpu_init done, current fid 0xa, vid 0x2 scheduling while atomic: swapper/0x00000001/1 Call Trace:{schedule+122} {poison_obj+70} {sysfs_new_dirent+41} {dbg_redzone1+25} {sysfs_new_dirent+41} {cache_alloc_debugcheck_after+280} {powernowk8_target+139} {dbg_redzone1+25} {cpufreq_stat_notifier_policy+304} {__cpufreq_driver_target+116} {sysfs_new_dirent+41} {cpufreq_governor_performance+62} {__cpufreq_governor+173} {__cpufreq_set_policy+440} {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} 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+440} {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} input: AT Translated Set 2 keyboard//class/input as input1 scheduling while atomic: swapper/0x00000001/1 Call Trace:{schedule+122} {cpufreq_frequency_table_target+371} {powernowk8_target+139} {__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} 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} Additionally there are some problems with freezing processes by swsusp. 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/