We have four beta testers in SCC-DC.
The beta has been installed on three SCC-DC systems.
Beta downloaded by over 30 remote users.
Usage observations so far are:
The new default linux memory allocation different from that of the 188.8.131.52 default image
Top reports only around half of the memory available vs the 184.108.40.206 image
Mem: 40280K used, 215172K free, 0K shrd, 0K buff, 30908K cached
Mem: 68956K used, 574204K free, 0K shrd, 0K buff, 56404K cached
Issue with running at a higher frequency on marc042 and marc006.
Higher frequency currently works fine on marc004.
selecting (1) Tile800_Mesh1600_DDR1066 causes boot failure on marc042 and marc006 (bug 402)
If the target SCC system is currently setup with 220.127.116.11 emac enabled, the install is simple.
Basically untar and change the “current” softlink to point to 1.4.2.
New Linux CPU usage observation from beta tester:
The cores on 1.4.2 seemed more overwhelmed when running my programs (>90% CPU usage) than those on 18.104.22.168 (~30-40% CPU usage)
1 of 1 people found this helpful
Actually, we have issue with running at a higher frequency on own system. Until when runing the install script, the problem is existing.
I have three SC-DC systems that would not run at the higher frequency until I ran the install script. Now all three have been working fine at the higher frequency.
Did running the script solve your problem?
I am also interested in knowing if you incremented the update.txt file before running the script.
>Did running the script solve your problem?I have been incremented the update.txt file before running the script and also running the script without updated the update.txt.Still, the system would not run at the higher frequency.
I had a similar problem here in the MARC lab. Replacing the RockyLake chip fixed the problem.
It would seem the prior chip that would not run at the higher frequency was defective when running at the higher frequency.