Bug 155415 - Slab corruption: (Not tainted)
Slab corruption: (Not tainted)
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
4
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Dave Jones
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-20 03:01 EDT by Doug Henderson
Modified: 2015-01-04 17:18 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-04-21 22:08:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
snippet from /var/log/messages (1.26 KB, text/plain)
2005-04-20 03:02 EDT, Doug Henderson
no flags Details
2.6.11-1.1251_FC4 log entires (27.74 KB, text/plain)
2005-04-20 20:30 EDT, Doug Henderson
no flags Details
2.6.11-1.1251_FC4 lsmod output (1.53 KB, text/plain)
2005-04-20 20:32 EDT, Doug Henderson
no flags Details

  None (edit)
Description Doug Henderson 2005-04-20 03:01:21 EDT
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):
kernel-2.6.11-1.1240_FC4

How reproducible:
Didn't try

Steps to Reproduce:

  

Additional info:
Comment 1 Doug Henderson 2005-04-20 03:02:09 EDT
Created attachment 113390 [details]
snippet from /var/log/messages
Comment 2 Dave Jones 2005-04-20 03:17:20 EDT
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).
Comment 3 Doug Henderson 2005-04-20 20:30:05 EDT
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
Comment 4 Doug Henderson 2005-04-20 20:32:06 EDT
Created attachment 113449 [details]
2.6.11-1.1251_FC4 lsmod output

output from lsmod after system booted with build 1251.
Comment 5 Dave Jones 2005-04-20 20:38:42 EDT
does this go away if you boot with selinux=0 ?
Comment 6 Dave Jones 2005-04-20 20:43:17 EDT
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 ?
Comment 7 Doug Henderson 2005-04-20 23:24:16 EDT
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.
Comment 8 Doug Henderson 2005-04-21 22:08:06 EDT
ran memtest86. lots of errors. one of the 512M memory sticks has gone bad. 
Comment 9 Doug Henderson 2005-04-28 02:28:00 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.