You are not logged in.

Dear visitor, welcome to Dreamboard. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Friday, December 10th 2010, 11:09am

CRC problems with JFFS2

From time to time, when starting up from poweroff (deep standby) I see these messages appearing :



JFFS2 notice: (27) check_node_data: wrong data CRC in data node at 0x00645000: read 0xd608c0ba, calculated 0xda5f595a

The result is that enigma2 somethimes does not start properly (tuner config not correct or somethimes or bus error when starting enigma binary)

After a warm reboot, the messages are gone. they only appear in first boot from a coldstart. Is this a software or hardware error causing this?

Any idea what could cause this problem?

Homey

Dreamer

Posts: 2,133

Location: NRW

Occupation: Softwareentwickler

  • Send private message

2

Saturday, December 11th 2010, 5:29am

already tried to flash the image/firmware again, using DREAMUP and the "Repair Bad Sector" Option? It sometimes can happen that a sector in the Nand flash goes bad ... if you flash with DREAMUP the bad sector will get marked as BAD again and never get used anymore.

Anyway, I saw that message on my box already too a few times already. But never had any problems ;)
Theorie ist, wenn man alles weiß, aber nichts funktioniert.
Praxis ist, wenn alles funktioniert aber niemand weiß warum.

3

Saturday, December 11th 2010, 11:44am

Thanks for your tip. I'll try it out.



I also saw this message in dmesg :

Bad eraseblock 719 at 0x059e0000
Bad eraseblock 1693 at 0x0d3a0000
Creating 7 MTD partitions on "NAND 256MiB 3,3V 8-bit":
0x0000000000000000-0x0000000010000000 : "complete"
0x0000000000000000-0x0000000000100000 : "loader"
0x0000000000100000-0x0000000000400000 : "boot partition"
0x0000000000400000-0x0000000004000000 : "root partition"
0x0000000004000000-0x0000000008000000 : "home partition"
0x0000000008000000-0x000000000f800000 : "unused partition"
0x000000000f800000-0x0000000010000000 : "preset partition"

The bad reaseblock is in the root partition. could it be related?

(nand is allowed to have bad eraseblocks at shipping. so for the moment I do not think a return for repair is needed.)



Is this forum also followed up by dream multimedia technicians itself?