David Wragg wrote:
>
> I'm testing XFS (from CVS as of sometime yesterday) on a machine with
> 1GB memory and the kernel built with CONFIG_HIGHMEM. The kernel
> contains code of my own which is provoking the problem, though it
> isn't the root cause.
Hi,
I'm using XFS on a SMP machine with 2 GB, also built with
CONFIG_HIGHMEM. I'm receiving these errors after the machine has been up
for a while. I didn't have this problem with the standard 2.4.0 kernel
or with a 2.2.18 kernel. Or my memory is suddenly faulty, or perhaps
there is a problem with the 2.4.0-XFS kernel. Can anyone help me here?
It's a redhat7 box, all the latest patches applied, 2.4.0-XFS kernel
from cvs (from 30 januari) build with kgcc.
snippet from /var/log/messages:
Jan 30 17:01:49 molgen kernel: Uhhuh. NMI received. Dazed and confused,
but trying to continue
Jan 30 17:01:49 molgen kernel: Uhhuh. NMI received. Dazed and confused,
but trying to continue
Jan 30 17:01:49 molgen kernel: You probably have a hardware problem with
your RAM chips
Jan 30 17:01:49 molgen kernel: You probably have a hardware problem with
your RAM chips
I've placed /var/log/dmesg online for some more information about my
system:
http://molgen.biol.rug.nl/dmesg
some information about mounted partitions:
[root@molgen html]# mount
/dev/hda8 on / type ext2 (rw)
none on /proc type proc (rw)
/dev/hda1 on /boot type ext2 (rw)
/dev/hda6 on /home type ext2 (rw)
/dev/hda5 on /usr type ext2 (rw)
/dev/hda7 on /var type ext2 (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda1 on /mnt/sda1 type ext2 (rw)
/dev/sdb1 on /mnt/sdb1 type xfs (rw)
--
Ing. Aldert Zomer, | Tel: +31 50 36 32 360
Research Technician, | Fax: +31 50 36 35 205
IMEnz Bioengineering, | Email: zomeral@xxxxxxxxxxx
PO BOX 14, 9750 AA Haren, Netherlands | Homepage: http://www.imenz.com
------------------------------------------------------------------------
Automated Medline search:
http://molgen.biol.rug.nl/cgi-bin/biomail/users.pl
|