From: Joaquim Fellmann <mljf@altern.org>
To: Andrew Morton <akpm@digeo.com>
Cc: Andreas Boman <aboman@nerdfest.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.39 "Sleeping function called from illegal context at slab.c:1374"
Date: 02 Oct 2002 01:24:02 +0200 [thread overview]
Message-ID: <1033514643.451.7.camel@kro> (raw)
In-Reply-To: <3D9A207A.14BFF440@digeo.com>
Le mer 02/10/2002 à 00:23, Andrew Morton a écrit :
> > Call Trace:
> > [__kmem_cache_alloc+255/272]__kmem_cache_alloc+0xff/0x110
> > [get_vm_area+38/256]get_vm_area+0x26/0x100
> > [__vmalloc+75/304]__vmalloc+0x4b/0x130
> > [vmalloc+34/48]vmalloc+0x22/0x30
> > [<e08fe502>]sg_init+0x82/0x130 [sg]
> > [<e09022c7>].rodata.str1.1+0x23/0x2b0 [sg]
> > [<e0903be0>]sg_fops+0x0/0x58 [sg]
> > [<e0903b20>]sg_template+0x0/0x94 [sg]
>
> That is known - sg_init() is blatantly calling vmalloc under
> write_lock_irqsave().
Hye,
is that the same problem ?
Apparently it's not scsi related as the one above:
Debug: sleeping function called from illegal context at slab.c:1374
c72a5f60 c01170b4 c02809c0 c0284df1 0000055e c72dfc80 c01311aa c0284df1
0000055e 00000000 00000400 bffffd24 c72dfc80 c01aebcf c72df960 00000011
c010d142 00000080 000001d0 c72a4000 00000100 bffffd24 bffffc2c 00000000
Call Trace:
[<c01170b4>]__might_sleep+0x54/0x60
[<c01311aa>]kmalloc+0x56/0x214
[<c01aebcf>]capable+0x1b/0x34
[<c010d142>]sys_ioperm+0x82/0x11c
[<c0108a3f>]syscall_call+0x7/0xb
It's from a 2.5.40 pulled from bk.
Regards
--
Joaquim Fellmann
next prev parent reply other threads:[~2002-10-01 23:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 11:34 2.4.39 "Sleeping function called from illegal context at slab.c:1374" Helge Hafting
2002-10-01 11:39 ` Jens Axboe
2002-10-01 18:54 ` Andrew Morton
2002-10-01 21:59 ` Andreas Boman
2002-10-01 22:23 ` Andrew Morton
2002-10-01 22:23 ` Andrew Morton
2002-10-01 23:24 ` Joaquim Fellmann [this message]
2002-10-02 16:24 ` Mike Anderson
2002-10-02 18:44 ` Andreas Boman
2002-10-02 19:31 ` Mike Anderson
2002-10-02 21:21 ` Mike Anderson
2002-10-02 23:53 ` Andreas Boman
2002-10-03 17:17 ` Mike Anderson
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=1033514643.451.7.camel@kro \
--to=mljf@altern.org \
--cc=aboman@nerdfest.org \
--cc=akpm@digeo.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.