From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Description of problem:
I observed a large number of "Slab corruption" error in the previous kernel build.
The 1240 build has fewer instances of the error.
The error often seems to occur when I run yum, and usually yum fails to perform as expected, or crashes.
I have attached a clip from the log showing two consecutive instances.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 113390 [details]
snippet from /var/log/messages
I've added some extra debugging-fu to tomorrows rawhide kernel. Can you try and
repeat it on that one when it appears? You should get a stack trace to go with
the corruption messages.
What modules do you have loaded ? (lsmod output please).
Created attachment 113448 [details]
2.6.11-1.1251_FC4 log entires
Here is the /var/log/messages from reboot on.
About line 218 is a single instance of a Slab corruption error
Created attachment 113449 [details]
2.6.11-1.1251_FC4 lsmod output
output from lsmod after system booted with build 1251.
does this go away if you boot with selinux=0 ?
actually, look more closely at that log
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6f 6b
that last but one entry should be 6b, but we flipped a bit for no reason.
we went from 01101011 to 01101111.
A single bit error like that is very likely to be bad memory.
Can you run memtest86 on this box for a few hours please ?
I rebooted numerous times, seems like about 20, with 5 or 6 useing the selinx=0
parameter. The Slab corruption error showed up in the first reboot after
installing the 1251 build kernel, and finally again in the next to last reboot.
I'll attach a copy when the memtest has run a few hours.
ran memtest86. lots of errors. one of the 512M memory sticks has gone bad.
My system has a Gigabyte K7 Triton GA-7N400-L motherboard, with two 512MB DDR400
sticks of memory. It ran Fedora Core 3 sucessfully from 2004-11 to 2005-04 when
I installed FC4test2. The memory was/is good. I replaced it with a pair of
consecutive serial numbered sticks. The memory tested good one stick at a time
but memtest86 failed on test#5 with two sticks in a dual channel configuration.
It suceeded with the memory in single channel mode.
It appears that FC4test2 contains code which tends to trigger the problem
detected by memtest86's test#5.