From: Andrew Morton <akpm@osdl.org>
To: Jesse Barnes <jbarnes@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-rc1-mm2
Date: Wed, 31 Mar 2004 15:56:26 -0800 [thread overview]
Message-ID: <20040331155626.3f196a18.akpm@osdl.org> (raw)
In-Reply-To: <200403311515.01289.jbarnes@sgi.com>
Jesse Barnes <jbarnes@sgi.com> wrote:
>
> On Wednesday 31 March 2004 12:06 pm, Andrew Morton wrote:
> > So are we to assume that this is the offending process? That the periodic
> > slab reaping code has screwed up?
>
> It looks like it. Disabling the slab cache reaping function allows it to boot
> again.
I suspect that the reap timer is innocent and what we have is simply
scribbled-on slab metadata. Which means it could be anything at all.
One last thing: could you please stick a
printk(KERN_EMERG "destroying slab %s\n", cachep->name);
at the start of slab_destroy()? That'll help narrow it down.
Could you also punt me over the .config? If I can make it happen, the
binary search will find it. But it probably won't happen here.
next prev parent reply other threads:[~2004-03-31 23:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 4:14 2.6.5-rc1-mm2 Andrew Morton
2004-03-18 16:01 ` 2.6.5-rc1-mm2 John Cherry
2004-03-18 20:31 ` USB: gphoto2 hangs, device disconnection oddity (was Re: 2.6.5-rc1-mm2) Sean Neakums
2004-03-19 9:27 ` 2.6.5-rc1-mm2 Marc-Christian Petersen
2004-03-30 19:27 ` 2.6.5-rc1-mm2 Jesse Barnes
2004-03-30 19:36 ` 2.6.5-rc1-mm2 Andrew Morton
2004-03-30 19:44 ` 2.6.5-rc1-mm2 Jesse Barnes
2004-03-31 19:02 ` 2.6.5-rc1-mm2 Jesse Barnes
2004-03-31 20:06 ` 2.6.5-rc1-mm2 Andrew Morton
2004-03-31 23:15 ` 2.6.5-rc1-mm2 Jesse Barnes
2004-03-31 23:56 ` Andrew Morton [this message]
2004-03-31 23:58 ` 2.6.5-rc1-mm2 Jesse Barnes
2004-04-01 0:16 ` 2.6.5-rc1-mm2 Jesse Barnes
2004-04-01 19:28 ` 2.6.5-rc1-mm2 Jesse Barnes
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=20040331155626.3f196a18.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jbarnes@sgi.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
all inboxes | Powered by JetHome®