failed write verify causes segmentation fault
tglx at linutronix.de
Wed Mar 16 14:53:11 EST 2005
On Tue, 2005-03-15 at 19:09 -0600, Sergei Sharonov wrote:
> test conditions. I was testing NAND flash endurance at elevated
> temperatures and after a few weeks of continuous
> write/remount/read/verify/erase of a 10 MByte random test file
> the nand_verify_pages() failed and caused segmentation fault.
The write/verify failure is nothing scary. Its the nature of NAND Flash
that this can and will happen.
The segfault of your user space application/script is a consequence of a
BUG() in the kernel. This _is_ scary.
> Test setup: at91rm9200 based custom board, linux 2.6.10 patched with
> mtd-snapshot-20050123, JFFS2 filesystem (non-root) on a 2 Gbit Toshiba
> NAND chip, write verify enabled, compression disabled.
> Seems that when (eventually) write verify failed the system could not
> handle it graciously. Has anybody seen this before?
This should be handled by JFFS2 and I'm know for sure this worked some
time ago. I have no idea yet, which part of the code has been changed to
make this functionality go away. I will fake the write failure and check
whether I can reprocude your problem here. If it is reproducable then we
can fix it, if not we'll see. :)
> [<c00d9c40>] (jffs2_flash_writev+0x4/0x5a0) from [<c00d0694>]
> [<c00d0520>] (jffs2_write_dnode+0x0/0x684) from [<c00d14b0>]
> [<c00d11c8>] (jffs2_write_inode_range+0x0/0x46c) from [<c00ccae4>]
> [<c00cc93c>] (jffs2_commit_write+0x0/0x304) from [<c004ad34>]
Not very helpful to find the source of the problem, but thanks for
providing a detailed and descriptive bug report.
> After rebooting the file system appears to be intact except that the
> last file was partially written (1323008 bytes instead of 10000000)
> and CRC error:
That's an expected consequence of the problem.
More information about the linux-mtd