Hi Christophe,
It could be the wireless, or something else. Below is my blacklist on modprobe.d:
# Rack mount no extra rubbish blacklist rfcomm blacklist bnep blacklist bluetooth blacklist ppdev blacklist lp blacklist parport blacklist wl12xx_sdio blacklist wl12xx blacklist mac80211 blacklist twl6040_vibra blacklist ff_memless blacklist cfg80211
This involves wireless, bluetooth, parallel ports etc. It is also almost all kernel modules active (with the exception of the led driver).
I also removed some silly packages and disabled most daemons, but I guess your image is much cleaner than mine.
cheers, --renato
On 22 January 2013 13:26, Christophe Lyon christophe.lyon@linaro.orgwrote:
It makes sense indeed (reminds me of my guru-plug getting very hot with wifi enabled).
But currently ifconfig only shows eth0 and lo; it looks like wifi is not activated already :-(
Christophe.
On 22 January 2013 11:43, Matthew Gretton-Dann matthew.gretton-dann@linaro.org wrote:
Interesting. Christophe do you want to take a look?
Matt
On 22/01/13 10:24, Dave Pigott wrote:
Hi Matt,
Interesting discovery by Renato re overheating on Pandas - he had a similar problem and just disabled wifi, and the board ran a *lot*
cooler.
Could this be your problem in the toolchain pandas?
Thanks
Dave
On 21 Jan 2013, at 19:53, Matthew Gretton-Dann matthew.gretton-dann@linaro.org wrote:
On 21/01/13 19:38, Paul Sokolovsky wrote:
Hello,
I'm offline Tue/Wed, so here's update on CBuild/LAVA (other folks from Infra should be present on Tue hangout).
We've been doing integration testing since end of last week, and generally it looks good. We didn't have complete end-to-end GCC build due to PandaES + USB drive availability issues, but I tested gcc build on Panda instead (this has some OOMs during "make check" in gcc), and smaller builds like cortex-strings on PandaES.
Some tests deliberately try to exhaust all memory - if they're not already we should be explicitly ulimiting the make check process to not cause random processes to be killed.
So, everything looks good for deployment on Thurs, just 2 following issues are on critical path:
- Patches
(https://code.launchpad.net/~linaro-infrastructure/+activereviews) review by TCWG. Matt, I guess you were busy with toolchain release last week, but we'd appreciate your review now.
I'll try and do that in the next 48 hours.
- Merging the changes, assuming they're ok. Infra people don't have
commit access to CBuild repos, so we depend on TCWG here too.
Actually,
it may be expected that after initial launch, we'll need to do more changes and tweaks, so it may be good idea to give Infra (temporary) commit access to streamline process. It would be nice to discuss this during Tue hangout.
I thought you had access, and was expecting you to merge all changes.
I
am happy for anyone to merge their own stuff when the merge has been approved. Can someone send me (off-list) the appropriate list of
people (or
Launchpad group) to give commit access to?
Thanks,
Matt
-- Matthew Gretton-Dann Toolchain Working Group, Linaro
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
-- Matthew Gretton-Dann Toolchain Working Group, Linaro