"top" generates Floating point exception (core dumped)

Hi,
every time i use "top" i have this message:

top

12:19pm up 274 days, 18:53, 1 user, load average: 0.00, 0.01, 0.00
187 processes: 182 sleeping, 1 running, 4 zombie, 0 stopped
CPU0 states: 6.0% user, 93.0% system, 0.0% nice, 0.0% idle
Floating point exception (core dumped)

againg....
top C

   1:57pm  up 274 days, 20:30,  1 user,  load average: 0.03, 0.03, 0.00
185 processes: 180 sleeping, 1 running, 4 zombie, 0 stopped
CPU states:  0.2% user,  0.6% system,  0.0% nice,  0.4% idle
CPU0 states:  6.0% user, 93.0% system,  0.0% nice,  0.0% idle
Floating point exception

again...

top C

   1:57pm  up 274 days, 20:30,  1 user,  load average: 0.10, 0.04, 0.01
185 processes: 180 sleeping, 1 running, 4 zombie, 0 stopped
CPU states:  0.2% user,  0.6% system,  0.0% nice,  0.4% idle
Floating point exception

i think can help to know that procps is the 2.0.7 version.
the kernel is an 2.4.2-2smp and it is build from source (the redhat source).

Here the kernel settings:


# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
CONFIG_MPENTIUMIII=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_PGE=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_TOSHIBA is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
# CONFIG_E820_PROC is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
CONFIG_1GB=y
# CONFIG_2GB is not set
# CONFIG_3GB is not set
# CONFIG_MATH_EMULATION is not set
# CONFIG_MTRR is not set
CONFIG_SMP=y
CONFIG_HAVE_DEC_LOCK=y

Looking in /proc/cpuinfo all is ok.

Can u help me about this error? can it be an hw error (i look the log but 
dont find anything that can help me)?

bye

Giovanni Stinco

p.s.:sorry for my bad english