All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Malkowski <Eric_Malkowski@adc.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Lisa & Eric Malkowski <malk@charter.net>,
	linux-smp@vger.kernel.org, gordonl@world.std.com
Subject: Re: IBM xSeries 360 4 x Xeon kernel 2.2 problems
Date: Mon, 12 Aug 2002 11:41:02 -0400	[thread overview]
Message-ID: <3D57D70E.F43EE73C@adc.com> (raw)
In-Reply-To: 1029147715.16216.129.camel@irongate.swansea.linux.org.uk

Alan-

Thanks a ton.  This works great.

I realize interrupts are all on the first CPU, but this box will be doing
primarily CPU work for userspace processes.
Not spreading the interrupts across CPUs therefore won't be a problem.

Plus we'll be heading for a 2.4 setup in the future and we'll phase out our 2.2
bound stuff.
We've got 2.4 running on some of these systems also and it's been working fine.

Thanks again,

--
Eric Malkowski
ADC - The Broadband Company

Alan Cox wrote:

> On Mon, 2002-08-12 at 02:29, Lisa & Eric Malkowski wrote:
> > I've tried SMP 2.2.21 and 2.2.21-rc4 and get the same results.  It
> > behaves as if interrupts just aren't occurring at all.  Apparently an
> > APIC table isn't being parsed properly -- the boot messages below can
> > help confirm this.
>
> If so you can boot with "noapic".
>
> Please be aware that the 2.2 kernel does not support PIV SMP,
> Hyperthreading, PIV APIC IRQ load balancing and some other things.
> Actually not working suprises me a little but not vastly.


      reply	other threads:[~2002-08-12 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-12  1:29 IBM xSeries 360 4 x Xeon kernel 2.2 problems Lisa & Eric Malkowski
2002-08-12 10:21 ` Alan Cox
2002-08-12 15:41   ` Eric Malkowski [this message]

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=3D57D70E.F43EE73C@adc.com \
    --to=eric_malkowski@adc.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gordonl@world.std.com \
    --cc=linux-smp@vger.kernel.org \
    --cc=malk@charter.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.