From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Adrien Thierry <athierry@redhat.com>,
linux-rt-users@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Kevin Hilman <khilman@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Andrew Halaney <ahalaney@redhat.com>,
Eric Chanudet <echanude@redhat.com>,
Brian Masney <bmasney@redhat.com>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH RFC] base: power: replace generic_pm_domain spinlock by raw spinlock
Date: Fri, 16 Dec 2022 11:20:20 +0100 [thread overview]
Message-ID: <cefad5f6-8aa4-acb8-231c-91170ec10bcf@linaro.org> (raw)
In-Reply-To: <20220615203605.1068453-1-athierry@redhat.com>
On 15/06/2022 22:36, Adrien Thierry wrote:
> We've been encountering a BUG: scheduling while atomic while running the
> 5.18.0-rt11 kernel on a Qualcomm SoC (see stacktrace below).
>
> It seems to occur because a spinlock is taken in the PSCI idle code path
> in the idle loop. With the RT patchset applied and CONFIG_PREEMPT_RT
> enabled, spinlocks can sleep, thus triggering the bug.
>
> In order to prevent this, replace the generic_pm_domain spinlock by a
> raw spinlock.
>
> [ 2.994433] BUG: scheduling while atomic: swapper/6/0/0x00000002
> [ 2.994439] Modules linked in:
> [ 2.994447] [<ffff80000810b0ec>] migrate_enable+0x3c/0x160
> [ 2.994461] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 5.18.0-rt11+ #1
> [ 2.994464] Hardware name: Qualcomm SA8295P ADP (DT)
> [ 2.994466] Call trace:
> [ 2.994467] dump_backtrace+0xb0/0x120
> [ 2.994473] show_stack+0x1c/0x6c
> [ 2.994477] dump_stack_lvl+0x64/0x7c
> [ 2.994483] dump_stack+0x14/0x2c
> [ 2.994487] __schedule_bug+0xa8/0xc0
> [ 2.994489] schedule_debug.constprop.0+0x154/0x170
> [ 2.994492] __schedule+0x58/0x520
> [ 2.994496] schedule_rtlock+0x20/0x44
> [ 2.994499] rtlock_slowlock_locked+0x110/0x260
> [ 2.994503] rt_spin_lock+0x74/0x94
> [ 2.994505] genpd_lock_nested_spin+0x20/0x30
Hi Adrian,
I also hit it now on v6.1 RT kernel. I see no more discussions happened
here. Do you have any progress on your side for this issue?
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-12-16 10:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 20:36 [PATCH RFC] base: power: replace generic_pm_domain spinlock by raw spinlock Adrien Thierry
2022-06-15 21:44 ` Ulf Hansson
2022-06-15 21:53 ` Ulf Hansson
2022-06-16 6:17 ` Greg Kroah-Hartman
2022-12-16 10:20 ` Krzysztof Kozlowski [this message]
2022-12-16 14:13 ` Adrien Thierry
2022-12-16 14:42 ` Krzysztof Kozlowski
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=cefad5f6-8aa4-acb8-231c-91170ec10bcf@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=ahalaney@redhat.com \
--cc=athierry@redhat.com \
--cc=bmasney@redhat.com \
--cc=echanude@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=khilman@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=ulf.hansson@linaro.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.