mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>,
	cpufreq@vger.kernel.org, Arjan van de Ven <arjan@infradead.org>
Subject: Re: Linux 2.6.35-rc3
Date: Sat, 12 Jun 2010 09:34:21 -0700	[thread overview]
Message-ID: <20100612093421.589932c6.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100612095903.GA2951@liondog.tnic>

On Sat, 12 Jun 2010 11:59:03 +0200 Borislav Petkov <bp@alien8.de> wrote:

> From: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Fri, Jun 11, 2010 at 08:01:22PM -0700
> 
> > So give it a good testing.
> 
> This one still triggers the warning below. Now there's supposedly a fix
> at least at http://www.spinics.net/lists/cpufreq/msg01631.html
> 
> Can we get it in anytime soon?
> 
> Thanks.
> 
> [   13.120063] BUG: using smp_processor_id() in preemptible [00000000] code: cpufreq-set/1757
> [   13.120310] caller is nr_iowait_cpu+0x1a/0x30
> [   13.120495] Pid: 1757, comm: cpufreq-set Not tainted 2.6.35-rc3 #2
> [   13.120636] Call Trace:
> [   13.120777]  [<ffffffff811ab552>] debug_smp_processor_id+0xc2/0xdc
> [   13.120919]  [<ffffffff81028e1e>] nr_iowait_cpu+0x1a/0x30
> [   13.120921]  [<ffffffff81062a22>] update_ts_time_stats+0x3c/0x77
> [   13.120925]  [<ffffffff8105e390>] ? ktime_get+0x65/0xbe
> [   13.120927]  [<ffffffff81062c03>] get_cpu_idle_time_us+0x49/0x68
> [   13.120932]  [<ffffffffa0047d20>] cpufreq_governor_dbs+0xeb/0x40f [cpufreq_ondemand]
> [   13.120936]  [<ffffffff81348094>] __cpufreq_governor+0x16b/0x1c6
> [   13.120941]  [<ffffffff8134937a>] __cpufreq_set_policy+0x119/0x156
> [   13.120943]  [<ffffffff813497e6>] store_scaling_governor+0x195/0x1cf
> [   13.120946]  [<ffffffff8134a033>] ? handle_update+0x0/0x13
> [   13.120949]  [<ffffffff8134923f>] store+0x5e/0x80
> [   13.120952]  [<ffffffff811320ac>] sysfs_write_file+0x108/0x144
> [   13.120955]  [<ffffffff810dd3d2>] vfs_write+0xb2/0x153
> [   13.120957]  [<ffffffff810dd536>] sys_write+0x4a/0x71
> [   13.120960]  [<ffffffff8100221b>] system_call_fastpath+0x16/0x1b

Last I heard, Arjan was looking into this.

      reply	other threads:[~2010-06-12 16:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-12  3:01 Linus Torvalds
2010-06-12  9:59 ` Borislav Petkov
2010-06-12 16:34   ` Andrew Morton [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=20100612093421.589932c6.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=bp@alien8.de \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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®