On Wed, Feb 27, 2008 at 12:51 AM, Peter Teoh <htmldeveloper@xxxxxxxxx> wrote: > On Thu, Feb 21, 2008 at 3:21 PM, tomy <tomy@xxxxxxxxxxxx> wrote: > > > Hi, > > During Linux booting, some bad erase block printf is coming as following. > > Scanning device for bad blocks > > Bad eraseblock 0 at 0x00000000 > > Bad eraseblock 1 at 0x00020000 > > Bad eraseblock 2 at 0x00040000 > > Bad eraseblock 3 at 0x00060000 > > Bad eraseblock 8 at 0x00100000 > > Bad eraseblock 9 at 0x00120000 > > ..... > > What will be reason behind this ?. > > > > -- > > Thanks & Regards > > > > Tomy Devasia > > Product Devpt & Support > > Kalki Communication Technologies Ltd > > Bangalore > > India > > > > > > Found here: > > ./drivers/mtd/onenand/onenand_bbt.c: > printk(KERN_WARNING "Bad eraseblock %d > at 0x%08x\n", > > ./drivers/mtd/nand/nand_bbt.c: > printk(KERN_WARNING "Bad eraseblock %d at 0x%08x\n", > > May be Thomas will have better insights. What happened is that the > NAND devices may have a BBT (bad block table) setup within by the > manufacturer. And Linux kernel is reading it, but as indicated, it > is just a warning, as anything in the BBT "should" not be read by the > kernel. > > The reason that I suggested to check the timings etc. is that the bad blocks start from 1 and counts sequentially. I doubt that there is an actual bad block... Another reason is that tomy seems relatively new to all of this, so this could be a likely cause of error. Thomas -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
