On Sun, 30 Mar 2014 20:56:57 +0200
Olliver Schinagl <[email protected]> wrote:
> On 03/30/2014 05:59 PM, Ian Campbell wrote:
> > On Sun, 2014-03-30 at 14:26 +0200, Olliver Schinagl wrote:
> >>> That said the sorts of random crashed you've been posting sound a lot
> >>> like either a DRAM issue or overheating. Either of which could be down
> >>> to u-boot setting up something wrong or bad hardware I suppose.
> >> Overheating, maybe. It feels hottish to the touch, but can hold a finger
> >> on it without any problem whatsoever. Not close to the pain point. So I
> >> estimate < 50 C? Shouldn't be reason to be concerned imo.
> >
> > Doesn't sound like it.
> >
> >> Power might be the problem, i see the input voltage under heavy load
> >> drop to 4.65 Volts @ 0.9 amps
> >
> > Could be that.
> >
> >>> Have you checked the checksum of the tarball you are extracting and
> >>> tried unpacking it on a known good system?
> >> The sha1sum matches, calculated on the board, so that's good. xz -d
> >> completed successfully!
> >>
> >> tar xvf fails however, with a big ass 5 page long oops.
> >
> > I'd have thought that xz -d would be *far* more CPU intensive and
> > therefore liable to cause issues than tar xvf. If you were using
> > spinning rust rather than an SSD then I would be inclined to suspect the
> > power draw, but with you using an SSD I'm just not sure.
>
> I agree! though even a heavily stressed CPU doesn't change power draw
> hugely. Ssvb and I did some power tests a few months ago on the list.
I'm not sure if I can really agree with this statement. Heavily
stressed CPU can draw a *lot* of power. Especially if it is
overclocked and overvolted:
https://www.mail-archive.com/[email protected]/msg00906.html
There is also a recent discussion thread in the cubieboard support
mailing list:
https://groups.google.com/forum/#!topic/cubieboard/9WMBFAL7JBE
It looks like the failures reported there are caused by overheating,
when the temperature is gradually increasing under constant CPU load.
And it appears that the cubieboard folks are providing pre-built images
which set the CPU clock speed 1008MHz. This may make a significant
difference.
Too bad that really few people are willing or able to do the current
draw measurements on their hardware. But at the same time, tweaking
the CPU clock speed seems to be somewhat popular. It is not good when
people overclock their CPU and decide that this is 'stable' after
only letting it idle for a while. Then the very same people may
encounter problems later and blame the first random thing that
seems to be 'wrong' in their opinion, for example using the
non-mainline kernel :-)
To make power consumption measurements easier even for inexperienced
users, I tried to hack on the AXP209 voltage/current monitoring support
and sent some preliminary patches:
https://www.mail-archive.com/[email protected]/msg03447.html
--
Best regards,
Siarhei Siamashka
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
