From: paulmck@linux.vnet.ibm.com (Paul E. McKenney)
To: linux-arm-kernel@lists.infradead.org
Subject: WARNING: suspicious RCU usage
Date: Tue, 12 Dec 2017 11:36:38 -0800 [thread overview]
Message-ID: <20171212193638.GH7829@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAOMZO5DBMpCHfgmNND6=qJD+sxOLMPFqEsyz+GiBVhMzN3H+Zg@mail.gmail.com>
On Tue, Dec 12, 2017 at 04:11:07PM -0200, Fabio Estevam wrote:
> Hi Russell,
>
> On Tue, Dec 12, 2017 at 3:34 PM, Russell King - ARM Linux
> <linux@armlinux.org.uk> wrote:
>
> > It's fundamentally unsafe.
> >
> > You need to test with CONFIG_BL_SWITCHER enabled - there's spinlocks
> > in smp_call_function_single() path that are conditional on that symbol.
> > If CONFIG_BL_SWITCHER is disabled, then the spinlocks are not present.
>
> Ok, just tested with CONFIG_BL_SWITCHER=y on a imx6q-cubox-i:
Just to confirm, your dmesg below is illustrating the hang, correct?
Thanx, Paul
> # echo enabled > /sys/class/tty/ttymxc0/power/wakeup
> # echo mem > /sys/power/state
> [ 10.503462] PM: suspend entry (deep)
> [ 10.507479] PM: Syncing filesystems ... done.
> [ 10.555024] Freezing user space processes ... (elapsed 0.002 seconds) done.
> [ 10.564511] OOM killer disabled.
> [ 10.567760] Freezing remaining freezable tasks ... (elapsed 0.002 seconds) d.
> [ 10.577420] Suspending console(s) (use no_console_suspend to debug)
> [ 10.657748] PM: suspend devices took 0.080 seconds
> [ 10.669329] Disabling non-boot CPUs ...
> [ 10.717049] IRQ17 no longer affine to CPU1
> [ 10.837141] Enabling non-boot CPUs ...
> [ 10.839386] CPU1 is up
> [ 10.840342] CPU2 is up
> [ 10.841300] CPU3 is up
> [ 11.113735] mmc0: queuing unknown CIS tuple 0x80 (2 bytes)
> [ 11.115676] mmc0: queuing unknown CIS tuple 0x80 (3 bytes)
> [ 11.117595] mmc0: queuing unknown CIS tuple 0x80 (3 bytes)
> [ 11.121014] mmc0: queuing unknown CIS tuple 0x80 (7 bytes)
> [ 11.124454] mmc0: queuing unknown CIS tuple 0x80 (7 bytes)
> [ 11.177299] ata1: SATA link down (SStatus 0 SControl 300)
> [ 11.181930] PM: resume devices took 0.330 seconds
> [ 11.243729] OOM killer enabled.
> [ 11.246886] Restarting tasks ... done.
> [ 11.253012] PM: suspend exit
>
next prev parent reply other threads:[~2017-12-12 19:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-10 11:39 WARNING: suspicious RCU usage Peng Fan
2017-12-10 12:00 ` Russell King - ARM Linux
2017-12-10 19:07 ` Paul E. McKenney
2017-12-10 19:34 ` Russell King - ARM Linux
2017-12-10 21:39 ` Paul E. McKenney
2017-12-10 21:54 ` Russell King - ARM Linux
2017-12-10 23:16 ` Paul E. McKenney
2017-12-12 16:49 ` Paul E. McKenney
2017-12-12 16:56 ` Fabio Estevam
2017-12-12 17:21 ` Paul E. McKenney
2017-12-12 17:34 ` Russell King - ARM Linux
2017-12-12 18:11 ` Fabio Estevam
2017-12-12 19:36 ` Paul E. McKenney [this message]
2017-12-12 19:44 ` Fabio Estevam
2017-12-12 19:54 ` Russell King - ARM Linux
2017-12-12 21:05 ` Fabio Estevam
2017-12-13 9:12 ` Russell King - ARM Linux
2017-12-15 6:38 ` Paul E. McKenney
2017-12-15 13:16 ` Fabio Estevam
2017-12-15 15:52 ` Paul E. McKenney
2017-12-15 18:23 ` Paul E. McKenney
2017-12-15 20:36 ` Fabio Estevam
2017-12-15 21:34 ` Paul E. McKenney
2017-12-15 21:43 ` Fabio Estevam
2017-12-15 22:56 ` Paul E. McKenney
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=20171212193638.GH7829@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).