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: <49C28494.5030403@shakaweb.org>
Date:	Thu, 19 Mar 2009 18:44:52 +0100
From:	Christopher Schramm <debian@...kaweb.org>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Yinghai Lu <yinghai@...nel.org>,
	"Maciej W. Rozycki" <macro@...ux-mips.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: APIC problem report

Ingo Molnar schrieb:
> By the looks of it, chances are that various APIC fixes and 
> robustization patches might have fixed your problem:
> 
>  691874f: x86: I/O APIC: timer through 8259A second-chance
>  03be750: x86: I/O APIC: keep the timer IRQ masked during set-up
>  24742ec: x86: I/O APIC: unmask the second-chance timer interrupt
>  d11d579: x86: I/O APIC: AEOI timer acknowledgement clean-ups
> 
> These first showed up in v2.6.27. Which would match your reported 
> symptoms of v2.6.26 failig and 2.6.28 working.

Yes, you're right. Looking at the detailed kernel messages, the "8259A 
second-chance" seems to do the trick. So it's already tackled. :-)

Christopher
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ