Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 1 hr ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 1 day, 21 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 6 hrs ago - more...
 |
|
2015-06-15
, 18:41
|
|
Posts: 868 |
Thanked: 2,516 times |
Joined on Feb 2012
@ Germany
|
#3
|
Originally Posted by PMaff
I guess your N900 runs as it should? It seems you have an initial bad block.
Does this mean the memory of my good old trusty N900 is getting faulty?
What can I do?
ECC errors is a normal phenomena on OneNAND and they happen quite often. Flash-aware file-systems like JFFS2 or UBIFS are able to handle them gracefully.
since ECC errors are supposed to be handled by upper level SW, we do not really have to print these messages, and we may consider them as debugging prints.
I advise you to save important data every week. Everything can die. Sometimes a reflash could wake up again.
__________________
N900: gpxsee, fahrplan, gpscon, genwall, qrcode, hextool, libjansson4, libevent-2.0-5, cnee, psi-plus, mihphoto, shc
Maemo flasher/rescue live image.
Fremantle Harmattan SDK VM
N900: gpxsee, fahrplan, gpscon, genwall, qrcode, hextool, libjansson4, libevent-2.0-5, cnee, psi-plus, mihphoto, shc
Maemo flasher/rescue live image.
Fremantle Harmattan SDK VM
| The Following 2 Users Say Thank You to Halftux For This Useful Post: | ||
 |
| Tags |
| memory fault, n900 memory |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 02:34.
...
[29809.985687] OneNAND driver initializing
[29809.986907] omap2-onenand omap2-onenand: initializing on CS0, phys base 0x04000000, virtual base d0880000
[29809.986999] OneNAND Manufacturer: Samsung (0xec)
[29809.987030] Muxed OneNAND 256MB 1.8V 16-bit (0x40)
[29809.987060] OneNAND version = 0x0121
[29809.987091] Chip support all block unlock
[29809.987091] Chip has 2 plane
[29809.988616] Scanning device for bad blocks
[29810.026184] onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400
[29810.026214] Bad eraseblock 668 at 0x05380000
...
[29810.109252] UBI: physical eraseblock size: 131072 bytes (128 KiB)
[29810.109283] UBI: logical eraseblock size: 129024 bytes
[29810.109344] UBI: smallest flash I/O unit: 2048
[29810.109375] UBI: sub-page size: 512
[29810.109405] UBI: VID header offset: 512 (aligned 512)
[29810.109436] UBI: data offset: 2048
[29810.243835] UBI: attached mtd5 to ubi0
[29810.243896] UBI: MTD device name: "rootfs"
[29810.243927] UBI: MTD device size: 251 MiB
[29810.243957] UBI: number of good PEBs: 2009
[29810.243988] UBI: number of bad PEBs: 1
...
[29810.244171] UBI: total number of reserved PEBs: 2009
[29810.244201] UBI: number of PEBs reserved for bad PEB handling: 20
[29810.244232] UBI: max/mean erase counter: 407/61
[29810.244262] UBI: image sequence number: 1
..."
Does this mean the memory of my good old trusty N900 is getting faulty?
What can I do?