From: Stefan Wahren <wahrenst@gmx.net>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
linux-arm-kernel@lists.infradead.org,
linux-integrity@vger.kernel.org, kernel@pengutronix.de,
Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
"imx@lists.linux.dev" <imx@lists.linux.dev>
Subject: Re: tpm: spi: do not call blocking ops when !TASK_RUNNING; during shutdown
Date: Mon, 4 May 2026 18:05:25 +0200 [thread overview]
Message-ID: <6964bec7-3dbb-453b-89ef-9b990217a8b9@gmx.net> (raw)
In-Reply-To: <afiiUdFv7p0fuK-5@kernel.org>
Am 04.05.26 um 15:42 schrieb Jarkko Sakkinen:
> Hi Stefan,
>
> On Mon, Apr 20, 2026 at 12:25:21PM +0200, Stefan Wahren wrote:
>> Hi,
>> we use a custom i.MX93 board, which based on Phytec Phycore i.MX93 with a
>> TPM connected via SPI. If I enable CONFIG_DEBUG_ATOMIC_SLEEP=y in our kernel
>> config with mainline kernel 6.18.23 and reboot our board, I will get the
>> following warning:
> Please provide results with the latest mainline kernel.
>
Here you are
[ 69.085410] do not call blocking ops when !TASK_RUNNING; state=1 set
at [<0000000090f4020f>] prepare_to_wait_event+0x54/0x14c
[ 69.097076] WARNING: kernel/sched/core.c:9086 at
__might_sleep+0x74/0x7c, CPU#0: systemd-shutdow/1
[ 69.106026] Modules linked in: flexcan can_dev rtc_rv3028 mse102x
phy_can_transceiver fuse autofs4
[ 69.114991] CPU: 0 UID: 0 PID: 1 Comm: systemd-shutdow Not tainted
7.1.0-rc2-00005-g6d35786de281-dirty #45 PREEMPT
[ 69.125405] Hardware name: chargebyte Charge SOM Evaluation Kit (DT)
[ 69.131741] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS
BTYPE=--)
[ 69.138690] pc : __might_sleep+0x74/0x7c
[ 69.142608] lr : __might_sleep+0x74/0x7c
[ 69.146525] sp : ffff800081b7b710
[ 69.149827] x29: ffff800081b7b710 x28: 0000000000000080 x27:
ffff000002cafe80
[ 69.156951] x26: ffff800081965000 x25: 0000000000000018 x24:
0000000000000000
[ 69.164075] x23: ffff800081b7b8f7 x22: 0000000000000000 x21:
0000000000000080
[ 69.171199] x20: 000000000000013c x19: ffff8000813e2880 x18:
0000000000000000
[ 69.178323] x17: 003fffffffffffff x16: 000000000017d600 x15:
ffff00003fda1a00
[ 69.185447] x14: ffff000000132c00 x13: 00000000000002ce x12:
0000000000000000
[ 69.192571] x11: 00000000000000c0 x10: 00000000000009e0 x9 :
ffff800081b7b580
[ 69.199695] x8 : ffff0000001335c0 x7 : ffff00003fda1280 x6 :
0000000000000000
[ 69.206819] x5 : 000000001fffffff x4 : 0000000000000001 x3 :
0000000000000010
[ 69.213943] x2 : 0000000000000000 x1 : 0000000000000000 x0 :
ffff000000132b80
[ 69.221068] Call trace:
[ 69.223503] __might_sleep+0x74/0x7c (P)
[ 69.227420] mutex_lock+0x24/0x80
[ 69.230731] spi_bus_lock+0x20/0x50
[ 69.234214] tpm_tis_spi_transfer_full+0x70/0x2c4
[ 69.238912] tpm_tis_spi_read_bytes+0x3c/0x48
[ 69.243263] tpm_tis_status+0x58/0xf8
[ 69.246920] wait_for_tpm_stat_cond+0x30/0x90
[ 69.251271] wait_for_tpm_stat+0x1cc/0x2e0
[ 69.255361] tpm_tis_send_data+0xdc/0x35c
[ 69.259365] tpm_tis_send_main+0x74/0x18c
[ 69.263369] tpm_tis_send+0xd4/0x13c
[ 69.266940] tpm_transmit+0xc4/0x3c4
[ 69.270511] tpm_transmit_cmd+0x38/0xd4
[ 69.274341] tpm2_shutdown+0x6c/0xa4
[ 69.277912] tpm_class_shutdown+0x60/0x88
[ 69.281916] device_shutdown+0x130/0x258
[ 69.285833] kernel_restart+0x44/0xa4
[ 69.289491] __do_sys_reboot+0x114/0x244
[ 69.293408] __arm64_sys_reboot+0x24/0x30
[ 69.297412] invoke_syscall+0x54/0x10c
[ 69.301156] el0_svc_common.constprop.0+0x40/0xe0
[ 69.305853] do_el0_svc+0x1c/0x28
[ 69.309164] el0_svc+0x38/0x138
[ 69.312301] el0t_64_sync_handler+0xa0/0xe4
[ 69.316478] el0t_64_sync+0x198/0x19c
prev parent reply other threads:[~2026-05-04 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 10:25 tpm: spi: do not call blocking ops when !TASK_RUNNING; during shutdown Stefan Wahren
2026-04-21 9:04 ` Peng Fan
2026-04-21 18:28 ` Jarkko Sakkinen
2026-05-04 13:42 ` Jarkko Sakkinen
2026-05-04 16:05 ` Stefan Wahren [this message]
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=6964bec7-3dbb-453b-89ef-9b990217a8b9@gmx.net \
--to=wahrenst@gmx.net \
--cc=Frank.Li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-integrity@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=s.hauer@pengutronix.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