Re: Kernel oops after sync command in jffs2

[David Woodhouse <dwmw2@infradead.org>]

fgiasson@mediatrix.com said:
>  When the oops happen, the do_erase_oneblock() function if
> cfi_cmdset_0002.c complains that DQ5 has been asserted to "1" while
> the flash was still erasing, meaning that a program command has been
> attempted.  

> So I examined the chip driver to see if there were a gap in the mutual
> exclusion of the chip access.  I found that function
> cfi_amdstd_write() send unlock bypass command to the flash without
> verifying if the flash is ready first, if cfi->fast_prog is true.  I
> tryied to disable fast_prog in cfi_probe.c, and the oops did not
> happen again.  It sound like it were the problem, although I am not
> 100% sure yet.

Thanks. I've disabled fast programming mode completely, until the code gets 
fixed. 

That should have just caused an I/O error though; not an oops.


--
dwmw2