From: Vijay Nikam <vijay.t.nikam@gmail.com>
To: Ron Madrid <ron_madrid@sbcglobal.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: JFFS2 warnings
Date: Fri, 5 Mar 2010 15:36:00 +0530 [thread overview]
Message-ID: <f234e2141003050206p7b945f8flfac60914b9239772@mail.gmail.com> (raw)
In-Reply-To: <248783.45498.qm@web83507.mail.sp1.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
Hello,
I too facing the same problems. I too have mpc8313 based customized board.
Would you please let me know, if you know how to resolve these messages.
Kindly please acknowledge, thank you
Kind Regards,
Vijay Nikam
On Tue, Mar 2, 2010 at 12:13 AM, Ron Madrid <ron_madrid@sbcglobal.net>wrote:
> I'm getting a bunch of these after I 'reboot' or 'poweroff'
> several times.
>
> Empty flash at 0x0056205c ends at 0x00562800
> Empty flash at 0x00565334 ends at 0x00565800
> Empty flash at 0x00576104 ends at 0x00576800
>
> JFFS2 notice: (848) check_node_data: wrong data CRC
> in data node at 0x00577034: read 0xe6adad18, calculated
> 0x202a305c.
> JFFS2 notice: (848) check_node_data: wrong data CRC
> in data node at 0x00575768: read 0xe6adad18, calculated
> 0xfc64f8a3.
>
> I'm not too sure why I'm getting these, but recently
> they seem to have caused a few problems with parts of
> my filesystem (i.e. programs not running correctly).
>
> Can someone tell me what these are or what could be
> causing them?
>
> I'm using 2.6.33rc1 and this is on an mpc8313 based board.
> Not sure what other info would be useful.
>
> Thanks,
>
> Ron
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
[-- Attachment #2: Type: text/html, Size: 1873 bytes --]
prev parent reply other threads:[~2010-03-05 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 18:43 JFFS2 warnings Ron Madrid
2010-03-05 10:06 ` Vijay Nikam [this message]
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=f234e2141003050206p7b945f8flfac60914b9239772@mail.gmail.com \
--to=vijay.t.nikam@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=ron_madrid@sbcglobal.net \
/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).