From: Tim Blechmann <tim@klingt.org>
To: linux-rt-users@vger.kernel.org
Subject: BUG: sleeping function called from invalid context at kernel/rtmutex.c:683
Date: Tue, 07 Apr 2009 12:48:36 +0200 [thread overview]
Message-ID: <grfb2b$dps$1@ger.gmane.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]
using kernel 2.6.29-rt3, i get the following BUG, when waking from
suspend-to-ram:
[13899.995628] BUG: sleeping function called from invalid context at
kernel/rtmutex.c:683
[13899.995630] in_atomic(): 0, irqs_disabled(): 1, pid: 15817, name:
pm-suspend
[13899.995632] Pid: 15817, comm: pm-suspend Not tainted 2.6.29-rt3-tip #29
[13899.995634] Call Trace:
[13899.995642] [<ffffffff80242a2c>] __might_sleep+0xfc/0x100
[13899.995647] [<ffffffff8052c151>] rt_spin_lock+0x81/0x90
[13899.995651] [<ffffffff80219555>] read_persistent_clock+0x15/0x40
[13899.995655] [<ffffffff802779ee>] timekeeping_suspend+0xe/0x90
[13899.995658] [<ffffffff8044cf89>] sysdev_suspend+0xc9/0x220
[13899.995663] [<ffffffff802880b5>] suspend_devices_and_enter+0x1a5/0x220
[13899.995666] [<ffffffff802882c6>] enter_state+0x166/0x1e0
[13899.995668] [<ffffffff802883fa>] state_store+0xba/0x100
[13899.995672] [<ffffffff803bb217>] kobj_attr_store+0x17/0x20
[13899.995675] [<ffffffff8035e0e5>] sysfs_write_file+0xc5/0x140
[13899.995679] [<ffffffff802fb4db>] vfs_write+0xcb/0x190
[13899.995682] [<ffffffff802fb690>] sys_write+0x50/0x90
[13899.995686] [<ffffffff802120c2>] system_call_fastpath+0x16/0x1b
best, tim
--
tim@klingt.org
http://tim.klingt.org
Avoid the world, it's just a lot of dust and drag and means nothing in
the end.
Jack Kerouac
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
reply other threads:[~2009-04-07 10:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='grfb2b$dps$1@ger.gmane.org' \
--to=tim@klingt.org \
--cc=linux-rt-users@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;
as well as URLs for NNTP newsgroup(s).