linux-kernel - Re: [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (HPET)

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 10 Sep 2010 00:57:19 +0100
From:	Nix <nix@...eri.org.uk>
To:	John Drescher <drescherjm@...il.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Venkatesh Pallipadi <venki@...gle.com>,
	Damien Wyart <damien.wyart@...e.fr>,
	linux-kernel@...r.kernel.org
Subject: Re: [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (HPET)

On 10 Sep 2010, John Drescher spake thusly:

>> John, Damien, you seem to be experiencing this: are you using HPET as
>> your clocksource? Do you also have ICH10 82801JIs, or is this more
>> widespread?
>>
> I am not using hpet as my clocksource.
>
> jmd1 ~ # uname -a
> Linux jmd1 2.6.35-std160-amd64 #2 SMP Fri Aug 13 18:42:02 UTC 2010
> x86_64 Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz GenuineIntel GNU/Linux
> jmd1 ~ # cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> tsc

Hm, interesting. Perhaps the HPET is needed anyway? (That would explain
why my other system, with identical specs to those above and using tsc
as clocksource, was seeing intermittent problems in this area.)

But 82801JI looks like a common factor.
--
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/