FS#4035 - Broken NAND ECC with kernel 5.10 on Fritzbox 7362 SL #7043
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
{{ message }}
janhoffmann:
Something about NAND seems to be broken with kernel 5.10 on Fritzbox 7362 SL (using Micron 29F1G08ABADA flash chip). Data written with kernel 5.10 results in ECC errors when read with kernel 5.4 (and vice versa).
When the kernel image is written using kernel 5.10, the bootloader refuses to boot it due to a NAND read error:
ROM VER: 1.1.4 CFG 05 ** START RVEC bf200000 [/](AVM) EVA Revision: 1.1964 Version: 2964
(C) Copyright 2005 AVM Date: Nov 8 2013 Time: 15:45:15 (0) 3 0x0-0x740D
[FLASH:] WINBOND Uniform-Flash 1MB 256 Bytes WriteBuffer
[FLASH:](Eraseregion [0] 16 sectors a 64kB)
[NAND:] 128MB MICRON 2048 Pagesize 128k Blocksize 1024 Blocks 8Bit 1 CS HW
[SYSTEM:] VR9 on 500MHz/250MHz/250MHz
.Atheros 8030/35 detected
Eva_AVM >##[nand_read]<ERROR: page 0x0 - -6>
[nand_read]<ERROR: page 0x3400000 - -6>
<ERROR: FIRMWARE_ILLEGAL_CONFIG>
To get back to a working state, one needs to boot a image with kernel 5.4 via FTP and erase the kernel and ubi MTD partitions before performing a sysupgrade.
Here is an excerpt from dmesg showing ECC read errors (many errors like this are printed):
[ 345.485685] __nand_correct_data: uncorrectable ECC error [ 345.490813] ubi0 warning: ubi_io_read: error -77 (ECC error) while reading 64 bytes from PEB 941:0, read only 64 bytes, retry [ 345.502176] __nand_correct_data: uncorrectable ECC error [ 345.507421] ubi0 warning: ubi_io_read: error -77 (ECC error) while reading 64 bytes from PEB 941:0, read only 64 bytes, retry [ 345.518792] __nand_correct_data: uncorrectable ECC error [ 345.523979] ubi0 warning: ubi_io_read: error -77 (ECC error) while reading 64 bytes from PEB 941:0, read only 64 bytes, retry [ 345.535428] __nand_correct_data: uncorrectable ECC error [ 345.540686] ubi0 error: ubi_io_read: error -77 (ECC error) while reading 64 bytes from PEB 941:0, read 64 bytes [ 345.550746] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.63 #0 [ 345.556685] Stack : 80788ec0 00000000 822c8c00 80082154 808a0000 80789c34 00000000 00000000 [ 345.565047] 81425c24 80e70000 80757e04 814383b8 80826ba7 00000001 81425bc8 4cc6774e [ 345.573398] 00000000 00000000 80757e04 81425a60 c000c40c 0000d40c 00000000 ffffffea [ 345.581754] 0000e40c 81425a6c 0000040c 8082c600 00000000 00000001 00000000 80750000 [ 345.590110] 00000000 075a0000 00000040 00000000 00000018 00000030 00000000 80e70000 [ 345.598465] ... [ 345.600900] Call Trace: [ 345.603348] [<8000bd90>] show_stack+0x30/0x100 [ 345.607801] [<80362be8>] dump_stack+0x9c/0xcc [ 345.612136] [<80438e04>] ubi_io_read+0x208/0x3f4 [ 345.616749] [<804392a4>] ubi_io_read_ec_hdr+0x64/0x298 [ 345.621898] [<8043f06c>] ubi_attach+0x374/0x1568 [ 345.626509] [<80432a28>] ubi_attach_mtd_dev+0x4f0/0xbfc [ 345.631733] [<808c7ec8>] ubi_init+0x33c/0x3e0 [ 345.636072] [<80002648>] do_one_initcall+0x50/0x1ac [ 345.640968] [<808ae07c>] kernel_init_freeable+0x26c/0x304 [ 345.646342] [<8066e60c>] kernel_init+0x10/0x100 [ 345.650886] [<80006d58>] ret_from_kernel_thread+0x14/0x1cThe text was updated successfully, but these errors were encountered: