From: Andi Kleen <ak@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Stephen Hemminger <shemminger@osdl.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: sleeping functions called in invalid context during resume
Date: Fri, 17 Nov 2006 07:49:01 +0100 [thread overview]
Message-ID: <200611170749.02129.ak@suse.de> (raw)
In-Reply-To: <20061116221800.bfbd80c4.akpm@osdl.org>
> > I have no idea what causes:
> >
> > APIC error on CPU0: 00(00)
> >
> > Is it an ACPI problem?
What CPU/chipset?
>
> Strange. x86_64 has that stray exit_idle() in smp_error_interrupt() but
> afaict it won't cause this to happen.
>
> What's that idle_notifier doing in x86_64 anyway?
I originally added it for my (now abandoned in favour of dyntick) noidletick
implementation. I would have removed it again, but perfmon plans to use it
too and I suspect dyntick will too (?)
> It appears to have no
> users. If there _is_ a user, and if its IDLE_END handler is altering the
> preempt-count then perhaps there's your explanation.
There shouldn't be a user currently in tree.
> But it all appears to be dead code to me.
Right now it is yes.
-Andi
next prev parent reply other threads:[~2006-11-17 6:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 6:30 sleeping functions called in invalid context during resume Stephen Hemminger
2006-11-15 9:20 ` Andrew Morton
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 [this message]
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=200611170749.02129.ak@suse.de \
--to=ak@suse.de \
--cc=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