From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: andrew hendry <andrew.hendry@gmail.com>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: BUG: using smp_processor_id() in preemptible [00000000] code: ondemand/1327
Date: Sun, 6 Jun 2010 07:46:05 +0200 [thread overview]
Message-ID: <201006060746.05251.maciej.rutecki@gmail.com> (raw)
In-Reply-To: <AANLkTikjZxmlWmDIHuKbNSpz7UfINwvjamyZ-xdFNjzh@mail.gmail.com>
On niedziela, 30 maja 2010 o 10:35:44 andrew hendry wrote:
> Running hdparm -tT /dev/sda gets a similar one.
>
> [ 2705.519946] BUG: using smp_processor_id() in preemptible [00000000]
> code: hdparm/2479
> [ 2705.519948] caller is vfs_quota_sync+0x18c/0x350
> [ 2705.519950] Pid: 2479, comm: hdparm Not tainted 2.6.34 #2
> [ 2705.519951] Call Trace:
> [ 2705.519953] [<ffffffff81288548>] debug_smp_processor_id+0xd8/0xf0
> [ 2705.519956] [<ffffffff8118d21c>] vfs_quota_sync+0x18c/0x350
> [ 2705.519958] [<ffffffff811621c0>] ? sync_one_sb+0x0/0x30
> [ 2705.519960] [<ffffffff811621c0>] ? sync_one_sb+0x0/0x30
> [ 2705.519962] [<ffffffff81162161>] __sync_filesystem+0x41/0xa0
> [ 2705.519964] [<ffffffff811621e0>] sync_one_sb+0x20/0x30
> [ 2705.519966] [<ffffffff8113cd54>] iterate_supers+0x84/0xd0
> [ 2705.519969] [<ffffffff8116221f>] sys_sync+0x2f/0x70
> [ 2705.519971] [<ffffffff8100b0f2>] system_call_fastpath+0x16/0x1b
>
> On Sun, May 30, 2010 at 6:02 PM, andrew hendry <andrew.hendry@gmail.com>
wrote:
> > I get 6 of these logged together about 1 minute after startup on an
> > i7-860. Config attached. Distro is Ubuntu 10.04 64 bit.
> > Is this one known or should I start a bisect?
> >
> > [ 64.924201] BUG: using smp_processor_id() in preemptible [00000000]
> > code: ondemand/1327
> > [ 64.924625] caller is nr_iowait_cpu+0x1a/0x40
> > [ 64.924627] Pid: 1327, comm: ondemand Not tainted 2.6.34 #2
> > [ 64.924629] Call Trace:
> > [ 64.924634] [<ffffffff81288548>] debug_smp_processor_id+0xd8/0xf0
> > [ 64.924637] [<ffffffff81042c7a>] nr_iowait_cpu+0x1a/0x40
> > [ 64.924641] [<ffffffff81089f42>] update_ts_time_stats+0x72/0x90
> > [ 64.924645] [<ffffffff81012759>] ? read_tsc+0x9/0x20
> > [ 64.924647] [<ffffffff81084733>] ? ktime_get+0x63/0xe0
> > [ 64.924650] [<ffffffff8108a162>] get_cpu_idle_time_us+0x52/0x80
> > [ 64.924654] [<ffffffff8140a44c>] cpufreq_governor_dbs+0x1dc/0x430
> > [ 64.924657] [<ffffffff81407af5>] __cpufreq_governor+0xc5/0x190
> > [ 64.924660] [<ffffffff81407552>] ? lock_policy_rwsem_write+0x52/0x90
> > [ 64.924662] [<ffffffff81407d07>] __cpufreq_set_policy+0x147/0x190
> > [ 64.924665] [<ffffffff81408125>] store_scaling_governor+0xe5/0x210
> > [ 64.924667] [<ffffffff81408480>] ? handle_update+0x0/0x20
> > [ 64.924672] [<ffffffff8151dc00>] ? _raw_write_unlock_irq+0x40/0x50
> > [ 64.924675] [<ffffffff814075f7>] store+0x67/0xa0
> > [ 64.924679] [<ffffffff811a1375>] sysfs_write_file+0xe5/0x170
> > [ 64.924682] [<ffffffff8113b088>] vfs_write+0xb8/0x180
> > [ 64.924685] [<ffffffff8113b231>] sys_write+0x51/0x90
> > [ 64.924689] [<ffffffff8100b0f2>] system_call_fastpath+0x16/0x1b
Seems be similar:
http://lkml.org/lkml/2010/5/31/21
Regards
--
Maciej Rutecki
http://www.maciek.unixy.pl
prev parent reply other threads:[~2010-06-06 5:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-30 8:02 andrew hendry
2010-05-30 8:35 ` andrew hendry
2010-06-06 5:46 ` Maciej Rutecki [this message]
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=201006060746.05251.maciej.rutecki@gmail.com \
--to=maciej.rutecki@gmail.com \
--cc=andrew.hendry@gmail.com \
--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
all inboxes | Powered by JetHome®