From: Scott Branden <sbranden@broadcom.com>
To: <linux-mtd@lists.infradead.org>
Subject: suspect UBIFS async operations causing issues during reboot
Date: Wed, 5 Nov 2014 00:32:16 -0800 [thread overview]
Message-ID: <5459E090.1010300@broadcom.com> (raw)
We are doing reboot testing with UBIFS on the 3.10 kernel with a new
chipset we are working on.
Over 1000's of reboots we eventually find that the NAND has
uncorrectable ECC errors reported on a random page when it is mounted.
We have found the problem is that a NAND erase operation is in progress
when the reboot occurs. Since the NAND is in the middle of the erase
operation the page is mostly FF with some random bits not erased when
the reboot occurs.
We suspect the problem is the asynchronous nature of the UBIFS
operations. Perhaps the small write buffer that can take 3-5 seconds to
be written or some other operation occuring in UBI/UBIFS? I don't think
the shutdown of the filesystem is dealing with all the threads properly.
Log below with printks adding in iproc_nand driver showing erase
operations in progress when "Restarting system." happens.
Stopped Setup Virtual Console.
Stopping Apply Kernel Variables...
Stopped Apply Kernel Variables.
Starting Notify Audit System and Update UTMP about System Shutdown...
Stopping Runtime Directory...
Stopping Remount API VFS...
Stopped Remount API VFS.
Stopping Remount Root FS...
Stopped Remount Root FS.
Stopping Collect Read-Ahead Data...
Stopped Collect Read-Ahead Data.
Stopping Media Directory...[ 18.370000] systemd[1]: Unit
systemd-readahead-collect.service entered failed state.
Started Console System Reboot Logging.
Stopped Runtime Directory.
Stopped Media Directory.
[ 18.490000] systemd[1]: Shutting down.
Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
Unmounting file systems.
[ 18.530000] iproc_nand_cmdfunc: cmd 0x60 addr 0x14a40000
[ 18.540000] iproc_nand_waitfunc: native cmd 8 intfc status 0xc00000e0
[ 18.550000] UBIFS: background thread "ubifs_bgt0_0" stops
Disabling swaps.
Detaching loop devices.
Detaching DM devices.
[ 18.560000] iproc_nand_cmdfunc: cmd 0x60 addr 0x18680000
[ 18.570000] iproc_nand_waitfunc: native cmd 8 intfc status 0xc00000e0
[ 18.580000] Restarting system.
[ 18.580000] iproc_nand_cmdfunc: cmd 0x60 addr 0x18700000
<REBOOT happens here with NAND ERASE COMMAND in progress corrupting
0x18700000 NAND Addresses!> Corrupted NAND only happens when erase
operation in progress when restarting system happens.
next reply other threads:[~2014-11-05 8:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 8:32 Scott Branden [this message]
2014-11-05 9:22 ` suspect UBIFS async operations causing issues during reboot Richard Weinberger
2014-11-05 17:56 ` Scott Branden
2014-11-05 18:21 ` Richard Weinberger
2014-11-05 22:52 ` Scott Branden
2014-11-06 21:56 ` Scott Branden
2014-11-07 8:45 ` Richard Weinberger
2014-11-07 17:31 ` Scott Branden
2014-11-09 10:20 ` Richard Weinberger
2014-11-10 5:10 ` Scott Branden
2014-11-26 8:17 ` Brian Norris
2014-11-26 8:30 ` Richard Weinberger
2014-11-26 9:25 ` Brian Norris
2014-11-27 19:07 ` Scott Branden
2014-11-10 8:44 ` Ricard Wanderlof
2014-11-10 9:08 ` Richard Weinberger
2014-11-10 7:44 ` Tanya Brokhman
2014-11-12 11:20 ` Artem Bityutskiy
2014-11-15 3:30 ` Scott Branden
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=5459E090.1010300@broadcom.com \
--to=sbranden@broadcom.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).