From: Xavier Bestel <xavier.bestel@free.fr>
To: Andi Kleen <ak@suse.de>
Cc: Vladimir Dvorak <dvorakv@vdsoft.org>, linux-kernel@vger.kernel.org
Subject: Re: APIC error on CPUx
Date: Mon, 22 May 2006 15:13:04 +0200 [thread overview]
Message-ID: <1148303583.26628.167.camel@capoeira> (raw)
In-Reply-To: <200605221454.05874.ak@suse.de>
On Mon, 2006-05-22 at 14:54, Andi Kleen wrote:
> > Can "noapic" or "nolapic" solve this ? Does it mean ( with these
> > parameters ) that devices will start to use 8259 interrupt controller
> > instead APIC ?
>
> nolapic won't work on SMP (or rather forced UP mode)
>
> You'll not see the messages anymore, but might get silent corruption.
> Or it might work around it because it will make everything a bit slower.
>
> >
> > Is harmfull put "noapic" on "nolapic" to cmdline ?
>
> If all devices can still be accessed noapic is just slower.
So, is there a software solution to this problem ?
I have the same one on an old Dell server.
Thanks,
Xav
next prev parent reply other threads:[~2006-05-22 13:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 7:38 APIC error on CPUx 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 [this message]
2006-05-22 19:44 ` Junio C Hamano
-- 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 14:47 Brown, Len
2006-05-22 14:50 ` Andi Kleen
2006-05-23 6:44 ` Vladimir Dvorak
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=1148303583.26628.167.camel@capoeira \
--to=xavier.bestel@free.fr \
--cc=ak@suse.de \
--cc=dvorakv@vdsoft.org \
--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