public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Klaffenbach <danielklaffenbach@gmail.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: "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 20:01:00 +0200	[thread overview]
Message-ID: <200804282001.06680.danielklaffenbach@gmail.com> (raw)
In-Reply-To: <924EFEDD5F540B4284297C4DC59F3DEEF31621@orsmsx423.amr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1921 bytes --]

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_wakeuppatch.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.

- Daniel

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-04-28 18:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-25  0:15 [2.6.25-stable PATCH] regression: powertop says 120K wakeups/sec 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 [this message]
2008-04-28 21:13       ` Pallipadi, Venkatesh
2008-04-28 21:39         ` Ray Lee
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=200804282001.06680.danielklaffenbach@gmail.com \
    --to=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