| 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
| ||
|
Message-ID: <20061107091628.GA5399@rhlx01.hs-esslingen.de> Date: Tue, 7 Nov 2006 10:16:28 +0100 From: Andreas Mohr <andi@...x01.fht-esslingen.de> To: Thomas Gleixner <tglx@...utronix.de> Cc: Ingo Molnar <mingo@...e.hu>, Len Brown <lenb@...nel.org>, Andreas Mohr <andi@...x01.fht-esslingen.de>, linux-kernel@...r.kernel.org Subject: Re: CONFIG_NO_HZ: missed ticks, stall (keyb IRQ required) [2.6.18-rc4-mm1] Hi, On Tue, Nov 07, 2006 at 09:25:35AM +0100, Thomas Gleixner wrote: > Andreas tested with the latest -mm1-hrt-dyntick patches, so he has all > the checks already. The thing which worries me here is, that we detect > the breakage and use the fallback path already, but it still has this > weird effect on that system, while others just work fine. I'm cooking a > more brute force fallback right now. That's what I didn't understand all that time: I do get the "C2 unusable, kills APIC timer" message, so I expected the code to not use C2, but it seems it did use it (causing hangs) and I didn't fully analyze the code whether it truly tried to prevent C2 here (handling was a bit opaque to me, should have analyzed it more thoroughly to get to know exactly what happens). And like I said, brutally hard-wiring max_cstate to C1 already fixed dynticks things for me, so it seems as if it still touched C2 before. Andreas Mohr - 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/
Powered by blists - more mailing lists