Patchwork add FAQ entry for "task pdflush:110 blocked for more than 120 seconds"

login
register
mail settings
Submitter Norbert van Bolhuis
Date Nov. 18, 2009, 1:23 p.m.
Message ID <200911181323.nAIDNf94012115@linpc062.aimsys.nl>
Download mbox | patch
Permalink /patch/38744/
State New
Headers show

Comments

Norbert van Bolhuis - Nov. 18, 2009, 1:23 p.m.
This FAQ entry explains the possible relationship with the
warning "INFO: task pdflush:110 blocked for more than 120 seconds" and the
UBI background thread.

Signed-off-by: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
---
 faq/ubifs.xml |   28 ++++++++++++++++++++++++++++
 1 files changed, 28 insertions(+), 0 deletions(-)
Artem Bityutskiy - Nov. 24, 2009, 3:03 p.m.
On Wed, 2009-11-18 at 14:23 +0100, Norbert van Bolhuis wrote:
> This FAQ entry explains the possible relationship with the
> warning "INFO: task pdflush:110 blocked for more than 120 seconds" and the
> UBI background thread.
> 
> Signed-off-by: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>

Tweaked and pushed to mtd-www, thanks.

Patch

diff --git a/faq/ubifs.xml b/faq/ubifs.xml
index 9a731c1..84a79d7 100644
--- a/faq/ubifs.xml
+++ b/faq/ubifs.xml
@@ -39,6 +39,7 @@ 
 	<li><a href="ubifs.html#L_sudden_ro">UBIFS suddenly became read-only - what is this?</a></li>
 	<li><a href="ubifs.html#L_lebsz_mismatch">I see this UBIFS error: "validate_sb: LEB size mismatch: 129024 in superblock, 126976 real"</a></li>
 	<li><a href="ubifs.html#L_ecc_error">I see this UBI error: "ubi_io_read: error -74 while reading 126976 bytes from PEB 47:4096, read 126976 bytes"</a></li>
+	<li><a href="ubifs.html#L_pdflush_blocked">Is UBI/UBIFS related to this error: "INFO: task pdflush:110 blocked for more than 120 seconds"?</a></li>
 	<li><a href="ubifs.html#L_study_ubifs">I want to study UBIFS - any recommendations?</a></li>
 </ol>
 
@@ -1146,6 +1147,33 @@  them properly. In that case the <code>-74</code> error happens when reading the
 first NAND page.</p>
 
 
+<h2><a name="L_pdflush_blocked">
+Is UBI/UBIFS related to this error: "INFO: task pdflush:110 blocked for more than 120 seconds"?
+</a></h2>
+
+<p>There is a known case for which the UBI background thread is related. If you are using
+NOR flash and UBI attaches to empty flash the UBI background thread will format it (only
+this way it can allow using the entire UBI volume). Formatting means that for
+each eraseblock it
+<ul>
+	<li>erases (very slow on NOR!)</li>
+	<li>writes the UBI headers</li>
+</ul>
+Depending on your CFI/MTD chip driver the "MTD/CFI chip lock" may be held for the time
+it needs to erase a block.
+User-space applications which manipulate files may be blocked by the UBI background thread because
+of the "MTD/CFI chip lock". This causes pdflush to block as well since it acquires the
+UBIFS journal io_mutex that the application holds. See
+<a href="http://lists.infradead.org/pipermail/linux-mtd/2009-November/027993.html">this</a>
+mail thread for details.
+There are two ways to solve this:
+<ol>
+	<li>ubiformat the entire NOR partition before UBI attaches</li>
+	<li>use erase-suspend for writing (if your chip supports this)</li>
+</ol>
+</p>
+
+
 
 <h2><a name="L_study_ubifs">I want to study UBIFS - any recommendations?</a></h2>