From: Jon Hunter <jonathanh@nvidia.com>
To: <kernel@martin.sperl.org>, Mark Brown <broonie@kernel.org>
Cc: linux-tegra <linux-tegra@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<linux-spi@vger.kernel.org>
Subject: Regression: spi: core: avoid waking pump thread from spi_sync instead run teardown delayed
Date: Mon, 14 Jan 2019 15:35:51 +0000 [thread overview]
Message-ID: <f86eaebb-0359-13be-f4a2-4f2b8832252e@nvidia.com> (raw)
Hi Martin, Mark,
I have noticed that system suspend has started failing consistently on a
couple Tegra boards over the last few days with the linux-next branch.
The following error is seen on on entering suspend ...
[ 58.222033] spi_master spi1: could not stop message queue
[ 58.222038] spi_master spi1: queue stop failed
[ 58.222048] dpm_run_callback(): platform_pm_suspend+0x0/0x54 returns -16
[ 58.222052] PM: Device 7000da00.spi failed to suspend: error -16
[ 58.222057] PM: Some devices failed to suspend, or early wake event detected
Bisecting today's -next points to commit 412e60373245 ("spi: core: avoid
waking pump thread from spi_sync instead run teardown delayed") and
reverting this on top of -next fixes the problem. I have not had chance
to dig any further but wanted to report this issue to see if you have
any thoughts.
Cheers
Jon
--
nvpublic
next reply other threads:[~2019-01-14 15:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 15:35 Jon Hunter [this message]
[not found] ` <7C4A5EFC-8235-40C8-96E1-E6020529DF72@martin.sperl.org>
2019-01-15 14:26 ` Jon Hunter
2019-01-15 15:10 ` Mark Brown
2019-01-15 16:09 ` Jon Hunter
2019-01-15 19:27 ` Mark Brown
2019-01-15 17:39 ` kernel
2019-01-15 19:26 ` Mark Brown
2019-01-15 20:58 ` Martin Sperl
2019-01-15 21:25 ` Mark Brown
2019-01-16 11:01 ` Jon Hunter
2019-01-18 17:11 ` kernel
2019-01-18 19:12 ` Mark Brown
2019-01-20 11:24 ` kernel
2019-01-23 17:56 ` Mark Brown
2019-05-09 19:47 ` Martin Sperl
2019-05-12 8:54 ` Mark Brown
2019-01-16 10:58 ` Jon Hunter
2019-01-22 9:36 ` Geert Uytterhoeven
[not found] ` <CGME20190123082650eucas1p243ce21346a00e9b3e9eed2863cd3d280@eucas1p2.samsung.com>
2019-01-23 8:26 ` Marek Szyprowski
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=f86eaebb-0359-13be-f4a2-4f2b8832252e@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=broonie@kernel.org \
--cc=kernel@martin.sperl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-tegra@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®