public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik Mouw <erik@harddisk-recovery.com>
To: linux-scsi@vger.kernel.org
Subject: [BUG 2.6.17-git] kmem_cache_create: duplicate cache scsi_cmd_cache
Date: Thu, 11 May 2006 17:14:57 +0200	[thread overview]
Message-ID: <20060511151456.GD3755@harddisk-recovery.com> (raw)

Hi,

While playing with libata in 2.6.17-git from today, I got this bug:

SCSI subsystem initialized
libata version 1.20 loaded.
sata_promise 0000:02:05.0: version 1.04
kmem_cache_create: duplicate cache scsi_cmd_cache
 <c0159591> kmem_cache_create+0x331/0x390
 <e0924371> scsi_setup_command_freelist+0x71/0xf0 [scsi_mod]
 <e092588e> scsi_host_alloc+0x17e/0x270 [scsi_mod]
 <e08fd061> ata_host_add+0x41/0xc0 [libata]
 <c0148c9f> __kzalloc+0x1f/0x50
 <e08fd190> ata_device_add+0xb0/0x240 [libata]
 <e0839baf> pdc_ata_init_one+0x27f/0x330 [sata_promise]
 <c01dd1a9> pci_call_probe+0x19/0x20
 <c01dd20e> __pci_device_probe+0x5e/0x70
 <c01dd24f> pci_device_probe+0x2f/0x50
 <c0220977> driver_probe_device+0xb7/0xe0
 <c02b338a> klist_dec_and_del+0x1a/0x20
 <c0220a30> __driver_attach+0x0/0x90
 <c0220aa1>__driver_attach+0x71/0x90
 <c021fd49> bus_for_each_dev+0x69/0x80
 <c0220ae6> driver_attach+0x26/0x30
 <c0220a30> __driver_attach+0x0/0x90
 <c02202a3> bus_add_driver+0x83/0xc0
 <c01dd4ed> __pci_register_driver+0x4d/0x70
 <e0880017> pdc_ata_init+0x17/0x1b [sata_promise]
 <c013a1a0> sys_init_module+0x120/0x1b0
 <c0102f27> syscall_call+0x7/0xb

How to recreate:

- fully modular scsi and libata
- modprobe sata_promise ; modprobe sd_mod
- rmmod sd_mod ; rmmod sata_promise ; rmmod libata ; rmmod scsi_mod
- modprobe sata_promise

At first glance Looks to me like scsi_mod forgot to delete the
scsi_cmd_cache at module unload. Note that I can only trigger the bug
when there are devices connected to the SATA controller.

It doesn't look libata related, cause I can also trigger it using the
sym53c8xx driver:

SCSI subsystem initialized
sym0: <895> rev 0x1 at pci 0000:02:06.0 irq 17
kmem_cache_create: duplicate cache scsi_cmd_cache
 <c0159591> kmem_cache_create+0x331/0x390
 <e0924371> scsi_setup_command_freelist+0x71/0xf0 [scsi_mod]
 <e092588e> scsi_host_alloc+0x17e/0x270 [scsi_mod]
 <c011e697> printk+0x17/0x20
 <e09493e5> sym_attach+0x75/0x3d0 [sym53c8xx]
 <e0949d99> sym2_probe+0xc9/0x130 [sym53c8xx]
 <c01dd1a9> pci_call_probe+0x19/0x20
 <c01dd20e> __pci_device_probe+0x5e/0x70
 <c01dd24f> pci_device_probe+0x2f/0x50
 <c0220977> driver_probe_device+0xb7/0xe0
 <c02b338a> klist_dec_and_del+0x1a/0x20
 <c0220a30> __driver_attach+0x0/0x90
 <c0220aa1> __driver_attach+0x71/0x90
 <c021fd49> bus_for_each_dev+0x69/0x80
 <c0220ae6> driver_attach+0x26/0x30
 <c0220a30> __driver_attach+0x0/0x90
 <c02202a3> bus_add_driver+0x83/0xc0
 <c01dd4ed> __pci_register_driver+0x4d/0x70
 <e083903a> sym2_init+0x3a/0x5b [sym53c8xx]
 <c013a1a0> sys_init_module+0x120/0x1b0
 <c0102f27> syscall_call+0x7/0xb


Erik

-- 
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands

             reply	other threads:[~2006-05-11 15:14 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-11 15:14 Erik Mouw [this message]
2006-05-12  4:53 ` [BUG 2.6.17-git] kmem_cache_create: duplicate cache scsi_cmd_cache Or Gerlitz
2006-05-12 17:16   ` Erik Mouw
2006-05-12 17:27     ` Andrew Vasquez
2006-05-12 20:18       ` Erik Mouw
2006-05-12 17:36     ` Linus Torvalds
2006-05-12 17:47       ` James Bottomley
2006-05-12 18:58         ` James Bottomley
2006-05-12 19:09           ` Linus Torvalds
2006-05-12 20:38             ` Russell King
2006-05-12 20:50               ` Linus Torvalds
2006-05-12 20:58                 ` Russell King
2006-05-12 21:27                   ` Linus Torvalds
2006-05-12 21:46                     ` Linus Torvalds
2006-05-12 21:51                     ` Russell King
2006-05-12 22:15                       ` Linus Torvalds
2006-05-12 22:37                         ` Linus Torvalds
2006-05-12 23:57                           ` Greg KH
2006-05-14 16:01                             ` Russell King
2006-05-12 21:18                 ` Greg KH
2006-05-12 21:32                   ` Linus Torvalds
2006-05-12 22:45                     ` Greg KH
2006-05-12 20:52               ` Greg KH
2006-05-12 21:03                 ` Russell King
2006-05-12 21:34                   ` Greg KH
2006-05-12 21:39                   ` Al Viro
2006-05-12 20:30           ` Erik Mouw
2006-05-12 20:37           ` Russell King
2006-05-12 20:21       ` Erik Mouw
2006-05-12 20:34       ` Russell King
2006-05-12 21:43         ` Al Viro
2006-05-12 21:55           ` Russell King
2006-05-12 22:08             ` Al Viro
2006-05-12 22:22               ` Linus Torvalds
2006-05-12 22:28                 ` Al Viro
2006-05-12 22:48                   ` Al Viro
2006-05-12 22:51                     ` Al Viro
2006-05-12 23:04                       ` Linus Torvalds
2006-05-12 23:21                         ` Al Viro
2006-05-12 23:37                           ` Al Viro
2006-05-12 23:50                             ` Linus Torvalds
2006-05-13  0:20                               ` Al Viro
2006-05-24 14:07                               ` Erik Mouw
2006-05-13  0:08                   ` Greg KH
2006-05-12 22:37                 ` Russell King
2006-05-12 21:58           ` Al Viro

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=20060511151456.GD3755@harddisk-recovery.com \
    --to=erik@harddisk-recovery.com \
    --cc=linux-scsi@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