You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My employer has noticed a small fraction of devices failing with a trunk-based software image (OpenWrt SNAPSHOT, r13134+521-f57230c4e6) on the WPJ428 platform (ipq40xx).
After reboot, the problem goes away (probably because it's very unlikely to appear twice in a row).
The problem occurs with various flash chip revisions, so we believe it is a driver issue.
On an (un-)lucky day, the error occured on my device and i created two dumps of /dev/mtd8ro (the whole 32M of flash), one while error was occuring and another after the reboot.
1290 consecutive bytes are read as FF in the error state (reliably when running dd multiple times).
The diff from before and after the reboot looks like this (cmp -l output converted to hex, xx for redacted bytes):
01BB36BD FF xx
01BB36BE FF xx
01BB36BF FF xx
01BB36C0 FF xx
...
01BB3BC7 FF xx
The syslog from above belongs to the same occurance as diff.
It's worth noting that the file that couldn't be read is in the ROM portion of the flash while the offset of the diff is near the end.
I've reached the limits of my knowledge. If there's anything else that would be interesting to know from the error state, let me know, i'll see what i can do.
The text was updated successfully, but these errors were encountered:
yogo1212:
Hello :-)
My employer has noticed a small fraction of devices failing with a trunk-based software image (OpenWrt SNAPSHOT, r13134+521-f57230c4e6) on the WPJ428 platform (ipq40xx).
Messages like these appear in syslog:
After reboot, the problem goes away (probably because it's very unlikely to appear twice in a row).
The problem occurs with various flash chip revisions, so we believe it is a driver issue.
On an (un-)lucky day, the error occured on my device and i created two dumps of /dev/mtd8ro (the whole 32M of flash), one while error was occuring and another after the reboot.
1290 consecutive bytes are read as FF in the error state (reliably when running dd multiple times).
The diff from before and after the reboot looks like this (
cmp -l
output converted to hex, xx for redacted bytes):The syslog from above belongs to the same occurance as diff.
It's worth noting that the file that couldn't be read is in the ROM portion of the flash while the offset of the diff is near the end.
I've reached the limits of my knowledge. If there's anything else that would be interesting to know from the error state, let me know, i'll see what i can do.
The text was updated successfully, but these errors were encountered: