public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg <graycardinal@pisem.net>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-kernel@vger.kernel.org, manfred@colorfullife.com
Subject: Re[2]: PROBLEM: kmem_cache_create: duplicate cache fat_cache
Date: Fri, 20 May 2005 18:31:27 +0400	[thread overview]
Message-ID: <200505201831.27842.graycardinal@pisem.net> (raw)
In-Reply-To: <87br779jen.fsf@devron.myhome.or.jp>

On Thursday 19 May 2005 22:10, you wrote:
> Oleg <graycardinal@pisem.net> writes:
> > [1.] kmem_cache_create: duplicate cache fat_cache
> > [2.] When I load module vfat, I'm have BUG. vfat is embedded in my
> > kernel. [3.] modules
> > [4.] Linux version 2.6.12-rc3-mm3 (root@localhost.localdomain) (gcc
> > version 3.3.2 20031022 (Red Hat Linux 3.3.2-1)) #18 SMP
> > [5.] kmem_cache_create: duplicate cache fat_cache
> > ------------[ cut here ]------------
> > kernel BUG at mm/slab.c:1491!
> > invalid operand: 0000 [#1]
> > PREEMPT SMP
> > Modules linked in: fat nls_utf8 nls_cp866 nls_cp855 video hotkey
> > CPU:    0
> > EIP:    0060:[<c014a38f>]    Not tainted VLI
> > EFLAGS: 00010202   (2.6.12-rc3-mm3)
> > EIP is at kmem_cache_create+0x45f/0x5e0
> > eax: 00000030   ebx: f7d187b4   ecx: 0000000d   edx: 00000202
> > esi: c03c91ef   edi: f885ed6e   ebp: f7de1580   esp: f74d1f44
> > ds: 007b   es: 007b   ss: 0068
> > Process modprobe (pid: 2487, threadinfo=f74d0000 task=f7eef090)
> > Stack: c03c6f80 f885ed64 00000004 00020000 f74d1f6c f7de15d8 000000a9
> > c0000000 fffffffc 00000004 00000010 f8862540 00000000 0804e130 f74d0000
> > f8806037 f885ed64 00000014 00000000 00020000 f8857000 00000000 f88060e5
> > c013a8f4 Call Trace:
> >  [<f8806037>] fat_cache_init+0x37/0x80 [fat]
> >  [<f8857000>] init_once+0x0/0x20 [fat]
> >  [<f88060e5>] init_fat_fs+0x5/0xc [fat]
> >  [<c013a8f4>] sys_init_module+0x124/0x1a0
> >  [<c0103175>] syscall_call+0x7/0xb
> > Code: 00 04 00 74 ec e9 8a 01 00 00 8b 4c 24 40 c7 04 24 80 6f 3c c0 89
> > 4c 24 04 e8 4e 44 fd ff f0 ff 05 ac d2 50 c0 0f 8e 73 1a 00 00 <0f> 0b d3
> > 05 95 65 3c c0 8b 0b e9 65 ff ff ff 8b 47 50 c7 04 24
>
> [...]
>
> > [7.7.] module vfat && embedded vfat normal situation, and I'm don't like
> > BUG in my dmesg... Sorry, I'm from Russia.
>
> Ummm... why is this normal situation? Didn't you run the
> modules_install after changed .config?  Anyway, this patch returns
> NULL instead of calling BUG().  This case seems to also happen with
> user error.
>
> Manfred, what do you think of this?

Thank you, but "goto opps", not "goto oops" in patch. 
>Didn't you run the  modules_install after changed .config?
No, I'm don't run modules_install. I'm build all modules first and use it (if required) for all my kernel's... And I have one init script, where :
...
/sbin/modprobe vfat
...
I want test to load any modules. Why not ?




  reply	other threads:[~2005-05-20 11:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-18  8:17 PROBLEM: kmem_cache_create: duplicate cache fat_cache Oleg
2005-05-19 18:10 ` OGAWA Hirofumi
2005-05-20 14:31   ` Oleg [this message]
2005-05-20 13:16     ` OGAWA Hirofumi
2005-06-06 19:43   ` Manfred Spraul
2005-06-07 14:26     ` OGAWA Hirofumi

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=200505201831.27842.graycardinal@pisem.net \
    --to=graycardinal@pisem.net \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    /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