Red Hat Bugzilla – Bug 155409
slab: Internal list corruption detected in cache 'avc_node'
Last modified: 2007-11-30 17:11:04 EST
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:
There was no response to Ctrl-Alt-F1 to switch from X session to text console.
It responded to ping from another box, then rebooted.
After reboot, log showed attached messages.
System is also experiencing periodic "slab corruption" errors and "Unable to handle kernel paging request" errors.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 113387 [details]
clipping from /var/log/messages
(In reply to comment #0)
> System is also experiencing periodic "slab corruption" errors and "Unable to
handle kernel paging request" errors.
Do you know if these appear related to SELinux too? How often are you seeing
these, and when did they start?
Can you try running your system with the kernel boot parameter selinux=0 for a
while and see what happens?
Created attachment 113452 [details]
2.6.11-1.1251_FC4 log with slab error
I don't know if this is related the original error I reported against build
I rebooted once with the selinu=0 boot parameter. There seemed to be no
significant difference from booting without that parameter.
I suspect you have a hardware problem, or are for some reason hitting a bug
deeper in the core kernel.
Ran memtest86. Found errors. One of the 512M memory sticks was 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.
in dual channel mode, the theoretical bandwidth across the memory bus increases.
Linux will use as much as the system has, so there's no particular code which
could explain this.
If you bought them as dual-channel capable DIMMs I'd talk to your hardware vendor.
The fact that memtest fails is conclusive that its a hardware fault. It does
nothing but walk through memory flipping bits and reading them back.