From: mikpe@csd.uu.se
To: Rene Rebe <rene.rebe@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APIC error
Date: Thu, 15 May 2003 11:03:04 +0200 [thread overview]
Message-ID: <16067.22472.306565.803037@gargle.gargle.HOWL> (raw)
In-Reply-To: <20030514.221858.846957347.rene.rebe@gmx.net>
Rene Rebe writes:
> HI,
>
> On: Wed, 14 May 2003 14:55:37 +0200,
> mikpe@csd.uu.se wrote:
>
> > > Those errors only seem to happen during high disk-io (SCSI or IDE).
> > > What specific meaning do those errors have? Are they dangerous?
> >
> > They are defined in Intel's IA32 manual set, volume 3,
> > "System Programming Guide", downloadable from developer.intel.com.
> >
> > These errors mean that APIC bus messages are lost or have checksum errors.
> > You don't say which kernel you're using or which chipset, but chances are
> > your mobo's APIC bus is noisy.
> >
> > > Each CPU survives hours in memtest86 ... And with maxcpus=1 it also
> > > does not seem to happen ... The BIOS is latest.
> >
> > You can try booting with "noapic", that should let you keep using SMP
> > while avoiding your possibly buggy APIC bus.
>
> Thanks for the anwer I googled for this before the mail but only found
> much noise ... I'll triy noapic (I thought this would disable SMP,
> too), but I already had to notice that with maxcpus=1 I also get some
> few APIC errors.
>
> Is there drawback in using noapic in SMP mode?
No load balancing of I/O interrupts since they will all be directed to
CPU 0 only. Unless your dual P5 is servicing a lot of interrupts, I doubt
it will make a noticeable difference.
next prev parent reply other threads:[~2003-05-15 8:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 19:31 Rene Rebe
2003-05-14 12:55 ` mikpe
2003-05-14 20:18 ` Rene Rebe
2003-05-15 9:03 ` mikpe [this message]
2003-05-15 10:09 ` Jos Hulzink
2003-05-15 10:25 ` Rene Rebe
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=16067.22472.306565.803037@gargle.gargle.HOWL \
--to=mikpe@csd.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.rebe@gmx.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 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®