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]

Message-ID: <4C8A3131.7030003@gmail.com>
Date:	Fri, 10 Sep 2010 15:22:57 +0200
From:	Artur Skawina <art.08.09@...il.com>
To:	Jiri Slaby <jirislaby@...il.com>
CC:	Thomas Gleixner <tglx@...utronix.de>, Nix <nix@...eri.org.uk>,
	Venkatesh Pallipadi <venki@...gle.com>,
	Damien Wyart <damien.wyart@...e.fr>,
	John Drescher <drescherjm@...il.com>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	LKML <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown
 to unusability (HPET)

On 09/10/10 11:41, Jiri Slaby wrote:
> AFAIU, clocksource=jiffies shouldn't fix this issue. If that's the case
> we have another 2.6.32->2.6.33 regression (and I will report it
> separately). People report the system is unusable (sleepers are not
> woken), unless clocksource=jiffies, clocksource=tsc or nolapic_timer is
> used or a key pressed (i.e. some HW interrupt):
> https://bugzilla.novell.com/show_bug.cgi?id=579932
> (there is also a report with 2.6.35.3 vanilla)

I saw this first in v2.6.35-rc4. The symptom is that suddenly everything
stops and the only way to make things progress is to generate some events.
Apps that are waiting for a timeout aren't woken up unless you press a key
etc. After a few minutes (and lots of key presses ;) ) the machine usually
recovers, leaving no trace in logs.
It's a nasty bug to debug as there's no way to trigger it, at least here,
and it usually does not want to happen when you most want it to; took me
~week to strike a bios upgrade from the suspect list, another one to
exclude intel_idle and so on. Never got around to check 30a564be9d955,
which was on the list too, unfortunately. I'll bet it /is/ the cause, but
won't be able to confirm this for quite a while...

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