From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [81.3.11.18] (helo=mail.ku-gbr.de) by canuck.infradead.org with esmtps (Exim 4.52 #1 (Red Hat Linux)) id 1EFuUf-0006NO-4v for linux-mtd@lists.infradead.org; Thu, 15 Sep 2005 10:13:50 -0400 Received: from p5482748b.dip.t-dialin.net ([84.130.116.139]:59079 helo=synertronixx3) by mail.ku-gbr.de with esmtpa (Exim 4.50 #1 (Debian)) id 1EFudf-0005dY-Sd for ; Thu, 15 Sep 2005 16:23:00 +0200 Received: from localhost ([127.0.0.1] helo=synertronixx3.doom ident=konsti) by synertronixx3 with esmtp (Exim 3.36 #1 (Debian)) id 1EFuUX-0002Ao-00 for ; Thu, 15 Sep 2005 16:13:33 +0200 Date: Thu, 15 Sep 2005 16:13:33 +0200 Message-ID: <87ek7qpgfm.wl%kletschke@synertronixx.de> From: Konstantin Kletschke To: linux-mtd@lists.infradead.org MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Subject: How to cope with locked flash List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , How do you people cope with flash devices that power up locked? I have intel K3 devices which are unlocked by flash_unlocke in the /etc/inittab while booting the system. However, if the fs was never mounted before the jffs2 hangs with this in an endless loop: jffs2_write_dirent in garbage_collect_dirent failed: -30 Write of 43 bytes at 0x00363928 failed. returned -30, retlen 0 Not marking the space at 0x00363928 as dirty because the flash driver returned retlen zero Is there any help to avoid this situation? Konsti PS.: sorry, I missed the subject in my mail before so it looks like spam :( I am still trying to get used to my new MUA :-/ -- GPG KeyID EF62FCEF Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF