From: Kun Song <Kun.Song@windriver.com>
To: <gaurav.jain@nxp.com>
Cc: <Kun.Song@windriver.com>, <V.Sethi@nxp.com>,
<aymen.sghaier@nxp.com>, <davem@davemloft.net>,
<filip.pudak@windriver.com>, <heng.guo@windriver.com>,
<herbert@gondor.apana.org.au>, <horia.geanta@nxp.com>,
<linux-crypto@vger.kernel.org>, <meenakshi.aggarwal@nxp.com>,
<richard.danter@windriver.com>
Subject: RE: [PATCH v5.10.y] crypto: caam/jr - Fix possible caam_jr crash
Date: Wed, 10 Jan 2024 19:56:53 +0800 [thread overview]
Message-ID: <20240110115653.3170977-1-Kun.Song@windriver.com> (raw)
In-Reply-To: <AM0PR04MB600455078CE01BE8246117B7E7692@AM0PR04MB6004.eurprd04.prod.outlook.com>
>https://github.com/torvalds/linux/commit/06e39357c36b0d3cc2779d08ed04cb389eaa22ba - drivers: crypto: caam/jr - Allow quiesce when quiesced
>apply this one as well.
Hi, Gaurav
Our version has backport this commiti(06e39357c36b0d3cc2779d08ed04cb389eaa22ba), but the problem still exists.
When crash occurs, the log will output
<3>caam_jr 8030000.jr: Device is busy
<3>caam_jr 8020000.jr: Device is busy
<3>caam_jr 8010000.jr: Device is busy
<3>caam_jr 8010000.jr: job ring error: irqstate: 00000103
Thanks!
BR/SK
next prev parent reply other threads:[~2024-01-10 11:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 9:32 [PATCH v5.10.y] crypto: caam/jr - Fix possible caam_jr crash Kun Song
2023-12-22 11:43 ` Gaurav Jain (OSS)
2023-12-25 3:05 ` Kun Song
2024-01-10 1:39 ` [REMINDER] " Kun Song
2024-01-10 6:57 ` Gaurav Jain (OSS)
2024-01-10 7:00 ` Gaurav Jain
2024-01-10 8:25 ` Kun Song
2024-01-10 9:14 ` [EXT] " Gaurav Jain
2024-01-10 11:56 ` Kun Song [this message]
2024-01-11 10:46 ` Gaurav Jain
2024-01-31 13:34 ` Horia Geanta
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=20240110115653.3170977-1-Kun.Song@windriver.com \
--to=kun.song@windriver.com \
--cc=V.Sethi@nxp.com \
--cc=aymen.sghaier@nxp.com \
--cc=davem@davemloft.net \
--cc=filip.pudak@windriver.com \
--cc=gaurav.jain@nxp.com \
--cc=heng.guo@windriver.com \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=linux-crypto@vger.kernel.org \
--cc=meenakshi.aggarwal@nxp.com \
--cc=richard.danter@windriver.com \
/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