[Testing] 11.2.0 build 23 available for testing

[Mitch Bradley]

That is a huge number of bad blocks.

Two possibilities:

Either this NAND is close to complete failure, or else the bad block 
table has become corrupted.

You could try recreating the bad block table as follows:

ok select /nandflash  scrub!  unselect


On 6/18/2011 12:19 AM, forster at ozonline.com.au wrote:
>> If you tell us the addresses of the first 10-or-so bad blocks, we
>> could set up a laptop in the same way and try to reproduce. You can do
>> this by booting with the game-key-up cheat code
>> (http://wiki.laptop.org/go/Cheat_codes) and then using the arrow keys
>> to move to the first red block. When you get there it will say
>> something like "28f Marked bad in Bad Block Table". 28f is the
>> address. Then collect addresses of the next 9.
>
> rocker up gave me pong but scan-nand works
>
> bad blocks:
> a
> 1a
> 2a
> 3a
> 4a
> ... the a's through to fa
>
> then ok for a while
>
> the a's  30a thru to 3ba
> the a's  50a thru to 5ca
>
> first bad block thats not 'a' is at 6b1
>
>
>
> _______________________________________________
> Testing mailing list
> Testing at lists.laptop.org
> http://lists.laptop.org/listinfo/testing