public inbox for cpufreq@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram
Date: Sun, 24 Mar 2013 09:48:42 +0000 (UTC)	[thread overview]
Message-ID: <20130324094842.397A811F9F4@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-55411-12968@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=55411





--- Comment #31 from Duncan <1i5t5.duncan@cox.net>  2013-03-24 09:48:41 ---
(In reply to comment #28)
> My weekend is already spoiled (due to my bugs :) ) and i don't want to spoil
> yours.

Don't worry about it.  They're all days in the week, to me.  I don't really
have a defined "weekend".  In fact, I had been (somewhat impatiently) grumbling
to myself Friday that I was likely to have to wait until Monday for something
concrete to test, so I'm happy to be demonstrated wrong! =:^)

> [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):

Testing against 3.9-rc4 now.

Patch applied pre-suspend ls -dl as above (original pairing is 0/1, 2/3, 4/5,
with the first always a dir and the second always a symlink to the first, as
seen in comment #0):

/sys/devices/system/cpu/cpu0/cpufreq/
/sys/devices/system/cpu/cpu1/cpufreq -> ../cpu0/cpufreq/
/sys/devices/system/cpu/cpu2/cpufreq/
/sys/devices/system/cpu/cpu3/cpufreq/
/sys/devices/system/cpu/cpu4/cpufreq -> ../cpu3/cpufreq/
/sys/devices/system/cpu/cpu5/cpufreq -> ../cpu2/cpufreq/

Post s2ram/resume cycle:

/sys/devices/system/cpu/cpu0/cpufreq/
/sys/devices/system/cpu/cpu1/cpufreq -> ../cpu0/cpufreq/
/sys/devices/system/cpu/cpu2/cpufreq -> ../cpu4/cpufreq/
/sys/devices/system/cpu/cpu3/cpufreq -> ../cpu5/cpufreq/
/sys/devices/system/cpu/cpu4/cpufreq/
/sys/devices/system/cpu/cpu5/cpufreq/


But I don't know whether it's CPU ordering that's weird, or the cpufreq
ordering.  IOW, I don't know whether it /should/ be 0/1, 2/3, 4/5 or not,
because I don't know whether those numbers actually reflect the hardware so
it's the ordering above that's bad, or if the cpu numbers are just arbitrarily
assigned, and the ordering above reflects the actual hardware, and just looks
strange due to the arbitrary cpu numbering.

Either way, there's the correct number of dirs and links now, but the ordering
is extremely confusing and looks wrong, regardless of whether it actually
corresponds to the hardware or not, something I don't have the ability to
judge.

Thanks! =:^)

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2013-03-24  9:48 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-18  9:13 [Bug 55411] New: sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram 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 [this message]
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
     [not found] <bug-55411-70601@https.bugzilla.kernel.org/>
     [not found] ` <20130319074953.C200811FB80@bugzilla.kernel.org>
2013-03-19  8:50   ` 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
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-23 18:35     ` 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=20130324094842.397A811F9F4@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=cpufreq@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