From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Linux Mailing List <linux-kernel@vger.kernel.org>
Subject: Preempted by idle thread?
Date: Wed, 12 May 2004 12:23:26 +1000 [thread overview]
Message-ID: <200405121223.26115.ncunningham@linuxmail.org> (raw)
Hi all.
I've been seeing some funny bad_scheduling_while_atomic messages that might be
my own fault (they only occur after suspending). The funny thing, though, is
that they are all the same, and show a calling chain:
schedule_tail -> preempt_schedule -> cpu_idle
Am I misunderstanding this, or is a thread being preempted by cpu_idle? If
that is the case, real work shouldn't be preempted to idle, should it?
Nigel
reply other threads:[~2004-05-12 2:23 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=200405121223.26115.ncunningham@linuxmail.org \
--to=ncunningham@linuxmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.