From: Matt Mackall <mpm@selenic.com>
To: "Hmamouche, Youssef" <youssef@ece.utexas.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sleeping function called from invalid context include/linux/rwsem.h:43
Date: Wed, 20 Aug 2003 13:03:47 -0500 [thread overview]
Message-ID: <20030820180347.GC23889@waste.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0308200117220.1817-100000@linux08.ece.utexas.edu>
On Wed, Aug 20, 2003 at 01:38:09AM -0500, Hmamouche, Youssef wrote:
>
> Hi,
>
> I get this debug message right before the oops(Oops linux-2.6.0-test3
> sound) that I sent earlier to the list. When this Debug message happens
> before the oops, the system freezes. All of this is related to the
> Maestro3.c sound card. I've ran 2.4{16, 20, 21, 22-pre8} without a
> problem. I searched through the list archive for a similar problem, in
> vain. Can someone please tell what's causing this?
Could you post the oops together with the might_sleep trace? This is
something calling down_read in a context where its not safe to sleep.
The rest of the backtrace doesn't make much sense..
Did you build with preempt enabled?
>
> Thanks
>
> Debug: sleeping function called from invalid context at
> include/linux/rwsem.h:43
> Aug 19 23:59:34 darkstar kernel: Debug: sleeping function called from
> invalid context at include/linux/rwsem.h:43
>
> Call Trace:
> [<c012722e>] __might_sleep+0x5e/0x70
> [<c0127b20>] autoremove_wake_function+0x0/0x50
> [<c0122869>] do_page_fault+0x79/0x4dc
> [<c01c71ad>] ext2_get_inode+0xdd/0x140
> [<c022973c>] avc_has_perm+0x6c/0x7b
> [<c01227f0>] do_page_fault+0x0/0x4dc
> [<c010b1b9>] error_code+0x2d/0x38
> [<c03dabe1>] m3_open+0x131/0x390
> [<c0159b94>] check_poison_obj+0x54/0x1d0
> [<c03d4d25>] soundcore_open+0x1e5/0x4e0
> [<c0186c90>] exact_match+0x0/0x10
> [<c0186696>] chrdev_open+0x156/0x3e0
> [<c017a388>] get_empty_filp+0x98/0x100
> [<c017823c>] dentry_open+0x12c/0x1c0
> [<c0178106>] filp_open+0x66/0x70
> [<c0178855>] sys_open+0x55/0x90
> [<c010b00f>] syscall_call+0x7/0xb
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Matt Mackall : http://www.selenic.com : of or relating to the moon
next prev parent reply other threads:[~2003-08-20 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 6:38 sleeping function called from invalid context include/linux/rwsem.h:43 Hmamouche, Youssef
2003-08-20 18:03 ` Matt Mackall [this message]
2003-08-21 2:40 ` Hmamouche, Youssef
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=20030820180347.GC23889@waste.org \
--to=mpm@selenic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=youssef@ece.utexas.edu \
/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.