From: Ronald Monthero <debug.penguin32@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: richard@nod.at, vigneshr@ti.com, heiko@sntech.de,
martin.blumenstingl@googlemail.com, paul@crapouillou.net,
robh@kernel.org, u.kleine-koenig@pengutronix.de,
debug.penguin32@gmail.com, AVKrasnov@sberdevices.ru,
r.czerwinski@pengutronix.de, andriy.shevchenko@linux.intel.com,
jaimeliao.tw@gmail.com, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Nicolas Ferre" <nicolas.ferre@microchip.com>
Subject: [PATCH v2] mtd: rawnand: Increment IFC_TIMEOUT_MSECS for nand controller response
Date: Tue, 14 Nov 2023 02:07:49 +1000 [thread overview]
Message-ID: <20231113160751.620810-1-debug.penguin32@gmail.com> (raw)
In-Reply-To: <20231113131634.614467-1-debug.penguin32@gmail.com>
Under heavy load it is likely that the controller is done
with its own task but the thread unlocking the wait is not
scheduled in time. Increasing IFC_TIMEOUT_MSECS allows the
controller to respond within allowable timeslice of 1 sec
fsl,ifc-nand 7e800000.nand: Controller is not responding
main/smp_fsm.c:1884 <inrcu: rcu_preempt detected stalls on CPUs/tasks:
rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P116/2:b..l
(detected by 1, t=2102 jiffies, g=7729, q=754)
task:irq/31-arm-irq1 state:D stack: 0 pid: 116 ppid: 2 flags:0x00000000
[<8064b97f>] (__schedule) from [<8064bb01>] (schedule+0x8d/0xc2)
[<8064bb01>] (schedule) from [<8064dacd>]
[<8064dacd>] (rt_mutex_slowlock_block.constprop.0) from [<8064db57>]
[<8064db57>] (__rt_mutex_slowlock.constprop.0) from [<8064dbf7>]
[<8064dbf7>] (rt_mutex_slowlock.constprop.0) from [<804b2047>]
[<804b2047>] (nand_get_device) from [<804b5335>] (nand_write_oob+0x1b/0x4a)
[<804b5335>] (nand_write_oob) from [<804a3585>] (mtd_write+0x41/0x5c)
[<804a3585>] (mtd_write) from [<804c1d47>] (ubi_io_write+0x17f/0x22c)
[<804c1d47>] (ubi_io_write) from [<804c047b>] (ubi_eba_write_leb+0x5b/0x1d0)
Cc: stable@vger.kernel.org
Signed-off-by: Ronald Monthero <debug.penguin32@gmail.com>
---
drivers/mtd/nand/raw/fsl_ifc_nand.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/nand/raw/fsl_ifc_nand.c b/drivers/mtd/nand/raw/fsl_ifc_nand.c
index 20bb1e0cb5eb..42f8ea46b6a8 100644
--- a/drivers/mtd/nand/raw/fsl_ifc_nand.c
+++ b/drivers/mtd/nand/raw/fsl_ifc_nand.c
@@ -21,7 +21,7 @@
#define ERR_BYTE 0xFF /* Value returned for read
bytes when read failed */
-#define IFC_TIMEOUT_MSECS 500 /* Maximum number of mSecs to wait
+#define IFC_TIMEOUT_MSECS 1000 /* Maximum number of mSecs to wait
for IFC NAND Machine */
struct fsl_ifc_ctrl;
--
2.34.1
next prev parent reply other threads:[~2023-11-13 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231113131634.614467-1-debug.penguin32@gmail.com>
2023-11-13 15:53 ` [PATCH v2] mtd: rawnand: Increment IFC_TIMEOUT_MSECS for nand controller response Ronald Monthero
2023-11-13 15:56 ` kernel test robot
2023-11-13 16:04 ` Andy Shevchenko
2023-11-13 16:11 ` Ronald Monthero
2023-11-13 17:32 ` [PATCH v3] " Ronald Monthero
2023-11-14 8:13 ` Miquel Raynal
2023-11-13 16:07 ` Ronald Monthero [this message]
2023-11-13 16:15 ` [PATCH v2] " Andy Shevchenko
2023-11-13 16:21 ` Ronald Monthero
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=20231113160751.620810-1-debug.penguin32@gmail.com \
--to=debug.penguin32@gmail.com \
--cc=AVKrasnov@sberdevices.ru \
--cc=andriy.shevchenko@linux.intel.com \
--cc=heiko@sntech.de \
--cc=jaimeliao.tw@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=miquel.raynal@bootlin.com \
--cc=nicolas.ferre@microchip.com \
--cc=paul@crapouillou.net \
--cc=philmd@linaro.org \
--cc=r.czerwinski@pengutronix.de \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vigneshr@ti.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