From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from crowe.psilongbeach.com ([63.168.124.5]) by pentafluge.infradead.org with esmtp (Exim 4.14 #3 (Red Hat Linux)) id 19VbPG-0000T6-3j for ; Thu, 26 Jun 2003 19:23:38 +0100 Message-ID: <3EFB3A35.3060104@psilongbeach.com> Date: Thu, 26 Jun 2003 13:23:49 -0500 From: crowe@psilongbeach.com MIME-Version: 1.0 To: Kevin Liao References: <00fd01c33b07$948945e0$5f0a10ac@kevinliao> <004001c33bc9$a1b40260$5f0a10ac@kevinliao> In-Reply-To: <004001c33bc9$a1b40260$5f0a10ac@kevinliao> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: linux-mtd@lists.infradead.org Subject: Re: JFFS2 warning message List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Kevin Liao wrote: > Does anyone have any idea about this problem? Thanks a lot. > > Regards, > Kevin > > ----- Original Message ----- > From: "Kevin Liao" > To: > Sent: Wednesday, June 25, 2003 6:50 PM > Subject: JFFS2 warning message > > > >>Dear all, >> >>I had a mtd partition on NAND flash mounted as JFFS2. If the power was shutdown abnormally, after that each time when the system >>rebooted and tried to mount it again, I always saw a warning message "Empty flash at 0x00000a14 ends at 0x00000c00". Although I >>finally found that message was printed by jffs2_scan_eraseblock function in jffs2/scan.c, I still had no idea about what's really >>happened. Does anyone could explain the reason about that warning message or tell me what should I do to avoid the kernel's >>complaint? Thanks a lot. I see this warning message too, but the conditions are different (Type I flash, normal boot, ...). I haven't really dug into it, but I know that I've been creating the jffs2 file system image on a different machine (creating a target filesystem) on a i386 Linux box, then moving it over to my embedded arm target. I just assumed that it was generated by having slightly different versions jffs2, or that I have debugging turned on. Haven't had time to really look at it yet. So what I guess I'm saying is I see this too, and would also like to know how to get rid of it. Thanks -- Mike Crowe crowe@psilongbeach.com