mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jim Studt <jim@federated.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Zwane Mwaikambo <zwane@linux.realnet.co.sz>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Jim Studt <jim@federated.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problem with ServerWorks CNB20LE and lost interrupts
Date: Mon, 14 Jan 2002 10:14:48 -0600 (CST)	[thread overview]
Message-ID: <200201141614.g0EGEmrj011739@core.federated.com> (raw)
In-Reply-To: <Pine.GSO.3.96.1020114164019.16706H-100000@delta.ds2.pg.gda.pl>

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

  reply	other threads:[~2002-01-14 16:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-11 14:53 Zwane Mwaikambo
2002-01-11 14:55 ` Zwane Mwaikambo
2002-01-11 17:32 ` Jim Studt
2002-01-13  9:39   ` Zwane Mwaikambo
2002-01-14  0:29     ` Jim Studt
2002-01-14  6:42       ` Zwane Mwaikambo
2002-01-14  9:10       ` Zwane Mwaikambo
2002-01-14 12:14         ` Maciej W. Rozycki
2002-01-14 13:44           ` Zwane Mwaikambo
2002-01-14 14:19             ` Maciej W. Rozycki
2002-01-14 14:23               ` Zwane Mwaikambo
2002-01-14 14:43                 ` Alan Cox
2002-01-14 15:28                   ` Maciej W. Rozycki
2002-01-14 15:31                     ` Zwane Mwaikambo
2002-01-14 15:49                       ` Maciej W. Rozycki
2002-01-14 16:14                         ` Jim Studt [this message]
2002-01-14 21:04               ` Keith Owens
2002-01-15 11:44                 ` Maciej W. Rozycki
  -- strict thread matches above, loose matches on Subject: below --
2002-01-11  9:22 Jim Studt

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=200201141614.g0EGEmrj011739@core.federated.com \
    --to=jim@federated.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@ds2.pg.gda.pl \
    --cc=zwane@linux.realnet.co.sz \
    /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

all inboxes | Powered by JetHome®