Messages in this thread Patch in this message | | | Date | Wed, 24 Nov 1999 04:59:38 +0100 (CET) | From | Mike Galbraith <> | Subject | Re: Linux 2.2.14pre8 (kmem_grow again) |
| |
On Tue, 23 Nov 1999, Richard A Nelson wrote:
> Now getting kmem_grow erros on both machines (before only on the tr0) box! > > It still seems to be comming from the ipmasq rules. > kmem_grow: Called nonatomically from int - size-128 > kmem_grow: Called nonatomically from int - size-128 > kmem_grow: Called nonatomically from int - size-128 > kmem_grow: Called nonatomically from int - size-128
Hi Richard,
If you (or anyone else who sees it) are willing to go after the cause of this...
Grab ikd for 2.2.13 amd apply it ignoring the two rejects. Then, apply this on top of it.
--- linux-2.2.14-pre8/mm/slab.c.org Wed Nov 24 04:31:55 1999 +++ linux-2.2.14-pre8/mm/slab.c Wed Nov 24 04:35:51 1999 @@ -1186,6 +1186,7 @@ if (in_interrupt() && (flags & SLAB_LEVEL_MASK) != SLAB_ATOMIC) { printk(KERN_ERR "kmem_grow: Called nonatomically from int - %s\n", cachep->c_name); + printk(KERN_ERR "kmem_grow: Called by - %s line %d\n", IDPTR->file, IDPTR->line); flags &= ~SLAB_LEVEL_MASK; flags |= SLAB_ATOMIC; } Save your .config, make mrproper (otherwise, you'll have module symbol troubles) and rebuild with memleak enabled. If finding the caller isn't enough, contact me offline and I'll show you a couple of easy ways to get spiffy call trace info. (or just look at ktrace and/or kdb source:)
-Mike
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |