From: hugang <gang_hu@soul.com.cn>
To: Andrew Morton <akpm@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] kmem_cache_grow.
Date: Mon, 15 Apr 2002 16:00:18 +0800 [thread overview]
Message-ID: <20020415160018.012f01dd.gang_hu@soul.com.cn> (raw)
In-Reply-To: <3CBA835D.484DB0B1@zip.com.au>
Thank your. Your are right, I use devfs.
When I disable the devfs, I insert and eject pcmcia card , The linux is fine .
On Mon, 15 Apr 2002 00:38:05 -0700
Andrew Morton <akpm@zip.com.au> wrote:
> hugang wrote:
> >
> > Hell all:
> >
> > Problem: first run "find /" , eject and insert pcmcia network's card, the kernel will crash.
> >
> > Kernel oops: at
> > linux/mm/slab.c->kmem_cache_grow.
> > if (in_interrupt() && (flags & SLAB_LEVEL_MASK) != SLAB_ATOMIC)
> > BUG(); <-- here.
>
> Known problem, I'm afraid. The PCMCIA Card Services layer
> in a number of places is doing stuff from inside a timer
> handler which it should not be.
>
> > Can I remove this check ?
>
> It's best not to, really. It'll probably appear to have
> worked but your kernel could still fail in mysterious ways,
> much later, very occasionally.
>
> If you're using devfs, you could try disabling that. Not
> that this is a devfs bug, but disabling devfs reduces
> the number of functions which the buggy drivers call at
> timer-interrupt time.
>
> The bottom line is that we have a pcmcia_cs staffing shortage.
> Somebody needs to go in, pull out the timers, use schedule_task().
>
> -
>
--
thanks with regards!
hugang.
***********************************
Beijing Soul Technology Co.,Ltd.
Tel:010-68425741/42/43/44
Fax:010-68425745
email:gang_hu@soul.com.cn
web:http://www.soul.com.cn
***********************************
next prev parent reply other threads:[~2002-04-15 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-15 6:40 hugang
2002-04-15 7:38 ` Andrew Morton
2002-04-15 8:00 ` hugang [this message]
2002-04-15 9:16 ` Alan Cox
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=20020415160018.012f01dd.gang_hu@soul.com.cn \
--to=gang_hu@soul.com.cn \
--cc=akpm@zip.com.au \
--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
all inboxes | Powered by JetHome®