From: Rik van Riel <riel@redhat.com>
To: Christoph Lameter <cl@linux.com>
Cc: Linux kernel Mailing List <linux-kernel@vger.kernel.org>,
Kyle McMartin <kyle@redhat.com>
Subject: Re: SLUB BUG: check_slab called with interrupts enabled
Date: Thu, 16 Jun 2011 20:22:10 -0400 [thread overview]
Message-ID: <4DFA9E32.1080700@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1106161056450.3738@router.home>
On 06/16/2011 11:57 AM, Christoph Lameter wrote:
> On Thu, 16 Jun 2011, Rik van Riel wrote:
>
>> After backing them out, I got 18 hours of uptime so far.
>>
>> This could just be dumb luck, or it could be some slub vs. kswapd
>> interaction. Or maybe I simply am not triggering the original
>> bug any more because kswapd is now doing all the work, but may
>> still be able to trigger it under more memory pressure...
>
> Could be some memory issue or stack corruption. This is a machine with ECC
> ram right?
Yes it is, 12GB of ECC memory.
Running that much without ECC is probably a bad idea :)
>> Either way, since this could still be dumb luck, I'll let you
>> guys know if/when I see a next crash :)
>
> OK.
30 hours uptime already.
Just a little beyond the "dumb luck" threshold.
However, I suspect the bug may still be there and
the fact that kswapd is doing more work may simply
be hiding it.
--
All rights reversed
prev parent reply other threads:[~2011-06-17 0:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 14:56 SLUB BUG: check_slab called with interrupts enabled Rik van Riel
2011-06-15 15:03 ` Christoph Lameter
2011-06-15 15:16 ` Rik van Riel
2011-06-15 15:45 ` Christoph Lameter
2011-06-15 16:24 ` Rik van Riel
2011-06-16 12:34 ` Rik van Riel
2011-06-16 15:57 ` Christoph Lameter
2011-06-17 0:22 ` Rik van Riel [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=4DFA9E32.1080700@redhat.com \
--to=riel@redhat.com \
--cc=cl@linux.com \
--cc=kyle@redhat.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