Hi,
on a dual Pentium-mmx 233Mhz box (I got for free ...) I get many APIC
errors, like:
APIC error on CPU1: 08(00)
APIC error on CPU0: 02(00)
... ...
I also sometimes got 04(00).
Those errors only seem to happen during high disk-io (SCSI or IDE).
What specific meaning do those errors have? Are they dangerous?
Each CPU survives hours in memtest86 ... And with maxcpus=1 it also
does not seem to happen ... The BIOS is latest.
Sincerely,
Ren? Rebe
--
Ren? Rebe - Europe/Germany/Berlin
[email protected] [email protected]
http://www.rocklinux.org http://www.rocklinux.org/people/rene
http://gsmp.tfh-berlin.de/gsmp http://gsmp.tfh-berlin.de/rene
Rene Rebe writes:
> Hi,
>
> on a dual Pentium-mmx 233Mhz box (I got for free ...) I get many APIC
> errors, like:
>
> APIC error on CPU1: 08(00)
> APIC error on CPU0: 02(00)
> ... ...
>
> I also sometimes got 04(00).
>
> 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.
HI,
On: Wed, 14 May 2003 14:55:37 +0200,
[email protected] 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?
Sincerely,
Ren? Rebe
--
Ren? Rebe - Europe/Germany/Berlin
[email protected] [email protected]
http://www.rocklinux.org http://www.rocklinux.org/people/rene
http://gsmp.tfh-berlin.de/gsmp http://gsmp.tfh-berlin.de/rene
Rene Rebe writes:
> HI,
>
> On: Wed, 14 May 2003 14:55:37 +0200,
> [email protected] 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.
On Thu, 15 May 2003 [email protected] wrote:
> Rene Rebe writes:
> > HI,
> >
> > On: Wed, 14 May 2003 14:55:37 +0200,
> > [email protected] 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.
On my Dual PII 333, KDE 3.1 runs fine with interrupts mapped to both CPUs,
and performance is horrible when only CPU0 receives the interrupts.
Especially moving the timer interrupt to both CPUs makes difference like
night and day.
Jos
Hi,
On: Thu, 15 May 2003 12:09:38 +0200 (CEST),
Jos Hulzink <[email protected]> wrote:
> > 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.
>
> On my Dual PII 333, KDE 3.1 runs fine with interrupts mapped to both CPUs,
> and performance is horrible when only CPU0 receives the interrupts.
>
> Especially moving the timer interrupt to both CPUs makes difference like
> night and day.
Thanks for all your contributions ;-) But with noapic I also get APIC
errors from time to time (altough /etc/intrerrupts shows that the
XT-PIC is used). But anyway the box is not running very reliable in
both modes and processes seg-fault every now and then and sometimes
the box freezed. I'll get rid of the box I got for free and no longer
waste our time ... ;-)
> Jos
Sincerely,
Ren? Rebe
--
Ren? Rebe - Europe/Germany/Berlin
[email protected] [email protected]
http://www.rocklinux.org http://www.rocklinux.org/people/rene
http://gsmp.tfh-berlin.de/gsmp http://gsmp.tfh-berlin.de/rene