linux-kernel - Re: 100% C0 with 2.6.25-rc

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: <47BEF0A6.9000405@willies.info>
Date:	Fri, 22 Feb 2008 16:56:22 +0100
From:	Jan Willies <jan@...lies.info>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	linux-acpi@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Venki Pallipadi <venkatesh.pallipadi@...el.com>
Subject: Re: 100% C0 with 2.6.25-rc

Rafael J. Wysocki wrote:
> On Thursday, 21 of February 2008, Jan Willies wrote:
>> Since 2.6.25-rc1 I have a lot of wakeups/s (≈134191,4) and spend 100% in C0.
>> It worked fine with 2.6.24 and commandline nolapic. Without nolapic I had 80k
>> wakeups/s after some time, but not right from the start like now.  
> 
> We have a regression from 2.6.24, apparently interrupts-related.

After a lot of bisecting I've found the bad commit: 

9b12e18cdc1553de62d931e73443c806347cd974 is first bad commit
commit 9b12e18cdc1553de62d931e73443c806347cd974
Author: venkatesh.pallipadi@...el.com <venkatesh.pallipadi@...el.com>
Date:   Thu Jan 31 17:35:05 2008 -0800

    ACPI: cpuidle: Support C1 idle time accounting
    
    Show C1 idle time in /sysfs cpuidle interface. C1 idle time may not
    be entirely accurate in all cases. It includes the time spent
    in the interrupt handler after wakeup with "hlt" based C1. But, it will
    be accurate with "mwait" based C1.


Reverting the commit brings my laptop back to C2.


HTH

- Jan
--
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/