From: Vladimir Dvorak <dvorakv@vdsoft.org>
To: "Brown, Len" <len.brown@intel.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>, Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: APIC error on CPUx
Date: Tue, 23 May 2006 08:44:30 +0200 [thread overview]
Message-ID: <4472AF4E.7010206@vdsoft.org> (raw)
In-Reply-To: <CFF307C98FEABE47A452B27C06B85BB681D44D@hdsmsx411.amr.corp.intel.com>
Brown, Len wrote:
>
>
>
>>The problem goes away with noapic or acpi=off, but of course that also
>>means you don't have IRQs > 15.
>>
>>
>
>"acpi=off" is a superset of "noapic" here, presumably because the
>board doesn't have MPS tables that describe the IOAPIC when ACPI is
>off.
>
>"noapic" is a perfectly reasonable thing to use if you don't
>have a lot of interrupt sources and there is no more sharing
>in PIC mode than IOAPIC mode.
>
>The advantage of using IOAPIC mode is that the system has more interrupt
>pins
>availalble and this allows sharing to be avoided. It also allows
>the system to target the interrupts to any processor when you
>have more than one.
>
>cheers,
>-Len
>
>
>
My experience yesterday:
Server with 'noapic' cannot boot, kernel reports something like "Lost
interrupt: hde" ( it was said by my college, server is not in my
physical control ) . With 'acpi=off' it boots, but errors appear again.
Brief datasheet about the board is here:
http://www.abclinuxu.cz/images/hosting/sr1200.pdf
Vladimir
next prev parent reply other threads:[~2006-05-23 6:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 14:47 APIC error on CPUx Brown, Len
2006-05-22 14:50 ` Andi Kleen
2006-05-23 6:44 ` Vladimir Dvorak [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-24 5:15 Brown, Len
2006-05-24 8:10 ` Mikael Pettersson
2006-05-23 20:16 Brown, Len
2006-05-23 20:37 ` Vladimir Dvorak
2006-05-25 11:51 ` Jan Engelhardt
2006-05-22 7:38 Vladimir Dvorak
2006-05-22 11:15 ` Andi Kleen
2006-05-22 11:58 ` Vladimir Dvorak
2006-05-22 12:03 ` Andi Kleen
2006-05-22 12:19 ` Vladimir Dvorak
2006-05-22 12:31 ` Jan Engelhardt
2006-05-22 12:54 ` Andi Kleen
2006-05-22 13:13 ` Xavier Bestel
2006-05-22 19:44 ` Junio C Hamano
2002-01-13 12:51 Teodor Iacob
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=4472AF4E.7010206@vdsoft.org \
--to=dvorakv@vdsoft.org \
--cc=ak@suse.de \
--cc=jengelh@linux01.gwdg.de \
--cc=len.brown@intel.com \
--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