From: Arjan van de Ven <arjan@linux.intel.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Steevven1 <steevven1@gmail.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Bug Report for Linux Kernel 3.x
Date: Wed, 24 Aug 2011 08:08:42 -0700 [thread overview]
Message-ID: <4E5513FA.6060904@linux.intel.com> (raw)
In-Reply-To: <20110824135852.GE23979@somewhere>
On 8/24/2011 6:58 AM, Frederic Weisbecker wrote:
> (Please don't top-post)
>
> On Tue, Aug 23, 2011 at 08:21:50PM -0400, Steevven1 wrote:
>> QUICK NOTE - Thanks for replying directly to me as well as the mailing
>> list. I am NOT on that mailing list. Please continue to do this.
>>
>> That is correct about sparse irq. That was causing the first problem,
>> and solving that did in fact result in better power performance, but
>> it was apparently NOT the bulk of the problem.
>>
>> We still have no diagnosis at all for the apparently still-present
>> other (mystery) problem. Powertop now reports to me very low processor
>> wakeups (basically the same as the 2.6-series kernels), which
>> indicates to me that the problem is PROBABLY not related to processor
>> wakeups. I am by no means an expert. The top wakeup-causers with the
>> modified 3.0 kernel (no sparse irq) and an idle system are "[iwlagn]
>> <interrupt>" (wifi), "[i915]<interrupt>" (I don't know what this is),
>> and "[kernel scheduler] Load balancing tick"
>>
>> P-states/frequencies are handled about the same as with the 2.6
>> kernels, so I don't see a problem there either.
>>
>> What else can I check? It seems like powertop is telling me nothing
>> about this mystery power drain.
> Well, if powertop has nothing to tell about that, I have no clue where
> to go. I'm adding more people in Cc in the hope they can be more
> helpful.
>
make sure to use powertop 1.98
next prev parent reply other threads:[~2011-08-24 15:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 23:19 Bug Report for Linux Kernel 3.x Steevven1
2011-08-24 0:11 ` Frederic Weisbecker
2011-08-24 0:21 ` Steevven1
2011-08-24 13:58 ` Frederic Weisbecker
2011-08-24 15:08 ` Arjan van de Ven [this message]
2011-08-24 15:52 ` Anca Emanuel
2011-08-24 16:44 ` Steevven1
2011-08-24 16:46 ` Arjan van de Ven
2011-08-26 6:37 ` Steevven1
2011-08-24 3:58 ` Dave Jones
2011-08-24 4:00 ` Steevven1
2011-08-24 13:25 ` Jeff Chua
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=4E5513FA.6060904@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steevven1@gmail.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.