Hi, On 04/01/2014 10:45 PM, Olliver Schinagl wrote: > Top Posting! > > I found the culprit. FAST_MBUS breaks it. After 48 hours of runs, enabling > fast_mbus immediately breaks it even after boot. > > Jens and Emilio hinted that the 3.4 driver reads the FEX file for the > voltage. So the higher freq. runs at a lower voltage and that may cause it.
That is an interesting theory, which should be easy to verify. When you've some time can you edit the fex file and change dcdc3_vol to 1300 in there, generate a new script.bin and give that a try with a u-boot with FAST_MBUS enabled ? > So I'll run without fast mbus for now, and it's stable again. Rock Solid if I > may. > > Sorry for all the noise :( No need to be sorry this is very valuable info! Either we need to revert FAST_MBUS support or update dcdc3_vol in all fex files for boards which have FAST_MBUS set. Regards, Hans > > Olliver > > On 03/30/2014 08:56 PM, Olliver Schinagl 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. >> >> Additionally! I should mention, my CT has a battery backup which should >> be near full charge. a 1220 mAh battery, so even if the power supply >> should drop to low or something, Wens assured me that the battery would >> take over and no problem should be caused by bad power. Unless the >> battery has run down of course, which I highly doubt, especially seeing >> the constant current draw over USB. >> >> So for now, I just hope it's not user error ... >> >> Olliver >> >>> >>> Ian. >>> >> > -- 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 linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
