From: Andrew Morton <akpm@osdl.org>
To: "Mike Black" <mblack@csi-inc.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: 2.1.6 st.o sleeping invalid context
Date: Fri, 23 Jan 2004 14:32:08 -0800 [thread overview]
Message-ID: <20040123143208.54b4f962.akpm@osdl.org> (raw)
In-Reply-To: <000701c3e1a6$ac762330$c8de11cc@black>
"Mike Black" <mblack@csi-inc.com> wrote:
>
> Testing 2.6.1 and got the following message during boot -- apparently when loading the st.o module -- although the modules still
> loads successfully.
>
> Jan 23 06:41:49 yeti kernel: Debug: sleeping function called from invalid context at mm/slab.c:1856
> Jan 23 06:41:49 yeti kernel: in_atomic():1, irqs_disabled():0
> Jan 23 06:41:49 yeti kernel: Call Trace:
> Jan 23 06:41:49 yeti kernel: [<c011da0c>] __might_sleep+0xab/0xc9
> Jan 23 06:41:49 yeti kernel: [<c0142a4a>] kmem_cache_alloc+0x74/0x76
> Jan 23 06:41:49 yeti kernel: [<c0162e81>] cdev_alloc+0x24/0x5e
> Jan 23 06:41:49 yeti kernel: [<f8871743>] st_probe+0x3f4/0x7c1 [st]
> Jan 23 06:41:49 yeti kernel: [<c018f7b0>] init_dir+0x0/0x22
> Jan 23 06:41:49 yeti kernel: [<c01f7d29>] bus_match+0x3d/0x65
> Jan 23 06:41:49 yeti kernel: [<c01f7e42>] driver_attach+0x59/0x83
> Jan 23 06:41:49 yeti kernel: [<c01f810b>] bus_add_driver+0x9e/0xb1
> Jan 23 06:41:49 yeti kernel: [<f881905e>] init_st+0x5e/0x9c [st]
> Jan 23 06:41:49 yeti kernel: [<c013898f>] sys_init_module+0x13e/0x29a
> Jan 23 06:41:49 yeti kernel: [<c01091e3>] syscall_call+0x7/0xb
>
st_probe() is calling cdev_alloc() under write_lock(&st_dev_arr_lock);
Optimistically Cc'ing linux-scsi...
prev parent reply other threads:[~2004-01-23 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 11:47 Mike Black
2004-01-23 22:32 ` Andrew Morton [this message]
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=20040123143208.54b4f962.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mblack@csi-inc.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
all inboxes | Powered by JetHome®