Re: Re: UBIFS and bad blocks

2011-09-24 Thread forster
 Hi,
 
 Thanks for the logs, but they seem to be a bit messed up, e.g.

sorry, here they are attached

tony

ubif-capture text.doc
Description: MS-Word document
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: UBIFS and bad blocks

2011-09-21 Thread Daniel Drake
Hi,

Thanks for the logs, but they seem to be a bit messed up, e.g.

On Sun, Sep 18, 2011 at 2:21 AM,  fors...@ozonline.com.au wrote:
 Bad block at 0x1e14 = page 0x3c280 = eblock 0xf0a
  cons
 Bad block at 0x1e34 = page 0x3c680 = eblock 0xf1a
 Loading ramdisk image from /pci/nandflash@c:\
 Bad block at 0x1e54 = page 0x3ca80 = eblock 0xf2a
 [    0.00] Linux ve
 Bad block at 0x1e74 = page
 Bad block at 0x2234 = page 0x44680 = eblock 0x111ae814000
 Bad block at 0x2254 = page 0x44a80 = eblock 0x112a0e814600 - 0ec0
 Bad block at 0x2274 = page 0x44e80 = eblock 0x113a - 00bc4a00
 Bad block at 0x2294 = page 0x45280 = eblock 0x114a00e814600 - 
 0ebf to 007d9000
 Bad block at 0x22b4 = page 0x45680 = eblock 0x115a
  - 00bc49ff
 [    0.00] 232M
 Bad block at 0x22d4 = page 0x45a80 = eblock 0x116a
 [    0.00]   mapped low ram: 0 - 0e814000
 Bad block at 0x22f4 = page 0x45e80 = eblock 0x117a  low ram: 0 - 0e814000
 Bad block at 0x2314 = page 0x46280 = eblock 0x118a14000
 Bad block at 0x2334 = page 0x46680 = eblock 0x119a

 Bad block at 0x2614 = page 0x4c280 = eblock 0x130a10]    BIOS 
 reserved == [09fc00 -

This looks like a copy/paste issue from a buffer. Could you instead
configure your serial console software to log to a file, and then just
send the file? With minicom this is Ctrl+A then L, or with screen this
is: screen -L /dev/ttyUSB0 115200

Thanks,
Daniel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel