On Thu, May 31, 2018 at 4:58 PM, Tony Lindgren tony@atomide.com wrote:
- Grazvydas Ignotas notasas@gmail.com [180531 08:38]:
On Wed, May 30, 2018 at 5:42 PM, Tony Lindgren tony@atomide.com wrote:
- Grazvydas Ignotas notasas@gmail.com [180530 08:41]:
Hi,
On Tue, May 29, 2018 at 7:10 PM, Tony Lindgren tony@atomide.com wrote:
Note that we still can have pyra hang running two instances of memtester 1500M for about 10 minutes on bare CPU boards with no heat sink connected. The boards now boot reliably after that though, so presumably the pyra heat sink will solve this issue.
I've tried these patches on my 4g board from last year (also with double memtesters) and although it did not crash, memtester detected errors after running for about an hour. My board is "lucky" that it boots even with old code, but it used to crash in around 20 minutes or so. I haven't seen it crash with 1.37V with the old code, although it might just have been luck. I'll do some more testing later (don't want to leave it unattended while I'm at work).
Yeah worth testing for sure.
I've tested 2 more scenarios: new timings, 1.37V: memtester errors after ~1h old timings, 1.37: memtester errors after 4h+ hours
Could just be randomness or heat related, second test was done in the evening under slightly lower room temperature.
Hmm OK. What CPU speed are you running it at?
Oh right, forgot about that. Turns out I had all Nikolaus' made up non-TI-approved OPPs in so got rid of them first, but without the 500MHz OPP my unit does thermal shutdown, even if I only leave the 1GHz OPP in. My unit doesn't boot without a battery (too weak supply?), so I've pointed a PC case fan at the cased unit and it maintains 90C now while running at 1GHz only. With that it ran stable for 4h, I'll run it like that for more time later after work.
GraÅžvydas