Red Hat Bugzilla – Bug 182238
slab: double free detected in cache 'size-64'
Last modified: 2015-01-04 17:25:31 EST
Description of problem:
syslogd sent me a message to my pts over ssh, the message will be as an
attachment. Kernel oops on an SMP machine PII@300MHz Katmai.
Tyan Tahoe 1686D dual processor board, Intel 440FX chipset.
Standard peripherals, Serial, Parallel, USB PS/2 mouse and keyboard.
Version-Release number of selected component (if applicable):
Did not try to reproduce it, as kernel oops aren't common.
I will of course attempt to reproduce it, and post back to this bz entry if so.
Please note in the attachment text, that yum install irssi was the last command
executed, but the yum session and oops were not immediately in succession, I
would have to guess about 15 to 20 minutes later.
Steps to Reproduce:
Idling ssh session to the machine, gkrellmd and a gkrellm client active to the
daemon, is all that was going on.
No additional information at this time.
Created attachment 124947 [details]
Kernel oops output from syslogd
did the full message reach the log on the affected box ? Some lines are missing.
which modules had been in use at the of the oops ? (Or what typically is the
output of lsmod)
Yeah, I'll attach these things below, the
/var/log/messages and lsmod output.
Created attachment 125169 [details]
/var/log/messages, relevant section of kernel logging.
You will see, for reference I have provided just a few lines before, and after
kernel logging at that time.
Created attachment 125170 [details]
Typical output from lsmod.
Is this reproducable with the latest kernel from
I couldn't reproduce this issue with the kernel above.
It seems to be it was a one time thing, could be bad hardware too.
I am not sure, I don't know if bad hardware could cause an error like that.
Anyhow, it was unreproduceable.
Have you tried running memtest86 on that box ?
I just ran memtest on it for a total of one passes, and it showed no errors.
I of course used the Fedora Core 4 disc #1 memtest.
If I need to use another let me know, or if you need any other information.
I've still been unable to duplicate this behavior.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.