simulate a bad NAND block cause kernel hang

[Thomas Gleixner]

On Thu, 2005-08-25 at 09:27 -0400, ahgu wrote:
> I forced the flash_erase function to fail. I expect the jffs2 will pick up 
> the return error and mark the block bad and put the bad block in a bad_block 
> list. But what I get is kernel failure:
> I get similar error when I simulate a write error.
> Am I doing the bad block simulation correctly? Is this a correct response? 
> What is supposed to happen when the NAND flash grow a bad block?

JFFS2 should handle this.

The oops trace is worthless, as it does not show the stack trace in
human readable form (function names decoded) 

Make sure that CONFIG_KALLSYMS is set in your kernel .config file. 

Also information about kernel version and possibly applied MTD/JFFS2
patches is missing.


tglx