From: "Miles Lane" <miles.lane@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>, "Andrew Morton" <akpm@osdl.org>
Subject: 2.6.16-rc5-mm3 -- BUG: sleeping function called from invalid context at include/linux/rwsem.h:43 in_atomic():0, irqs_disabled():1
Date: Wed, 8 Mar 2006 22:53:10 -0800 [thread overview]
Message-ID: <a44ae5cd0603082253sfb4a1e1q687c56a6f6a386fb@mail.gmail.com> (raw)
Apologies. This bug caused my video to get messed up. I was able to
run Gnome, but the apps weren't rendering correctly, so I couldn't be
sure my subject line was correct.
I would have edited out some of the context info, but that was tough
as well. Here's the BUG message by itself. Perhaps all the dmesg
output in the previous message will be helpful.
As you can see in the dmesg output, I hit this by suspending and
resuming. I am running Fedora Core 5 Test 3 + all yum updates.
Andrew, the full dmesg output is in the LKML message with the subject
line set to "v". Let me know if you would like me to send it directly
to you.
BUG: sleeping function called from invalid context at include/linux/rwsem.h:43
in_atomic():0, irqs_disabled():1
<c1003f81> show_trace+0xd/0xf <c100401b> dump_stack+0x17/0x19
<c1015f77> __might_sleep+0x86/0x90 <c1024738>
blocking_notifier_call_chain+0x1b/0x4d
<c1183bb2> cpufreq_resume+0xf5/0x11d <c112b27c> __sysdev_resume+0x23/0x57
<c112b3c9> sysdev_resume+0x19/0x4b <c112f736> device_power_up+0x8/0xf
<c1033339> swsusp_suspend+0x6e/0x8b <c1033918> pm_suspend_disk+0x51/0xf3
<c10328c7> enter_state+0x53/0x1c1 <c1032abe> state_store+0x89/0x97
<c108af00> subsys_attr_store+0x20/0x25 <c108b020> sysfs_write_file+0xb5/0xdc
<c1056578> vfs_write+0xab/0x154 <c1056aa3> sys_write+0x3b/0x60
<c1002b43> syscall_call+0x7/0xb
PM: Image restored success
next reply other threads:[~2006-03-09 6:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 6:53 Miles Lane [this message]
2006-03-09 10:32 ` Andrew Morton
2006-03-09 12:06 ` Rafael J. Wysocki
2006-03-09 13:46 ` Miles Lane
2006-03-09 16:11 ` Alan Stern
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=a44ae5cd0603082253sfb4a1e1q687c56a6f6a386fb@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®