From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
"Arjan van de Ven" <arjan@infradead.org>
Cc: "Daniel Klaffenbach" <danielklaffenbach@gmail.com>,
"Len Brown" <lenb@kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.25-stable PATCH] regression: powertop says 120K wakeups/sec
Date: Mon, 28 Apr 2008 14:39:30 -0700 [thread overview]
Message-ID: <2c0942db0804281439j492ab98fmf80e5ab669b6c9e1@mail.gmail.com> (raw)
In-Reply-To: <924EFEDD5F540B4284297C4DC59F3DEEF31967@orsmsx423.amr.corp.intel.com>
On Mon, Apr 28, 2008 at 2:13 PM, Pallipadi, Venkatesh
<venkatesh.pallipadi@intel.com> wrote:
> >-----Original Message-----
> >From: Daniel Klaffenbach [mailto:danielklaffenbach@gmail.com]
>
> >Sent: Monday, April 28, 2008 11:01 AM
> >To: Pallipadi, Venkatesh
> >Cc: Len Brown; Linux Kernel Mailing List
> >Subject: Re: [2.6.25-stable PATCH] regression: powertop says
> >120K wakeups/sec
> >
>
>
> >Pallipadi, Venkatesh wrote:
> >> Did C1, C2 work fine with 2.6.24?
> >> Can you send me the full dmesg when it is failing to enter
> >C1, C2 with
> >> latest git + patch.
> >> Output of
> >> #grep . /sys/devices/system/cpu/cpu*/cpuidle/*/*
> >> And also attach the acpidump output (pmtools package here
> >> http://www.lesswatts.org/projects/acpi/utilities.php)
> >No, C1/C2 did not seem to work with 2.6.24 - at least powertop
> >reported 99,9%
> >C0 usage. It was the same behavior as after applying the wakeup patch.
> >However in 2.6.25 and 2.6.25-git11 C1/C2 worked correctly and
> >C2 showed up in
> >pt. But after applying your patch to 2.6.25-git11 they did not:
> >
> >git11:
> >PowerTOP version 1.9 (C) 2007 Intel Corporation
> >Cn Avg residency P-states (frequencies)
> >C0 (cpu running) ( 9,4%) 1,80 Ghz 100,0%
> >C1 0,0ms ( 0,0%) 1,60 Ghz 0,0%
> >C2 0,4ms (90,6%) 800 Mhz 0,0%
> >Wakeups-from-idle per second : 9051,0 interval: 5,0s
> >
> >git11 with wakeup-patch:
> >PowerTOP version 1.9 (C) 2007 Intel Corporation
> >Cn Avg residency P-states (frequencies)
> >C0 (cpu running) (99,9%) 1,80 Ghz 100,0%
> >C1 0,0ms ( 0,0%) 1,60 Ghz 0,0%
> >C2 0,2ms ( 0,1%) 800 Mhz 0,0%
> >Wakeups-from-idle per second : 59,8 interval: 10,0s
> >
> >In both cases the system was idle. I've uploaded the files you wanted:
> >http://www-user.tu-chemnitz.de/~klada/misc/kernel/cpuidle_git11.txt
> >http://www-user.tu-chemnitz.de/~klada/misc/kernel/cpuidle_git11
> >_wakeuppatch.txt
> >http://www-user.tu-chemnitz.de/~klada/misc/kernel/dmesg_git11.txt
> >http://www-user.tu-chemnitz.de/~klada/misc/kernel/dmesg_git11_w
> akeuppatch.txt
> >http://www-user.tu-chemnitz.de/~klada/misc/kernel/nx6125_acpidump.out
> >
> >If there is anything else I can do for debugging this issue
> >please let me
> >know.
> >
>
> With git11+wakeup patch, things seems to be working fine as per
> >http://www-user.tu-chemnitz.de/~klada/misc/kernel/cpuidle_git11_wakeupp
> atch.txt
>
> CPU is spending most of the time in C3 state. Looks like there is some
> problem with
> powertop reporting here. I know there were some changes to this area in
> powertop.
> Can you try the latest powertop version from svn
> (http://www.lesswatts.org/projects/powertop/download.php) and see
> whether the issue is fixed.
I have the same laptop. Powertop (as I'd last tested it) misreports C3
as C2 -- the laptop (nx6125) does not support C2 according to
$ cat /proc/acpi/processor/C000/power
active state: C0
max_cstate: C8
bus master activity: 00000000
maximum allowed latency: 2000 usec
states:
C1: type[C1] promotion[--] demotion[--]
latency[000] usage[21566331] duration[00000000000000000000]
C2: <not supported>
C3: type[C3] promotion[--] demotion[--]
latency[010] usage[20968443] duration[00000000000478095079]
I sent a patch for powertop (
http://www.bughost.org/pipermail/power/2008-February/001306.html ),
but as far as I can see it hasn't been picked up. (Perhaps it's wrong
or incomplete, dunno -- Arjan never replied.) [goes and pulls svn...]
Powertop SVN head (rev 290) still has the problem.
next prev parent reply other threads:[~2008-04-28 21:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 0:15 Len Brown
2008-04-26 1:51 ` [stable] " Greg KH
2008-04-28 10:09 ` Daniel Klaffenbach
2008-04-28 16:36 ` Pallipadi, Venkatesh
2008-04-28 18:01 ` Daniel Klaffenbach
2008-04-28 21:13 ` Pallipadi, Venkatesh
2008-04-28 21:39 ` Ray Lee [this message]
2008-04-29 9:14 ` Daniel Klaffenbach
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=2c0942db0804281439j492ab98fmf80e5ab669b6c9e1@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=arjan@infradead.org \
--cc=danielklaffenbach@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.com \
/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®