From: Dave Jones <davej@redhat.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: signal_cache slab corruption.
Date: Thu, 16 Mar 2006 15:50:56 -0500 [thread overview]
Message-ID: <20060316205056.GA11091@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0603162013350.25141@goblin.wat.veritas.com>
On Thu, Mar 16, 2006 at 08:29:08PM +0000, Hugh Dickins wrote:
> I'd be interested in the signal_cache line from your /proc/slabinfo,
> to see what cachep->num is usually in your configuration. But it's
> an idle interest: I won't have anything interesting to say, whatever
> it is...
after 3 days of uptime on a slightly newer kernel..
signal_cache 134 143 696 11 2 : tunables 32 16 8 : slabdata 13 13 0 : globalstat 98892 176 173 156 0 0 129 940 : cpustat 19802 17821 36683 2
the other had seen a little more abuse. These last three days, that
box has been quite idle most of the time, whereas the box that crashed
was my workhorse for most of last week.
Dave
--
http://www.codemonkey.org.uk
prev parent reply other threads:[~2006-03-16 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 18:15 signal_cache slab corruption Dave Jones
2006-03-14 9:22 ` Hugh Dickins
2006-03-14 17:01 ` Dave Jones
2006-03-16 20:29 ` Hugh Dickins
2006-03-16 20:50 ` Dave Jones [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060316205056.GA11091@redhat.com \
--to=davej@redhat.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox