On Sun, 11 May 2014 10:36:25 +0200
Hans de Goede <[email protected]> wrote:
> We've several bug reports indicating that this causes stability issues,
> so lets just drop it.
I'm afraid that the reporters still have not done their homework
properly. And suspect that the FAST_MBUS just happens to be the last
straw to break the camel's back on slightly unstable systems.
They first should try the updated fex files with dcdc3 set to 1.3V
https://www.mail-archive.com/[email protected]/msg04662.html
And also run https://github.com/ssvb/lima-memtester/ before and
after the dcdc3 change. Not having the sunxi-3.4 kernel is not a good
excuse! It should not take too long to try it.
The lima-memtester program exposes dram reliability issues at roughly
~50MHz lower dram clock speeds than the other exclusively CPU based
tests. If somebody is even able to notice problems after tens of hours
of unpacking tarballs, then lima-memtester should expose the same
problem in a matter of a few minutes (or even a few seconds).
This may be partially explained by the "as soon as mali works noise
on dcdc3 is much higher" jemk's observation:
http://irclog.whitequark.org/linux-sunxi/2014-04-17#7155572
And partially by the fact that mali is very aggressively accessing
memory. And this stresses the dram controller a lot.
NAK, until we get better reports from the users.
--
Best regards,
Siarhei Siamashka
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
