From: Samuel Flory <sflory@rackable.com>
To: linux-kernel@vger.kernel.org
Subject: sleeping function called from invalid context
Date: Tue, 09 Sep 2003 08:03:01 -0700 [thread overview]
Message-ID: <3F5DEBA5.9060607@rackable.com> (raw)
I'm seeing this on arjanv's 2.6.0-0.test4.1.33 kernel.
Debug: sleeping function called from invalid context at
include/asm/uaccess.h:473
Call Trace:
[<c011b7dd>] __might_sleep+0x5d/0x70
[<c010d0ea>] save_v86_state+0x6a/0x200
[<c010c8b5>] do_IRQ+0xd5/0x110
[<c010acd2>] work_notifysig_v86+0x6/0x14
[<c010ac7f>] syscall_call+0x7/0xb
Debug: sleeping function called from invalid context at
include/asm/uaccess.h:473
Call Trace:
[<c011b7dd>] __might_sleep+0x5d/0x70
[<c010d0ea>] save_v86_state+0x6a/0x200
[<c010bba0>] do_general_protection+0x0/0xb0
[<c010acd2>] work_notifysig_v86+0x6/0x14
[<c010ac7f>] syscall_call+0x7/0xb
Any thoughts. The system seems to function despite the issue. It
seems to have also occurred under 2.6.0-0.test3.1.31:
Aug 25 16:28:49 goblin kernel: Call Trace:
Aug 25 16:28:49 goblin kernel: [<c011af2d>] __might_sleep+0x5d/0x70
Aug 25 16:28:49 goblin kernel: [<c010d06a>] save_v86_state+0x6a/0x200
Aug 25 16:28:49 goblin kernel: [<c010bb50>] do_general_protection+0x0/0xb0
Aug 25 16:28:49 goblin kernel: [<c010ac82>] work_notifysig_v86+0x6/0x14
Aug 25 16:28:49 goblin kernel: [<c010ac2f>] syscall_call+0x7/0xb
Aug 25 16:28:49 goblin kernel:
Aug 25 16:28:50 goblin kernel: Debug: sleeping function called from
invalid cont
ext at include/asm/uaccess.h:473
Aug 25 16:28:50 goblin kernel: Call Trace:
Aug 25 16:28:50 goblin kernel: [<c011af2d>] __might_sleep+0x5d/0x70
Aug 25 16:28:50 goblin kernel: [<c010d06a>] save_v86_state+0x6a/0x200
Aug 25 16:28:50 goblin kernel: [<c010bb50>] do_general_protection+0x0/0xb0
Aug 25 16:28:50 goblin kernel: [<c010ac82>] work_notifysig_v86+0x6/0x14
Aug 25 16:28:50 goblin kernel: [<c010ac2f>] syscall_call+0x7/0xb
Aug 25 16:28:50 goblin kernel:
Aug 25 16:28:51 goblin kernel: Debug: sleeping function called from
invalid cont
ext at include/asm/uaccess.h:473
Aug 25 16:28:51 goblin kernel: Call Trace:
Aug 25 16:28:51 goblin kernel: [<c011af2d>] __might_sleep+0x5d/0x70
Aug 25 16:28:51 goblin kernel: [<c010d06a>] save_v86_state+0x6a/0x200
Aug 25 16:28:51 goblin kernel: [<c010c865>] do_IRQ+0xd5/0x110
Aug 25 16:28:51 goblin kernel: [<c010ac82>] work_notifysig_v86+0x6/0x14
Aug 25 16:28:51 goblin kernel: [<c010ac2f>] syscall_call+0x7/0xb
--
Once you have their hardware. Never give it back.
(The First Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
next reply other threads:[~2003-09-09 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 15:03 Samuel Flory [this message]
2003-09-09 19:47 ` sleeping function called from invalid context Matt Mackall
2003-09-09 20:10 ` Samuel Flory
-- strict thread matches above, loose matches on Subject: below --
2011-05-10 5:38 BUG: " Amit Virdi
2011-05-10 9:32 ` Alan Cox
2011-05-11 8:43 ` Amit Virdi
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=3F5DEBA5.9060607@rackable.com \
--to=sflory@rackable.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox