From: Oleg Kechin <okechin@gmail.com>
To: linux-rt-users@vger.kernel.org
Subject: BUG: at kernel/sched.c:4031 __schedule()
Date: Thu, 07 Jun 2007 17:07:39 +0300 [thread overview]
Message-ID: <4668112B.4090406@gmail.com> (raw)
Hi
I run 2.6.20-rt8 kernel on board like innovator1510 (OMAP5910 cpu)
I notice in boot string:
BUG: at kernel/sched.c:4031 __schedule()
kernel complain interrupts are enabled after schedule.
digging in sched.c I figured out that interrupts are disabled when cpu
enter __sched(),
but are enabled when it went out.
Playing with the code i can find out, that problem is in the next
fragment: (line 4024)
if (likely(prev != next)) {
next->timestamp = now;
rq->nr_switches++;
rq->curr = next;
++*switch_count;
prepare_task_switch(rq, next);
prev = context_switch(rq, prev, next);
barrier();
trace_special_pid(prev->pid, PRIO(prev), PRIO(current));
/*
* this_rq must be evaluated again because prev may have moved
* CPUs since it called schedule(), thus the 'rq' on its stack
* frame will be invalid.
*/
finish_task_switch(this_rq(), prev);
__preempt_enable_no_resched();
} else {
in prepare_task_switch(rq, next); interrupts are enabled,
but in finish_task_switch(this_rq(), prev); interrupts not disabled
(it look not symmetrical for me).
Can anybody tell - is this right behavior?
I think interrupts should be disabled somewhere in this fragment,
or may be, scheduler should not complain?
Oleg Kechin.
next reply other threads:[~2007-06-07 14:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 14:07 Oleg Kechin [this message]
2007-06-07 15:39 ` BUG: at kernel/sched.c:4031 __schedule() Steven Rostedt
2007-06-07 15:58 ` Jan Altenberg
2007-06-07 16:13 ` Steven Rostedt
2007-06-07 16:20 ` Daniel Walker
2007-06-07 16:21 ` Daniel Walker
2007-06-07 16:33 ` Daniel Walker
2007-06-08 10:08 ` Oleg Kechin
2007-06-08 10:52 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2007-04-06 13:29 Oleg Kechin
2007-04-07 7:49 ` Dirk Behme
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=4668112B.4090406@gmail.com \
--to=okechin@gmail.com \
--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 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.