On 16 April 2013 07:43, Tushar Behera <email address hidden> wrote:
> Any update on this?
The GCC build itself is pretty solid. I've run Matt's script on a
daily basis on my Arndale, using Linaro's daily build that contains
only the patch for u-boot (ie I haven't used the 3 errata kernel
patches floating around).
However, I lose the network after some time:
[43894.480000] asix 1-3.2.2:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[43911.500000] asix 1-3.2.2:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
It happens on various workload and isn't specific to the GCC build use
case. I think it's another issue since I reproduce it reliably.
Also, I monitored the temperature during the build: 47 degrees Celsius
on boot and goes up to the critical temperature (85 degrees Celsius)
during the GCC build. After the build is complete, it goes down to 47
degrees Celsius (assuming it's idling since I don't run anything else
after the build).
On 16 April 2013 07:43, Tushar Behera <email address hidden> wrote:
> Any update on this?
The GCC build itself is pretty solid. I've run Matt's script on a
daily basis on my Arndale, using Linaro's daily build that contains
only the patch for u-boot (ie I haven't used the 3 errata kernel
patches floating around).
However, I lose the network after some time:
[43894.480000] asix 1-3.2.2:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[43911.500000] asix 1-3.2.2:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
It happens on various workload and isn't specific to the GCC build use
case. I think it's another issue since I reproduce it reliably.
Also, I monitored the temperature during the build: 47 degrees Celsius
on boot and goes up to the critical temperature (85 degrees Celsius)
during the GCC build. After the build is complete, it goes down to 47
degrees Celsius (assuming it's idling since I don't run anything else
after the build).