linux-kernel - Re: Why do so many machines need "noapic"?

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: <1190711215.4035.283.camel@chaos>
Date:	Tue, 25 Sep 2007 11:06:55 +0200
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Chuck Ebbert <cebbert@...hat.com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Prakash Punnoor <prakash@...noor.de>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Why do so many machines need "noapic"?

Chuck,

On Thu, 2007-09-13 at 12:38 -0400, Chuck Ebbert wrote:
> On 09/10/2007 03:44 PM, Andi Kleen wrote:
> >> Yes, it has an hpet. And I tried every combination of options I could
> >> think of.
> > 
> >> But, even stranger, x86_64 works (only i386 fails.)
> > 
> > x86-64 has quite different time code (at least until the dyntick patches
> > currently in mm) 
> > 
> > Obvious thing would be to diff the boot messages and see if anything
> > jumps out (e.g. in interrupt routing).  
> > 
> > Or check with mm and if x86-64 is broken there too then it's likely
> > the new time code.
> 
> I reported too soon that x86_64 works. It does not work, it just takes
> a bit longer before it freezes. There are message threads all over the
> place discussing this problem with the HP Pavilion tx 1000, and it seems
> the best workaround is to use the "nolapic" option instead of "noapic".
> Using that, it is totally stable _and_ there are no spurious interrupts
> that would otherwise break USB. Interrupt setup is a bit strange, though:

can you please send me 32 and 64 bit boot logs of mainline and fedora
kernels ?

	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/