On 27 January 2013 23:30, Michael Hudson-Doyle michael.hudson@linaro.orgwrote:

In the past hasn't this sort of problem usually turned out to be heat related? Or is this something else?

Hi Michael,

It could very well be, I don't know how the heating problem used to manifest before...

However, the original kernel I was using (12.02) had no problem whatsoever, and I ran it many many times on the same set of boards, without an issue.

"rootfs": " http://releases.linaro.org/12.02/ubuntu/oneiric-images/nano/linaro-o-nano-ta... ", "hwpack": " http://releases.linaro.org/12.02/ubuntu/oneiric-images/nano/hwpack_linaro-lt... "

Maybe it's the conjunction of heating up + some change with newer kernels... I'll keep downgrading until it starts working again and will let you know.

cheers, --renato

On 28 January 2013 12:43, Andy Green andy.green@linaro.org wrote:

Without this or something doing a similar deal, a Panda ES will blow chunks after a short period at 1.2GHz.

Hi Andy,

I agree kernel panic is better than blowing up the board, but that might indicate the scaling is not working very well.

Also, does that mean I should not use the 12.02 image because the risk of blowing up my board?

cheers, --renato

On 28 January 2013 14:17, Andy Green andy.green@linaro.org wrote:

No, "blowing chunks" (slang for vomiting) is different than "blowing up"... the 4460 has a separate comparator that is able to reset the SoC if it gets really too hot.

Ah, another term for my collection of disgusting things to talk about during lunch. ;)

It will crash colourfully before then is what I mean, unless one of these

thermal mechanisms is helping. It varies by chip actually, some can idle at 1.2GHz for a long time before choking others crash in a few seconds.

Not sure it adds anything, but I had a Panda here at home (room temperature between 18 and 21 Celsius) running Ubuntu 12.04 desktop version referred from the Panda wiki (with GUI and everything) for 6 days building LLVM 24/7 without a single glitch.

The moment I put on the LAVA rack, it failed before the end of the first build.

I then remove all GUI packages, useless services, kernel modules (left only the LED driver) and it went back to almost-normal. It failed only once since then.

The failure is simple: it freezes. I haven't seen anything on the screen (it blacks out), or over serial and the machine stops responding to ping. Dead. But on. And hot. It looks as though it hit an area outside the system and is running the same NOPs over and over.

Some say there was an Indian cemetery in that land before The Quorum was built, it could be a curse, ghosts or even leprechauns. Scratch that, there isn't a single pub nearby, probably ghosts, then.

cheers, --renato