From: Andrew Morton <akpm@osdl.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: sleeping functions called in invalid context during resume
Date: Wed, 15 Nov 2006 01:20:25 -0800 [thread overview]
Message-ID: <20061115012025.13c72fc1.akpm@osdl.org> (raw)
In-Reply-To: <20061114223002.10c231bd@localhost.localdomain>
On Tue, 14 Nov 2006 22:30:02 -0800
Stephen Hemminger <shemminger@osdl.org> wrote:
> Lots of sleeping while atomic warnings on 2.6.19-rc5
> During resume I see the following:
>
>
> platform floppy.0: EARLY resume
> APIC error on CPU0: 00(00)
> PM: Finishing wakeup.
> BUG: sleeping function called from invalid context at drivers/base/power/resume.c:99
> in_atomic():1, irqs_disabled():0
>
> Call Trace:
> [<ffffffff80266117>] show_trace+0x34/0x47
> [<ffffffff8026613c>] dump_stack+0x12/0x17
> [<ffffffff803734e5>] device_resume+0x19/0x51
> [<ffffffff80292157>] enter_state+0x19b/0x1b5
> [<ffffffff802921cf>] state_store+0x5e/0x79
> [<ffffffff802cc157>] sysfs_write_file+0xc5/0xf8
> [<ffffffff80215059>] vfs_write+0xce/0x174
> [<ffffffff802159a5>] sys_write+0x45/0x6e
> [<ffffffff802593de>] system_call+0x7e/0x83
> DWARF2 unwinder stuck at system_call+0x7e/0x83
>
> Leftover inexact backtrace:
Could mean that someone somewhere forgot to release a spinlock.
Ingo had a patch which would find the culprit (preempt-tracing.patch).
Does it still live?
next prev parent reply other threads:[~2006-11-15 9:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 6:30 Stephen Hemminger
2006-11-15 9:20 ` Andrew Morton [this message]
2006-11-15 9:33 ` Ingo Molnar
2006-11-15 18:01 ` Stephen Hemminger
2006-11-15 18:04 ` Ingo Molnar
2006-11-17 5:21 ` Stephen Hemminger
2006-11-17 6:18 ` Andrew Morton
2006-11-17 6:49 ` Andi Kleen
2006-11-17 6:52 ` Ingo Molnar
2006-11-17 15:46 ` Rafael J. Wysocki
2006-11-17 16:30 ` Stephen Hemminger
2006-11-18 11:43 ` Paolo Ornati
2006-11-18 12:55 ` Karsten Wiese
2006-11-18 15:28 ` Paolo Ornati
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=20061115012025.13c72fc1.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=shemminger@osdl.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®