Kernel oops after sync command in jffs2

David Woodhouse dwmw2 at
Wed May 22 02:27:10 EDT 2002

fgiasson at said:
> The 'called while erasing!' message means that I put a trace in the
> map driver write16() function to tell me if write16()is called when a
> global variable is set.  This global variable indicates that
> do_erase_oneword has sent the erase sector command and is currently
> polling for the erase operation to complete. 

OK. We already fixed one of these by disabling fast programming mode, after 
you pointed out that it was sending the unlock command without paying due 
attention to the state machine. If you're definitely using v1.55 of 
cfi_cmdset_0002.c, can you put a BUG() in the mtxmap_write16() call just 
after it prints the 'called while erasing!' message, and we'll see where 
it's being called _from_. 


More information about the linux-mtd mailing list