This is a discussion on Re: Why do so many machines need "noapic"? - Kernel ; 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. > > ...
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
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/