* Concern regarding Booting up of linux board ...
@ 2008-06-05 8:49 Misbah khan
2008-06-05 12:04 ` Josh Boyer
2008-06-05 12:26 ` Misbah khan
0 siblings, 2 replies; 4+ messages in thread
From: Misbah khan @ 2008-06-05 8:49 UTC (permalink / raw)
To: linuxppc-embedded
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 <><
--
View this message in context: http://www.nabble.com/Concern-regarding-Booting-up-of-linux-board-...-tp17665078p17665078.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Concern regarding Booting up of linux board ...
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
1 sibling, 0 replies; 4+ messages in thread
From: Josh Boyer @ 2008-06-05 12:04 UTC (permalink / raw)
To: Misbah khan; +Cc: linuxppc-embedded
On Thu, 5 Jun 2008 01:49:27 -0700 (PDT)
Misbah khan <misbah_khan@engineer.com> 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 :-
This is the linux powerpc embedded list. I'm sure there are ARM lists
somewhere, which can probably help you much more than this one can.
josh
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Concern regarding Booting up of linux board ...
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
2008-06-05 12:32 ` Marco Stornelli
1 sibling, 1 reply; 4+ messages in thread
From: Misbah khan @ 2008-06-05 12:26 UTC (permalink / raw)
To: linuxppc-embedded
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Concern regarding Booting up of linux board ...
2008-06-05 12:26 ` Misbah khan
@ 2008-06-05 12:32 ` Marco Stornelli
0 siblings, 0 replies; 4+ messages in thread
From: Marco Stornelli @ 2008-06-05 12:32 UTC (permalink / raw)
To: Misbah khan; +Cc: linuxppc-embedded
Misbah khan ha scritto:
>
>
> 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 <><
>
Ok but for this mailing list a generic problem related to booting of a
board is off-topic. You can certainly find a mailing list about JFFS2.
--
Marco Stornelli
Embedded Software Engineer
CoRiTeL - Consorzio di Ricerca sulle Telecomunicazioni
http://www.coritel.it
marco.stornelli@coritel.it
+39 06 72582838
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-06-05 12:30 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2008-06-05 12:32 ` Marco Stornelli
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).