linux-kernel - Re: [REGRESSION from 2.6.23-rc8]

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, 28 Sep 2007 17:10:16 +0200
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Chuck Ebbert <cebbert@...hat.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>, Andi Kleen <ak@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>
Subject: Re: [REGRESSION from 2.6.23-rc8]

On Fri, 2007-09-28 at 11:07 -0400, Chuck Ebbert wrote:
> On 09/26/2007 06:35 PM, Thomas Gleixner wrote:
> > It's even worse than I thought on the first check:
> > 
> > "noapictimer" on the command line of an SMP box prevents _ONLY_ the boot
> > CPU apic timer from being used. But the secondary CPU is still
> > unconditionally setting up the APIC timer and uses the non calibrated
> > variable calibration_result, which is of course 0, to setup the APIC
> > timer. Wreckage guaranteed.
> > 
> 
> Is this why I get 1000 spurious interrupts/second on IRQ7 when booting
> x86_64 with "noapic"?

No, thats a different problem. The wreckage is a stuck local apic timer
interrupt.

	tglx


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