From: Duncan <1i5t5.duncan@cox.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Borislav Petkov <bp@alien8.de>, "Rafael J. Wysocki" <rjw@sisk.pl>,
bugzilla-daemon@bugzilla.kernel.org,
Andre Przywara <andre.przywara@linaro.org>,
cpufreq@vger.kernel.org,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
Thomas Renninger <trenn@suse.de>
Subject: Re: [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
Date: Sun, 24 Mar 2013 04:49:27 -0700 [thread overview]
Message-ID: <20130324044927.6a2b1588@ws> (raw)
In-Reply-To: <CAKohpoksBOpW59YETR-SMWJSGsJSWKoXktJoVM38SietN9p3Ug@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3662 bytes --]
On Sun, 24 Mar 2013 15:32:39 +0530
Viresh Kumar <viresh.kumar@linaro.org> wrote:
> Hi Duncan,
>
> Please reply to this mail rather than using bugzilla as all others
> might not be following bugzilla rerport.
Thanks. I'm used to it being the other way 'round.
> >> [PATCH] cpufreq: acpi-cpufreq: Set policy->cpus correctly
> >> from .init()
> >
> > You appear to be on the right path as all the dirs and symlinks are
> > there now, but it looks like you'll need a v2 as the order/pairing
> > is now very strange, both as booted and after a s2ram/resume (which
> > changes the order but it's still strange):
> Hmm.. Can you try one thing? Run 3.8 over your machine and give
> output of cpufreq-info and ls -ld after boot and resume..
>
> I would like to see what's the original behavior.
Good idea! =:^) It now appears that your bug simply cascaded on a
previously unreported bug in earlier kernels.
The 3.8 ls -dl isn't too interesting as they were all dirs not symlinks
then, and if they hadn't stuck around after a suspend/resume I'd have
definitely noticed and reported the bug back then, but it's still
useful to confirm.
The 3.8 pre-suspend and post resume ls -dl are identical -- no missing
dirs (and no symlinks):
/sys/devices/system/cpu/cpu0/cpufreq/
/sys/devices/system/cpu/cpu1/cpufreq/
/sys/devices/system/cpu/cpu2/cpufreq/
/sys/devices/system/cpu/cpu3/cpufreq/
/sys/devices/system/cpu/cpu4/cpufreq/
/sys/devices/system/cpu/cpu5/cpufreq/
The interesting results are the 3.8 cpufreq-info. I'll attach the full
output, but here's the interesting bit:
3.8 pre-suspend cpufreq-info excerpts (nicely paired, as are the
pre-patch pre-suspend results for 3.9-rc):
analyzing CPU 0:
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
analyzing CPU 1:
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 1
analyzing CPU 2:
CPUs which run at the same hardware frequency: 2 3
CPUs which need to have their frequency coordinated by software: 2
analyzing CPU 3:
CPUs which run at the same hardware frequency: 2 3
CPUs which need to have their frequency coordinated by software: 3
analyzing CPU 4:
CPUs which run at the same hardware frequency: 4 5
CPUs which need to have their frequency coordinated by software: 4
analyzing CPU 5:
CPUs which run at the same hardware frequency: 4 5
CPUs which need to have their frequency coordinated by software: 5
3.8 post-resume (screwed up pairing, so that bit's not a 3.9 thing, I
just noticed it in 3.9 due to the now missing symlinks/dirs):
analyzing CPU 0:
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
analyzing CPU 1:
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 1
analyzing CPU 2:
CPUs which run at the same hardware frequency: 2
CPUs which need to have their frequency coordinated by software: 2
analyzing CPU 3:
CPUs which run at the same hardware frequency: 3
CPUs which need to have their frequency coordinated by software: 3
analyzing CPU 4:
CPUs which run at the same hardware frequency: 2 4
CPUs which need to have their frequency coordinated by software: 4
analyzing CPU 5:
CPUs which run at the same hardware frequency: 3 5
CPUs which need to have their frequency coordinated by software: 5
--
Duncan - No HTML messages please, as they are filtered as spam.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
[-- Attachment #2: cpufreq-info.3.8.pre --]
[-- Type: text/plain, Size: 4366 bytes --]
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 4.0 us.
hardware limits: 1.40 GHz - 3.60 GHz
available frequency steps: 3.60 GHz, 3.00 GHz, 2.40 GHz, 1.80 GHz, 1.40 GHz
available cpufreq governors: conservative, performance
current policy: frequency should be within 1.40 GHz and 3.60 GHz.
The governor "conservative" may decide which speed to use
within this range.
current CPU frequency is 1.40 GHz.
cpufreq stats: 3.60 GHz:0.00%, 3.00 GHz:0.20%, 2.40 GHz:0.16%, 1.80 GHz:0.20%, 1.40 GHz:99.44% (4)
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 4.0 us.
hardware limits: 1.40 GHz - 3.60 GHz
available frequency steps: 3.60 GHz, 3.00 GHz, 2.40 GHz, 1.80 GHz, 1.40 GHz
available cpufreq governors: conservative, performance
current policy: frequency should be within 1.40 GHz and 3.60 GHz.
The governor "conservative" may decide which speed to use
within this range.
current CPU frequency is 1.40 GHz.
cpufreq stats: 3.60 GHz:0.03%, 3.00 GHz:0.14%, 2.40 GHz:0.18%, 1.80 GHz:0.35%, 1.40 GHz:99.29% (6)
analyzing CPU 2:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 2 3
CPUs which need to have their frequency coordinated by software: 2
maximum transition latency: 4.0 us.
hardware limits: 1.40 GHz - 3.60 GHz
available frequency steps: 3.60 GHz, 3.00 GHz, 2.40 GHz, 1.80 GHz, 1.40 GHz
available cpufreq governors: conservative, performance
current policy: frequency should be within 1.40 GHz and 3.60 GHz.
The governor "conservative" may decide which speed to use
within this range.
current CPU frequency is 1.40 GHz.
cpufreq stats: 3.60 GHz:0.00%, 3.00 GHz:0.15%, 2.40 GHz:0.15%, 1.80 GHz:0.17%, 1.40 GHz:99.54% (4)
analyzing CPU 3:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 2 3
CPUs which need to have their frequency coordinated by software: 3
maximum transition latency: 4.0 us.
hardware limits: 1.40 GHz - 3.60 GHz
available frequency steps: 3.60 GHz, 3.00 GHz, 2.40 GHz, 1.80 GHz, 1.40 GHz
available cpufreq governors: conservative, performance
current policy: frequency should be within 1.40 GHz and 3.60 GHz.
The governor "conservative" may decide which speed to use
within this range.
current CPU frequency is 1.40 GHz.
cpufreq stats: 3.60 GHz:0.04%, 3.00 GHz:0.11%, 2.40 GHz:0.22%, 1.80 GHz:0.18%, 1.40 GHz:99.45% (4)
analyzing CPU 4:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 4 5
CPUs which need to have their frequency coordinated by software: 4
maximum transition latency: 4.0 us.
hardware limits: 1.40 GHz - 3.60 GHz
available frequency steps: 3.60 GHz, 3.00 GHz, 2.40 GHz, 1.80 GHz, 1.40 GHz
available cpufreq governors: conservative, performance
current policy: frequency should be within 1.40 GHz and 3.60 GHz.
The governor "conservative" may decide which speed to use
within this range.
current CPU frequency is 1.40 GHz.
cpufreq stats: 3.60 GHz:0.00%, 3.00 GHz:0.17%, 2.40 GHz:0.30%, 1.80 GHz:0.20%, 1.40 GHz:99.34% (4)
analyzing CPU 5:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 4 5
CPUs which need to have their frequency coordinated by software: 5
maximum transition latency: 4.0 us.
hardware limits: 1.40 GHz - 3.60 GHz
available frequency steps: 3.60 GHz, 3.00 GHz, 2.40 GHz, 1.80 GHz, 1.40 GHz
available cpufreq governors: conservative, performance
current policy: frequency should be within 1.40 GHz and 3.60 GHz.
The governor "conservative" may decide which speed to use
within this range.
current CPU frequency is 1.40 GHz.
cpufreq stats: 3.60 GHz:0.00%, 3.00 GHz:0.22%, 2.40 GHz:0.15%, 1.80 GHz:0.30%, 1.40 GHz:99.33% (4)
[-- Attachment #3: cpufreq-info.3.8.post --]
[-- Type: text/plain, Size: 4362 bytes --]
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 4.0 us.
hardware limits: 1.40 GHz - 3.60 GHz
available frequency steps: 3.60 GHz, 3.00 GHz, 2.40 GHz, 1.80 GHz, 1.40 GHz
available cpufreq governors: conservative, performance
current policy: frequency should be within 1.40 GHz and 3.60 GHz.
The governor "conservative" may decide which speed to use
within this range.
current CPU frequency is 1.40 GHz.
cpufreq stats: 3.60 GHz:0.00%, 3.00 GHz:0.04%, 2.40 GHz:0.03%, 1.80 GHz:0.04%, 1.40 GHz:99.89% (6)
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 4.0 us.
hardware limits: 1.40 GHz - 3.60 GHz
available frequency steps: 3.60 GHz, 3.00 GHz, 2.40 GHz, 1.80 GHz, 1.40 GHz
available cpufreq governors: conservative, performance
current policy: frequency should be within 1.40 GHz and 3.60 GHz.
The governor "conservative" may decide which speed to use
within this range.
current CPU frequency is 1.40 GHz.
cpufreq stats: 3.60 GHz:0.00%, 3.00 GHz:0.00%, 2.40 GHz:0.08%, 1.80 GHz:0.04%, 1.40 GHz:99.88% (3)
analyzing CPU 2:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 2
CPUs which need to have their frequency coordinated by software: 2
maximum transition latency: 4.0 us.
hardware limits: 1.40 GHz - 3.60 GHz
available frequency steps: 3.60 GHz, 3.00 GHz, 2.40 GHz, 1.80 GHz, 1.40 GHz
available cpufreq governors: conservative, performance
current policy: frequency should be within 1.40 GHz and 3.60 GHz.
The governor "conservative" may decide which speed to use
within this range.
current CPU frequency is 1.40 GHz.
cpufreq stats: 3.60 GHz:0.00%, 3.00 GHz:0.00%, 2.40 GHz:0.00%, 1.80 GHz:0.76%, 1.40 GHz:99.24% (2)
analyzing CPU 3:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 3
CPUs which need to have their frequency coordinated by software: 3
maximum transition latency: 4.0 us.
hardware limits: 1.40 GHz - 3.60 GHz
available frequency steps: 3.60 GHz, 3.00 GHz, 2.40 GHz, 1.80 GHz, 1.40 GHz
available cpufreq governors: conservative, performance
current policy: frequency should be within 1.40 GHz and 3.60 GHz.
The governor "conservative" may decide which speed to use
within this range.
current CPU frequency is 1.40 GHz.
cpufreq stats: 3.60 GHz:0.00%, 3.00 GHz:0.04%, 2.40 GHz:0.04%, 1.80 GHz:0.15%, 1.40 GHz:99.77% (4)
analyzing CPU 4:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 2 4
CPUs which need to have their frequency coordinated by software: 4
maximum transition latency: 4.0 us.
hardware limits: 1.40 GHz - 3.60 GHz
available frequency steps: 3.60 GHz, 3.00 GHz, 2.40 GHz, 1.80 GHz, 1.40 GHz
available cpufreq governors: conservative, performance
current policy: frequency should be within 1.40 GHz and 3.60 GHz.
The governor "conservative" may decide which speed to use
within this range.
current CPU frequency is 1.40 GHz.
cpufreq stats: 3.60 GHz:0.02%, 3.00 GHz:0.03%, 2.40 GHz:0.02%, 1.80 GHz:0.21%, 1.40 GHz:99.71% (4)
analyzing CPU 5:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 3 5
CPUs which need to have their frequency coordinated by software: 5
maximum transition latency: 4.0 us.
hardware limits: 1.40 GHz - 3.60 GHz
available frequency steps: 3.60 GHz, 3.00 GHz, 2.40 GHz, 1.80 GHz, 1.40 GHz
available cpufreq governors: conservative, performance
current policy: frequency should be within 1.40 GHz and 3.60 GHz.
The governor "conservative" may decide which speed to use
within this range.
current CPU frequency is 1.40 GHz.
cpufreq stats: 3.60 GHz:0.00%, 3.00 GHz:0.04%, 2.40 GHz:0.03%, 1.80 GHz:0.12%, 1.40 GHz:99.81% (4)
next prev parent reply other threads:[~2013-03-24 11:49 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-55411-70601@https.bugzilla.kernel.org/>
[not found] ` <20130319074953.C200811FB80@bugzilla.kernel.org>
2013-03-19 8:50 ` [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram Viresh Kumar
2013-03-22 12:17 ` Rafael J. Wysocki
2013-03-22 12:15 ` Viresh Kumar
2013-03-22 13:12 ` Rafael J. Wysocki
2013-03-22 13:21 ` Borislav Petkov
2013-03-22 12:53 ` Thomas Renninger
2013-03-22 13:43 ` Viresh Kumar
2013-03-22 13:54 ` Borislav Petkov
2013-03-22 14:05 ` Viresh Kumar
2013-03-22 14:11 ` Borislav Petkov
2013-03-22 14:04 ` Thomas Renninger
2013-03-22 14:10 ` Viresh Kumar
2013-03-22 14:13 ` Borislav Petkov
2013-03-24 9:05 ` Thomas Renninger
2013-03-24 9:10 ` Viresh Kumar
2013-03-24 10:02 ` Viresh Kumar
2013-03-24 11:49 ` Duncan [this message]
2013-03-24 12:16 ` Viresh Kumar
2013-03-24 12:23 ` Viresh Kumar
2013-03-25 11:15 ` Duncan
2013-03-25 11:23 ` Viresh Kumar
2013-03-25 13:55 ` Borislav Petkov
2013-03-29 14:14 ` Viresh Kumar
2013-03-24 10:31 ` Borislav Petkov
2013-03-22 15:12 ` More cpufreq breakage Borislav Petkov
2013-03-22 15:13 ` Borislav Petkov
2013-03-22 16:22 ` Viresh Kumar
2013-03-22 16:27 ` Viresh Kumar
2013-03-23 13:45 ` Borislav Petkov
2013-03-23 14:27 ` Rafael J. Wysocki
2013-03-23 14:34 ` Viresh Kumar
2013-03-23 15:16 ` Viresh Kumar
2013-03-23 16:06 ` Borislav Petkov
2013-03-23 17:04 ` Viresh Kumar
2013-03-23 18:50 ` Borislav Petkov
2013-03-24 9:05 ` Viresh Kumar
2013-03-24 10:35 ` Borislav Petkov
2013-03-23 18:35 ` [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram Viresh Kumar
2013-03-18 9:13 [Bug 55411] New: " bugzilla-daemon
2013-03-18 9:21 ` [Bug 55411] " bugzilla-daemon
2013-03-18 9:26 ` bugzilla-daemon
2013-03-18 9:27 ` bugzilla-daemon
2013-03-18 9:38 ` bugzilla-daemon
2013-03-18 9:39 ` bugzilla-daemon
2013-03-18 9:56 ` bugzilla-daemon
2013-03-18 10:40 ` bugzilla-daemon
2013-03-18 11:53 ` bugzilla-daemon
2013-03-18 12:14 ` bugzilla-daemon
2013-03-19 6:16 ` bugzilla-daemon
2013-03-19 7:49 ` bugzilla-daemon
2013-03-19 7:57 ` bugzilla-daemon
2013-03-19 8:23 ` bugzilla-daemon
2013-03-19 8:27 ` bugzilla-daemon
2013-03-19 8:50 ` bugzilla-daemon
2013-03-22 12:10 ` bugzilla-daemon
2013-03-22 12:15 ` bugzilla-daemon
2013-03-22 12:53 ` bugzilla-daemon
2013-03-22 13:05 ` bugzilla-daemon
2013-03-22 13:21 ` bugzilla-daemon
2013-03-22 13:43 ` bugzilla-daemon
2013-03-22 14:03 ` Rafael J. Wysocki
2013-03-22 14:06 ` Viresh Kumar
2013-03-22 13:54 ` bugzilla-daemon
2013-03-22 13:56 ` bugzilla-daemon
2013-03-22 14:04 ` bugzilla-daemon
2013-03-22 14:05 ` bugzilla-daemon
2013-03-22 14:06 ` bugzilla-daemon
2013-03-22 14:10 ` bugzilla-daemon
2013-03-22 14:11 ` bugzilla-daemon
2013-03-22 14:13 ` bugzilla-daemon
2013-03-23 18:35 ` bugzilla-daemon
2013-03-24 9:05 ` bugzilla-daemon
2013-03-24 9:10 ` bugzilla-daemon
2013-03-24 9:48 ` bugzilla-daemon
2013-03-24 10:02 ` bugzilla-daemon
2013-03-24 10:31 ` bugzilla-daemon
2013-03-24 11:49 ` bugzilla-daemon
2013-03-24 12:16 ` bugzilla-daemon
2013-03-24 12:23 ` bugzilla-daemon
2013-03-25 11:15 ` bugzilla-daemon
2013-03-25 11:23 ` bugzilla-daemon
2013-03-25 13:55 ` bugzilla-daemon
2013-03-29 14:14 ` bugzilla-daemon
2013-04-13 17:45 ` bugzilla-daemon
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=20130324044927.6a2b1588@ws \
--to=1i5t5.duncan@cox.net \
--cc=andre.przywara@linaro.org \
--cc=bp@alien8.de \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=rjw@sisk.pl \
--cc=trenn@suse.de \
--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