> > > That's exactly why I consider the removal a Good Thing. ;-) The only
> > > drawback I see is it would require an actively-maintained SMP hw
> > > compatibility list.
> >
> > And an even more fervishly maintained procmailrc!!! ;)
>
Maciej W. Rozycki wrote...
> Why? Since Linux doesn't work on these boards without the "noapic"
> workaround anyway, I don't expect the number of mails with an ask for help
> to grow. Only the answer would be different.
The machine that started this thread is a single processor Gateway 7450
1U rackmount server with a two processor option.
Using the slightly better apic routing isn't going to make any
difference to its performance. I think being able to avoid unstable
hardware/software interractions when they aren't needed is a great
idea and `noapic' should stay in. This thread should be google-able
shortly and lead people with interrupt problems to the noapic workaround.
I also think that if this is a problem with Gateway's BIOS the best
solution is for them to fix it. I will contact Gateway and see about
that today.
--
Jim Studt, President
The Federated Software Group, Inc.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Jan 15 2002 - 21:00:45 EST