From: Misbah khan <misbah_khan@engineer.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Concern regarding Booting up of linux board ...
Date: Thu, 5 Jun 2008 05:26:15 -0700 (PDT) [thread overview]
Message-ID: <17668657.post@talk.nabble.com> (raw)
In-Reply-To: <17665078.post@talk.nabble.com>
Misbah khan wrote:
>
> Hi all ..
>
> we are using IMX-31 (ARM Core) processor with Linux 2.6 and redboot as
> boot loader with jffs2 for NAND flash and facing the concerned problem :-
>
> The board is booting fine but it sometimes takes 21 sec to boot and
> sometimes takes 31 sec to boot which is a concern for us actually it takes
> usually 21 sec and 31 sec sometimes
>
> If we remove the power after booting and again insert the power supply It
> gives the following warning message related to jffs2 ....
>
> JFFS2 notice: (878) check_node_data: wrong data CRC in data node at
> 0x011dec00: read 0x2464ba56, calculated 0x474915f8.
> JFFS2 notice: (878) check_node_data: wrong data CRC in data node at
> 0x0112be00: read 0x149efa32, calculated 0x8f32b0eb.
> JFFS2 notice: (878) check_node_data: wrong data CRC in data node at
> 0x0112ba00: read 0xdcfafeb2, calculated 0xb86eb888.
> JFFS2 notice: (878) check_node_data: wrong data CRC in data node at
> 0x013e8600: read 0x20bed1fc, calculated 0xe9509808.
> JFFS2 notice: (878) check_node_data: wrong data CRC in data node at
> 0x013e9200: read 0x6e4f40bd, calculated 0x28248aa4.
> JFFS2 notice: (878) check_node_data: wrong data CRC in data node at
> 0x013e8e00: read 0x6e4f40bd, calculated 0x59eaeede.
> JFFS2 notice: (878) check_node_data: wrong data CRC in data node at
> 0x011df000: read 0x6e4f40bd, calculated 0xbf916037.
> JFFS2 notice: (878) check_node_data: wrong data CRC in data node at
> 0x011dde00: read 0x6e4f40bd, calculated 0x946d0599.
> JFFS2 notice: (878) check_node_data: wrong data CRC in data node at
> 0x011dc800: read 0x6e4f40bd, calculated 0x1e890eaa.
> JFFS2 notice: (759) check_node_data: wrong data CRC in data node at
> 0x008c0200: read 0xd3ad877b, calculated 0xf4f0b5f9.
> JFFS2 notice: (759) check_node_data: wrong data CRC in data node at
> 0x0097b800: read 0x8d0623a1, calculated 0xefce6ce7.
> JFFS2 notice: (759) check_node_data: wrong data CRC in data node at
> 0x00965200: read 0x8d0623a1, calculated 0x92a2a227.
>
> Having never experienced this before i do believe that this could be the
> jffs2 related concern hence just thinking of using YAFFS to increase the
> booting effeciency ...
>
>
> I would remain thankful if any of you could share your experience or
> thaught regarding this ...
>
> Thank you
> Misbah <><
>
Thank you for your reply ....
This is not related to ARM processor specific rather its a generic problem
related to booting of Board Hence need for your help ...
Misbah <><
--
View this message in context: http://www.nabble.com/Concern-regarding-Booting-up-of-linux-board-...-tp17665078p17668657.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
next prev parent reply other threads:[~2008-06-05 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 8:49 Concern regarding Booting up of linux board Misbah khan
2008-06-05 12:04 ` Josh Boyer
2008-06-05 12:26 ` Misbah khan [this message]
2008-06-05 12:32 ` Marco Stornelli
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=17668657.post@talk.nabble.com \
--to=misbah_khan@engineer.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).