xfs
[Top] [All Lists]

ADD 800992 - pagebuf_init call to kmem_cache_create BUG()

To: dxm@xxxxxxxxxxxx
Subject: ADD 800992 - pagebuf_init call to kmem_cache_create BUG()
From: pv@xxxxxxxxxxxxx (lord@xxxxxxx)
Date: Wed, 13 Sep 2000 19:54:43 -0700 (PDT)
Cc: linux-xfs@xxxxxxxxxxx
Reply-to: sgi.bugs.xfs@xxxxxxxxxxxxxxxxx
Sender: owner-linux-xfs@xxxxxxxxxxx
Webexec: webpvupdate,pvincident
Webpv: 192.82.201.52
View Incident: 
http://co-op.engr.sgi.com/BugWorks/code/bwxquery.cgi?search=Search&wlong=1&view_type=Bug&wi=800992

 Status : open                         Priority : 2                         
 Assigned Engineer : dxm               Submitter : dxm                      
*Modified User : lord                 *Modified User Domain : sgi.com       
*Description :
On my test box, I'd been playing with xfs, then
umounted, rmmoded and insmoded the modules. When
pagebuf was insmoded, this kernel BUG() was tripped.

I'll see if I can get some more info on this one.

kmem_cache_destroy: Can't free all objects c116d764
kernel BUG at slab.c:806!

Entering kdb (0xc215e000) Panic: invalid operand

.....


==========================
ADDITIONAL INFORMATION (ADD)
From: lord@xxxxxxx (BugWorks)
Date: Sep 13 2000 07:54:43PM
==========================


> PS. This bug is assigned to me, but if someone else wants
> it/or can shed some light on it, that'd be just peachy.

See my previous add for a way to track this down to specific
pagebufs, although it looks like we are leaking something in
a failed mount case which narrows it down somewhat. If it is
this simple to hit then renabling pagebuf tracing as well as
the previous suggestion will probably even tell you where the
buffers were allocated.

<Prev in Thread] Current Thread [Next in Thread>