From: Christian Eggers <ceggers@arri.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>, <tglx@linutronix.de>,
<linux-rt-users@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: sched: system doesn't boot since "sched: Add new migrate_disable() implementation"
Date: Mon, 19 Oct 2020 12:21:06 +0200 [thread overview]
Message-ID: <1654655.1jrfHnk7pZ@n95hx1g2> (raw)
I have problems with the latest 5.9-rt releases on i.MX6ULL (!CONFIG_SMP):
-rc8-rt13 works fine
-rc8-rt14 doesn't compile (due to CONFIG_FRACE, already fixed in -rt16)
-rt15 dito.
-rt16 compiles, but doesn't boot (no console output at all)
After reverting (on -rt16)
de1c0755e6f9 ("tracing: fix compile failure on RT with PREEMPT_RT off")
30763ce6c15d ("sched: Add new migrate_disable() implementation")
the system boots fine again.
Tracking the problem down showed that calls to wait_for_completion_timeout()
(e.g. during imx_rngc_probe) will never return. The IRQ routine which should
fire the completion is not executed, and the call doesn't return after the
timeout. The IRQ flag on the ARM is not set before entering
wait_for_completion_timeout(), so CPU interrupts seem to be on.
When building with CONFIG_SMP, the system boots fine.
Any hints?
Best regards
Christian
next reply other threads:[~2020-10-19 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 10:21 Christian Eggers [this message]
2020-10-19 15:09 ` sched: system doesn't boot since "sched: Add new migrate_disable() implementation" Sebastian Andrzej Siewior
2020-10-20 11:30 ` Peter Zijlstra
2020-10-20 11:38 ` Sebastian Andrzej Siewior
2020-10-20 11:41 ` Peter Zijlstra
2020-10-20 11:51 ` Sebastian Andrzej Siewior
2020-10-20 12:38 ` Christian Eggers
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=1654655.1jrfHnk7pZ@n95hx1g2 \
--to=ceggers@arri.de \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).