• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: My plug stopped working! "Bad Data CRC"  (Read 1267 times)
elBradford
Newbie
*

Karma: 0
Posts: 44


View Profile
« on: May 01, 2009, 04:37:15 PM »

In this crowd I am a total newbie. I did manage to get the supplied ubuntu image installed using tftp and nfs. I have installed lighttpd, mysql, php5 (wordpress), samba, transmission and it all works great.

Today I was moving some stuff I got off of torrents around (using an external USB HDD). I noticed performance was sluggish, and had windows have a few complaints like the share was disconnected. They were immediately resolved though. I typed in the top command in the console, and smbd (or something like that, the samba daemon) was about 96% cpu utilization. After that my console connection crashed. I rebooted the plug, couldn't connect.

After connecting using the serial cable, this is the output I get when booting:

Code:
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Mar  2 2009 - 12:16:00) Marvell version: 3.4.16

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CEE60

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x100000, size 0x400000

Reading data from 0x4ff800 -- 100% complete.
 4194304 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2009-04-04   1:49:44 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2070252 Bytes =  2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC

I'm booting off the SDIO following instructions on the wiki. When I printenv, all the required settings are  the same - I wonder is my NAND flash bad?

Hope this is the right forum. Any input would be much appreciated! Thank you!
Logged

elBradford
Newbie
*

Karma: 0
Posts: 44


View Profile
« Reply #1 on: June 01, 2009, 08:35:28 AM »

I re-flashed the kernel onto the NAND using the USB recovery package from marvel. I then changed the rootfs back to the SD card and everything worked for about 2 weeks.

Again, yesterday, I have the same exact error as before - bad crc when loading the kernel. I fixed it again using the USB recovery drive.


I really don't want to do this every 2 weeks. Does anyone have some helpful advice on what this might be? I am very noobly when it comes to NAND and pretty noobly with anything linux.
Logged

tony.p.lee
Newbie
*

Karma: 0
Posts: 11


View Profile
« Reply #2 on: June 06, 2009, 06:59:23 AM »


This can happen if there is a script/command that accidently overwrite the kernel image partitions in the NAND.

It is tough to debug when and why that can happen.

1) Double check all the partition commands and make sure there is no overlapping in the NAND flash partition.
2) To debug it - try to dump the first 8-16 bytes of every 4K block in the kernel image.
Once for the non-corrupted image
Once for the corrupted image.
Diff the output.

That might give you some hints on where the corruption start and can start zoom into "why".

Logged

Pages: [1]
Print
Jump to: