From: Valdis.Kletnieks@vt.edu
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: next-20130206 cpufreq - WARN in sysfs_add_one
Date: Thu, 07 Feb 2013 14:18:56 -0500 [thread overview]
Message-ID: <3542.1360264736@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 07 Feb 2013 13:11:52 +0530." <CAOh2x=mjTX3hM0uxJh9qk=9OUWqZaAjAV57r2H4AgH+ZjY+eCg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
On Thu, 07 Feb 2013 13:11:52 +0530, Viresh Kumar said:
> First of all i want to confirm something about your system. I am sure it is a
> multi-policy system (or multi cluster system). i.e. there are more than one
> clock line for different cpus ? And so multiple struct policy exist
> simultaneously.
Hmm.. it's a bog-standard Dell Latitude E6500 laptop, with a single
Core2 Duo P8700 CPU (one die, 2 cores, no HT). It's apparently able
to clock both cores at different speeds (one core running busy at 2540mhz
and the other idling at 800mhz), if that's what you mean by multiple
clock lines.
In any case, next-20130206 complained, and with this patch added I see
nothing in dmesg and cpufreq is acting properly on both cores, so:
Tested-By: Valdis Kletnieks <valdis.kletnieks@vt.edu>
(btw - I had to hand-apply your patch, as it showed up white-space
damaged. Three lines wrapped, and tabs converted to spaces).
[-- Attachment #2: Type: application/pgp-signature, Size: 865 bytes --]
next prev parent reply other threads:[~2013-02-07 19:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 17:44 Valdis Kletnieks
2013-02-06 21:24 ` Rafael J. Wysocki
2013-02-07 0:55 ` Valdis.Kletnieks
2013-02-07 1:12 ` Rafael J. Wysocki
2013-02-07 2:03 ` Rafael J. Wysocki
2013-02-07 7:41 ` Viresh Kumar
2013-02-07 19:18 ` Valdis.Kletnieks [this message]
2013-02-08 2:45 ` Viresh Kumar
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=3542.1360264736@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=viresh.kumar@linaro.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®