On Sun, 22 Apr 2001 20:02:54 -0600,
"R. Steve McKown" <smckown@xxxxxxxxxxxxxxxxxx> wrote:
>I decided to check out xfs by using the Redhat 7.1 installer. The
>desktop I decided to rebuild has been running as a general purpose
>productivity/development workstation for many months running first
>RedHat 6.1 then 6.2 with various versions of the 2.2. kernel (most
>recently 2.2.19 final).
>
>Issue 1: See the following erros in syslog rather frequently:
> Apr 22 19:40:33 steve kernel: APIC error on CPU0: 08(01)
Those messages are coming from standard 2.4 kernel code, XFS does not
change any code in that area. As you noted in your message, 2.2 did
not log these errors. 2.4 SMP is more aggressive with cross cpu
messages and can lock hardware that worked under 2.2. Bottom line,
this is a generic 2.4 problem, not XFS related. I suggest that you
take this particular problem to linux-smp@xxxxxxxxxxxxxxx, and include
information about the motherboard chipset.
Adding "nmi_watchdog=1 kdb=on" to the boot line will help with
debugging lockups, especially if you use a serial console. Debugging
lockups is almost impossible under X without a serial console.
>Issue 3: After several hours, I see the following symptoms:
> top: syslogd is consuming 50-100% of a single processor (this is a
>dual-proc pIII)
There is a known bug in syslogd where it loops when fed binary data
from the kernel. AFAIK there is one network card (3com?) that confuses
syslog.
|