From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: JFFS2: INFO: task touch:2827 blocked for more than 120 seconds.
Date: Tue, 13 Oct 2020 15:11:23 +0000 [thread overview]
Message-ID: <50936dea01571575bce58d985730fb533bf340f3.camel@infinera.com> (raw)
Got this on 4.19.127:
[ 738.602063] Waiting for chip to be ready timed out.
[ 738.607294] jffs2: Newly-erased block contained word 0x1108114c at offset 0x010ae000
[ 738.609372] jffs2: Header CRC failed on REF_PRISTINE node at 0x00de01e4: Read 0x11481108, calculated 0xf421d7f4
[ 967.758099] INFO: task touch:2827 blocked for more than 120 seconds.
[ 967.764465] Tainted: G O 4.19.127+ #4
[ 967.769955] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 967.777807] touch D 0 2827 2754 0x00000000
[ 967.777812] Call Trace:
[ 967.777818] [d978fba0] [1008486c] 0x1008486c (unreliable)
[ 967.777827] [d978fc60] [c0386a28] __schedule+0x170/0x440
[ 967.777832] [d978fca0] [c0386d2c] schedule+0x34/0x9c
[ 967.777837] [d978fcb0] [c0386f44] schedule_preempt_disabled+0x10/0x20
[ 967.777843] [d978fcc0] [c0387b40] __mutex_lock.isra.12+0x174/0x2f4
[ 967.777851] [d978fd00] [c013b100] jffs2_reserve_space+0x38/0x298
[ 967.777856] [d978fd60] [c013e170] jffs2_do_create+0x38/0x324
[ 967.777860] [d978fda0] [c01382e8] jffs2_create+0xa8/0x164
[ 967.777868] [d978fdc0] [c00e05a8] path_openat+0xab0/0xf8c
[ 967.777873] [d978fe50] [c00e1ac4] do_filp_open+0xac/0xfc
[ 967.777878] [d978ff00] [c00cec08] do_sys_open+0x154/0x21c
[ 967.777885] [d978ff40] [c000f1d8] ret_from_syscall+0x0/0x3c
[ 967.777890] — interrupt: c01 at 0xff47d2c
[ 967.777890] LR = 0xffeca78
This "ready timed out" is likely an Erase resume(not sure though) that times out and indicate that the flash is somewhat buggy.
What surprises me is that it hung "touch" and lost some files in a directory, seems like error recovery
in jffs2 is somewhat lax, a tmo here should not hang/loose files I think.
Jocke
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
reply other threads:[~2020-10-13 15:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50936dea01571575bce58d985730fb533bf340f3.camel@infinera.com \
--to=joakim.tjernlund@infinera.com \
--cc=linux-mtd@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).