linux-kernel - Re: [PATCH] clocksource: Load the ACPI PM clocksource asynchronously

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]

Date:	Wed, 11 Apr 2012 23:13:05 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Michael Witten <mfwitten@...il.com>
cc:	Arjan van de Ven <arjanvandeven@...il.com>,
	Arjan van de Ven <arjan@...radead.org>,
	John Stultz <johnstul@...ibm.com>, Len Brown <lenb@...nel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] clocksource: Load the ACPI PM clocksource
 asynchronously

On Wed, 11 Apr 2012, Michael Witten wrote:
> On Sun, 8 Apr 2012 19:20:22 -0700, Arjan van de Ven wrote:
> 
> >> to which I bisected as the culprit for very strange load balance
> >> behavior on my machine.
> >>
> >> With this patch in place, my CPU is constantly being pegged at 100%
> >> (and my CPU monitor sometimes registers NaN%), regardless of the
> >> active governor and under conditions when my computer would normally
> >> be idling quite placidly.
> >>
> >> Reverting this commit does indeed remove the problem from previously
> >> problematic builds.
> >>
> >>
> > any chance of a dmesg? (or even better, a diff of the dmesg from
> > abefore and fter)
> 
> Doh! I should have thought of that.
> 
> The dmesg output for a kernel built from your patch's commit yields
> this interesting line:
> 
>   PM-Timer running at invalid rate: 113% of normal - aborting.

Duh. The original code does this with interrupts disabled and not from
the context of some random worker thread.

Aside of that, this will blow up if something else touches the CTC
channel 2, which is possible as this code runs async to other init
stuff.

Arjan, did you ever verify that patch extensivly on hardware which
relies on the PM-Timer? I doubt it. :(

There is no other choice than reverting it.

Thanks,

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