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: Windows password security audit tool. GUI, reports in PDF.

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

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

> On 09/10/10 00:34, Nix wrote:
> > It did: I found a system on which the fault was consistently
> > reproducible. Bisected.

Thanks for doing this! Nice work!

* Artur Skawina <art.08.09@...il.com> [2010-09-10 02:59]:
> I'm seeing this too, except here it happens every couple of days of uptime,
> lasts for a few minutes, and then goes away. Which made bisecting a bit
> impractical... Thank you for doing it. 
> HW is similar; x64 and X58/82801JI/ICH10, tsc clocksrc.
> Did that printk trigger? Empirically confirming that this is the problem
> could take weeks here, as it happens so rarely...

Same here, I have not yet seen the problem with 2.6.35.4 and a max
uptime of 3 or 4 days.

My details are identical: tsc clocksource, x86-64 and X58/82801JI/ICH10.

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