From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>
Subject: 2.6.14-git3: scheduling while atomic from cpufreq on Athlon64
Date: Mon, 31 Oct 2005 16:06:36 +0100 [thread overview]
Message-ID: <200510311606.36615.rjw@sisk.pl> (raw)
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:<ffffffff8035014a>{schedule+122} <ffffffff80163576>{poison_obj+70}
<ffffffff801be269>{sysfs_new_dirent+41} <ffffffff80162989>{dbg_redzone1+25}
<ffffffff801be269>{sysfs_new_dirent+41} <ffffffff80163908>{cache_alloc_debugcheck_after+280}
<ffffffff8011cf1b>{powernowk8_target+139} <ffffffff80162989>{dbg_redzone1+25}
<ffffffff802e0830>{cpufreq_stat_notifier_policy+304}
<ffffffff802dfdb4>{__cpufreq_driver_target+116} <ffffffff801be269>{sysfs_new_dirent+41}
<ffffffff802e097e>{cpufreq_governor_performance+62}
<ffffffff802dec8d>{__cpufreq_governor+173} <ffffffff802df3a8>{__cpufreq_set_policy+440}
<ffffffff802df5bf>{cpufreq_set_policy+79} <ffffffff802df946>{cpufreq_add_dev+806}
<ffffffff802df540>{handle_update+0} <ffffffff802ae21a>{sysdev_driver_register+170}
<ffffffff802df106>{cpufreq_register_driver+198} <ffffffff8010c122>{init+194}
<ffffffff8010f556>{child_rip+8} <ffffffff8010c060>{init+0}
<ffffffff8010f54e>{child_rip+0}
scheduling while atomic: swapper/0x00000001/1
Call Trace:<ffffffff8035014a>{schedule+122} <ffffffff802e2453>{cpufreq_frequency_table_target+371}
<ffffffff8011d60c>{powernowk8_target+1916} <ffffffff802dfdb4>{__cpufreq_driver_target+116}
<ffffffff801be269>{sysfs_new_dirent+41} <ffffffff802e097e>{cpufreq_governor_performance+62}
<ffffffff802dec8d>{__cpufreq_governor+173} <ffffffff802df3a8>{__cpufreq_set_policy+440}
<ffffffff802df5bf>{cpufreq_set_policy+79} <ffffffff802df946>{cpufreq_add_dev+806}
<ffffffff802df540>{handle_update+0} <ffffffff802ae21a>{sysdev_driver_register+170}
<ffffffff802df106>{cpufreq_register_driver+198} <ffffffff8010c122>{init+194}
<ffffffff8010f556>{child_rip+8} <ffffffff8010c060>{init+0}
<ffffffff8010f54e>{child_rip+0}
input: AT Translated Set 2 keyboard//class/input as input1
scheduling while atomic: swapper/0x00000001/1
Call Trace:<ffffffff8035014a>{schedule+122} <ffffffff802e2453>{cpufreq_frequency_table_target+371}
<ffffffff8011cf1b>{powernowk8_target+139} <ffffffff802dfdb4>{__cpufreq_driver_target+116}
<ffffffff801be269>{sysfs_new_dirent+41} <ffffffff802e097e>{cpufreq_governor_performance+62}
<ffffffff802dec8d>{__cpufreq_governor+173} <ffffffff802df417>{__cpufreq_set_policy+551}
<ffffffff802df5bf>{cpufreq_set_policy+79} <ffffffff802df946>{cpufreq_add_dev+806}
<ffffffff802df540>{handle_update+0} <ffffffff802ae21a>{sysdev_driver_register+170}
<ffffffff802df106>{cpufreq_register_driver+198} <ffffffff8010c122>{init+194}
<ffffffff8010f556>{child_rip+8} <ffffffff8010c060>{init+0}
<ffffffff8010f54e>{child_rip+0}
scheduling while atomic: swapper/0x00000001/1
Call Trace:<ffffffff8035014a>{schedule+122} <ffffffff802e2453>{cpufreq_frequency_table_target+371}
<ffffffff8011d60c>{powernowk8_target+1916} <ffffffff802dfdb4>{__cpufreq_driver_target+116}
<ffffffff801be269>{sysfs_new_dirent+41} <ffffffff802e097e>{cpufreq_governor_performance+62}
<ffffffff802dec8d>{__cpufreq_governor+173} <ffffffff802df417>{__cpufreq_set_policy+551}
<ffffffff802df5bf>{cpufreq_set_policy+79} <ffffffff802df946>{cpufreq_add_dev+806}
<ffffffff802df540>{handle_update+0} <ffffffff802ae21a>{sysdev_driver_register+170}
<ffffffff802df106>{cpufreq_register_driver+198} <ffffffff8010c122>{init+194}
<ffffffff8010f556>{child_rip+8} <ffffffff8010c060>{init+0}
<ffffffff8010f54e>{child_rip+0}
Additionally there are some problems with freezing processes by swsusp.
Greetings,
Rafael
next reply other threads:[~2005-10-31 15:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 15:06 Rafael J. Wysocki [this message]
2005-10-31 19:34 ` 2.6.14-git3: scheduling while atomic from cpufreq on Athlon64 Andrew Morton
2005-10-31 19:45 ` Rafael J. Wysocki
2005-10-31 20:42 ` Ashok Raj
2005-11-01 19:07 ` Rafael J. Wysocki
2005-11-01 19:14 ` Ashok Raj
2005-11-01 19:44 ` Rafael J. Wysocki
2005-11-01 20:00 ` Ashok Raj
2005-11-01 19:49 ` Lee Revell
2005-11-04 22:30 ` Andrew Morton
2005-11-05 0:00 ` Ashok Raj
2005-11-05 23:19 ` Ashok Raj
2005-11-05 23:33 ` Andrew Morton
2005-11-05 23:54 ` Ashok Raj
2005-11-06 0:06 ` Andrew Morton
2005-11-06 4:32 ` Keith Owens
2005-10-31 21:42 ` [patch] preempt-trace.patch Ingo Molnar
2005-11-01 19:08 ` Rafael J. Wysocki
2005-11-02 6:27 ` 2.6.14-git3: scheduling while atomic from cpufreq on Athlon64 Dave Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200510311606.36615.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox