linux-kernel - Re: Bug Report for Linux Kernel 3.x

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4E5513FA.6060904@linux.intel.com>
Date:	Wed, 24 Aug 2011 08:08:42 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Frederic Weisbecker <fweisbec@...il.com>
CC:	Steevven1 <steevven1@...il.com>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: Bug Report for Linux Kernel 3.x

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/