From: Andrew Morton <akpm@linux-foundation.org>
To: Ingo Oeser <ioe-lkml@rameria.de>
Cc: Andi Kleen <andi@firstfloor.org>,
Chuck Ebbert <cebbert@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Why do so many machines need "noapic"?
Date: Sat, 15 Sep 2007 04:08:02 -0700 [thread overview]
Message-ID: <20070915040802.bb3c7093.akpm@linux-foundation.org> (raw)
In-Reply-To: <200709151258.28745.ioe-lkml@rameria.de>
On Sat, 15 Sep 2007 12:58:27 +0200 Ingo Oeser <ioe-lkml@rameria.de> wrote:
> On Saturday 15 September 2007, Andrew Morton wrote:
> > There are 48 bugs in bugzilla which mention "noapic"
> >
> > http://bugzilla.kernel.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=noapic&kernel_version_type=allwordssubstr&kernel_version=&bug_status=NEW&bug_status=REOPENED&bug_status=ASSIGNED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=®ression=both&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=
> >
> > And there are 173,000 on the internet ;)
> > http://www.google.com/search?hl=en&q=linux+noapic&btnG=Google+Search
> >
> > We screwed this pooch a long time ago - years. Perhaps if some of the many
> > noapic users could run a bisection search to work out when it broke we
> > could start fixing things. But they all have a workaround so there's no
> > motivation.
>
> I have 2 SMP-Boards and both need noapic. One is from 2001 (AUSUS CUR-DLS),
> one is from June 2006 (Gigabyte M57SLI-S4).
>
> There are many reasons:
>
> 1. Bugs which have such a simple workaround don't get much attention.
>
> 2. Usually SMP boards are used for machines, which just HAVE to work,
> since they have been expensive. These are not consumer boards.
>
> 3. I usually had only USB problems (no IRQ), if ommiting noapic.
> USB technology is a cosumer grade technology and enterprise
> grade developers don't have much interest in it (until now?).
>
> 4. IRQ routing setup is often a BIOS issue. You might be able
> to fix that by upgrading your BIOS. That often needs a Windows
> tool. Linux people not always (want to) have access to Windows :-)
>
> I reported the all the problems (starting 2001), no developer
> seemed interested.
>
> I can report them against the latest RC6 kernel tomorrow and put them
> into bugzilla, if we now REALLY care.
>
I believe that about two years ago we broke something which caused quite a
large number of people to need noapic. Is that the case with any of your
machines? Do you know if they run 2.6.ancient without noapic?
Thanks.
next prev parent reply other threads:[~2007-09-15 11:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 23:30 Why do so many machines need "noapic"? Chuck Ebbert
2007-09-06 11:31 ` Andi Kleen
2007-09-07 19:34 ` Chuck Ebbert
2007-09-08 5:17 ` Prakash Punnoor
2007-09-10 19:12 ` Chuck Ebbert
2007-09-10 19:44 ` Andi Kleen
2007-09-10 23:33 ` Chuck Ebbert
2007-09-13 16:38 ` Chuck Ebbert
2007-09-25 9:06 ` Thomas Gleixner
2007-09-15 7:39 ` Andrew Morton
2007-09-15 10:58 ` Ingo Oeser
2007-09-15 11:08 ` Andrew Morton [this message]
2007-09-15 12:08 ` Matthew Garrett
2007-09-24 21:32 ` Dave Jones
2007-09-27 22:03 ` Phillip Susi
2007-09-15 18:42 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2007-09-08 4:12 Al Boldi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070915040802.bb3c7093.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=cebbert@redhat.com \
--cc=ioe-lkml@rameria.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox