public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ard van Breemen <ard@kwaak.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [openib-general] Re: possible bug in kmem_cache related code
Date: Thu, 4 May 2006 00:04:17 +0200	[thread overview]
Message-ID: <20060503220417.GI24722@kwaak.net> (raw)
In-Reply-To: <44560FE0.2000004@voltaire.com>

Or Gerlitz wrote:
> However, for the mean time can more people of the openib and
> open iscsi communities set 2.6.17-rcX to see that the issue
> reproduces with my synthetic module and with ib/iscsi code (you
> know this kernel will be out in few weeks from now...)

For what it's worth:
On a dual opteron running 2.6.17-rc2-git6 with reiser4 for 2.6.16
patch:
md layer, raid5 on 4 disks, no other stuff then that.
at 23:38 I said: mdadm --stop /dev/md6
May  2 20:38:27 jip kernel: <5>reiser4[dd(2791)]: disable_write_barrier (fs/reiser4/wander.c:234)[zam-1055]:
May  2 20:38:27 jip kernel: NOTICE: md6 does not support write barriers, using synchronous write instead.
May  2 20:38:27 jip kernel: 
May  3 23:38:19 jip kernel: slab error in kmem_cache_destroy(): cache `raid5/md6': Can't free all objects
May  3 23:38:19 jip kernel: 
May  3 23:38:19 jip kernel: Call Trace: <ffffffff802749cc>{kmem_cache_destroy+156}
May  3 23:38:19 jip kernel:        <ffffffff8044ed71>{shrink_stripes+33} <ffffffff80452993>{stop+51}
May  3 23:38:19 jip kernel:        <ffffffff8045daf5>{do_md_stop+245} <ffffffff80255035>{filemap_nopage+389}
May  3 23:38:19 jip kernel:        <ffffffff8045f648>{md_ioctl+744} <ffffffff802631a0>{do_no_page+576}
May  3 23:38:19 jip kernel:        <ffffffff8035ba14>{blkdev_driver_ioctl+100} <ffffffff8035bc3d>{blkdev_ioctl+493}
May  3 23:38:19 jip kernel:        <ffffffff80369451>{__up_read+33} <ffffffff802826bb>{block_ioctl+27}
May  3 23:38:19 jip kernel:        <ffffffff8028c83a>{do_ioctl+58} <ffffffff8028cb61>{vfs_ioctl+449}
May  3 23:38:19 jip kernel:        <ffffffff8028cbdd>{sys_ioctl+77} <ffffffff802a814b>{do_ioctl32_pointer+11}
May  3 23:38:19 jip kernel:        <ffffffff802a61e2>{compat_sys_ioctl+386} <ffffffff8021c85e>{ia32_sysret+0}
May  3 23:38:19 jip kernel: md: md6 stopped.

Second system, same specs, except running drbd on all sata disks instead of
raid5 (yes, external module):
May  3 15:49:19 localhost kernel: drbd1: drbd_cleanup: (!list_empty(&mdev->data.work.q)) in /usr/src/kernel/tyan-s2891/git/modules/drbd/drbd/drbd_main.c:2173
May  3 15:49:19 localhost kernel: drbd1: lp = ffff81007c4f8888 in /usr/src/kernel/tyan-s2891/git/modules/drbd/drbd/drbd_main.c:2176
May  3 15:49:19 localhost kernel: slab error in kmem_cache_destroy(): cache `drbd_ee_cache': Can't free all objects
May  3 15:49:19 localhost kernel: 
May  3 15:49:19 localhost kernel: Call Trace: <ffffffff802749cc>{kmem_cache_destroy+156}
May  3 15:49:19 localhost kernel:        <ffffffff8807df01>{:drbd:drbd_destroy_mempools+113}
May  3 15:49:19 localhost kernel:        <ffffffff8807f2f2>{:drbd:drbd_cleanup+1074} <ffffffff802484e8>{sys_delete_module+312}
May  3 15:49:19 localhost kernel:        <ffffffff802663b5>{sys_munmap+85} <ffffffff80209b5a>{system_call+126}
May  3 15:49:19 localhost kernel: drbd: kmem_cache_destroy(drbd_ee_cache) FAILED
May  3 15:49:19 localhost kernel: slab error in kmem_cache_destroy(): cache `drbd_req_cache': Can't free all objects
May  3 15:49:19 localhost kernel: 
May  3 15:49:19 localhost kernel: Call Trace: <ffffffff802749cc>{kmem_cache_destroy+156}
May  3 15:49:19 localhost kernel:        <ffffffff8807df24>{:drbd:drbd_destroy_mempools+148}
May  3 15:49:19 localhost kernel:        <ffffffff8807f2f2>{:drbd:drbd_cleanup+1074} <ffffffff802484e8>{sys_delete_module+312}
May  3 15:49:19 localhost kernel:        <ffffffff802663b5>{sys_munmap+85} <ffffffff80209b5a>{system_call+126}
May  3 15:49:19 localhost kernel: drbd: kmem_cache_destroy(drbd_request_cache) FAILED
May  3 15:49:19 localhost kernel: drbd: module cleanup done.


NUMA and such is enabled


-- 
begin  LOVE-LETTER-FOR-YOU.txt.vbs
I am a signature virus. Distribute me until the bitter
end

  reply	other threads:[~2006-05-03 22:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-27  8:40 possible bug in kmem_cache related code Or Gerlitz
2006-04-27 11:19 ` Pekka Enberg
2006-04-27 22:22   ` Christoph Lameter
2006-04-28  6:03     ` Pekka J Enberg
2006-04-28  8:10     ` Pekka J Enberg
2006-04-28 19:24       ` [openib-general] " Or Gerlitz
2006-04-29  6:44         ` Pekka Enberg
2006-05-01 13:40           ` Or Gerlitz
2006-05-03 22:04             ` Ard van Breemen [this message]
     [not found] <OF74DEDEC9.CB33A0DB-ON8725715E.0023266E-8825715E.002874C1@us.ibm.com>
2006-04-28  6:46 ` Christoph Lameter

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=20060503220417.GI24722@kwaak.net \
    --to=ard@kwaak.net \
    --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