[mk01]

@CurlyMo

the issues we are having "sudden breaking of sd/mmc errors":

in october RPI "programmers" have been playing with internal clocking on busses again (both firmware and kernel above 3.10.24+). at first the issues have been explained as user/hw error and again stupid user.

until I yesterday found this:

https://github.com/raspberrypi/linux/issues/467#issuecomment-31073648

I as was joking that maybe this is the SD card corruption fix - it was true. official fix for bad design was fixing one freq to another freq to avoid collisions but somehow they don't think of freq changes on core, they don't consider OC system. for OC system they just made possibility of corruption 2.5x higher, because emmc changed from 100 to 250 (to match vpu) but on such system it is again not 250 (at 420core clock it is 210VPU).

so thanks RPI again. I'm back to firmware 1.4.7. all problems gone and system boots 5s faster.

you can read more here http://forum.stmlabs.com/showthread.php?tid=10756 and then some links .

---

can you maybe just for info post:

Code:

for f in core arm h264 isp v3d uart pwm emmc pixel vec hdmi dpi; do echo "$f: vcgencmd measure_clock $f"; done

this is hacked FW:
mem: frequency(0)=0
core: frequency(1)=420000000
arm: frequency(45)=920000000
h264: frequency(28)=210000000
isp: frequency(42)=210000000
v3d: frequency(43)=210000000
uart: frequency(22)=3000000
pwm: frequency(25)=0
emmc: frequency(47)=250047000
pixel: frequency(29)=74250000
vec: frequency(10)=0
hdmi: frequency(9)=163682000
dpi: frequency(4)=0


this is original: - before the change
mem: frequency(0)=0
core: frequency(1)=420000000
arm: frequency(45)=920000000
h264: frequency(28)=210000000
isp: frequency(42)=210000000
v3d: frequency(43)=0
uart: frequency(22)=3000000
pwm: frequency(25)=0
emmc: frequency(47)=100000000
pixel: frequency(29)=148500000
vec: frequency(10)=0
hdmi: frequency(9)=163683000
dpi: frequency(4)=0