From: crowe@psilongbeach.com
To: Kevin Liao <kevinliao@iei.com.tw>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 warning message
Date: Thu, 26 Jun 2003 13:23:49 -0500 [thread overview]
Message-ID: <3EFB3A35.3060104@psilongbeach.com> (raw)
In-Reply-To: <004001c33bc9$a1b40260$5f0a10ac@kevinliao>
Kevin Liao wrote:
> Does anyone have any idea about this problem? Thanks a lot.
>
> Regards,
> Kevin
>
> ----- Original Message -----
> From: "Kevin Liao" <kevinliao@iei.com.tw>
> To: <linux-mtd@lists.infradead.org>
> 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
next prev parent reply other threads:[~2003-06-26 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 10:50 JFFS2 warning message Kevin Liao
2003-06-26 9:59 ` Kevin Liao
2003-06-26 18:23 ` crowe [this message]
2003-06-26 22:33 ` Thomas Gleixner
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=3EFB3A35.3060104@psilongbeach.com \
--to=crowe@psilongbeach.com \
--cc=kevinliao@iei.com.tw \
--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