![]() |
Lots of ECC errors in dmesg
Hello,
I ran dmesg and got quite a lot of errors like this: Code:
correctable ECC error = 0x5555, addr1 0xa, addr8 0x0 Rebooted approx. 3 times and output is always like this. My N9 is a bit older than a year and I really hope that doesn't mean it's failing? Thanks, b. |
Re: Lots of ECC errors in dmesg
its a feature, just ignore those lines :)
|
Re: Lots of ECC errors in dmesg
I've had them too. But it disappeared. Flash memory will fail, that's why the ECC is there. I guess at some point the controller will swap the faulty block for a fresh spare one, so the errors go away.
|
Re: Lots of ECC errors in dmesg
Quote:
|
Re: Lots of ECC errors in dmesg
Correct me if I'm wrong, but I looked for those errors in code and they originated from a piece of code used for Samsung's OneNAND, which is flash memory.
AFAIK there's OMAP's 512MiB internal/embedded flash, and the 16/64GB "external". Is that what you meant? I've read that worn out flash cells could be revitalized by heating them. You can try putting your device in the oven :D (kidding here ofc. But flash-heating is a valid way to fix it.) |
Re: Lots of ECC errors in dmesg
Quote:
|
Re: Lots of ECC errors in dmesg
Quote:
See, the densities are growing anyway so mfg's will offer larger capacity devices all the time, obsoleting the smaller devices. There's no need to obsolete devices by building in faults... |
Re: Lots of ECC errors in dmesg
Quote:
The same ECC principles should still apply though regardless of whether the memory is volatile or non-volatile. Interestingly enough, OneNAND is actually known as "fusion" memory which not only consists of flash memory but also includes a 5KB SRAM buffer (as well as controller logic and hardware ECC) on the same chip so it's possible (but not likely) that the errors come from the SRAM buffer. |
All times are GMT. The time now is 23:16. |
vBulletin® Version 3.8.8