linux-kernel - Re: Interrupt latency on some 945GM platforms

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:	Tue, 28 Sep 2010 00:18:01 +0300
From:	Vasily Khoruzhick <anarsoul@...il.com>
To:	Stefan Biereigel <security@...reigel-wb.de>
Cc:	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Sitsofe Wheeler <sitsofe@...oo.com>,
	Venkatesh Pallipadi <venki@...gle.com>,
	intel-gfx@...ts.freedesktop.org, Len Brown <lenb@...nel.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: Interrupt latency on some 945GM platforms

On 26 of September 2010 13:53:35 Stefan Biereigel wrote:

> Hello Everyone,
> just to add on to reports of this problem, there was a Thread here in
> LKML some months ago targeting the same problem (but not really
> attacking it at the Chipset driver). As I have one of those Laptops with
> a 945GM-Chipset and am stuck with the same Problem (disabled tickless
> now as a workaround and set ticks to 1000) I could maybe do some testing
> of patches.
> So what I can summarize is what the others did before: Disabling CPU1
> helps, adding nohz=off helps, changing the Clocksource afterwards helps,
> binding the Interrupt does NOT help.
> So here's the Link to the old Discussion with follow-ups, maybe you can
> get some furter information from there.
> http://linux.derkeiler.com/Mailing-Lists/Kernel/2010-05/msg03696.html
> We targeted the BIOS itself as everyone in this thread happened to own
> an Phoenix BIOS with some special version string.
> best, Stefan

Yep, my laptop has Phoenix BIOS too. Btw, this BIOS has buggy DSDT (thermal 
and battery don't work reliably without patching DSDT). But I tested with and 
without patched DSDT - so my custom DSDT is not cause of bug in my case.
--
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/