mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Huggins-Daines <dhd@eradicator.org>
To: fpieraut@casi.polymtl.ca
Cc: linux-kernel@vger.kernel.org
Subject: Re: Activating APIC on single processor
Date: 28 Dec 2000 12:15:45 -0500	[thread overview]
Message-ID: <87ae9g8o1q.fsf@monolith.cepstral.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10012281242140.9711-100000@thales.casi.polymtl.ca>
In-Reply-To: <fpieraut@casi.polymtl.ca>'s message of "Thu, 28 Dec 2000 17:00:15 GMT"

<fpieraut@casi.polymtl.ca> writes:

> I activate APIC interruption with the configuration of linux kernel
> 2.4.0test-11. In the linux kernel configuration under processor type and
> features I activate "APIC and IO-APIC support on uniprocessor",  and I
> desactivate "Symmetric multi-processing support". The only way I found to
> check APIC activation is looking into /proc/interrupts, no "IO-APIC" can
> be found there. So I read IO-APIC.txt and I suppose there sould be
> conflicts with IRQ of my PCI cards. So I remove all my PCI cards and still
> have no APIC interrupt. 
> Is there another way to check APIC activation? 
> Am-I doing to right things to activate IO-APIC?

You might not actually have an IO-APIC or even a local APIC.  This is
the case with the Mobile PIII for instance (I puzzled over this myself
for a long time).

To find out for sure, run:

grep 'flags.*apic' /proc/cpuinfo

-- 
David Huggins-Daines		-		dhd@eradicator.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-28 17:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-28 18:00 fpieraut
2000-12-28 17:15 ` David Huggins-Daines [this message]
2000-12-28 17:44   ` John Levon
2000-12-28 19:22     ` fpieraut
2000-12-28 18:39 Mikael Pettersson

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=87ae9g8o1q.fsf@monolith.cepstral.com \
    --to=dhd@eradicator.org \
    --cc=fpieraut@casi.polymtl.ca \
    --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

all inboxes | Powered by JetHome®