Jump to content
  • 0

Armbian running on Pine64 (and other A64/H5 devices)


tkaiser
 Share

Question

We have initial support for Pine64/Pine64+ for a long time in our repository but not released any official images yet. Since this will change soon a sneak preview what to expect.

 

Hardware related issues:

 

Please don't blame Armbian for the few design flaws Pine64 and Pine64+ show:

  • These boards use Micro USB for DC-IN which is the worst possible decision. Most USB cables have a resistance way too high and are responsible for severe voltage drops when consumption increases, then the tiny Micro USB contacts have also a pretty high contact resistance and also maximum amperage for this connector is limited to 1.8A by USB specs. So in case you want to do heavy stuff immediately look into linux-sunxi wiki page for Pine64 to get the idea how to use the pins on the so called Euler connector to power the board more reliably. If you think about buying a Pine now consider ordering their PSU  too since there cable resistance shouldn't be a problem (should also apply to the Micro USB cables they sell)
  • The only led on this board is a power led that immediately lights when power is provided. Pre-production samples had a green led, on the normal batches this has been replaced with a red led. So there's no way for an OS image to provide user feedback (activate an led when u-boot or kernel boots) and the red light has often been interpreted as 'something is wrong'
  • USB: you find 2 USB type A receptacles on the board but only one is a true USB host port, the other/upper is A64's USB OTG port exposed not as Mini/Micro USB (with ID pin to be able to switch roles) but as a normal type A port. Expect performance to be lower on this port. I've also never been able to do disk benchmarking on the upper port but that might have changed in the meantime (I only have a pre-production developer sample here). Please note also that the maximum amperage available on the USB port is 650mA so connecting bus-powered USB disks might already exceed this so be prepared to use a powered USB hub in between
  • A64 is prone to overheating but unfortunately the Pine64 folks do not sell the board with an effective heatsink by default (compare with ODROID-C1+ or ODROID-C2 for example how it looks like if the vendor cares about heat dissipation). They promised to provide a good heatsink as option but at least I'm not able to find one in their online store. But a heatsink is mandatory if you plan to run this device constantly with high loads, otherwise throttling will occur (when we tested an unrealistic heavy workload without a heatsink -- cpuburn-a53 -- A64 had to throttle down to as less as 600 MHz (for some numbers see IRC log from a while ago)
  • Not a real hardware issue but a problem anyway: the HDMI driver in Allwinner's BSP does not negotiate any display output with a lot of displays that are connected with a HDMI <--> DVI converter or use non-common resolutions. Better do not expect any display output if your display is neither connected directly using HDMI nor capable of 1080p (we can't do anything here since Allwinner's driver uses closed source blobs and no documentation or code with useable license exists)
  • On a couple of Gbit equipped Pine64+ users report that they're not able to negotiate Gbit Ethernet reliably and have to force the connection to Fast Ethernet (since we know that the RTL8211E PHY used on the boards needs an additional ~350 mW when negotiating a Gbit Ethernet connection this might be related to power problems or maybe different PHY batches or something else). Confirmed in the meantime to be a hardware issue.

Now combine Micro USB encouraging users to combine this SBC with crappy phone chargers, 'smart' hubs/chargers that do only provide 500mA since Pine64 isn't able to ask for more and crappy USB cables leading to voltage drops (all sorts of power related issues 'by design' due to crappy Micro USB connector) with a missing custom led able to be used to provide user feedback while booting and the inability to use a lot of displays then you might already get what a support nightmare this device is.

 

The only reliable DOA detection method without a serial console is to ensure you have a working SD card (test it before using either F3 or H2testw as outlined in our docs), then check download integrity of the Armbian image (again see the documentation), then ensure you burn the image correctly to SD card (see docs), insert SD card, power on the board and wait 20 seconds. If then the leds on the Ethernet jack start to flash randomly at least the kernel boots and after waiting an additional 2 minutes you'll be able to login with SSH or serial console (for the latter better choose the EXP header over the Euler connector -- reason here)

 

Anyway: In case you run in booting or stability problems with Armbian on Pine64/Pine64+ be assured that it's not an Armbian issue. You run into any of the problems above therefore please try to resolve them on your own and send your complaints to Pine64 forum and not ours: http://forum.pine64.org/forumdisplay.php?fid=21  (really, we don't do hardware and these issues are all related to hardware design decisions)

 

3245dc9c-e90c-11e5-9bb9-a0bfab2f3e4d.jpg

 

Expectations:

 

The Pine64 folks did a great job raising expectations to the maximum. They advertised this board as 'first $15 64-Bit Single Board Super Computer', promised an average consumption of just 2.5W, the SoC remaining at 32°C and a few other weird things while they already knew that reality differs a lot (the journey started here last Dec).

 

Pine64 is not a 'Super Computer' but most probably the slowest 64-bit ARM board around due to A64 being limited regarding maximum cpufreq and overheating issues (40nm process being responsible for) and lack of fast IO interconnections (only one real USB 2.0 host port present, no eMMC option possible, no SD card implementation using the faster modes). If you then combine the high expectations with a rather clueless kickstarter crowd (many of them not even getting that they did not buy products but backed a project) and the hardware flaws it's pretty obvious why their forums are full of complaints and why they receive so much boards as being DOA that work flawlessly in reality.

 

So why bringing Armbian to Pine64? Since for some (headless) use cases these boards are really nice and also cheap, A64 support is progressing nicely thanks to our awesome linux-sunxi community and also a few more A64 devices will be available soon.

 

What do you get with Armbian on Pine64?

 

User experience will not be much different compared to longsleep's minimal Ubuntu image. If you prefer Debian then at least you can be assured that our images do not contain bad settings and silly bugs like the one's from official Pine64 downloads section (since they fiddle around manually with their OS images for example all Pine boards running these have the same MAC address by default which will cause network troubles if you've more than one board in the same collision domain).

 

We use the same thermal/throttling settings like OS images based on longsleep's kernel (since we helped developing them back in March), we use the same BSP kernel (patched by Zador up to the most recent version back in May) and share a few more similarities since our modifications were sent back to longsleep so all OS images for Pine64 might be able to benefit from.

 

Differences: You don't need to execute longsleep's various platform scripts since kernel and u-boot updates are done using the usual apt-get upgrade mechanism in Armbian. You also don't need (and should not use) scripts like pine64_tune_network.sh since they decrease network performance with Armbian (stay with our defaults unless you're an expert). And a few more tweaks might result in better performance and at least by using Armbian you have the usual Armbian experience with some additional tools at the usual location, automatic fs resize on first boot and so on.

 

We already provide a vanilla image currently based on kernel 4.7 but that's stuff for developers only, see below.

 

Performance with legacy Armbian image:

 

'Out of the box' CPU performance with A64 is not that great unless you are able to benefit from the new CPU features: A64 uses Cortex-A53 CPU cores that feature 64-bit capabilities (which are not that interesting since A64 devices are limited to 2 GB DRAM anyway at the moment) but more interestingly ARMv8 instruction set can be used which might increase performance a lot when software will be compiled for this platform. Best example: the commonly mis-used sysbench cpu test: When running an ARMv6 'optimized' sysbench binary on an ARMv8 CPU then performance will be 15 times slower than necessary (applies to the RPi 3 or the upcoming Banana Pi M64 when used with their OS images)

 

But as soon as ARMv8 optimized code is used A64 can really shine in some areas. I used the default sysbench contained in Ubuntu Xenial's arm64 version, tried it with 20000 settings and got less than 8 seconds execution time (an RPi 3 running Raspbian has the faster CPU cores but here it will take 120 seconds -- just due to different compiler switches!). Then I tried whether I can optimize performance building sysbench from source using

export AM_CFLAGS="-march=armv8-a -mtune=cortex-a53"

and got 11 seconds execution time, so optimized code led to a huge performance loss? Not really, I checked out sysbench version 0.5 by accident and there for whatever reasons execution with ARMv8 optimization or in general takes longer (great! benchmark version influences execution time, so one more reason to never trust in sysbench numbers found on the net!). Using the '0.4' branch at version 0.4.12 I got an execution time of less than 7.5 seconds which is a 10 percent increase in performance for free just by using appropriate compiler flags:

 

 

 

 


root@pine64:/# /usr/bin/sysbench --test=cpu --cpu-max-prime=20000 run --num-threads=4
sysbench 0.4.12:  multi-threaded system evaluation benchmark

Running the test with following options:
Number of threads: 4

Doing CPU performance benchmark

Threads started!
Done.

Maximum prime number checked in CPU test: 20000


Test execution summary:
    total time:                          7.9788s
    total number of events:              10000
    total time taken by event execution: 31.8939
    per-request statistics:
         min:                                  3.17ms
         avg:                                  3.19ms
         max:                                  8.74ms
         approx.  95 percentile:               3.19ms

Threads fairness:
    events (avg/stddev):           2500.0000/3.54
    execution time (avg/stddev):   7.9735/0.00

root@pine64:/# /usr/local/src/sysbench-0.4.12/sysbench/sysbench --test=cpu --cpu-max-prime=20000 run --num-threads=4
sysbench 0.4.12:  multi-threaded system evaluation benchmark

Running the test with following options:
Number of threads: 4
Random number generator seed is 0 and will be ignored


Doing CPU performance benchmark

Primer numbers limit: 20000

Threads started!
Done.


General statistics:
    total time:                          7.4608s
    total number of events:              10000
    total time taken by event execution: 29.8223
    response time:
         min:                                  2.96ms
         avg:                                  2.98ms
         max:                                  8.51ms
         approx.  95 percentile:               2.99ms

Threads fairness:
    events (avg/stddev):           2500.0000/3.67
    execution time (avg/stddev):   7.4556/0.00

root@pine64:/# /usr/local/src/sysbench/sysbench/sysbench --test=cpu --cpu-max-prime=20000 run --num-threads=4
sysbench 0.5:  multi-threaded system evaluation benchmark

Running the test with following options:
Number of threads: 4
Random number generator seed is 0 and will be ignored


Prime numbers limit: 20000

Initializing worker threads...

Threads started!


General statistics:
    total time:                          11.0451s
    total number of events:              10000
    total time taken by event execution: 44.1223s
    response time:
         min:                                  4.38ms
         avg:                                  4.41ms
         max:                                 27.34ms
         approx.  95 percentile:               4.41ms

Threads fairness:
    events (avg/stddev):           2500.0000/6.36
    execution time (avg/stddev):   11.0306/0.01

 

 

 

Another great example how using CPU features or not (NEON in this case) influences performance and 'benchmarking gone wrong' numbers are Linpack's MFLOPS scores. By choosing the package your distro provides instead of using one that makes use of your CPU's features you loose at lot of performance, ruin every performance per watt ratios and behave somewhat strange :)

 

Someone sent me Linpack MFLOPS numbers generated with Debian Jessie which is known for horribly conserative compiler settings when building packages -- if you switch your distro from Jessie to Ubuntu Xenial for example you get a 30 percent improvement in sysbench numbers, yeah that's the 'benchmark' we already laughed at above.

 

With Jessie's/Raspbian's hpcc package, Pine64+ gets a score of 1625 MFLOPS and RPi 3 just 1035. So is Pine64 1.6 times faster than RPi 3? Nope, that's just 'benchmarking gone wrong' since these numbers are the result of a joke: Using tools for 'High performance computing' with standard settings (no one interested in HPC would ever do that). By using the correct Linpack version that makes use of NEON optimizations on both CPUs we end up with 3400 MFLOPS (Pine64 at 1.3 GHz) vs 3600 MFLOPS (RPi 3 at 1.2 GHz).

 

So if we're talking about this use case (HPC -- high performance computing) RPi 3 easily outperforms A64 (please keep in mind that the 3400 MFLOPS I got are the result of overclocking/overvolting at 1296 MHz, Pine64 is limited to 1152 MHz by default so we're talking about 3000 MFLOPS for A64 vs. 3600 MFLOPS for RPi 3's SoC. So it's not Pine64 being 1.6 times faster but RPi 3 being more suited for Linpack numbers and this type of benchmarks only shows how wrong it is to use distro packages that are built using conservative settings (which is a must if the distro wants to support a wide range of different SoCs!)

 

Anyway: I's obvious that in case you want to use Pine64 for number crunching or performance stuff in general evaluating whether compiling packages from source might improve performance is a great idea (at least it's obvious that from a performance point of view using an ARMv6 distro with ARMv8 SoCs is stupid -- reality with Raspbian running on RPi 3 and BPi M64). ARMv8 also provides crypto extensions that might be used with OpenSSL for example. Didn't look into it yet but maybe huge performance gains when using a Pine64 as HTTPS enabled web server or VPN endpoint are possible just like we've already seen with sysbench.

 

Network performance: Pine64+ combines the SoC internal GbE MAC implementation (the same as in H3 and A83T SoCs from Allwinner) with an external RTL8211E PHY as used on most GbE capable SBC. Default iperf performance with Armbian/Xenial: +900 MBits/sec in both directions (920/940 MHz) so no need for further tuning (please read through this explanation here why blindly trusting in iperf numbers is always stupid and why it's neither necessary nor useful to further tune network settings to get better iperf numbers).

 

 

 

 


root@armbian:/var/git/Armbian# iperf3 -c 192.168.83.64
Connecting to host 192.168.83.64, port 5201
[  4] local 192.168.83.115 port 60392 connected to 192.168.83.64 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec   112 MBytes   938 Mbits/sec    0    356 KBytes       
[  4]   1.00-2.00   sec   112 MBytes   941 Mbits/sec    0    376 KBytes       
[  4]   2.00-3.00   sec   112 MBytes   943 Mbits/sec    0    376 KBytes       
[  4]   3.00-4.00   sec   112 MBytes   941 Mbits/sec    0    376 KBytes       
[  4]   4.00-5.00   sec   112 MBytes   938 Mbits/sec    0    376 KBytes       
[  4]   5.00-6.00   sec   113 MBytes   947 Mbits/sec    0    376 KBytes       
[  4]   6.00-7.00   sec   112 MBytes   940 Mbits/sec    0    395 KBytes       
[  4]   7.00-8.00   sec   112 MBytes   942 Mbits/sec    0    395 KBytes       
[  4]   8.00-9.00   sec   112 MBytes   942 Mbits/sec    0    395 KBytes       
[  4]   9.00-10.00  sec   112 MBytes   942 Mbits/sec    0    395 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec  1.10 GBytes   941 Mbits/sec    0             sender
[  4]   0.00-10.00  sec  1.09 GBytes   940 Mbits/sec                  receiver

root@pine64:~# iperf3 -c 192.168.83.115
Connecting to host 192.168.83.115, port 5201
[  4] local 192.168.83.64 port 39363 connected to 192.168.83.115 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec   114 MBytes   954 Mbits/sec    0   1.05 MBytes       
[  4]   1.00-2.00   sec   110 MBytes   922 Mbits/sec    0   1.24 MBytes       
[  4]   2.00-3.01   sec   110 MBytes   918 Mbits/sec    0   1.24 MBytes       
[  4]   3.01-4.00   sec   109 MBytes   917 Mbits/sec    0   1.24 MBytes       
[  4]   4.00-5.01   sec   110 MBytes   918 Mbits/sec    0   1.24 MBytes       
[  4]   5.01-6.01   sec   110 MBytes   923 Mbits/sec    0   1.24 MBytes       
[  4]   6.01-7.00   sec   109 MBytes   918 Mbits/sec    0   1.24 MBytes       
[  4]   7.00-8.00   sec   110 MBytes   923 Mbits/sec    0   1.24 MBytes       
[  4]   8.00-9.00   sec   109 MBytes   912 Mbits/sec    0   1.24 MBytes       
[  4]   9.00-10.00  sec   110 MBytes   923 Mbits/sec    0   1.24 MBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec  1.07 GBytes   923 Mbits/sec    0             sender
[  4]   0.00-10.00  sec  1.07 GBytes   920 Mbits/sec                  receiver

 

 

 
Please keep in mind that for yet unknown reasons a couple of Pine64+ are reported to not reliably work at Gbit Ethernet speeds. Please also keep in mind how settings might matter. If you run a standard iperf test in 'passive benchmarking' mode you might get throughput numbers 200-250 Mbits/sec lower than ours maybe just due to a wrong cpufreq governor. Ethernet throughput scales linearly with CPU clockspeed with most cheap ARM SoCs (our only known exception from this is Solid-Run's Clearfog which uses a SoC optimized for IO and network throughput) so by using the ondemand governor with wrong/default settings for example you ensure that an idle SBC will only slowly increase clockspeed when you start your iperf test. This is Armbian switching from interactive to ondemand governor now being below 700 Mbits/sec just due to adjusting CPU clockspeed too slow:
 
 

 

root@pine64:~# iperf3 -c 192.168.83.115
Connecting to host 192.168.83.115, port 5201
[  4] local 192.168.83.64 port 39365 connected to 192.168.83.115 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.02   sec  47.9 MBytes   395 Mbits/sec    1   99.0 KBytes       
[  4]   1.02-2.02   sec  55.0 MBytes   459 Mbits/sec    0    132 KBytes       
[  4]   2.02-3.01   sec  60.3 MBytes   511 Mbits/sec    0    151 KBytes       
[  4]   3.01-4.01   sec  91.2 MBytes   769 Mbits/sec    0    170 KBytes       
[  4]   4.01-5.01   sec  96.2 MBytes   804 Mbits/sec    0    182 KBytes       
[  4]   5.01-6.01   sec  96.2 MBytes   806 Mbits/sec    0    191 KBytes       
[  4]   6.01-7.01   sec  96.2 MBytes   808 Mbits/sec    0    195 KBytes       
[  4]   7.01-8.01   sec  96.2 MBytes   808 Mbits/sec    0    197 KBytes       
[  4]   8.01-9.00   sec  95.0 MBytes   805 Mbits/sec    0    198 KBytes       
[  4]   9.00-10.00  sec  97.5 MBytes   815 Mbits/sec    0    199 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec   832 MBytes   698 Mbits/sec    1             sender
[  4]   0.00-10.00  sec   832 MBytes   698 Mbits/sec                  receiver

 

 

 

The other stuff normally 'benchmarked' is not worth mentioning/testing it so just as quick notes:

  • A64 is showing the same SDIO limitation as most other SoCs limiting sequential transer speeds to/from SD card to ~23MB/s (do the math yourself: SDIO with 4 bit @ 50 MHz minus some overhead is 23 MB/s) -- fortunately that's rather uninteresting since random IO matters on SBCs and there it's your choice to choose between crappy cards that horribly suck or follow our recommendations and choose a really fast card. But Pine64 can not use the faster eMMC interface so if you really need high IO bandwidth and high IOPS better choose a different device
  • USB is USB 2.0 so expect ~35MB/s with BSP kernel and ~40MB/s with mainline kernel and UASP capable disk enclosures for individual USB connections (UASP + mainline kernel might show high random IO numbers if used together with an SSD!)
  • HW accelerated video decoding is already possible (see here for the codec matrix) and situation with HW accelerated video encoding looks promising too: http://forum.armbian.com/index.php/topic/1855-ffmpeg-with-cedrus-h264-hw-encoder-a64-cmos-camera/

In case one is interested in performance testing on SBCs monitoring what's happening is mandatory. Currently our armbianmonitor tool does not install the necessary templates on A64 so still my script to install this stuff on A64 should be used: http://kaiser-edv.de/tmp/4U4tkD/install-rpi-monitor-for-a64.sh (read the script's header how to install)

 

Performance with vanilla Armbian image:

 

Not interesting at all at the time of this writing since while Pine64 happily boots mainline u-boot/kernel it's way too early to do tests in this area. Currently there's no access to the AXP803 PMIC from mainline kernel so not even VDD_CPUX voltage regulation works and as a result cpufreq scaling is also not working and the SoC is clocked pretty conservative. Since most performance relevant stuff running on cheap ARM SoCs depends on (switching as fast as possible to) high CPU clockspeeds benchmarking is absolutely useless now.

 

You should also keep in mind that many core features still not work with mainline kernel so this is really stuff for developers (who normally prefer their own way to boot their freshly compiled kernels). So please don't expect that much from vanilla images for A64 boards now, better choose the legacy variant.

 

The future?

 

A few more A64 boards are announced or already available as dev samples, for example the aforementioned BPi M64 (possible advantages over Pine64: sane DC-IN, real USB OTG, more USB host ports behind an internal USB hub, eMMC available and custom leds being able to provide user feedback, everything else is more or less the same as the 2 GB Pine64+) or Olimex working on both an SBC and an A64 based Laptop.

 

And then Xunlong announced 2 new SBC based on Allwinner's H5. H5 (product brief) seems to be A64's bigger sibling providing video/GPU enhancements, 3 true USB host ports in addition to one USB OTG (just like H3 where we can use all 4 USB ports that do not have to share bandwidth), integrating a Fast Ethernet PHY (just like H3) but lacks PMIC support (again just like H3, so no mobile useage, no battery support out of the box and it gets interesting how VDD_CPUX voltage regulation will work there -- maybe 'just like H3' again).

 

Since A64 shares many/most IP blocks with H3 and A83T from Allwinner I still hope that H5 will be just a mixture of A64 and H3 and we will get full support based on what we now have for these 2 other SoCs pretty fast. But that's 100 percent speculation at this moment :)

 

Update regarding longsleep's pine64_tune_network.sh script. Benchmark results don't get automatically worse when applying the tweaks from his script but the result variation gets huge (730 - 950 Mbits/sec, exceeding 940 Mbits/sec is already an indication that buffers are invoked):

 

 

 


root@pine64:/home/tk# iperf3 -s
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Accepted connection from 192.168.83.115, port 50002
[  5] local 192.168.83.76 port 5201 connected to 192.168.83.115 port 50004
[ ID] Interval           Transfer     Bandwidth
[  5]   0.00-1.00   sec  90.7 MBytes   759 Mbits/sec                  
[  5]   1.00-2.00   sec  92.2 MBytes   774 Mbits/sec                  
[  5]   2.00-3.00   sec  92.5 MBytes   776 Mbits/sec                  
[  5]   3.00-4.00   sec  92.5 MBytes   776 Mbits/sec                  
[  5]   4.00-5.00   sec  92.6 MBytes   777 Mbits/sec                  
[  5]   5.00-6.00   sec   106 MBytes   889 Mbits/sec                  
[  5]   6.00-7.00   sec   112 MBytes   942 Mbits/sec                  
[  5]   7.00-8.00   sec   111 MBytes   927 Mbits/sec                  
[  5]   8.00-9.00   sec   101 MBytes   847 Mbits/sec                  
[  5]   9.00-10.00  sec   112 MBytes   942 Mbits/sec                  
[  5]  10.00-10.02  sec  1.66 MBytes   931 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  5]   0.00-10.02  sec  1007 MBytes   843 Mbits/sec    9             sender
[  5]   0.00-10.02  sec  1004 MBytes   841 Mbits/sec                  receiver
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Accepted connection from 192.168.83.115, port 50006
[  5] local 192.168.83.76 port 5201 connected to 192.168.83.115 port 50008
[ ID] Interval           Transfer     Bandwidth
[  5]   0.00-1.00   sec  88.4 MBytes   740 Mbits/sec                  
[  5]   1.00-2.00   sec  91.9 MBytes   771 Mbits/sec                  
[  5]   2.00-3.00   sec   109 MBytes   918 Mbits/sec                  
[  5]   3.00-4.00   sec   112 MBytes   941 Mbits/sec                  
[  5]   4.00-5.00   sec   112 MBytes   941 Mbits/sec                  
[  5]   5.00-6.00   sec   112 MBytes   942 Mbits/sec                  
[  5]   6.00-7.00   sec   112 MBytes   942 Mbits/sec                  
[  5]   7.00-8.00   sec   112 MBytes   942 Mbits/sec                  
[  5]   8.00-9.00   sec   112 MBytes   941 Mbits/sec                  
[  5]   9.00-10.00  sec   112 MBytes   941 Mbits/sec                  
[  5]  10.00-10.02  sec  1.89 MBytes   928 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  5]   0.00-10.02  sec  1.05 GBytes   904 Mbits/sec    0             sender
[  5]   0.00-10.02  sec  1.05 GBytes   902 Mbits/sec                  receiver
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Accepted connection from 192.168.83.115, port 50010
[  5] local 192.168.83.76 port 5201 connected to 192.168.83.115 port 50012
[ ID] Interval           Transfer     Bandwidth
[  5]   0.00-1.00   sec  87.7 MBytes   734 Mbits/sec                  
[  5]   1.00-2.00   sec  92.1 MBytes   773 Mbits/sec                  
[  5]   2.00-3.00   sec  92.2 MBytes   773 Mbits/sec                  
[  5]   3.00-4.00   sec  92.1 MBytes   773 Mbits/sec                  
[  5]   4.00-5.00   sec  92.1 MBytes   773 Mbits/sec                  
[  5]   5.00-6.00   sec   102 MBytes   859 Mbits/sec                  
[  5]   6.00-7.00   sec  93.1 MBytes   781 Mbits/sec                  
[  5]   7.00-8.00   sec  92.1 MBytes   773 Mbits/sec                  
[  5]   8.00-9.00   sec  92.1 MBytes   773 Mbits/sec                  
[  5]   9.00-10.00  sec  94.9 MBytes   796 Mbits/sec                  
[  5]  10.00-10.02  sec  1.62 MBytes   740 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  5]   0.00-10.02  sec   936 MBytes   783 Mbits/sec    0             sender
[  5]   0.00-10.02  sec   933 MBytes   781 Mbits/sec                  receiver
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Accepted connection from 192.168.83.115, port 50014
[  5] local 192.168.83.76 port 5201 connected to 192.168.83.115 port 50016
[ ID] Interval           Transfer     Bandwidth
[  5]   0.00-1.00   sec  87.1 MBytes   729 Mbits/sec                  
[  5]   1.00-2.00   sec  92.1 MBytes   774 Mbits/sec                  
[  5]   2.00-3.00   sec  91.8 MBytes   769 Mbits/sec                  
[  5]   3.00-4.00   sec  90.4 MBytes   759 Mbits/sec                  
[  5]   4.00-5.00   sec  96.4 MBytes   808 Mbits/sec                  
[  5]   5.00-6.00   sec  90.2 MBytes   758 Mbits/sec                  
[  5]   6.00-7.00   sec   113 MBytes   951 Mbits/sec                  
[  5]   7.00-8.00   sec   112 MBytes   941 Mbits/sec                  
[  5]   8.00-9.00   sec   112 MBytes   942 Mbits/sec                  
[  5]   9.00-10.00  sec   112 MBytes   942 Mbits/sec                  
[  5]  10.00-10.02  sec  1.83 MBytes   932 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  5]   0.00-10.02  sec  1003 MBytes   840 Mbits/sec    0             sender
[  5]   0.00-10.02  sec  1000 MBytes   837 Mbits/sec                  receiver

 

 

 

So better enjoy defaults unless you really know what you do since network performance tuning works in different directions. Stuff that might increase throughput might negatively affect latency and vice versa. So if you start to tune, tune for your specific use case!

Link to comment
Share on other sites

Recommended Posts

  • 0

And now he kicked me out of chat, I never even said anything in the chat. LOL. Man those forum rep points must be like water for him.

 

Well, let's stop speculating about motives and focus on the real problem again (him being a huge part of though). He closed the thread, censored the advise to measure voltages away and even discourages users to do so ('I have proven that the VDD33 voltage is not the problem').

 

So all we have now are Zador's measurements on his board where no problem occurs, we have @androsch's board where I can not measure since I sent it back to @androsch yesterday before new schematic release and Zador came up with the PHY_VDD33 suggestion and we now have to rely on others taking notice (quite unlikely given the weird situation in pine64 forum). So let's see what happens when @-L0thar-'s gear arrives and he's able to compare his two boards.

Link to comment
Share on other sites

Search Before Posting!

  • 0

@tkaiser

 

As far as I tried measured in iperf it seems out speed.
However, perhaps because of Packet loss, it takes a very time situation to apt-get update.
kometch@pine64:~$ iperf3 -c 192.168.122.223                                     
Connecting to host 192.168.122.223, port 5201                                   
[  4] local 192.168.122.171 port 42206 connected to 192.168.122.223 port 5201   
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd                
[  4]   0.00-1.01   sec  46.6 MBytes   386 Mbits/sec  130    215 KBytes         
[  4]   1.01-2.00   sec  34.7 MBytes   295 Mbits/sec   70   90.5 KBytes         
[  4]   2.00-3.00   sec  45.6 MBytes   382 Mbits/sec   10    173 KBytes         
[  4]   3.00-4.00   sec  55.9 MBytes   468 Mbits/sec   94    164 KBytes         
[  4]   4.00-5.00   sec  56.0 MBytes   470 Mbits/sec  120    191 KBytes         
[  4]   5.00-6.01   sec  57.7 MBytes   480 Mbits/sec   55    245 KBytes         
[  4]   6.01-7.00   sec  45.0 MBytes   381 Mbits/sec   59    141 KBytes         
[  4]   7.00-8.01   sec  45.4 MBytes   377 Mbits/sec   17    178 KBytes         
[  4]   8.01-9.02   sec  53.9 MBytes   447 Mbits/sec  120    133 KBytes         
[  4]   9.02-10.00  sec  56.5 MBytes   484 Mbits/sec   38    198 KBytes         
- - - - - - - - - - - - - - - - - - - - - - - - -                               
[ ID] Interval           Transfer     Bandwidth       Retr                      
[  4]   0.00-10.00  sec   497 MBytes   417 Mbits/sec  713             sender    
[  4]   0.00-10.00  sec   496 MBytes   416 Mbits/sec                  receiver  
                                                                                
iperf Done.   
Link to comment
Share on other sites

  • 0
 - - - - - - - - - - - - - - - - - - - - - - - -                               
[ ID] Interval           Transfer     Bandwidth       Retr                      
[  4]   0.00-10.00  sec   497 MBytes   417 Mbits/sec  713             sender    
[  4]   0.00-10.00  sec   496 MBytes   416 Mbits/sec                  receiver  

Well, there are retransmissions and speed is relatively low. Is this legacy kernel or mainline? How do you power your board (microUSB or GPIO pins, power supply characteristics)?

Link to comment
Share on other sites

  • 0

apt-get update

 

This is the other direction. Please have a look at posts #33 and #34. With @androsch's board by powering through the Euler pins I was able to immediately increase the throughput in the direction you tested now but not in the other. Please test again, this time from 192.168.122.171 to 192.168.122.223. I would assume numbers will be terribly low then.

 

Do you have a Multimeter and are able to measure PHY_VDD33 as Zador outlined yesterday?

Link to comment
Share on other sites

  • 0

First we need to check if we can reproduce both very low and normal results on the same board, otherwise we will get "numbers without meaning"

 

Hmm... just to document what I did (still noobie needing your help to understand electronics basics):

post-7-0-76842800-1473779910_thumb.jpg

  • In post #33 I started with the USB PSU on the right using an 'average' (crappy) USB cable and powered through Micro USB. Tested in the same direction as @kometchtech and got pretty bad results.
  • Then I replaced immediately USB PSU cable with the dual voltage PSU next to it and powered through Euler pins 4 and 6. In TX direction I got close to 900 Mbits/sec but in RX direction (apt-get update|upgrade ;) ) everything remained bad.
  • After I found my '5.5/2.1 to Micro USB' adapter (in the lower middle of the picture) I could use the next 2 PSUs. The larger one is rated 5V/3A (came IIRC as part of the 'UP Board' package) and the small one is cheap chinese crap rated 5V/2A and also the PSU showing 'best GbE performance' (since it provides 5.25V?). When I did tests with mainline kernel then using the larger dual voltage PSU with screw terminal (jumper wires connecting to Euler pins) I ended up with 'no PHY found' (PSU only providing 4.97V) and when using the small chinese crap connected to Micro USB connector GbE worked but showed still heavy symptoms in RX direction (TX being fine, I got the 470 Mbits/sec that can be expected with mainline kernel running at 408 MHz)
  • On friday I bought the large PSU on the left and re-tested with different voltages but got only results I don't understand and that were not that reproducable (at least it seems obvious to me that we're not only talking about voltage but instead about other PSU characteristics I have no idea of :)

I don't really trust in the large PSU since when I did tests with the Wandboard Quad on weekend testing through SATA and USB performance with i.MX6 using this PSU led reproducable to no Ethernet (not even PHY leds blinking). I wasted two hours testing through all different Wandboard OS images (could've ported Armbian to Wandboard in the same amount of time  :wacko: ) just to realize that I had to use a different PSU. But that's a different story and needs more time/investigation.

 

So I still find it hard to give any advice how to reproduce 'getting better numbers'. I only know that heavy undervolting (using a crappy USB cable) resulted in pretty bad TX numbers while providing almost 5V cured that. And I also know that I got strange voltage drops measured on the USB ports depending on how I powered @androsch's board. So it seems to be PSU related and I would already be happy if we're able to collect voltage numbers (measuring DC-IN, pins 4/6 on RPi and Euler headers and on the USB ports and of course also PHY_VDD33).

 

I hope I didn't forget anything relevant.

Link to comment
Share on other sites

  • 0

Currently I don't see any significant differences in PHY power part, but I think I found a point where the voltage can be measured, at least on my board, and running iperf3 test shows that voltage drops by 0.02V

 

Edit: I mean PHY 3.3V voltage (PHY_VDD33)

 

I have a 'bad' PINE64+ board, running armbian with legacy kernel, powered via micro-USB AC adapter. NIC and UART0 serial are the only active peripherals. 100Mbps is perfectly fine, but there's a major packet loss at 1Gbps, no need for iperf to tell there's an issue.

 

VDD33 voltage is between 3.26V and 3.27V, regardless of

- 1Gbps or 100Mbps or 10Mbps link speed

- CPU idle (/sys/class/thermal/thermal_zone0/temp @ 42 degrees) or busy (/sys/class/thermal/thermal_zone0/temp @ 65 degrees)

- 3 different microUSB AC 5V adapters and cables

 

That voltage is within tolerance range of 2.97V to 3.63V for PHY VDD33 (per PHY DS). PMIC AC input tolerance range is 3.5V to 7V (per PMIC DS), so PHY should be getting conditioned ~3.3V consistently, even when microUSB AC source is used. Unfortunately I don't have a scope to monitor continuously, but if AC-IN voltage drops were affecting 1Gbps communications, I'd expect them to equally affect 100Mbps communications and that is not the case. So the issue with my board doesn't seem to be caused by PHY input voltage fluctuations.

 

However, there is a noticeable difference in the amount of packet loss with different power sources:

1. laptop USB, so <500mA, 2 feet USB cable

PC -> SBC: 30% loss
SBC -> PC: 36% loss
 

2. AC 5V/2A adapter, 6 feet USB cable

PC -> SBC: 5% loss
SBC -> PC: 11% loss

 

3. AC 5V/3A adapter, 3 feet USB cable

PC -> SBC: 15% loss
SBC -> PC: 31% loss

 

I'd speculate that there's possibly another element sensitive to AC input inconsistencies that might not be conditioned by the PMIC or that may have a narrow tolerance range. Alternatively, PINE64+ PCB layout might not be strictly following guidelines for RTL8211E IC as set forth in PHY DS, resulting in EMI affecting its operation or VDD10 conditioned input being outside of a narrow 0.95V to 1.06V tolerance range.

 

References:

PHY DS - http://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf

PMIC DS - http://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf

Link to comment
Share on other sites

  • 0

So I've fiddled around with EMAC IC and its RGMII interface to PHY IC.

 

Some findings:

1. MII RXERC = 0 in mii-tool reg dump, supposedly that indicates PHY is not receiving erroneous frames

#mii-tool -vvv
  registers for MII PHY 0:
    1140 796d 001c c915 01e1 cde1 000d 2001
    6801 0300 7800 0000 0000 0000 0000 3000
    016e acc2 9f01 0000 8040 1006 4100 2100
    0000 8c00 0040 0106 21fc 8038 0123 0000 

2. EMAC reports RGMII speed/duplex and clock is consistent with PHY link type

 

1Gbps/full:
EMAC BASIC_CTL_0: 
#devmem2 0x1c30000 w

0x1 = 1Gbps/full

EMAC RGMII_STA:

#devmem2 0x1c300d0 w

0xD = 0b1101 - 1Gbps, 125MHz clock

MII PHY:

#mii-tool -vvv
  registers for MII PHY 0:
    1140 796d 001c c915 0001 cde1 000f 2001
    6801 0200 7800 0000 0000 0000 0000 3000
    016e acc2 9f01 6c52 8040 1006 4100 2100
    0000 8c00 0040 0106 21fc 8038 0123 0000
100Mbps/full:
EMAC BASIC_CTL_0: 
#devmem2 0x1c30000 w

0xD = 100Mbps/full

EMAC RGMII_STA:

#devmem2 0x1c300d0 w

0xB = 0b1011 - 100Mbps, 25MHz clock

MII PHY:

#mii-tool -vvv
  registers for MII PHY 0:
    1140 796d 001c c915 01e1 cde1 000d 2001
    6801 0300 7800 0000 0000 0000 0000 3000
    016e acc2 9f01 0000 8040 1006 4100 2100
    0000 8c00 0040 0106 21fc 8038 0123 0000

 

3. EMAC is using internal clock for 1Gbps/125MHz

A64 EMAC_CLK_REG:

#devmem2 0x1c00030 w

clock 0b01 = GMII/RGMII external
clock 0b10 = GMII/RGMII internal (default) 
This said, there could be a problem with 125MHz clock sync, required for proper RGMII communication between EMAC and PHY at 1Gbps rate. Judging by latest PCB diagrams, PHY CLK125 is attached to EMAC, presumably to supply 125MHz clock to EMAC, however EMAC's internal clock is enabled (by the EMAC driver?), so EMAC and PHY clocks are not synchronized. However, switching to external clock (supplied by PHY?) results in even higher packet loss, upwards of 80%
 
I was trying to dump EMAC DMA TX/RX descriptors and buffers to get an idea of whether frames received by PHY make it to EMAC over RGMII and vice versa, but so far didn't manage to access them from userland. I guess it would take to debug EMAC driver to monitor them and accumulate TX/RX frames and errors statistics.
Link to comment
Share on other sites

  • 0
in the mainline kernel, and I get the data in power from the GPIO.

The output of the power supply adapter is 5V/3A is written.


kometch@pine64:~$ iperf3 -c 192.168.122.223
Connecting to host 192.168.122.223, port 5201
[  4] local 192.168.122.176 port 38366 connected to 192.168.122.223 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec  57.6 MBytes   483 Mbits/sec   17    253 KBytes       
[  4]   1.00-2.00   sec  56.2 MBytes   471 Mbits/sec  127    253 KBytes       
[  4]   2.00-3.00   sec  55.9 MBytes   469 Mbits/sec  129    247 KBytes       
[  4]   3.00-4.00   sec  55.8 MBytes   468 Mbits/sec  194    180 KBytes       
[  4]   4.00-5.00   sec  56.2 MBytes   471 Mbits/sec  183    167 KBytes       
[  4]   5.00-6.00   sec  56.4 MBytes   473 Mbits/sec    0    256 KBytes       
[  4]   6.00-7.00   sec  56.4 MBytes   473 Mbits/sec  165    236 KBytes       
[  4]   7.00-8.00   sec  55.7 MBytes   468 Mbits/sec  208    180 KBytes       
[  4]   8.00-9.00   sec  55.7 MBytes   467 Mbits/sec   80    181 KBytes       
[  4]   9.00-10.00  sec  56.8 MBytes   476 Mbits/sec    0    256 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec   563 MBytes   472 Mbits/sec  1103             sender
[  4]   0.00-10.00  sec   561 MBytes   471 Mbits/sec                  receiver


iperf Done.
Link to comment
Share on other sites

  • 0

So, I know it isn't comparing apples with apples, but I just have to post this as it shows the GbE on the pine64 can indeed move when it wants too... 

 

I finally reformatted my USB flash drive as btrfs, and made a zeroed 1G file as you suggested earlier (with compression on). I'd started armbian up again a youtube upload for tonight, so thought I'd make that file first,and then see what the transfer speed was like. I'm copying to the same desktop computer as before, but it's booted in to windows (I know, you won't like it) this time (dual-boot), and it was... fast... damn near missed getting the screenshot! 

 

post-2100-0-36288500-1474016397_thumb.png

 

 

Link to comment
Share on other sites

  • 0

it shows the GbE on the pine64 can indeed move when it wants too... 

 

 

Well, it has been already known that Pine64+ is capable of exceeding 80 MB/s based on 'raw' iperf3 numbers (only one person needed to be convinced, thanks for doing the job). It would be great if you could grab 'Helios LanTest' (available at http://webshare.helios.de user 'tools', pwd 'tools') and run each 3 times with the settings for 'Very fast' and 'Enterprise' networks.

 

And while this sort of test using btrfs compression is somewhat useless since it only demonstrates what's possible if storage isn't the bottleneck (but most of the time disk IO will be the bottleneck since we're limited by USB 2.0) it gives also a nice preview of what will be possible later when mainline kernel is ready (and EMAC driver further improves) or when Pine64+ runs completely from fast network storage (since GbE is the fastest interface available on A64 this makes perfectly sense)

Link to comment
Share on other sites

  • 0

This what you wanted?

 

Exactly, I was especially interested in those little orange arrows (in case you ever test again with LanTest please mouse over a bar with huge variations and see what happens). Thanks!

 

BTW: Reasons why Explorer is capable of sucking more out of Pine64's Ethernet port here: http://www.helios.de/web/EN/support/TI/157.html

Link to comment
Share on other sites

  • 0

lol... sound about right... another file management tool I use does exactly the same thing... uses multiple I/O threads, and also uses larger buffers for certain transfers (i.e. drive to drive, or via network IIRC). I'll throw that in just for fun... and also the reverse direction file copy... the 1gb of zeros TO the pine64 this time... looks like the brtfs is pretty happy to compress that puppy down as it goes... so happy in fact that I don't see the USB lighting up much during the transfer :-) So it will be interesting to see what happens once the dual USB opens up. I will say that after transferring of the the more typical data types (for me anyway - some 270MB of uni assessments and notes, and about 250MB worth of PDF datasheets)... it processed very quickly...  It it understandably fell over the zillions of small files that were in a 2.1GB datasheet... (there were a heck of a lot of small c files in it) and was dropping to 10MB/s speeds... but picking up again when hitting some big files (bottom sceenshot).

 

And on a repeat run of LanTest on GbE, the measurement with the biggest swing was the 'write 300MB to file' test again, with a AVG as 52.7 MB/s, and the min and max in the tooltip were 51.2MB/s and 67.4MB/s. The read 300MB/s test only had about a 2MB/s swing... (65.0 - 67.4), and all the others really didn't have too much separation ether.

 

post-2100-0-43706700-1474071520_thumb.png

 

post-2100-0-10792200-1474071531_thumb.png

 

post-2100-0-86028400-1474072766_thumb.png

Link to comment
Share on other sites

  • 0

Small note: Since TL Lim said he will send an LCD to me, I just had a look what seems to be necessary to support the LCD in Linux (ayufan's commits from Sep 11, 2016 here). Looks like the usual adjustments we know from Allwinner BSP since ages (this time in DT and not in fex any more):

            screen0_output_type = <0x00000001>;
            screen0_output_mode = <0x00000004>;
            screen1_output_type = <0x00000003>;
            screen1_output_mode = <0x00000004>;
			...
            lcd_used = <0x00000001>;
Of course in boot_disp section also switching from HDMI to LCD necessary:
            output_type = <0x00000001>;
            output_mode = <0x00000004>;

And for the touch:

        ctp {
            device_type = "ctp";
            compatible = "allwinner,sun50i-ctp-para";
            status = "okay";
            ctp_used = <0x00000001>;
            ctp_name = "gt911_DB2";
            ctp_twi_id = <0x00000000>;
            ctp_twi_addr = <0x00000040>;
            ctp_screen_max_x = <0x00000400>;
            ctp_screen_max_y = <0x00000258>;
            ctp_revert_x_flag = <0x00000001>;
            ctp_revert_y_flag = <0x00000001>; 

When I played around with NanoPI M3 I realized that FriendlyARM uses code in u-boot to detect a connected LCD and then configures the kernel correctly (via cmdline there). Wonder whether this is also possible with Pine64...

Link to comment
Share on other sites

  • 0

Nice, just discovered the Azpen Hybrx A64 laptop starting at $69: http://hybrxpc.com/about-hybrx/(combining an A64 board with cheap and most probably ultra glossy 1366x768 LCD and starting with 1 GB DRAM and 16 GB flash). In case it's eMMC it should be possible to flash Armbian to it through USB/FEL...

 

LOL, the same person (Charbax) showcases Allwinner's reference design and 5 months later the very same device in pink (known as Azpen Hybrx now).

Link to comment
Share on other sites

  • 0

Update: TL Lim from Pine64 sent out a couple of hardware: 3 Pine64+ 2GB, WiFi/BT modules, one 7" LCD and a camera module.

 

I only had time to check for the GbE issue (only one Pine64+ affected so two are working!) and LCD. Works flawlessly with Android 7.0 (checked only whether Android on Pine64 now behaves like Armbian and resizes the image on first boot -- check!) but not with Linux in my few tests with Armbian legacy build, the board simply freezes or even powers down with LCD connected. It seems we have an AXP803 PMIC problem with legacy u-boot/kernel here since this occurs even without DT modifications.

 

Edit: Below first our legacy image freezing (with DT modification to activate LCD) and then most recent Android 7.0 image booting:

 

 

Armbian legacy:

boot0 version : 4.0.0
set pll start
set pll end
rtc[0] value = 0x00000000
rtc[1] value = 0x000000001c10000.sdmmc: smc 1 p1 err, cmd 5
rtc[2] value = 0x000000001c10000.sdmmc: smc 1 p1 err, cmd 5
rtc[3] value = 0x000000001c10000.sdmmc: smc 1 p1 err, cmd 5
rtc[4] value = 0x000000001c10000.sdmmc: smc 1 p1 err, cmd 5
rtc[5] value = 0x000000001c10000.sdmmc: sdc set ios: clk 40
DRAM driver version: V1.1
rsb_send_initseq: rsb clk 400Khz -> 3Mhz
PMU: AXP81X
ddr voltage = 1500 mv
DRAM Type = 3 (2:DDR2,3:DDR3,6:LPDDR2,7:LPDDR3)
DRAM clk = 672 MHz
DRAM zq value: 003b3bbb
DRAM single rank full DQ OK
DRAM size = 2048 MB
DRAM init ok
dram size =2048
card boot number = 0, boot0 copy = 0
card no is 0
sdcard 0 line count 4
[mmc]: mmc driver ver 2015-05-08 20:06
[mmc]: sdc0 spd mode error, 2
[mmc]: Wrong media type 0x00000000
[mmc]: ***Try SD card 0***
[mmc]: HSSDR52/SDR25 4 bit
[mmc]: 50000000 Hz
[mmc]: 7580 MB
[mmc]: ***SD/MMC 0 init OK!!!***
sdcard 0 init ok
The size of uboot is 000e4000.
sum=5ea832be
src_sum=5ea832be
Succeed in loading uboot from sdmmc flash.
boot0: start load other image
boot0: Loading BL3-1
Loading file 0 at address 0x40000000,size 0x0000a200 success
boot0: Loading scp
Loading file 2 at address 0x00040000,size 0x00019a00 success
set arisc reset to de-assert state
Ready to disable icache.
?  Configuring SPC Controller
NOTICE:  BL3-1: v1.0(debug):e9fc343
NOTICE:  BL3-1: Built : 18:48:04, Aug 31 2016
INFO:    BL3-1: Initializing runtime services
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address = 0x4a000000
INFO:    BL3-1: Next image spsr = 0x1d3


U-Boot 2014.07-4-pine64-g55c9c8c-dirty (Aug 31 2016 - 18:48:04) Allwinner Technology 

uboot commit : 55c9c8c8ac005b1c00ac948386c60c4a741ebaa9
 
rsb: secure monitor exist
[      0.380]pmbus:   ready
[      0.382][ARISC] :arisc initialize
[      0.710][ARISC] :arisc_dvfs_cfg_vf_table: support only one vf_table
[SCP] :sunxi-arisc driver begin startup 2
[SCP] :arisc_para size:1a8
[SCP] :arisc version: [v0.1.76]
[SCP] :sunxi-arisc driver v1.10 is starting
[      0.837][ARISC] :sunxi-arisc driver startup succeeded
[      0.870]PMU: AXP81X
[      0.872]PMU: AXP81X found
bat_vol=304, ratio=100
[      0.879]PMU: dcdc2 1100
[      0.882]PMU: cpux 1008 Mhz,AXI=336 Mhz
PLL6=600 Mhz,AHB1=200 Mhz, APB1=100Mhz AHB2=300Mhz MBus=400Mhz
device_type = 3253, onoff=1
dcdc1_vol = 3300, onoff=1
dcdc2_vol = 1100, onoff=1
dcdc6_vol = 1100, onoff=1
aldo1_vol = 2800, onoff=0
aldo2_vol = 1800, onoff=1
aldo3_vol = 3000, onoff=1
dldo1_vol = 3300, onoff=0
dldo2_vol = 3300, onoff=0
dldo3_vol = 2800, onoff=0
dldo4_vol = 3300, onoff=1
eldo1_vol = 1800, onoff=1
eldo2_vol = 1800, onoff=0
eldo3_vol = 1800, onoff=0
fldo1_vol = 1200, onoff=0
fldo2_vol = 1100, onoff=1
gpio0_vol = 3100, onoff=0
vbus not exist
no battery, limit to dc
run key detect
no key found
no uart input
DRAM:  2 GiB
fdt addr: 0xb6ebf0c0
Relocation Offset is: 75f11000
In:    serial
Out:   serial
Err:   serial
gic: sec monitor mode
[      1.691]start
drv_disp_init
init_clocks: finish init_clocks.
enable power vcc-hdmi-33, ret=0
drv_disp_init finish
boot_disp.output_disp=0
boot_disp.output_type=3
boot_disp.output_mode=10
fetch script data boot_disp.auto_hpd fail
disp0 device type(4) enable
attched ok, mgr0<-->device1, type=4, mode=10
[      2.066]end
workmode = 0,storage type = 1
[      2.070]MMC:        0
[mmc]: mmc driver ver 2015-06-03 13:50:00
WARNING: Unimplemented Standard Service Call: 0x8000ff05 
WARNING: Unimplemented Standard Service Call: 0x8000ff05 
WARNING: Unimplemented Standard Service Call: 0x8000ff05 
WARNING: Unimplemented Standard Service Call: 0x8000ff05 
WARNING: Unimplemented Standard Service Call: 0x8000ff06 
WARNING: Unimplemented Standard Service Call: 0x8000ff06 
WARNING: Unimplemented Standard Service Call: 0x8000ff06 
SUNXI SD/MMC: 0
[mmc]: start mmc_calibrate_delay_unit, don't access device...
[mmc]: delay chain cal done, sample: 185(ps)
[mmc]: media type 0x0
[mmc]: Wrong media type 0x0
[mmc]: ************Try SD card 0************
[mmc]: host caps: 0x27
[mmc]: MID 03 PSN 437635a9
[mmc]: PNM SL08G -- 0x53-4c-30-38-47
[mmc]: PRV 8.0
[mmc]: MDT m-7 y-2015
[mmc]: speed mode     : HSSDR52/SDR25 
[mmc]: clock          : 50000000 Hz
[mmc]: bus_width      : 4 bit
[mmc]: user capacity  : 7580 MB
[mmc]: ************SD/MMC 0 init OK!!!************
[mmc]: erase_grp_size      : 0x1WrBlk*0x200=0x200 Byte
[mmc]: secure_feature      : 0x0
[mmc]: secure_removal_type : 0x0
[      2.311]sunxi flash init ok
[mmc]: Has init
[      2.345]---drivers/mmc/mmc.c 2733 mmc_init

** Unable to use mmc 0:1 for loading the env **
Using default environment

--------fastboot partitions--------
mbr not exist
base bootcmd=run mmcbootcmd
bootcmd set setargs_mmc
key 0
recovery key high 12, low 10
fastboot key high 6, low 4
no misc partition is found
to be run cmd=run mmcbootcmd
update dtb dram start
update dtb dram  end
WARNING: Unimplemented Standard Service Call: 0x8000ff05 
WARNING: Unimplemented Standard Service Call: 0x8000ff05 
WARNING: Unimplemented Standard Service Call: 0x8000ff05 
WARNING: Unimplemented Standard Service Call: 0x8000ff05 
serial is: ffffffffffffffffffff
get Pine64 model from DRAM size
DRAM >512M
Pine64 model: pine64-plus
no battery exist
sunxi_bmp_logo_display
[mmc]: Has init
[      2.568]---drivers/mmc/mmc.c 2733 mmc_init
** Unrecognized filesystem type **
sunxi bmp info error : unable to open logo file bootlogo.bmp
[      2.582]inter uboot shell
Hit any key to stop autoboot:  0 
[mmc]: Has init
[      5.697]---drivers/mmc/mmc.c 2733 mmc_init
26 bytes read in 27 ms (0 Bytes/s)
Loading boot environment ...
[mmc]: Has init
[      5.740]---drivers/mmc/mmc.c 2733 mmc_init
1601 bytes read in 13 ms (120.1 KiB/s)
Booting with script ...
## Executing script at 41000000
[mmc]: Has init
[      5.778]---drivers/mmc/mmc.c 2733 mmc_init
** File not found /boot/.next **
[mmc]: Has init
[      5.804]---drivers/mmc/mmc.c 2733 mmc_init
** Unrecognized filesystem type **
[mmc]: Has init
[      5.813]---drivers/mmc/mmc.c 2733 mmc_init
** File not found .next **
[mmc]: Has init
[      5.840]---drivers/mmc/mmc.c 2733 mmc_init
69084 bytes read in 18 ms (3.7 MiB/s)
[mmc]: Has init
[      5.868]---drivers/mmc/mmc.c 2733 mmc_init
3789808 bytes read in 210 ms (17.2 MiB/s)
[mmc]: Has init
[      6.090]---drivers/mmc/mmc.c 2733 mmc_init
11730096 bytes read in 618 ms (18.1 MiB/s)
Image lacks image_size field, assuming 16MiB
## Loading init Ramdisk from Legacy Image at 45300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    3789744 Bytes = 3.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 45000000
   Booting using the fdt blob at 0x45000000
   reserving fdt memory region: addr=45000000 size=200000
   reserving fdt memory region: addr=41010000 size=10000
   reserving fdt memory region: addr=41020000 size=800
   reserving fdt memory region: addr=40100000 size=4000
   reserving fdt memory region: addr=40104000 size=1000
   reserving fdt memory region: addr=40105000 size=1000
   Loading Ramdisk to b6b1d000, end b6eba3b0 ... OK
   Loading Device Tree to 44fec000, end 44fffddb ... OK

Starting kernel ...

[mmc]: MMC Device 2 not found
[mmc]: mmc 2 not find, so not exit
INFO:    BL3-1: Next image address = 0x41080000
INFO:    BL3-1: Next image spsr = 0x3c9
Loading, please wait...
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ...  

Android 7.0:

boot0 version : 4.0.0
set pll start
set pll end
rtc[0] value = 0x00000000
rtc[1] value = 0x00000000
rtc[2] value = 0x00000000
rtc[3] value = 0x00000000
rtc[4] value = 0x00000000
rtc[5] value = 0x00000000
DRAM driver version: V1.1
rsb_send_initseq: rsb clk 400Khz -> 3Mhz
PMU: AXP81X
ddr voltage = 1500 mv
DRAM Type = 3 (2:DDR2,3:DDR3,6:LPDDR2,7:LPDDR3)
DRAM clk = 672 MHz
DRAM zq value: 003b3bbb
DRAM single rank full DQ OK
DRAM size = 2048 MB
DRAM init ok
dram size =2048
card boot number = 0, boot0 copy = 0
card no is 0
sdcard 0 line count 4
[mmc]: mmc driver ver 2015-05-08 20:06
[mmc]: sdc0 spd mode error, 2
[mmc]: Wrong media type 0x00000000
[mmc]: ***Try SD card 0***
[mmc]: HSSDR52/SDR25 4 bit
[mmc]: 50000000 Hz
[mmc]: 7580 MB
[mmc]: ***SD/MMC 0 init OK!!!***
sdcard 0 init ok
The size of uboot is 000e8000.
sum=832e0b41
src_sum=832e0b41
Succeed in loading uboot from sdmmc flash.
boot0: start load other image
boot0: Loading BL3-1
Loading file 0 at address 0x40000000,size 0x00008400 success
boot0: Loading scp
Loading file 2 at address 0x00040000,size 0x00019c00 success
set arisc reset to de-assert state
Ready to disable icache.
Jump to secend Boot.


U-Boot 2014.07-6-pine64-longsleep (Jun 18 2016 - 16:15:13) Allwinner Technology 

uboot commit : 55c9c8c8ac005b1c00ac948386c60c4a741ebaa9
 
rsb: secure monitor exist
[      0.363]pmbus:   ready
[      0.365][ARISC] :arisc initialize
[      0.693][ARISC] :arisc_dvfs_cfg_vf_table: support only one vf_table
[      0.807][ARISC] :sunxi-arisc driver startup succeeded
[      0.840]PMU: AXP81X
[      0.842]PMU: AXP81X found
bat_vol=330, ratio=100
[      0.849]PMU: dcdc2 1100
[      0.852]PMU: cpux 1008 Mhz,AXI=336 Mhz
PLL6=600 Mhz,AHB1=200 Mhz, APB1=100Mhz AHB2=300Mhz MBus=400Mhz
device_type = 3253, onoff=1
dcdc1_vol = 3300, onoff=1
dcdc2_vol = 1100, onoff=1
dcdc6_vol = 1100, onoff=1
aldo1_vol = 2800, onoff=0
aldo2_vol = 1800, onoff=1
aldo3_vol = 3000, onoff=1
dldo1_vol = 3300, onoff=0
dldo2_vol = 3300, onoff=0
dldo3_vol = 2800, onoff=0
dldo4_vol = 3300, onoff=1
eldo1_vol = 1800, onoff=1
eldo2_vol = 1800, onoff=0
eldo3_vol = 1800, onoff=0
fldo1_vol = 1200, onoff=0
fldo2_vol = 1100, onoff=1
gpio0_vol = 3100, onoff=0
vbus not exist
no battery, limit to dc
run key detect
no key found
no uart input
DRAM:  2 GiB
fdt addr: 0xb6ebf0a0
Relocation Offset is: 75f11000
In:    serial
Out:   serial
Err:   serial
gic: sec monitor mode
[      1.662]start
drv_disp_init
init_clocks: finish init_clocks.
enable power vcc-hdmi-33, ret=0
drv_disp_init finish
boot_disp.output_disp=0
boot_disp.output_type=3
boot_disp.output_mode=10
fetch script data boot_disp.auto_hpd fail
disp0 device type(4) enable
attched ok, mgr0<-->device1, type=4, mode=10
[      2.033]end
workmode = 0,storage type = 1
[      2.037]MMC:        0
[mmc]: mmc driver ver 2015-06-03 13:50:00
SUNXI SD/MMC: 0
[mmc]: start mmc_calibrate_delay_unit, don't access device...
[mmc]: delay chain cal done, sample: 185(ps)
[mmc]: media type 0x0
[mmc]: Wrong media type 0x0
[mmc]: ************Try SD card 0************
[mmc]: host caps: 0x27
[mmc]: MID 03 PSN 49e841fe
[mmc]: PNM SL08G -- 0x53-4c-30-38-47
[mmc]: PRV 8.0
[mmc]: MDT m-6 y-2016
[mmc]: speed mode     : HSSDR52/SDR25 
[mmc]: clock          : 50000000 Hz
[mmc]: bus_width      : 4 bit
[mmc]: user capacity  : 7580 MB
[mmc]: ************SD/MMC 0 init OK!!!************
[mmc]: erase_grp_size      : 0x1WrBlk*0x200=0x200 Byte
[mmc]: secure_feature      : 0x0
[mmc]: secure_removal_type : 0x0
[      2.243]sunxi flash init ok
[mmc]: Has init
[      2.276]---drivers/mmc/mmc.c 2733 mmc_init
reading uboot.env

** Unable to read "uboot.env" from mmc0:1 **
Using default environment

--------fastboot partitions--------
mbr not exist
base bootcmd=run mmcbootcmd
bootcmd set setargs_mmc
key 0
recovery key high 12, low 10
fastboot key high 6, low 4
no misc partition is found
to be run cmd=run mmcbootcmd
update dtb dram start
update dtb dram  end
serial is: 0410519008081422060e
get Pine64 model from DRAM size
DRAM >512M
Pine64 model: pine64-plus
no battery exist
sunxi_bmp_logo_display
[mmc]: Has init
[      2.477]---drivers/mmc/mmc.c 2733 mmc_init
reading bootlogo.bmp
** Unable to read file bootlogo.bmp **
sunxi bmp info error : unable to open logo file bootlogo.bmp
[      2.493]inter uboot shell
Hit any key to stop autoboot:  0 
[mmc]: Has init
[      5.605]---drivers/mmc/mmc.c 2733 mmc_init
reading uEnv.txt
[mmc]: blkcnt should not be 0
238 bytes read in 9 ms (25.4 KiB/s)
Loading boot environment ...
[mmc]: Has init
[      5.628]---drivers/mmc/mmc.c 2733 mmc_init
reading boot.scr
[mmc]: blkcnt should not be 0
305 bytes read in 6 ms (48.8 KiB/s)
Booting with script ...
## Executing script at 41000000
[mmc]: Has init
[      5.657]---drivers/mmc/mmc.c 2733 mmc_init
reading pine64/sun50i-a64-lcd-pine64-plus.dtb
69427 bytes read in 11 ms (6 MiB/s)
[mmc]: Has init
[      5.714]---drivers/mmc/mmc.c 2733 mmc_init
reading kernel
11165776 bytes read in 545 ms (19.5 MiB/s)
[mmc]: Has init
[      6.270]---drivers/mmc/mmc.c 2733 mmc_init
reading ramdisk.img
5862981 bytes read in 289 ms (19.3 MiB/s)
Image lacks image_size field, assuming 16MiB
## Flattened Device Tree blob at 45000000
   Booting using the fdt blob at 0x45000000
   reserving fdt memory region: addr=41010000 size=10000
   reserving fdt memory region: addr=41020000 size=800
   reserving fdt memory region: addr=40100000 size=4000
   reserving fdt memory region: addr=40104000 size=1000
   reserving fdt memory region: addr=40105000 size=1000
   reserving fdt memory region: addr=45000000 size=11000
   Loading Ramdisk to b6920000, end b6eb7645 ... OK
   Loading Device Tree to 44feb000, end 44ffefff ... OK

Starting kernel ...

[mmc]: MMC Device 2 not found
[mmc]: mmc 2 not find, so not exit
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.10.65+ (root@android-7.0-pine64-squashfs-4gb-ams6
[    0.000000] CPU: AArch64 Processor [410fd034] revision 4
[    0.000000] Machine: sun50iw1p1
[    0.000000] bootconsole [earlycon0] enabled
[    0.000000] cma: CMA: reserved 384 MiB at 9e800000
[    0.000000] On node 0 totalpages: 520192
[    0.000000]   DMA zone: 7112 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 520192 pages, LIFO batch:31
[    0.000000] script_init enter!
[    0.000000] script_init exit!
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv0.2 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] PERCPU: Embedded 12 pages/cpu @ffffffc07ef92000 s20288 r8192 d202
[    0.000000] pcpu-alloc: s20288 r8192 d20672 u49152 alloc=12*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pa0
[    0.000000] Kernel command line: console=ttyS0,115200n8 enforcing=0 cma=384M2
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.000000] Memory: 2032MB = 2032MB total
[    0.000000] Memory: 1637328k/1637328k available, 443440k reserved
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vmalloc : 0xffffff8000000000 - 0xffffffbbffff0000   (245759 )
[    0.000000]     vmemmap : 0xffffffbc00e38000 - 0xffffffbc02a00000   (    27 )
[    0.000000]     modules : 0xffffffbffc000000 - 0xffffffc000000000   (    64 )
[    0.000000]     memory  : 0xffffffc000000000 - 0xffffffc07f000000   (  2032 )
[    0.000000]       .init : 0xffffffc0009f5000 - 0xffffffc000a77f40   (   524 )
[    0.000000]       .text : 0xffffffc000080000 - 0xffffffc0009f45d4   (  9682 )
[    0.000000]       .data : 0xffffffc000a78000 - 0xffffffc000b26050   (   697 )
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:64 nr_irqs:64 0
[    0.000000] Architected cp15 timer(s) running at 24.00MHz (phys).
[    0.000000] Console: colour dummy device 80x25
[    8.589275] Calibrating delay loop (skipped), value calculated using timer f)
[    8.599414] pid_max: default: 32768 minimum: 301
[    8.604398] Security Framework initialized
[    8.607962] SELinux:  Initializing.
[    8.611425] SELinux:  Starting in permissive mode
[    8.616241] Mount-cache hash table entries: 256
[    8.622396] Initializing cgroup subsys debug
[    8.624574] Initializing cgroup subsys freezer
[    8.629193] ftrace: allocating 24867 entries in 98 pages
[    8.665547] CPU0: update cpu_power 1968128
[    8.665579] hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 7 countee
[    8.673692] virtual base = 0xffffff800000a000. 
[    8.676438] gicd_base = 0xffffff800000c000. 
[    8.680577] gicc_base = 0xffffff800000e000. 
[    8.686852] CPU1: Booted secondary processor
[    8.686875] CPU1: update cpu_power 1968128
[    8.689477] CPU2: Booted secondary processor
[    8.689491] CPU2: update cpu_power 1968128
[    8.693595] CPU3: Booted secondary processor
[    8.693608] CPU3: update cpu_power 1968128
[    8.693689] Brought up 4 CPUs
[    8.715640] SMP: Total of 4 processors activated (192.00 BogoMIPS).
[    8.723055] devtmpfs: initialized
[    8.755517] atomic64 test passed
[    8.755541] pinctrl core: initialized pinctrl subsystem
[    8.771192] NET: Registered protocol family 16
[    8.771776] script_sysfs_init success
[    8.776261] dump_class_init,806, success
[    8.778877] vdso: 2 pages (1 code, 1 data) at base ffffffc000a7d000
[    8.783597] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    8.791501] software IO TLB [mem 0xbd000000-0xbd400000] (4MB) mapped at [fff]
[    8.800993] DMA: preallocated 256 KiB pool for atomic allocations
[    8.806638] axp81x_board_init: axp regl_devs num = 23
[    8.811059] pll_audio-set_default_rate=24576000 success!
[    8.815928] pll_video0-set_default_rate=297000000 success!
[    8.821388] pll_video1-set_default_rate=297000000 success!
[    8.826741] pll_de-set_default_rate=297000000 success!
[    8.832807] de-set_default_source=pll_de success!
[    8.836283] de-set_default_rate=297000000 success!
[    8.841036] tcon0-set_default_source=pll_mipi success!
[    8.846052] tcon1-set_default_source=pll_video0 success!
[    8.851512] hdmi-set_default_source=pll_video0 success!
[    8.860156] sun50i-r-pinctrl 1f02c00.pinctrl: initialized sunXi PIO driver
[    8.863454] [sun50iw1p1_pinctrl_probe][838]
[    8.870000] sun50i-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver
[    8.876532] sunxi hwspinlock vbase:0xffffff800005c000
[    8.899255] sunxi_chipid_probe,150: soc bin:0
[    8.956323] bio: create slab <bio-0> at 0
[    8.957425] pwm module init!
[    8.962675] SCSI subsystem initialized
[    8.965888] usbcore: registered new interface driver usbfs
[    8.966804] usbcore: registered new interface driver hub
[    8.972083] usbcore: registered new device driver usb
[    8.979157] Linux video capture interface: v2.00
[    8.983423] [ARISC] :sunxi-arisc driver v1.10
[    9.006441] [ARISC] :sunxi-arisc driver v1.10 startup succeeded
[    9.007423] Advanced Linux Sound Architecture Driver Initialized.
[    9.014144] Bluetooth: Core ver 2.16
[    9.016397] NET: Registered protocol family 31
[    9.020534] Bluetooth: HCI device and connection manager initialized
[    9.026801] Bluetooth: HCI socket layer initialized
[    9.031558] Bluetooth: L2CAP socket layer initialized
[    9.036533] Bluetooth: SCO socket layer initialized
[    9.043959] cfg80211: Calling CRDA to update world regulatory domain
[    9.048320] [pm]aw_pm_init!
[    9.050283] rtc physical base = 0x0000000001f00000 . 
[    9.055216] np name = /soc@01c00000/rtc@01f00000. 
[    9.059849] base = ffffff8000070100, len = 4.
[    9.064112] pmu name: pmu0 .
[    9.066975] pmu0_enable = 0x1. 
[    9.069998] pmux_id = 0x6. 
[    9.072727] pmux_twi_id = 0x1. 
[    9.075796] pmux_twi_addr = 0x34. 
[    9.079130] pmu name: pmu1 .
[    9.081989] Warning: can not find np for pmu1. 
[    9.086609] add_sys_pwr_dm: get ldo name  for id: vcc-lpddr failed
[    9.092585] after inited: sys_mask config = 0x4a55. 
[    9.097307] Warning: can not find np for dynamic_standby_para. 
[    9.103214] [pm]valid
[    9.105301] [pm]valid
[    9.107519] Notice: sun9i&sun8iw5&sun50i not need support normal standby,   .
[    9.116952] Switching to clocksource arch_sys_counter
[    9.164628] FS-Cache: Loaded
[    9.165176] CacheFiles: Loaded
[    9.189481] get det_vbus is fail, 84
[    9.192931] NET: Registered protocol family 2
[    9.194452] TCP established hash table entries: 16384 (order: 6, 262144 byte)
[    9.199081] TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
[    9.205589] TCP: Hash tables configured (established 16384 bind 16384)
[    9.212867] TCP: reno registered
[    9.214837] UDP hash table entries: 1024 (order: 3, 32768 bytes)
[    9.220781] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
[    9.227863] NET: Registered protocol family 1
[    9.232289] Unpacking initramfs...
[    9.533089] Freeing initrd memory: 5724K (ffffffc075920000 - ffffffc075eb700)
[    9.536578] lock super standby defaultly!
[    9.538576] lookup_scene_lock_name: new scene lock super_standby
[    9.544453] scene_lock_init name=super_standby
[    9.548822] scene_lock: super_standby, type 5, count 1
[    9.555152] audit: initializing netlink socket (disabled)
[    9.559203] type=2000 audit(0.890:1): initialized
[    9.568739] NTFS driver 2.1.30 [Flags: R/W].
[    9.569022] fuse init (API version 7.22)
[    9.572861] msgmni has been set to 3977
[    9.575638] SELinux:  Registering netfilter hooks
[    9.582167] NET: Registered protocol family 38
[    9.584529] io scheduler noop registered
[    9.588287] io scheduler deadline registered
[    9.592572] io scheduler cfq registered (default)
[    9.599195] uart0: ttyS0 at MMIO 0x1c28000 (irq = 32) is a SUNXI
[    9.602969] sw_console_setup()1173 - console setup baud 115200 parity n bitsn
[    9.610808] console [ttyS0] enabled, bootconsole disabled
[    9.610808] console [ttyS0] enabled, bootconsole disabled
[    9.623008] uart1: ttyS1 at MMIO 0x1c28400 (irq = 33) is a SUNXI
[    9.634680] uart2: ttyS2 at MMIO 0x1c28800 (irq = 34) is a SUNXI
[    9.641904] uart3: ttyS3 at MMIO 0x1c28c00 (irq = 35) is a SUNXI
[    9.649129] uart4: ttyS4 at MMIO 0x1c29000 (irq = 36) is a SUNXI
[    9.656540] misc dump reg init
[    9.667845] loop: module loaded
[    9.671612] sunxi-bt bt.29: Missing bt_power.
[    9.676389] sunxi-bt bt.29: bt_power_name ((null))
[    9.681624] sunxi-bt bt.29: io_regulator_name (vcc-wifi-io)
[    9.687749] sunxi-bt bt.29: bt_rst gpio=356  mul-sel=1  pull=-1  drv_level=-0
[    9.696350] sunxi-bt bt.29: clk not config
[    9.701128] sunxi-bt bt.29: block state already is 1
[    9.707012] sunxi-wlan wlan.28: wlan_busnum (1)
[    9.711959] sunxi-wlan wlan.28: Missing wlan_power.
[    9.717298] sunxi-wlan wlan.28: wlan_power_name ((null))
[    9.723112] sunxi-wlan wlan.28: io_regulator_name (vcc-wifi-io)
[    9.729604] sunxi-wlan wlan.28: wlan_regon gpio=354  mul-sel=1  pull=-1  drv0
[    9.738956] sunxi-wlan wlan.28: wlan_hostwake gpio=355  mul-sel=6  pull=-1  0
[    9.748587] sunxi-wlan wlan.28: clk not config
[    9.756686] tun: Universal TUN/TAP device driver, 1.6
[    9.762223] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    9.770087] WARNING: Get ephy clock is failed
[    9.775879] geth_check_addr
[    9.778926] geth_check_addr: try to use mac str, 00:00:00:00:00:00
[    9.785686] chipid 0x4,0x10,0x51,0x90,0x8,0x8,0x14,0x22,0x6,0xe,
[    9.792331] result 0xfc,0xa,0xe3,0x97,0x75,0x19,0x0,0x4e,0xe,0x78,
[    9.799117] addr 0x0,0x6,0xdc,0x97,0x75,0x19,
[    9.803909] try to use hwaddr 0x0,0x6,0xdc,0x97,0x75,0x19,
[    9.810200] PPP generic driver version 2.4.2
[    9.815584] PPP BSD Compression module registered
[    9.820739] PPP Deflate Compression module registered
[    9.826265] PPP MPPE Compression module registered
[    9.831504] NET: Registered protocol family 24
[    9.836401] PPTP driver version 0.8.5
[    9.840666] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    9.848016] get ehci0-controller drv_vbus_gpio is fail
[    9.853638] get ehci0-controller, regulator_io is no nocare
[    9.859785] [sunxi-ehci0]: probe, pdev->name: 1c1a000.ehci0-controller, sunx8
[    9.873062] sunxi-ehci 1c1a000.ehci0-controller: SW USB2.0 'Enhanced' Host Cr
[    9.882974] sunxi-ehci 1c1a000.ehci0-controller: new USB bus registered, ass1
[    9.892907] sunxi-ehci 1c1a000.ehci0-controller: irq 104, io mem 0xffffffc00c
[    9.918684] sunxi-ehci 1c1a000.ehci0-controller: USB 0.0 started, EHCI 1.00
[    9.926414] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    9.933842] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber1
[    9.941741] usb usb1: Product: SW USB2.0 'Enhanced' Host Controller (EHCI) Dr
[    9.949924] usb usb1: Manufacturer: Linux 3.10.65+ ehci_hcd
[    9.956010] usb usb1: SerialNumber: sunxi-ehci
[    9.962019] hub 1-0:1.0: USB hub found
[    9.966142] hub 1-0:1.0: 1 port detected
[    9.970725] scene_lock_init name=ehci_standby
[    9.975591] get ehci1-controller drv_vbus_gpio is fail
[    9.981213] get ehci1-controller, regulator_io is no nocare
[    9.987350] [sunxi-ehci1]: probe, pdev->name: 1c1b000.ehci1-controller, sunxa
[   10.000632] sunxi-ehci 1c1b000.ehci1-controller: SW USB2.0 'Enhanced' Host Cr
[   10.010544] sunxi-ehci 1c1b000.ehci1-controller: new USB bus registered, ass2
[   10.020354] sunxi-ehci 1c1b000.ehci1-controller: irq 106, io mem 0xffffffc00c
[   10.046603] sunxi-ehci 1c1b000.ehci1-controller: USB 0.0 started, EHCI 1.00
[   10.054329] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[   10.061757] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber1
[   10.069695] usb usb2: Product: SW USB2.0 'Enhanced' Host Controller (EHCI) Dr
[   10.077881] usb usb2: Manufacturer: Linux 3.10.65+ ehci_hcd
[   10.083966] usb usb2: SerialNumber: sunxi-ehci
[   10.089729] hub 2-0:1.0: USB hub found
[   10.093844] hub 2-0:1.0: 1 port detected
[   10.098427] scene_lock_init name=ehci_standby
[   10.103565] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[   10.110525] get ohci0-controller drv_vbus_gpio is fail
[   10.116145] get ohci0-controller, regulator_io is no nocare
[   10.122282] [sunxi-ohci0]: probe, pdev->name: 1c1a000.ohci0-controller, sunx0
[   10.132521] sunxi-ohci 1c1a000.ohci0-controller: SW USB2.0 'Open' Host Contrr
[   10.142063] sunxi-ohci 1c1a000.ohci0-controller: new USB bus registered, ass3
[   10.151546] sunxi-ohci 1c1a000.ohci0-controller: irq 105, io mem 0xffffffc008
[   10.217929] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[   10.225356] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber1
[   10.233246] usb usb3: Product: SW USB2.0 'Open' Host Controller (OHCI) Driver
[   10.241050] usb usb3: Manufacturer: Linux 3.10.65+ ohci_hcd
[   10.247145] usb usb3: SerialNumber: sunxi-ohci
[   10.252883] hub 3-0:1.0: USB hub found
[   10.257021] hub 3-0:1.0: 1 port detected
[   10.261586] scene_lock_init name=ohci_standby
[   10.266461] get ohci1-controller drv_vbus_gpio is fail
[   10.272071] get ohci1-controller, regulator_io is no nocare
[   10.278212] [sunxi-ohci1]: probe, pdev->name: 1c1b000.ohci1-controller, sunx0
[   10.288447] sunxi-ohci 1c1b000.ohci1-controller: SW USB2.0 'Open' Host Contrr
[   10.297978] sunxi-ohci 1c1b000.ohci1-controller: new USB bus registered, ass4
[   10.307457] sunxi-ohci 1c1b000.ohci1-controller: irq 107, io mem 0xffffffc008
[   10.375371] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[   10.382799] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber1
[   10.390688] usb usb4: Product: SW USB2.0 'Open' Host Controller (OHCI) Driver
[   10.398493] usb usb4: Manufacturer: Linux 3.10.65+ ohci_hcd
[   10.404587] usb usb4: SerialNumber: sunxi-ohci
[   10.410312] hub 4-0:1.0: USB hub found
[   10.414440] hub 4-0:1.0: 1 port detected
[   10.418997] scene_lock_init name=ohci_standby
[   10.424466] usbcore: registered new interface driver cdc_acm
[   10.430657] cdc_acm: USB Abstract Control Model driver for USB modems and ISs
[   10.439690] usbcore: registered new interface driver usb-storage
[   10.446465] usbcore: registered new interface driver ums-alauda
[   10.453140] usbcore: registered new interface driver ums-cypress
[   10.459960] usbcore: registered new interface driver ums-datafab
[   10.466714] usbcore: registered new interface driver ums_eneub6250
[   10.473668] usbcore: registered new interface driver ums-freecom
[   10.480451] usbcore: registered new interface driver ums-isd200
[   10.487114] usbcore: registered new interface driver ums-jumpshot
[   10.493976] usbcore: registered new interface driver ums-karma
[   10.500545] usbcore: registered new interface driver ums-onetouch
[   10.507423] usbcore: registered new interface driver ums-realtek
[   10.514233] usbcore: registered new interface driver ums-sddr09
[   10.520905] usbcore: registered new interface driver ums-sddr55
[   10.527567] usbcore: registered new interface driver ums-usbat
[   10.534725] usbcore: registered new interface driver usbserial
[   10.541305] usbcore: registered new interface driver option
[   10.547584] usbserial: USB Serial support registered for GSM modem (1-port)
[   10.556606] mousedev: PS/2 mouse device common for all mice
[   10.563203] usbcore: registered new interface driver xpad
[   10.569316] usbcore: registered new interface driver usb_acecad
[   10.575986] usbcore: registered new interface driver aiptek
[   10.582294] usbcore: registered new interface driver gtco
[   10.588400] usbcore: registered new interface driver hanwang
[   10.594789] usbcore: registered new interface driver kbtab
[   10.601010] usbcore: registered new interface driver wacom
[   10.609216] sunxi-rtc 1f00000.rtc: rtc core: registered rtc-sunxi as rtc0
[   10.616675] sunxi-rtc 1f00000.rtc: RTC enabled
[   10.622194] IR NEC protocol handler initialized
[   10.627150] IR RC5(x) protocol handler initialized
[   10.632379] IR RC6 protocol handler initialized
[   10.637332] IR JVC protocol handler initialized
[   10.642275] IR Sony protocol handler initialized
[   10.647326] IR RC5 (streamzap) protocol handler initialized
[   10.653409] IR SANYO protocol handler initialized
[   10.658550] IR MCE Keyboard/mouse protocol handler initialized
[   10.665388] Registered IR keymap rc_map_sunxi
[   10.671161] input: sunxi_ir_recv as /devices/soc.0/1f02000.s_cir/rc/rc0/inpu0
[   10.679611] rc0: sunxi_ir_recv as /devices/soc.0/1f02000.s_cir/rc/rc0
[   10.687213] input: MCE IR Keyboard/Mouse (sunxi-rc-recv) as /devices/virtual1
[   10.697335] sunxi cedar version 0.1 
[   10.701350] [cedar]: install start!!!
[   10.705423] ycy the get irq is 90
[   10.709845] ycy clk_bass_vir 0x18  is ffffff8000150018, the value:3006207
[   10.717272] ycy clk_bass_vir 0x13c  is ffffff800015013c, the value:0
[   10.724210] ycy clk_bass_vir 0x64  is ffffff8000150064, the value:601810
[   10.731536] ycy clk_bass_vir 0x2c4  is ffffff80001502c4, the value:601c10
[   10.738957] ycy clk_bass_vir 0x100  is ffffff8000150100, the value:0
[   10.745902] [cedar]: install end!!!
[   10.785917] input: axp81x-supplyer as /devices/platform/axp81x_board/axp81x-2
[   10.810146] sunxi budget cooling probe start !
[   10.815049] CPU freq cooling register Success
[   10.819823] CPU hotplug cooling register Success
[   10.825250] CPU budget cooling register Success
[   10.830902] sunxi gpu cooling probe start !
[   10.835488] CPU gpu cooling register Success
[   10.840560] device-mapper: uevent: version 1.0.3
[   10.846139] device-mapper: ioctl: 4.24.0-ioctl (2013-01-15) initialised: dm-m
[   10.855564] Bluetooth: HCI UART driver ver 2.2
[   10.860416] Bluetooth: HCI H4 protocol initialized
[   10.865656] Bluetooth: HCI Three-wire UART (H5) protocol initialized
[   10.875545] cpuidle: using governor ladder
[   10.880016] cpuidle: using governor menu
[   10.885387] sunxi-mmc 1c0f000.sdmmc: SD/MMC/SDIO Host Controller Driver(v0.22
[   10.898282] sunxi-mmc 1c0f000.sdmmc: regulator prop vmmc,str none
[   10.904949] sunxi-mmc 1c0f000.sdmmc: regulator prop vqmmc,str none
[   10.911701] sunxi-mmc 1c0f000.sdmmc: regulator prop vdmmc,str vcc-sdc
[   10.918849] sunxi-mmc 1c0f000.sdmmc: No vmmc regulator found
[   10.925039] sunxi-mmc 1c0f000.sdmmc: No vqmmc regulator found
[   10.931845] sunxi-mmc 1c0f000.sdmmc: Got CD GPIO #166.
[   10.937834] sunxi-mmc 1c0f000.sdmmc: sdc set ios: clk 0Hz bm PP pm UP vdd 21B
[   10.948788] sunxi-mmc 1c0f000.sdmmc: no vqmmc,Check if there is regulator
[   10.971559] sunxi-mmc 1c0f000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[   11.001109] sunxi-mmc 1c0f000.sdmmc: base:0xffffff8000152000 irq:92
[   11.008389] sunxi-mmc 1c10000.sdmmc: SD/MMC/SDIO Host Controller Driver(v0.22
[   11.021272] sunxi-mmc 1c10000.sdmmc: Can't get vmmc regulator string
[   11.028211] sunxi-mmc 1c10000.sdmmc: Can't get vqmmc regulator string
[   11.035257] sunxi-mmc 1c10000.sdmmc: Can't get vdmmc regulator string
[   11.042306] get() with no identifier
[   11.046205] get() with no identifier
[   11.050102] get() with no identifier
[   11.054011] sunxi-mmc 1c10000.sdmmc: No vmmc regulator found
[   11.060207] sunxi-mmc 1c10000.sdmmc: No vqmmc regulator found
[   11.066481] sunxi-mmc 1c10000.sdmmc: No vdmmc regulator found
[   11.073497] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 0Hz bm PP pm UP vdd 21B
[   11.084459] sunxi-mmc 1c10000.sdmmc: no vqmmc,Check if there is regulator
[   11.100284] sunxi-mmc 1c0f000.sdmmc: smc 0 p0 err, cmd 52, RTO !!
[   11.107750] sunxi-mmc 1c0f000.sdmmc: smc 0 p0 err, cmd 52, RTO !!
[   11.109315] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[   11.125812] sunxi-mmc 1c0f000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[   11.129037] sunxi-mmc 1c10000.sdmmc: base:0xffffff800015a000 irq:93
[   11.146578] sunxi-mmc 1c0f000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[   11.147026] hidraw: raw HID events driver (C) Jiri Kosina
[   11.159127] usbcore: registered new interface driver usbhid
[   11.159131] usbhid: USB HID core driver
[   11.160020] zram: Created 1 device(s) ...
[   11.179751] ashmem: initialized
[   11.180808] sunxi-mmc 1c0f000.sdmmc: smc 0 p0 err, cmd 5, RTO !!
[   11.181620] sunxi-mmc 1c0f000.sdmmc: smc 0 p0 err, cmd 5, RTO !!
[   11.182432] sunxi-mmc 1c0f000.sdmmc: smc 0 p0 err, cmd 5, RTO !!
[   11.183243] sunxi-mmc 1c0f000.sdmmc: smc 0 p0 err, cmd 5, RTO !!
[   11.183873] sunxi-mmc 1c0f000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[   11.183930] sunxi-mmc 1c0f000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[   11.186302] sunxi-mmc 1c0f000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[   11.243923] logger: created 256K log 'log_main'
[   11.249188] logger: created 256K log 'log_events'
[   11.254633] logger: created 256K log 'log_radio'
[   11.256322] mmc0: host does not support reading read-only switch. assuming w.
[   11.259632] sunxi-mmc 1c0f000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[   11.259707] sunxi-mmc 1c0f000.sdmmc: sdc set ios: clk 50000000Hz bm PP pm ONB
[   11.259824] sunxi-mmc 1c0f000.sdmmc: sdc set ios: clk 50000000Hz bm PP pm ONB
[   11.259849] mmc0: new high speed SDHC card at address aaaa
[   11.309413] logger: created 256K log 'log_system'
[   11.314586] mmcblk0: mmc0:aaaa SL08G 7.40 GiB 
[   11.320973]  mmcblk0: p1 p2 p3 p4
[   11.327235] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 52, RTO !!
[   11.334718] sunxi-codec-machine sound.6:  codec-aif1 <-> 1c22c00.i2s0-controk
[   11.334725] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 52, RTO !!
[   11.334744] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[   11.337149] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[   11.338969] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 8, RTO !!
[   11.339776] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[   11.340580] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[   11.341385] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[   11.342189] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[   11.342996] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[   11.343800] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[   11.344605] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[   11.345409] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[   11.345425] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm OD pm ON vB
[   11.346262] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 1, RTO !!
[   11.346277] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 0Hz bm OD pm OFF vdd 0B
[   11.462102] sunxi-codec-machine sound.6:  codec-aif2 <-> bb-dai mapping ok
[   11.470275] sunxi-codec-machine sound.6:  codec-aif2 <-> bb-dai mapping ok
[   11.478334] sunxi-codec-machine sound.6:  codec-aif3 <-> bb-dai mapping ok
[   11.489138] input: audiocodec sunxi Audio Jack as /devices/soc.0/sound.6/sou3
[   11.499443] SUNXI_HMIC_STS:8,225
[   11.503377] sndhdmi sound.7:  sndhdmi <-> 1c22800.daudio mapping ok
[   11.512058] u32 classifier
[   11.515080] plugout_end:switch:0
[   11.518711]     Actions configured
[   11.522424] Netfilter messages via NETLINK v0.30.
[   11.527684] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[   11.534851] ctnetlink v0.93: registering with nfnetlink.
[   11.542705] NF_TPROXY: Transparent proxy support initialized, version 4.1.0
[   11.550307] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
[   11.557896] xt_time: kernel timezone is -0000
[   11.562788] ipip: IPv4 over IPv4 tunneling driver
[   11.568926] gre: GRE over IPv4 demultiplexor driver
[   11.574263] ip_gre: GRE over IPv4 tunneling driver
[   11.581756] ip_tables: (C) 2000-2006 Netfilter Core Team
[   11.587983] arp_tables: (C) 2002 David S. Miller
[   11.593150] TCP: bic registered
[   11.596575] TCP: cubic registered
[   11.600181] TCP: westwood registered
[   11.604088] TCP: htcp registered
[   11.607607] Initializing XFRM netlink socket
[   11.612608] NET: Registered protocol family 10
[   11.619936] mip6: Mobile IPv6
[   11.623266] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   11.629555] sit: IPv6 over IPv4 tunneling driver
[   11.636078] NET: Registered protocol family 17
[   11.641011] NET: Registered protocol family 15
[   11.646368] Bluetooth: RFCOMM TTY layer initialized
[   11.651757] Bluetooth: RFCOMM socket layer initialized
[   11.657365] Bluetooth: RFCOMM ver 1.11
[   11.661465] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   11.667262] Bluetooth: BNEP filters: protocol multicast
[   11.672995] Bluetooth: BNEP socket layer initialized
[   11.678413] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[   11.684905] Bluetooth: HIDP socket layer initialized
[   11.690944] Registering SWP/SWPB emulation handler
[   11.697178] registered taskstats version 1
[   11.702593] get usb_serial_number success from boot command line[sw_udc]: al)
[   11.717334] [sw_udc]: sunxi_udc_set_selfpowered_2320: usb device is not actie
[   11.725234] [sw_udc]: sunxi_udc_pullup, is_on = 0
[   11.730377] [sw_udc]: sunxi_udc_set_pullup_2337: usb device is not active
[   11.738018] file system registered
[   11.745508] android_usb gadget: Mass Storage Function, version: 2009/09/11
[   11.753035] android_usb gadget: Number of LUNs=3
[   11.758109]  lun0: LUN: removable file: (no medium)
[   11.763443]  lun1: LUN: removable file: (no medium)
[   11.768774]  lun2: LUN: removable file: (no medium)
[   11.774884] [sw_udc]: sunxi_udc_set_selfpowered_2320: usb device is not actie
[   11.782787] android_usb gadget: android_usb ready
[   11.787920] [sw_udc]: [sunxi_usb_udc]: binding gadget driver 'android_usb'
[   11.795631] sunxi-rtc 1f00000.rtc: setting system clock to 2010-01-01 00:00:)
[   11.806347] input: sunxi-ths as /devices/virtual/input/input4
[   11.812984] thermal thermal_zone0: failed to read out thermal zone 0
[   11.828448] ALSA device list:
[   11.831696]   #0: audiocodec
[   11.834835]   #1: sndhdmi
[   11.838298] Freeing unused kernel memory: 520K (ffffffc0009f5000 - ffffffc00)
[   11.849338] init: init first stage started!
[   11.863643] SELinux: 2048 avtab hash slots, 6593 rules.
[   11.876305] SELinux: 2048 avtab hash slots, 6593 rules.
[   11.882131] SELinux:  1 users, 2 roles, 653 types, 0 bools, 1 sens, 1024 cats
[   11.890058] SELinux:  63 classes, 6593 rules
[   11.898725] SELinux:  Completing initialization.
[   11.903762] SELinux:  Setting up existing superblocks.
[   11.909456] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
[   11.917315] SELinux: initialized (dev rootfs, type rootfs), uses genfs_contes
[   11.925380] SELinux: initialized (dev bdev, type bdev), not configured for lg
[   11.933760] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[   11.941402] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIs
[   11.949324] SELinux: initialized (dev devtmpfs, type devtmpfs), uses transits
[   11.958260] SELinux: initialized (dev debugfs, type debugfs), uses genfs_cons
[   11.971307] SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
[   11.978856] SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
[   11.986382] SELinux: initialized (dev anon_inodefs, type anon_inodefs), not g
[   11.996279] SELinux: initialized (dev devpts, type devpts), uses transition s
[   12.004394] SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfss
[   12.013031] SELinux: initialized (dev configfs, type configfs), uses genfs_cs
[   12.021405] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIs
[   12.029321] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
[   12.255729] type=1403 audit(1262304008.960:2): policy loaded auid=42949672955
[   12.265722] init: (Initializing SELinux non-enforcing took 0.42s.)
[   12.276343] init: init second stage started!
[   12.288426] init: Running restorecon...
[   12.365786] init: waitpid failed: No child processes
[   12.371629] init: (Loading properties from /default.prop took 0.00s.)
[   12.381603] init: (Parsing /init.environ.rc took 0.00s.)
[   12.387962] init: (Parsing /init.usb.rc took 0.00s.)
[   12.394033] init: /init.sun50iw1p1.rc: 185: invalid keyword 'ifeq'
[   12.400832] init: /init.sun50iw1p1.rc: 190: invalid keyword 'endif'
[   12.408334] init: (Parsing init.sensors.rc took 0.00s.)
[   12.414050] init: (Parsing init.common.rc took 0.01s.)
[   12.420051] init: (Parsing init.sun50iw1p1.usb.rc took 0.00s.)
[   12.426604] init: (Parsing init.zygote64_32.rc took 0.00s.)
[   12.432731] init: (Parsing /init.sun50iw1p1.rc took 0.04s.)
[   12.439671] init: (Parsing /init.usb.configfs.rc took 0.00s.)
[   12.446090] init: ignored duplicate definition of service 'zygote'init: igno)
[   12.463571] init: (Parsing /init.rc took 0.09s.)
[   12.694333] init: Starting service 'ueventd'...
[   12.700213] init: Waiting for /dev/.coldboot_done...
[   12.702418] ueventd: ueventd started!
[   13.136380] 
[   13.136380] 
[   13.136380] rmmod_host_driver
[   13.136380] 
[   13.144475] [ehci0-controller]: sunxi_usb_disable_ehci
[   13.150114] [sunxi-ehci0]: remove, pdev->name: 1c1a000.ehci0-controller, sun0
[   13.160423] scene_lock_destroy name=ehci_standby
[   13.165478] sunxi-ehci 1c1a000.ehci0-controller: remove, state 4
[   13.172072] usb usb1: USB disconnect, device number 1
[   13.179064] sunxi-ehci 1c1a000.ehci0-controller: USB bus 1 deregistered
[   13.186369] [ohci0-controller]: sunxi_usb_disable_ohci
[   13.191992] [sunxi-ohci0]: remove, pdev->name: 1c1a000.ohci0-controller, sun0
[   13.200695] ueventd: Coldboot took 0.50s.
[   13.206653] scene_lock_destroy name=ohci_standby
[   13.207418] init: Waiting for /dev/.coldboot_done took 0.52s.
[   13.207518] init: /dev/hw_random not found
[   13.207739] init: Unable to set adequate mmap entropy value!
[   13.228635] sunxi-ohci 1c1a000.ohci0-controller: remove, state 4
[   13.235242] usb usb3: USB disconnect, device number 1
[   13.242591] sunxi-ohci 1c1a000.ohci0-controller: USB bus 3 deregistered
[   13.242691] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contes
[   13.245175] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIs
[   13.252927] init: write_file: Unable to open '/proc/cpu/alignment': No such y
[   13.253242] init: write_file: Unable to open '/proc/sys/kernel/sched_compat_y
[   13.255529] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contes
[   13.255846] init: write_file: Unable to write to '/dev/cpuctl/cpu.shares': It
[   13.258036] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contes
[   13.265778] SELinux: initialized (dev pstore, type pstore), uses genfs_contes
[   13.266098] init: write_file: Unable to open '/proc/sys/abi/swp': No such fiy
[   13.267953] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIs
[   13.268659] init: /dev/hw_random not found
[   13.282380] [NAND]Failed to insmod nand!!!
[   13.282535] init: Starting service 'exec 1 (/sbin/busybox)'...
[   13.283772] type=1400 audit(1262304010.000:3): avc:  denied  { transition } 1
[   13.284269] type=1400 audit(1262304010.010:4): avc:  denied  { rlimitinh } f1
[   13.284309] type=1400 audit(1262304010.010:5): avc:  denied  { siginh } for 1
[   13.284371] type=1400 audit(1262304010.010:6): avc:  denied  { noatsecure } 1
[   13.306274] 
[   13.306274] The number of cylinders for this disk is set to 242560.
[   13.306274] There is nothing wrong with that, but this is larger than 1024,
[   13.306274] and could in certain setups cause problems with:
[   13.306274] 1) software that runs at boot time (e.g., old versions of LILO)
[   13.306274] 2) booting and partitioning software from other OSs
[   13.306274]    (e.g., DOS FDISK, OS/2 FDISK)
[   13.306274] 
[   13.306274] Command (m for help): Partition number (1-4): 
[   13.306274] Command (m for help): Command action
[   13.306274]    e   extended
[   13.306274]    p   primary partition (1-4)
[   13.483101] 
[   13.483101] 
[   13.483101] insmod_host_driver
[   13.483101] 
[   13.491336] [ehci0-controller]: sunxi_usb_enable_ehci
[   13.496853] [sunxi-ehci0]: probe, pdev->name: 1c1a000.ehci0-controller, sunx8
[   13.510122] sunxi-ehci 1c1a000.ehci0-controller: SW USB2.0 'Enhanced' Host Cr
[   13.520048] sunxi-ehci 1c1a000.ehci0-controller: new USB bus registered, ass1
[   13.530357] sunxi-ehci 1c1a000.ehci0-controller: irq 104, io mem 0xffffff800c
[   13.549641] sunxi-ehci 1c1a000.ehci0-controller: USB 0.0 started, EHCI 1.00
[   13.557367] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   13.564792] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber1
[   13.572688] usb usb1: Product: SW USB2.0 'Enhanced' Host Controller (EHCI) Dr
[   13.580868] usb usb1: Manufacturer: Linux 3.10.65+ ehci_hcd
[   13.586952] usb usb1: SerialNumber: sunxi-ehci
[   13.595282] hub 1-0:1.0: USB hub found
[   13.599594] hub 1-0:1.0: 1 port detected
[   13.604156] scene_lock_init name=ehci_standby
[   13.608923] [ohci0-controller]: sunxi_usb_enable_ohci
[   13.614438] [sunxi-ohci0]: probe, pdev->name: 1c1a000.ohci0-controller, sunx0
[   13.624666] sunxi-ohci 1c1a000.ohci0-controller: SW USB2.0 'Open' Host Contrr
[   13.634266] sunxi-ohci 1c1a000.ohci0-controller: new USB bus registered, ass3
[   13.643748] sunxi-ohci 1c1a000.ohci0-controller: irq 105, io mem 0xffffffc000
[   13.711110] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[   13.718535] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber1
[   13.726423] usb usb3: Product: SW USB2.0 'Open' Host Controller (OHCI) Driver
[   13.734223] usb usb3: Manufacturer: Linux 3.10.65+ ohci_hcd
[   13.740317] usb usb3: SerialNumber: sunxi-ohci
[   13.747045] hub 3-0:1.0: USB hub found
[   13.751186] hub 3-0:1.0: 1 port detected
[   13.755773] scene_lock_init name=ohci_standby
[   13.760550] host_chose finished 86!
[   14.295371] Selected partition 4
[   14.295371] First cylinder (1-242560, default 1): Last cylinder or +size or  
[   14.295371] Command (m for help): 
[   14.295372]  mmcblk0: p1 p2 p3 p4
[   14.324448] The partition table has been altered.
[   14.324448] Calling ioctl() to re-read partition table
[   14.350020] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. 1
[   14.359188] SELinux: initialized (dev mmcblk0p2, type ext4), uses xattr
[   14.893454] /dev/block/mmcblk0p4: 11/303104 files (0.0% non-contiguous), 277s
[   14.922309] resize2fs 1.42.9 (28-Dec-2013)
[   14.928947] The filesystem is already 1201664 blocks long.  Nothing to do!
[   14.928947] 
[   14.941081] Disk is resized
[   14.949408] init: Service 'exec 1 (/sbin/busybox)' (pid 1446) exited with st0
[   14.970175] SELinux: initialized (dev mmcblk0p1, type vfat), uses genfs_conts
[   14.978366] fs_mgr: __mount(source=/dev/block/mmcblk0p1,target=/bootloader,t0
[   14.997409] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. 1
[   15.006570] SELinux: initialized (dev mmcblk0p2, type ext4), uses xattr
[   15.013883] fs_mgr: __mount(source=/dev/block/mmcblk0p2,target=/system,type=0
[   15.023323] EXT4-fs (mmcblk0p3): Ignoring removed nomblk_io_submit option
[   15.035355] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. t
[   15.046884] SELinux: initialized (dev mmcblk0p3, type ext4), uses xattr
[   15.054180] fs_mgr: check_fs(): mount(/dev/block/mmcblk0p3,/cache,ext4)=0: Ss
[   15.069195] fs_mgr: check_fs(): unmount(/cache) succeeded
[   15.076712] fs_mgr: Running /system/bin/e2fsck on /dev/block/mmcblk0p3
[   15.269445] type=1400 audit(1262304012.020:7): avc:  denied  { getattr } for1
[   15.292619] type=1400 audit(1262304012.050:8): avc:  denied  { read } for  p1
[   15.314210] type=1400 audit(1262304012.070:9): avc:  denied  { open } for  p1
[   15.336898] type=1400 audit(1262304012.090:10): avc:  denied  { write } for 1
[   15.358710] type=1400 audit(1262304012.120:11): avc:  denied  { ioctl } for 1
[   15.423173] e2fsck: e2fsck 1.42.9 (28-Dec-2013)
[   15.423173] 
[   15.429790] e2fsck: Pass 1: Checking inodes, blocks, and sizes
[   15.429790] 
[   15.437780] e2fsck: Pass 2: Checking directory structure
[   15.437780] 
[   15.445213] e2fsck: Pass 3: Checking directory connectivity
[   15.445213] 
[   15.452927] e2fsck: Pass 4: Checking reference counts
[   15.452927] 
[   15.460071] e2fsck: Pass 5: Checking group summary information
[   15.460071] 
[   15.468063] e2fsck: /dev/block/mmcblk0p3: 11/49152 files (0.0% non-contiguous
[   15.468063] 
[   15.480627] EXT4-fs (mmcblk0p3): Ignoring removed nomblk_io_submit option
[   15.496573] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. c
[   15.511327] SELinux: initialized (dev mmcblk0p3, type ext4), uses xattr
[   15.518616] fs_mgr: __mount(source=/dev/block/mmcblk0p3,target=/cache,type=e0
[   15.527624] EXT4-fs (mmcblk0p4): Ignoring removed nomblk_io_submit option
[   15.539465] EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. t
[   15.550989] SELinux: initialized (dev mmcblk0p4, type ext4), uses xattr
[   15.558288] fs_mgr: check_fs(): mount(/dev/block/mmcblk0p4,/data,ext4)=0: Sus
[   15.568718] fs_mgr: check_fs(): unmount(/data) succeeded
[   15.574578] fs_mgr: Running /system/bin/e2fsck on /dev/block/mmcblk0p4
[   15.670625] e2fsck: e2fsck 1.42.9 (28-Dec-2013)
[   15.670625] 
[   15.677234] e2fsck: Pass 1: Checking inodes, blocks, and sizes
[   15.677234] 
[   15.685234] e2fsck: Pass 2: Checking directory structure
[   15.685234] 
[   15.692654] e2fsck: Pass 3: Checking directory connectivity
[   15.692654] 
[   15.700367] e2fsck: Pass 4: Checking reference counts
[   15.700367] 
[   15.707511] e2fsck: Pass 5: Checking group summary information
[   15.707511] 
[   15.715562] e2fsck: /dev/block/mmcblk0p4: 11/303104 files (0.0% non-contiguos
[   15.715562] 
[   15.728348] EXT4-fs (mmcblk0p4): Ignoring removed nomblk_io_submit option
[   15.740286] EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. c
[   15.755085] SELinux: initialized (dev mmcblk0p4, type ext4), uses xattr
[   15.762361] fs_mgr: __mount(source=/dev/block/mmcblk0p4,target=/data,type=ex0
[   15.773436] init: (Parsing /system/etc/init/atrace.rc took 0.00s.)
[   15.780925] init: (Parsing /system/etc/init/audioserver.rc took 0.00s.)
[   15.788892] init: (Parsing /system/etc/init/bootanim.rc took 0.00s.)
[   15.796542] init: (Parsing /system/etc/init/bootstat.rc took 0.00s.)
[   15.804159] init: (Parsing /system/etc/init/cameraserver.rc took 0.00s.)
[   15.812098] init: (Parsing /system/etc/init/debuggerd.rc took 0.00s.)
[   15.819773] init: (Parsing /system/etc/init/debuggerd64.rc took 0.00s.)
[   15.827628] init: (Parsing /system/etc/init/drmserver.rc took 0.00s.)
[   15.835390] init: (Parsing /system/etc/init/dumpstate.rc took 0.00s.)
[   15.843071] init: (Parsing /system/etc/init/gatekeeperd.rc took 0.00s.)
[   15.850957] init: (Parsing /system/etc/init/init-debug.rc took 0.00s.)
[   15.858721] init: (Parsing /system/etc/init/installd.rc took 0.00s.)
[   15.866312] init: (Parsing /system/etc/init/keystore.rc took 0.00s.)
[   15.873971] init: (Parsing /system/etc/init/lmkd.rc took 0.00s.)
[   15.881179] init: (Parsing /system/etc/init/logcatd.rc took 0.00s.)
[   15.888689] init: (Parsing /system/etc/init/logd.rc took 0.00s.)
[   15.895987] init: (Parsing /system/etc/init/mdnsd.rc took 0.00s.)
[   15.903285] init: (Parsing /system/etc/init/mediacodec.rc took 0.00s.)
[   15.911028] init: (Parsing /system/etc/init/mediadrmserver.rc took 0.00s.)
[   15.919244] init: (Parsing /system/etc/init/mediaextractor.rc took 0.00s.)
[   15.927394] init: (Parsing /system/etc/init/mediaserver.rc took 0.00s.)
[   15.935362] init: (Parsing /system/etc/init/mtpd.rc took 0.00s.)
[   15.942568] init: (Parsing /system/etc/init/netd.rc took 0.00s.)
[   15.949752] init: (Parsing /system/etc/init/perfprofd.rc took 0.00s.)
[   15.957514] init: (Parsing /system/etc/init/racoon.rc took 0.00s.)
[   15.964912] init: (Parsing /system/etc/init/rild.rc took 0.00s.)
[   15.972146] init: (Parsing /system/etc/init/servicemanager.rc took 0.00s.)
[   15.980372] init: (Parsing /system/etc/init/surfaceflinger.rc took 0.00s.)
[   15.988527] init: (Parsing /system/etc/init/uncrypt.rc took 0.00s.)
[   15.996129] init: (Parsing /system/etc/init/vdc.rc took 0.00s.)
[   16.003237] init: (Parsing /system/etc/init/vold.rc took 0.00s.)
[   16.105407] Adding 262140k swap on /dev/block/zram0.  Priority:-1 extents:1 S
[   16.488733] [DISP]disp_module_init
[   16.495005] [DISP] disp_boot_para_parse,line:302:of_property_read disp.boot_l
[   16.503591] [DISP] boot_disp:0x0
[   16.507866] [DISP] disp_sys_script_get_item,line:193:of_find_compatible_nodel
[   16.518179] [DISP] disp_sys_script_get_item,line:193:of_find_compatible_nodel
[   16.528488] [DISP] disp_sys_script_get_item,line:193:of_find_compatible_nodel
[   16.556130] [DISP] disp_boot_para_parse,line:302:of_property_read disp.fb_bal
[   16.564505] [DISP] fb_base:0x0
[   16.583238] [DISP] lcd_clk_config,line:808:disp 0, clk: pll(330000000),clk(3)
     clk real:pll(330000000),clk(330000000),dclk(82500000) dsi_rate(148500000)
[   16.603325] [DISP]disp_module_init finish
[   16.608495] mb709_mipi: LCD_power_on[   16.626789] enter tr_probe
[   16.629940] exit tr_probe
mb709_mipi: LCD_panel_init
[   16.642141] [DISP] disp_sys_pin_set_state,line:420:pinctrl_lookup_state for l
[   16.668515] [DISP] disp_boot_para_parse,line:302:of_property_read disp.boot_l
[   16.677111] [DISP] boot_disp:0x0
[   16.680683] HDMI base address: ffffff8001a80000
[   16.687123] [HDMI] power vcc-hdmi-33
[   16.691606] [HDMI] cec support = 0
[   16.924757] [mb709_mipi] send cmd=0x80
[   16.928849] [mb709_mipi] send cmd=0x81
[   16.932938] [mb709_mipi] send cmd=0x82
[   16.937037] [mb709_mipi] send cmd=0x83
[   16.941126] [mb709_mipi] send cmd=0x84
[   16.945223] [mb709_mipi] send cmd=0x85
[   16.949312] [mb709_mipi] send cmd=0x86
[   17.052672] mb709_mipi: LCD_bl_open[   17.070974] HDMI CEC base address: fff0
[   17.076851] HDMI CEC device_create
[   17.082012] HDMI CEC initialized: Oct  5 2016 12:14:36

[   17.087790] init: insmod: open("/system/vendor/modules/te_sec_storage.ko") fz
[   17.383650] Mali: Init Mali gpu clocks successfully
[   17.389983] gpu cooling callback register Success
[   17.399421] Mali: Mali device driver loaded
[   17.440632] input: sunxi-keyboard as /devices/virtual/input/input5
[   17.466418] get ctp_power_io is invalid. 
[   17.471751] get_detect_list name = sc7a30
[   17.476733] get_detect_list name = lsm303d
[   17.481204] get_detect_list name = fxos8700
[   17.485805] get_detect_list name = mxc622x
[   17.490644] get_detect_list name = dmard06
[   17.495493] get_detect_list name = dmard10
[   17.499969] get_detect_list name = kxtik
[   17.504249] get_detect_list name = lis3dh_acc
[   17.509474] get_detect_list name = lis3de_acc
[   17.514235] get_detect_list name = afa750
[   17.518642] get_detect_list name = mc32x0
[   17.523025] get_detect_list: script_get_item err.support_number = 6. 
[   17.530091] get_detect_list name = mma865x
[   17.534564] get_detect_list name = mma7660
[   17.539042] get_detect_list name = mma8452
[   17.543515] get_detect_list name = stk831x
[   17.547995] get_detect_list: script_get_item err.support_number = 2. 
[   17.555036] get_detect_list name = bma250
[   17.559414] get_detect_list name = lsm9ds0_acc_mag
[   17.564826] type=1400 audit(1262304014.360:12): avc:  denied  { write } for 1
[   17.579451] [VFE]cci probe end cci_sel = 0!
[   17.580308] [VFE]cci_init end
[   17.593140] type=1400 audit(1262304014.380:13): avc:  denied  { add_name } f1
[   17.612955] type=1400 audit(1262304014.400:14): avc:  denied  { create } for1
[   17.632747] type=1400 audit(1262304014.420:15): avc:  denied  { write open }1
[   17.656168] sw_get_write_info:read erro or read null !
[   17.661920] get write info erro!
[   17.665622] twi_start()370 - [i2c1] START can't sendout!
[   17.671663] twi_start()370 - [i2c1] START can't sendout!
[   17.677712] twi_start()370 - [i2c1] START can't sendout!
[   17.702266] twi_start()370 - [i2c1] START can't sendout!
[   17.708311] twi_start()370 - [i2c1] START can't sendout!
[   17.714371] twi_start()370 - [i2c1] START can't sendout!
[   17.721835] gpu cooling callback set freq limit 0
[   17.731785] twi_start()370 - [i2c1] START can't sendout!
[   17.737824] twi_start()370 - [i2c1] START can't sendout!
[   17.743875] twi_start()370 - [i2c1] START can't sendout!
[   17.761347] twi_start()370 - [i2c1] START can't sendout!
[   17.767434] twi_start()370 - [i2c1] START can't sendout!
[   17.767888] [VFE]Welcome to Video Front End driver
[   17.768159] [VFE]csi probe end csi_sel = 0!
[   17.769032] [VFE]csi_init end
[   17.769899] [VFE]isp probe start isp_sel = 0!
[   17.791296] twi_start()370 - [i2c1] START can't sendout!
[   17.797193] [ISP] isp platform_id = 3!
[   17.801304] [VFE]isp probe end isp_sel = 0!
[   17.806626] [VFE]sunxi_isp_platform_register end
[   17.810508] twi_start()370 - [i2c1] START can't sendout!
[   17.810756] twi_start()370 - [i2c1] START can't sendout!
[   17.811005] twi_start()370 - [i2c1] START can't sendout!
[   17.830089] [VFE]mipi probe start mipi_sel = 0!
[   17.830187] twi_start()370 - [i2c1] START can't sendout!
[   17.830435] twi_start()370 - [i2c1] START can't sendout!
[   17.830683] twi_start()370 - [i2c1] START can't sendout!
[   17.849861] twi_start()370 - [i2c1] START can't sendout!
[   17.850109] twi_start()370 - [i2c1] START can't sendout!
[   17.850358] twi_start()370 - [i2c1] START can't sendout!
[   17.869541] twi_start()370 - [i2c1] START can't sendout!
[   17.869789] twi_start()370 - [i2c1] START can't sendout!
[   17.870037] twi_start()370 - [i2c1] START can't sendout!
[   17.887234] [VFE]mipi probe end mipi_sel = 0!
[   17.889220] twi_start()370 - [i2c1] START can't sendout!
[   17.889468] twi_start()370 - [i2c1] START can't sendout!
[   17.889717] twi_start()370 - [i2c1] START can't sendout!
[   17.908901] twi_start()370 - [i2c1] START can't sendout!
[   17.909149] twi_start()370 - [i2c1] START can't sendout!
[   17.909397] twi_start()370 - [i2c1] START can't sendout!
[   17.927422] [VFE]mipi_init end
[   17.930770] [VFE]flash_init end
[   17.936097] [VFE]pdev->id = 0
[   17.938433] twi_start()370 - [i2c1] START can't sendout!
[   17.938682] twi_start()370 - [i2c1] START can't sendout!
[   17.938930] twi_start()370 - [i2c1] START can't sendout!
[   17.956739] [VFE]dev->vip_sel = 0
[   17.958096] twi_start()370 - [i2c1] START can't sendout!
[   17.958344] twi_start()370 - [i2c1] START can't sendout!
[   17.958593] twi_start()370 - [i2c1] START can't sendout!
[   17.977770] [VFE_WARN]fetch csi0_dev0_twi_id from device_tree failed
[   17.977776] twi_start()370 - [i2c1] START can't sendout!
[   17.978024] twi_start()370 - [i2c1] START can't sendout!
[   17.978273] twi_start()370 - [i2c1] START can't sendout!
[   18.002135] [VFE_WARN]fetch csi0_dev0_afvdd from device_tree failed
[   18.007306] twi_start()370 - [i2c1] START can't sendout!
[   18.007555] twi_start()370 - [i2c1] START can't sendout!
[   18.007803] twi_start()370 - [i2c1] START can't sendout!
[   18.026378] [VFE_WARN]fetch csi0_dev0_afvdd_vol from device_tree failed
[   18.026976] twi_start()370 - [i2c1] START can't sendout!
[   18.027225] twi_start()370 - [i2c1] START can't sendout!
[   18.027473] twi_start()370 - [i2c1] START can't sendout!
[   18.051001] [VFE_WARN]fetch csi0_dev0_power_en from device_tree failed
[   18.056502] twi_start()370 - [i2c1] START can't sendout!
[   18.056750] twi_start()370 - [i2c1] START can't sendout!
[   18.056999] twi_start()370 - [i2c1] START can't sendout!
[   18.075554] [VFE_WARN]fetch csi0_dev0_flash_en from device_tree failed
[   18.076177] twi_start()370 - [i2c1] START can't sendout!
[   18.076425] twi_start()370 - [i2c1] START can't sendout!
[   18.076673] twi_start()370 - [i2c1] START can't sendout!
[   18.086020] twi_start()370 - [i2c1] START can't sendout!
[   18.086268] twi_start()370 - [i2c1] START can't sendout!
[   18.086516] twi_start()370 - [i2c1] START can't sendout!
[   18.105700] twi_start()370 - [i2c1] START can't sendout!
[   18.105948] twi_start()370 - [i2c1] START can't sendout!
[   18.106197] twi_start()370 - [i2c1] START can't sendout!
[   18.125379] twi_start()370 - [i2c1] START can't sendout!
[   18.125628] twi_start()370 - [i2c1] START can't sendout!
[   18.125876] twi_start()370 - [i2c1] START can't sendout!
[   18.145059] twi_start()370 - [i2c1] START can't sendout!
[   18.145308] twi_start()370 - [i2c1] START can't sendout!
[   18.145556] twi_start()370 - [i2c1] START can't sendout!
[   18.164739] twi_start()370 - [i2c1] START can't sendout!
[   18.164988] twi_start()370 - [i2c1] START can't sendout!
[   18.165236] twi_start()370 - [i2c1] START can't sendout!
[   18.184419] twi_start()370 - [i2c1] START can't sendout!
[   18.184668] twi_start()370 - [i2c1] START can't sendout!
[   18.184916] twi_start()370 - [i2c1] START can't sendout!
[   18.204101] twi_start()370 - [i2c1] START can't sendout!
[   18.204349] twi_start()370 - [i2c1] START can't sendout!
[   18.204598] twi_start()370 - [i2c1] START can't sendout!
[   18.221768] [VFE_WARN]fetch csi0_dev0_flash_mode from device_tree failed
[   18.223779] twi_start()370 - [i2c1] START can't sendout!
[   18.224027] twi_start()370 - [i2c1] START can't sendout!
[   18.224275] twi_start()370 - [i2c1] START can't sendout!
[   18.243463] twi_start()370 - [i2c1] START can't sendout!
[   18.243711] twi_start()370 - [i2c1] START can't sendout!
[   18.243960] twi_start()370 - [i2c1] START can't sendout!
[   18.263143] twi_start()370 - [i2c1] START can't sendout!
[   18.263391] twi_start()370 - [i2c1] START can't sendout!
[   18.263639] twi_start()370 - [i2c1] START can't sendout!
[   18.281258] [VFE_WARN]fetch csi0_dev0_af_pwdn from device_tree failed
[   18.282822] twi_start()370 - [i2c1] START can't sendout!
[   18.283070] twi_start()370 - [i2c1] START can't sendout!
[   18.283319] twi_start()370 - [i2c1] START can't sendout!
[   18.302502] twi_start()370 - [i2c1] START can't sendout!
[   18.302751] twi_start()370 - [i2c1] START can't sendout!
[   18.302999] twi_start()370 - [i2c1] START can't sendout!
[   18.322182] twi_start()370 - [i2c1] START can't sendout!
[   18.322431] twi_start()370 - [i2c1] START can't sendout!
[   18.322679] twi_start()370 - [i2c1] START can't sendout!
[   18.340470] [VFE_WARN]fetch csi0_dev1_twi_id from device_tree failed
[   18.341863] twi_start()370 - [i2c1] START can't sendout!
[   18.342111] twi_start()370 - [i2c1] START can't sendout!
[   18.342360] twi_start()370 - [i2c1] START can't sendout!
[   18.361543] twi_start()370 - [i2c1] START can't sendout!
[   18.361791] twi_start()370 - [i2c1] START can't sendout!
[   18.362039] twi_start()370 - [i2c1] START can't sendout!
[   18.381222] twi_start()370 - [i2c1] START can't sendout!
[   18.381471] twi_start()370 - [i2c1] START can't sendout!
[   18.381719] twi_start()370 - [i2c1] START can't sendout!
[   18.399592] [VFE_WARN]fetch csi0_dev1_afvdd from device_tree failed
[   18.400901] twi_start()370 - [i2c1] START can't sendout!
[   18.401150] twi_start()370 - [i2c1] START can't sendout!
[   18.401398] twi_start()370 - [i2c1] START can't sendout!
[   18.420582] twi_start()370 - [i2c1] START can't sendout!
[   18.420831] twi_start()370 - [i2c1] START can't sendout!
[   18.421080] twi_start()370 - [i2c1] START can't sendout!
[   18.440263] twi_start()370 - [i2c1] START can't sendout!
[   18.440512] twi_start()370 - [i2c1] START can't sendout!
[   18.440760] twi_start()370 - [i2c1] START can't sendout!
[   18.458645] [VFE_WARN]fetch csi0_dev1_afvdd_vol from device_tree failed
[   18.459958] twi_start()370 - [i2c1] START can't sendout!
[   18.460206] twi_start()370 - [i2c1] START can't sendout!
[   18.460455] twi_start()370 - [i2c1] START can't sendout!
[   18.479623] twi_start()370 - [i2c1] START can't sendout!
[   18.479872] twi_start()370 - [i2c1] START can't sendout!
[   18.480120] twi_start()370 - [i2c1] START can't sendout!
[   18.499302] twi_start()370 - [i2c1] START can't sendout!
[   18.499551] twi_start()370 - [i2c1] START can't sendout!
[   18.499799] twi_start()370 - [i2c1] START can't sendout!
[   18.518037] [VFE_WARN]fetch csi0_dev1_power_en from device_tree failed
[   18.518982] twi_start()370 - [i2c1] START can't sendout!
[   18.519231] twi_start()370 - [i2c1] START can't sendout!
[   18.519479] twi_start()370 - [i2c1] START can't sendout!
[   18.538664] twi_start()370 - [i2c1] START can't sendout!
[   18.538912] twi_start()370 - [i2c1] START can't sendout!
[   18.539161] twi_start()370 - [i2c1] START can't sendout!
[   18.558342] twi_start()370 - [i2c1] START can't sendout!
[   18.558591] twi_start()370 - [i2c1] START can't sendout!
[   18.558840] twi_start()370 - [i2c1] START can't sendout!
[   18.577914] [VFE_WARN]fetch csi0_dev1_flash_en from device_tree failed
[   18.578024] twi_start()370 - [i2c1] START can't sendout!
[   18.578272] twi_start()370 - [i2c1] START can't sendout!
[   18.578521] twi_start()370 - [i2c1] START can't sendout!
[   18.597703] twi_start()370 - [i2c1] START can't sendout!
[   18.597951] twi_start()370 - [i2c1] START can't sendout!
[   18.598199] twi_start()370 - [i2c1] START can't sendout!
[   18.617382] twi_start()370 - [i2c1] START can't sendout!
[   18.617630] twi_start()370 - [i2c1] START can't sendout!
[   18.617879] twi_start()370 - [i2c1] START can't sendout!
[   18.637063] twi_start()370 - [i2c1] START can't sendout!
[   18.637312] twi_start()370 - [i2c1] START can't sendout!
[   18.637561] twi_start()370 - [i2c1] START can't sendout!
[   18.654590] [VFE_WARN]fetch csi0_dev1_flash_mode from device_tree failed
[   18.656743] twi_start()370 - [i2c1] START can't sendout!
[   18.656991] twi_start()370 - [i2c1] START can't sendout!
[   18.657240] twi_start()370 - [i2c1] START can't sendout!
[   18.676423] twi_start()370 - [i2c1] START can't sendout!
[   18.676671] twi_start()370 - [i2c1] START can't sendout!
[   18.676919] twi_start()370 - [i2c1] START can't sendout!
[   18.696102] twi_start()370 - [i2c1] START can't sendout!
[   18.696351] twi_start()370 - [i2c1] START can't sendout!
[   18.696599] twi_start()370 - [i2c1] START can't sendout!
[   18.714467] [VFE_WARN]fetch csi0_dev1_af_pwdn from device_tree failed
[   18.715782] twi_start()370 - [i2c1] START can't sendout!
[   18.716031] twi_start()370 - [i2c1] START can't sendout!
[   18.716279] twi_start()370 - [i2c1] START can't sendout!
[   18.735462] twi_start()370 - [i2c1] START can't sendout!
[   18.735711] twi_start()370 - [i2c1] START can't sendout!
[   18.735959] twi_start()370 - [i2c1] START can't sendout!
[   18.755142] twi_start()370 - [i2c1] START can't sendout!
[   18.755391] twi_start()370 - [i2c1] START can't sendout!
[   18.755639] twi_start()370 - [i2c1] START can't sendout!
[   18.773700] [VFE]fetch rear sensor list info start!
[   18.774822] twi_start()370 - [i2c1] START can't sendout!
[   18.775071] twi_start()370 - [i2c1] START can't sendout!
[   18.775319] twi_start()370 - [i2c1] START can't sendout!
[   18.794502] twi_start()370 - [i2c1] START can't sendout!
[   18.794751] twi_start()370 - [i2c1] START can't sendout!
[   18.794999] twi_start()370 - [i2c1] START can't sendout!
[   18.813823] [VFE]Fetch sensor list form"/system/etc/hawkview/sensor_list_cfg"
[   18.814182] twi_start()370 - [i2c1] START can't sendout!
[   18.814430] twi_start()370 - [i2c1] START can't sendout!
[   18.814679] twi_start()370 - [i2c1] START can't sendout!
[   18.833864] twi_start()370 - [i2c1] START can't sendout!
[   18.834112] twi_start()370 - [i2c1] START can't sendout!
[   18.834360] twi_start()370 - [i2c1] START can't sendout!
[   18.853543] twi_start()370 - [i2c1] START can't sendout!
[   18.853791] twi_start()370 - [i2c1] START can't sendout!
[   18.854040] twi_start()370 - [i2c1] START can't sendout!
[   18.873222] twi_start()370 - [i2c1] START can't sendout!
[   18.873470] twi_start()370 - [i2c1] START can't sendout!
[   18.873719] twi_start()370 - [i2c1] START can't sendout!
[   18.892897] twi_start()370 - [i2c1] START can't sendout!
[   18.898946] twi_start()370 - [i2c1] START can't sendout!
[   18.905031] twi_start()370 - [i2c1] START can't sendout!
[   18.922490] twi_start()370 - [i2c1] START can't sendout!
[   18.928548] twi_start()370 - [i2c1] START can't sendout!
[   18.934622] twi_start()370 - [i2c1] START can't sendout!
[   18.951995] twi_start()370 - [i2c1] START can't sendout!
[   18.958053] twi_start()370 - [i2c1] START can't sendout!
[   18.964134] twi_start()370 - [i2c1] START can't sendout!
[   18.981534] twi_start()370 - [i2c1] START can't sendout!
[   18.987587] twi_start()370 - [i2c1] START can't sendout!
[   18.993660] twi_start()370 - [i2c1] START can't sendout!
[   19.011054] twi_start()370 - [i2c1] START can't sendout!
[   19.017106] twi_start()370 - [i2c1] START can't sendout!
[   19.023181] twi_start()370 - [i2c1] START can't sendout!
[   19.040552] twi_start()370 - [i2c1] START can't sendout!
[   19.046611] twi_start()370 - [i2c1] START can't sendout!
[   19.052690] twi_start()370 - [i2c1] START can't sendout!
[   19.070090] twi_start()370 - [i2c1] START can't sendout!
[   19.076144] twi_start()370 - [i2c1] START can't sendout!
[   19.082222] twi_start()370 - [i2c1] START can't sendout!
[   19.099619] twi_start()370 - [i2c1] START can't sendout!
[   19.105681] twi_start()370 - [i2c1] START can't sendout!
[   19.111758] twi_start()370 - [i2c1] START can't sendout!
[   19.125211] [vfe_warn]open file failed!
[   19.129104] twi_start()370 - [i2c1] START can't sendout!
[   19.129353] twi_start()370 - [i2c1] START can't sendout!
[   19.129601] twi_start()370 - [i2c1] START can't sendout!
[   19.148788] twi_start()370 - [i2c1] START can't sendout!
[   19.154846] twi_start()370 - [i2c1] START can't sendout!
[   19.160935] twi_start()370 - [i2c1] START can't sendout!
[   19.178292] twi_start()370 - [i2c1] START can't sendout!
[   19.184349] twi_start()370 - [i2c1] START can't sendout!
[   19.190427] twi_start()370 - [i2c1] START can't sendout!
[   19.207851] twi_start()370 - [i2c1] START can't sendout!
[   19.213912] twi_start()370 - [i2c1] START can't sendout!
[   19.219988] twi_start()370 - [i2c1] START can't sendout!
[   19.237298] get node lightsensor failed
[   19.241501] get sysconfig para erro!
[   19.245482] get node gyroscopesensor failed
[   19.250077] get sysconfig para erro!
[   19.254064] get node compasssensor failed
[   19.258459] get sysconfig para erro!
[   19.262415] ctp_wakeup: !!!!gpio data 1
[   19.365214] get_detect_list name = icn83xx_ts
[   19.369993] get_detect_list: script_get_item err.support_number = 11. 
[   19.377160] get_detect_list name = aw5306_ts
[   19.381836] get_detect_list name = zet622x
[   19.386326] get_detect_list name = gt818_ts
[   19.390904] get_detect_list: script_get_item err.support_number = 8. 
[   19.397966] get_detect_list name = tu_ts
[   19.402254] get_detect_list: script_get_item err.support_number = 7. 
[   19.409322] get_detect_list name = gt9xxf_ts
[   19.413998] get_detect_list name = gt9xxnew_ts
[   19.418879] get_detect_list name = gt9xx_ts
[   19.423454] get_detect_list name = gslX680new
[   19.428231] get_detect_list name = gslX680
[   19.432713] get_detect_list: script_get_item err.support_number = 2. 
[   19.439769] get_detect_list name = gt82x
[   19.444380] get_detect_list name = ft5x_ts
[   19.448865] get_detect_list: script_get_item err.support_number = 0. 
[   19.450105] [VFE]fetch rear sensor list info end!
[   19.450154] [VFE]fetch front sensor list info start!
[   19.450157] [VFE]Fetch sensor list form"/system/etc/hawkview/sensor_list_cfg"
[   19.474967] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.503062] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.522728] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.542463] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.562057] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.581747] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.601443] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.621134] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.640820] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.660511] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.680175] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.683299] [vfe_warn]open file failed!
[   19.709677] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.729379] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.749075] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.768745] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.788966] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.808055] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.837605] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.857317] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.886810] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.906501] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.926169] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.945924] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.965497] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   19.986174] [VFE]fetch front sensor list info end!
[   19.991645] [VFE_WARN]os_gpio_request failed, gpio=145, ret=0xfffffff0, -16
[   19.994994] sunxi_i2c_do_xfer()902 - [i2c0] incomplete xfer (status: 0x20, d)
[   20.008288] [VFE_WARN]os_gpio_request failed, gpio=144, ret=0xfffffff0, -16
[   20.015903] [VFE_WARN]os_gpio_request failed, gpio=129, ret=0xfffffff0, -16
[   20.024382] [VFE]probe_work_handle start!
[   20.024721] [VFE]vfe_init end
[   20.032229] [VFE]vfe_runtime_resume
[   20.048053] [VFE]..........................vfe clk open!.....................
[   20.056045] [VFE_WARN]vfe dphy clock is null
[   20.060718] [VFE]v4l2 subdev register input_num = 0
[   20.066336] [VFE]vfe sensor detect start! input_num = 0
[   20.072063] [VFE]Find sensor name is "s5k4ec", i2c address is 5a, type is "Y!
[   20.080245] [VFE]Sub device register "s5k4ec" i2c_addr = 0x5a start!
[   20.087218] [VFE]v4l2_device_register_subdev return 0
[   20.092755] [VFE]registered sensor subdev is OK!
[   20.097811] [VFE]Check sensor!
[   20.113665] [s5k4ec]CSI_SUBDEV_PWR_ON 16:51
[   20.118239] CSI_SUBDEV_PWR_ON 12-21,11:10----------
[   20.128764] usbcore: registered new interface driver asix
[   20.136878] [VFE]mclk on
[   20.150944] usbcore: registered new interface driver qf9700
[   20.172969] usbcore: registered new interface driver MOSCHIP usb-ethernet drr
[   20.173950] [s5k4ec]sensor_init
[   20.184687] [VFE CCI_0 ERR] Status error at addr_8bit = 5a, wr_flag = 0, val0
[   20.193483] [VFE CCI_0 ERR] Status error at addr_8bit = 5a, wr_flag = 0, val0
[   20.201694] usbcore: registered new interface driver rtl8150
[   20.208486] [VFE CCI_0 ERR] Status error at addr_8bit = 5a, wr_flag = 0, val0
[   20.216787] usbcore: registered new interface driver cdc_ether
[   20.223449] [s5k4ec]sensor write retry=2
[   20.227962] [VFE CCI_0 ERR] Status error at addr_8bit = 5a, wr_flag = 0, val0
[   20.232551] init: insmod: open("/system/vendor/modules/smsc75xx.ko") failed:y
[   20.232552] [BT_LPM] bluesleep_init: BlueSleep Mode Driver Ver 1.1
[   20.232900] [BT_LPM] bluesleep_probe: bt_hostwake gpio=357  mul-sel=6  pull=0
[   20.232900] 
[   20.232924] [BT_LPM] bluesleep_probe: uart_index (1)
[   20.232924] 
[   20.235117] [BT_LPM] bluesleep_get_uart_port: bluesleep_get_uart_port get ua3
[   20.235120] [BT_LPM] bluesleep_start: bluesleep_acquire irq
[   20.235120] 
[   20.239109] init: Starting service 'logd'...
[   20.249402] init: SELinux: Could not set context for /logger:  Read-only film
[   20.253931] init: (Loading properties from /system/build.prop took 0.00s.)
[   20.254040] init: (Loading properties from /vendor/build.prop took 0.00s.)
[   20.254104] init: (Loading properties from /factory/factory.prop took 0.00s.)
[   20.254308] init: /recovery not specified in fstab
[   20.257678] init: Starting service 'debuggerd'...
[   20.259444] init: Starting service 'debuggerd64'...
[   20.261202] init: Starting service 'vold'...
[   20.263755] init: Not bootcharting.
[   20.362435] [VFE CCI_0 ERR] Status error at addr_8bit = 5a, wr_flag = 0, val0
[   20.362457] logd.auditd: start
[   20.362515] logd.klogd: 11873655004
[   20.378614] [VFE CCI_0 ERR] Status error at addr_8bit = 5a, wr_flag = 0, val0
[   20.387362] [s5k4ec]sensor write retry=2
[   20.391659] [s5k4ec]sensor_write err at sensor_detect!
[   20.397269] [s5k4ec]chip found is not an target chip.
[   20.402801] [s5k4ec]CSI_SUBDEV_PWR_OFF
[   20.407021] [VFE]mclk off
[   20.434060] [VFE]vfe sensor subdev unregister!
[   20.438966] [VFE]Sub device register "s5k4ec" failed!
[   20.444492] [VFE_ERR]vfe sensor register check error at input_num = 0
[   20.451546] [VFE]v4l2 subdev register input_num = 1
[   20.456920] axp81x_aldo1: Failed to create debugfs directory
[   20.463152] axp81x_dldo3: Failed to create debugfs directory
[   20.469366] axp81x_eldo3: Failed to create debugfs directory
[   20.475605] axp81x_aldo1: Failed to create debugfs directory
[   20.481806] [VFE]vfe sensor detect start! input_num = 1
[   20.487527] [VFE_WARN]NOT found this item:  gc2145, you can add this sensor !
[   20.497278] [VFE]Sub device register "gc2145" i2c_addr = 0x78 start!
[   20.504235] [VFE_ERR]Error registering v4l2 subdevice No such device!
[   20.511294] [VFE_ERR]vfe sensor register check error at input_num = 1
[   20.518387] [VFE]V4L2 device registered as (null)
[   20.523589] [VFE]vfe_runtime_suspend
[   20.527526] [VFE]..........................vfe clk close!....................
[   20.541807] [VFE]probe_work_handle end!
[   20.918467] init: Starting service 'exec 2 (/system/bin/tzdatacheck)'...
[   20.942054] init: Service 'exec 2 (/system/bin/tzdatacheck)' (pid 1609) exit0
[   20.954591] init: property_set("ro.bt.bdaddr_path", "/data/misc/bluetooth/bdd
[   25.893308] init: do_start: Service bootclone not found
[   25.899329] init: Starting service 'precopy'...
[   25.906103] init: (Loading properties from /data/local.prop took 0.00s.)
[   25.909338] type=1400 audit(1262304022.840:16): avc: denied { read } for pid1
[   25.911318] type=1400 audit(1262304022.840:17): avc: denied { execute } for 1
[   25.912120] type=1400 audit(1262304022.840:18): avc: denied { open } for pid1
[   25.912239] type=1400 audit(1262304022.840:19): avc: denied { execute_no_tra1
[   25.913149] type=1400 audit(1262304022.840:20): avc: denied { getattr } for 1
[   25.913668] type=1400 audit(1262304022.840:21): avc: denied { read } for pid1
[   25.913808] type=1400 audit(1262304022.840:22): avc: denied { open } for pid1
[   25.914283] type=1400 audit(1262304022.840:23): avc: denied { getattr } for 1
[   25.914830] type=1400 audit(1262304022.840:24): avc: denied { execute } for 1
[   25.915647] type=1400 audit(1262304022.840:25): avc: denied { read open } fo1
[   25.915846] type=1400 audit(1262304022.840:26): avc: denied { execute_no_tra1
[   25.935027] type=1400 audit(1262304022.840:27): avc: denied { write } for pi1
[   25.936471] type=1400 audit(1262304022.840:28): avc: denied { add_name } for1
[   25.936612] type=1400 audit(1262304022.840:29): avc: denied { create } for p1
[   25.936756] type=1400 audit(1262304022.840:30): avc: denied { read write ope1
[   26.250396] init: Service 'precopy' (pid 1610) exited with status 0
[   26.257818] init: Starting service 'logd-reinit'...
[   26.269414] init: Starting service 'healthd'...
[   26.275195] init: cannot find '/system/bin/tee_supplicant' (No such file or '
[   26.278106] binder: 1615:1615 transaction failed 29189, size 0-0
[   26.280114] logd.daemon: reinit
[   26.295860] init: Starting service 'watchdogd'...
[   26.302394] init: Starting service 'lmkd'...
[   26.304261] watchdogd: started (interval 60, margin 20)!
[   26.304335] watchdogd: Failed to open /dev/watchdog: No such file or directoy
[   26.322113] init: Starting service 'servicemanager'...
[   26.329065] init: Starting service 'surfaceflinger'...
[   26.335557] init: couldn't write 1619 to /sys/fs/cgroup/stune/foreground/tasy
[   26.335767] init: Service 'logd-reinit' (pid 1614) exited with status 0
[   26.335903] init: Service 'watchdogd' (pid 1616) exited with status 1
[   26.339344] init: Starting service 'zygote'...
[   26.340527] init: Starting service 'zygote_secondary'...
[   26.341610] init: couldn't write 1620 to /sys/fs/cgroup/stune/foreground/tasy
[   26.345519] type=1400 audit(1262304023.280:31): avc: denied { write } for pi1
[   26.346261] init: Starting service 'console'...
[   26.347388] init: cannot find '/system/bin/update_verifier' (No such file or'
[   26.347467] init: cannot find '/system/bin/install-recovery.sh' (No such fil'
[   26.348119] init: Starting service 'audioserver'...
[   26.349610] init: Starting service 'cameraserver'...
[   26.350940] init: Starting service 'drm'...
[   26.354526] init: Starting service 'installd'...
[   26.357339] init: Starting service 'keystore'...
[   26.358704] init: Starting service 'mediacodec'...
[   26.361170] init: Starting service 'mediadrm'...
[   26.362736] init: Starting service 'mediaextractor'...
[   26.364287] init: Starting service 'media'...
[   26.365687] init: Starting service 'netd'...
[   26.366955] init: Starting service 'ril-daemon'...
[   26.368246] init: Starting service 'gatekeeperd'...
[   27.157115] type=1400 audit(1262304024.100:32): avc: denied { write } for pi1
[   27.181587] type=1400 audit(1262304024.100:33): avc: denied { open } for pid1
[   27.264991] healthd: BatteryFullChargePath not found
[   27.270640] healthd: BatteryCycleCountPath not found
[   27.406220] init: Starting service 'perfprofd'...
[   27.426174] android_usb: already disabled
[   27.431164] init: Starting service 'adbd'...
[   27.444850] adb_open
[   27.447257] mtp_bind_config
[   27.450318] gadget_is_softwinner_otg is not -int
[   27.455432] gadget_is_softwinner_otg is not -int
[   27.460493] [sw_udc]: alloc request: ep(0xffffffc000ac98b8, ep1in-bulk, 512))
[   27.470684] [sw_udc]: alloc request: ep(0xffffffc000ac98b8, ep1in-bulk, 512))
[   27.480862] [sw_udc]: alloc request: ep(0xffffffc000ac98b8, ep1in-bulk, 512))
[   27.494015] [sw_udc]: alloc request: ep(0xffffffc000ac98b8, ep1in-bulk, 512))
[   27.504472] [sw_udc]: alloc request: ep(0xffffffc000ac9938, ep1out-bulk, 512)
[   27.532447] [sw_udc]: alloc request: ep(0xffffffc000ac9938, ep1out-bulk, 512)
[   27.561907] [sw_udc]: alloc request: ep(0xffffffc000ac9b38, ep4-int, 512), r)
tulip-chiphd:/ $ [   27.585060] [sw_udc]: alloc request: ep(0xffffffc000ac9b38,)
[   27.608100] [sw_udc]: alloc request: ep(0xffffffc000ac9b38, ep4-int, 512), r)
[   27.618122] [sw_udc]: alloc request: ep(0xffffffc000ac9b38, ep4-int, 512), r)
[   27.628058] [sw_udc]: alloc request: ep(0xffffffc000ac9b38, ep4-int, 512), r)
[   27.638024] adb_bind_config
[   27.641114] [sw_udc]: alloc request: ep(0xffffffc000ac9a38, ep2out-bulk, 512)
[   27.651418] [sw_udc]: alloc request: ep(0xffffffc000ac99b8, ep2in-bulk, 512))
[   27.661622] [sw_udc]: alloc request: ep(0xffffffc000ac99b8, ep2in-bulk, 512))
[   27.680252] [sw_udc]: alloc request: ep(0xffffffc000ac99b8, ep2in-bulk, 512))
[   27.699674] [sw_udc]: alloc request: ep(0xffffffc000ac99b8, ep2in-bulk, 512))
[   27.729143] [sw_udc]: sunxi_udc_pullup, is_on = 1
[   27.734323] [sw_udc]: sunxi_udc_set_pullup_2337: usb device is not active
[   28.735849] [DISP] disp_ioctl,line:1612:para err in disp_ioctl, cmd = 0xb,sc0
[   28.752669] type=1400 audit(1262304025.720:34): avc: denied { write } for pi1
[   28.775871] type=1400 audit(1262304025.730:35): avc: denied { open } for pid1
[   28.902146] type=1400 audit(1262304025.880:36): avc: denied { write } for pi1
[   28.926842] type=1400 audit(1262304025.900:37): avc: denied { open } for pid1
[   29.025712] type=1400 audit(1262304026.000:38): avc: denied { write } for pi1
[   29.048849] type=1400 audit(1262304026.000:39): avc: denied { open } for pid1
[   31.319745] init: Starting service 'bootanim'...
[   32.131185] type=1400 audit(1262304029.160:40): avc: denied { write } for pi1
[   32.154379] type=1400 audit(1262304029.160:41): avc: denied { open } for pid1
[   34.948016] alloc_contig_range test_pages_isolated(9f96c, 9fbc4) failed
[   48.849981] warning: `main' uses 32-bit capabilities (legacy support in use)
[   50.636137] type=1400 audit(1262304047.960:42): avc: denied { sys_nice } for1
[   86.304386] healthd: battery none chg=a
[   88.929421] type=1400 audit(1262304086.880:43): avc: denied { dac_override }1
[   88.930592] healthd: battery none chg=a
[   91.162515] type=1400 audit(1262304089.150:44): avc: denied { write } for pi1
[   91.184490] type=1400 audit(1262304089.150:45): avc: denied { open } for pid1
[  126.011087] mmc0:mmc_do_erase: erase from 4362816 to 4599807 arg 0x00000000
[  126.070082] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  126.099618] mmc0:mmc_do_erase: erase from 4600208 to 4861951 arg 0x00000000
[  126.178320] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 4 ms*
[  126.207892] mmc0:mmc_do_erase: erase from 4894720 to 5124095 arg 0x00000000
[  126.267033] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  126.286612] mmc0:mmc_do_erase: erase from 5124488 to 5386239 arg 0x00000000
[  126.365268] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 4 ms*
[  126.394866] mmc0:mmc_do_erase: erase from 5386240 to 5648383 arg 0x00000000
[  126.453817] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  126.512936] mmc0:mmc_do_erase: erase from 5648776 to 5910527 arg 0x00000000
[  126.571949] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  126.578656] mmc0:mmc_do_erase: erase from 5978688 to 6172671 arg 0x00000000
[  126.640808] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  126.719557] mmc0:mmc_do_erase: erase from 6250496 to 6434807 arg 0x00000000
[  126.758883] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 2 ms*
[  126.876972] mmc0:mmc_do_erase: erase from 6469208 to 6484023 arg 0x00000000
[  126.916331] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 2 ms*
[  126.924766] mmc0:mmc_do_erase: erase from 6494544 to 6533119 arg 0x00000000
[  126.965503] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 2 ms*
[  126.975402] mmc0:mmc_do_erase: erase from 6545896 to 6557687 arg 0x00000000
[  126.995071] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 1 ms*
[  127.004909] mmc0:mmc_do_erase: erase from 6620904 to 6696959 arg 0x00000000
[  127.044268] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 2 ms*
[  127.063979] mmc0:mmc_do_erase: erase from 6697480 to 6959103 arg 0x00000000
[  127.122956] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  127.132820] mmc0:mmc_do_erase: erase from 7024640 to 7221247 arg 0x00000000
[  127.191819] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  127.201762] mmc0:mmc_do_erase: erase from 7221768 to 7483391 arg 0x00000000
[  127.260746] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  127.270680] mmc0:mmc_do_erase: erase from 7483392 to 7745535 arg 0x00000000
[  127.329587] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  127.349310] mmc0:mmc_do_erase: erase from 7746056 to 8007679 arg 0x00000000
[  127.408344] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  127.428060] mmc0:mmc_do_erase: erase from 8007680 to 8269823 arg 0x00000000
[  127.487038] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  127.506851] mmc0:mmc_do_erase: erase from 8270344 to 8531967 arg 0x00000000
[  127.585470] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 4 ms*
[  127.605190] mmc0:mmc_do_erase: erase from 8531968 to 8794111 arg 0x00000000
[  127.664159] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  127.703604] mmc0:mmc_do_erase: erase from 8794112 to 9056255 arg 0x00000000
[  127.801958] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 5 ms*
[  127.831491] mmc0:mmc_do_erase: erase from 9056256 to 9318399 arg 0x00000000
[  127.949546] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 6 ms*
[  128.018448] mmc0:mmc_do_erase: erase from 9318400 to 9580543 arg 0x00000000
[  128.077465] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  128.116653] acc_open
[  128.119102] acc_release
[  128.126693] mmc0:mmc_do_erase: erase from 9580544 to 9842687 arg 0x00000000
[  128.185679] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  128.225104] mmc0:mmc_do_erase: erase from 9842688 to 10104831 arg 0x00000000
[  128.284105] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  128.296000] mmc0:mmc_do_erase: erase from 10172248 to 10366975 arg 0x00000000
[  128.343148] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 2 ms*
[  128.362875] mmc0:mmc_do_erase: erase from 10367000 to 10629119 arg 0x00000000
[  128.421833] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  128.431705] mmc0:mmc_do_erase: erase from 10629120 to 10891263 arg 0x00000000
[  128.480911] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 2 ms*
[  128.500612] mmc0:mmc_do_erase: erase from 10891264 to 11153407 arg 0x00000000
[  128.559621] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  128.638338] mmc0:mmc_do_erase: erase from 11153408 to 11415551 arg 0x00000000
[  128.697342] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  128.707303] mmc0:mmc_do_erase: erase from 11415552 to 11677695 arg 0x00000000
[  128.707640] type=1400 audit(1262304127.310:46): avc: denied { read write } f1
[  128.707761] type=1400 audit(1262304127.310:47): avc: denied { open } for pid1
[  128.707940] type=1400 audit(1262304127.310:48): avc: denied { ioctl } for pi1
[  128.785108] HDMI hdmi_cec_thread started
[  128.788912] [HDMI_CEC] set logical_address=15
[  128.844947] hdmi_cec_finish_send: msg_len=1 tx_answer=CEC_TX_NACK
[  128.844954] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  128.884359] mmc0:mmc_do_erase: erase from 11677696 to 11939839 arg 0x00000000
[  128.894148] hdmi_cec_finish_send: msg_len=1 tx_answer=CEC_TX_NACK
[  128.933509] hdmi_cec_finish_send: msg_len=1 tx_answer=CEC_TX_NACK
[  128.943503] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  128.963099] mmc0:mmc_do_erase: erase from 11939840 to 12201983 arg 0x00000000
[  129.022102] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  129.189391] mmc0:mmc_do_erase: erase from 12201984 to 12464127 arg 0x00000000
[  129.248394] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  129.277975] mmc0:mmc_do_erase: erase from 12464648 to 12726271 arg 0x00000000
[  129.336958] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  129.366506] mmc0:mmc_do_erase: erase from 12726272 to 12988415 arg 0x00000000
[  129.425506] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  129.435419] mmc0:mmc_do_erase: erase from 12988936 to 13250559 arg 0x00000000
[  129.494391] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  129.500913] mmc0:mmc_do_erase: erase from 13250560 to 13512703 arg 0x00000000
[  129.563281] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  129.569664] mmc0:mmc_do_erase: erase from 13512704 to 13774847 arg 0x00000000
[  129.651863] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 4 ms*
[  129.655040] libphy: 1c30000.eth: probed
[  129.662703] mmc0:mmc_do_erase: erase from 13774848 to 14036991 arg 0x00000000
[  129.691368] sunxi-gmac 1c30000.eth eth0: eth0: PHY ID 001cc915 at 0 IRQ poll)
[  129.740401] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 4 ms*
[  129.760308] mmc0:mmc_do_erase: erase from 14036992 to 14299135 arg 0x00000000
[  129.828955] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  130.025824] mmc0:mmc_do_erase: erase from 14319872 to 14561279 arg 0x00000000
[  130.038306] RTL871X: module init start
[  130.042406] RTL871X: rtl8723bs v4.3.16_13854.20150410_BTCOEX20150119-5844
[  130.050446] RTL871X: build time: Oct  5 2016 12:09:30
[  130.056150] RTL871X: rtl8723bs BT-Coex version = BTCOEX20150119-5844
[  130.063248] sunxi-wlan wlan.28: bus_index: 1
[  130.068378] sunxi-wlan wlan.28: check wlan io_regulator voltage: 1800000
[  130.084877] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  130.091951] mmc0:mmc_do_erase: erase from 14561280 to 14823423 arg 0x00000000
[  130.153769] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 3 ms*
[  130.160186] mmc0:mmc_do_erase: erase from 14823424 to 15085567 arg 0x00000000
[  130.185731] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 0Hz bm PP pm UP vdd 21B
[  130.197377] sunxi-mmc 1c10000.sdmmc: no vqmmc,Check if there is regulator
[  130.198657] RTL871X: module init ret=0
[  130.212751] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 2 ms*
[  130.219763] mmc0:mmc_do_erase: erase from 15085568 to 15347711 arg 0x00000000
[  130.222577] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[  130.243018] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 52, RTO !!
[  130.250500] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 52, RTO !!
[  130.257876] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[  130.271744] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 2 ms*
[  130.274148] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[  130.275977] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 8, RTO !!
[  130.276790] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  130.277751] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  130.278557] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  130.279361] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  130.280175] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  130.281991] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  130.282806] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  130.283613] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  130.283631] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm OD pm ON vB
[  130.284500] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 1, RTO !!
[  130.284515] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 0Hz bm OD pm OFF vdd 0B
[  130.389920] mmc0:mmc_do_erase: erase from 15347712 to 15523839 arg 0x00000000
[  130.429207] sunxi-mmc 1c0f000.sdmmc: *All wait r1 rdy 2 ms*
[  130.438710] init: Starting service 'p2p_supplicant'...
[  131.013811] SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
[  131.033884] SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
[  131.049436] SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
[  131.151442] init: Service 'p2p_supplicant' (pid 7712) exited with status 255
[  132.991826] type=1400 audit(1262304131.660:49): avc: denied { read } for pid1
[  133.015264] type=1400 audit(1262304131.660:50): avc: denied { open } for pid1
[  133.492375] type=1401 audit(1262304132.170:51): SELinux: unrecognized netlin2
[  133.492375] 
[  133.526047] type=1401 audit(1262304132.170:52): SELinux: unrecognized netlin2
[  133.526047] 
[  133.935566] type=1400 audit(1262304132.620:53): avc: denied { ioctl } for pi1
[  133.935719] [HDMI_CEC] set logical_address=4
[  134.099570] hdmi_cec_finish_send: msg_len=5 tx_answer=CEC_TX_DONE
[  134.247591] hdmi_cec_finish_send: msg_len=5 tx_answer=CEC_TX_DONE
[  134.611437] libphy: 1c30000.eth-0:00 - Link is Up - 1000/Full
[  134.642470] type=1401 audit(1262304133.330:54): SELinux: unrecognized netlin2
[  134.642470] 
[  134.815713] sunxi-bt bt.29: block state already is 1
[  135.019427] sunxi-bt bt.29: set block: 0
[  135.024794] sunxi-bt bt.29: check bluetooth io_regulator voltage: 1800000
[  135.087115] alloc_contig_range test_pages_isolated(a0445, a069d) failed
[  136.229713] alloc_contig_range test_pages_isolated(9ff94, a01bc) failed
[  139.967142] sunxi-bt bt.29: set block: 1
[  140.169873] sunxi-bt bt.29: set block: 0
[  140.174377] sunxi-bt bt.29: check bluetooth io_regulator voltage: 1800000
[  142.338281] init: Service 'bootanim' (pid 1896) exited with status 0
[  142.518689] usbcore: registered new interface driver uvcvideo
[  142.525480] USB Video Class driver (1.1.1)
[  142.558404] gspca_main: v2.14.0 registered
[  142.563536] init: write_file: Unable to open '/sys/devices/soc.0/cpu_budget_y
[  144.935511] CPU2: shutdown
[  144.938651] psci: CPU2 killed.
[  145.330459] CPU2: Booted secondary processor
[  145.335179] CPU2: update cpu_power 1968128
[  145.344358] healthd: battery none chg=a
[  145.528679] RTL871X: module exit start
[  145.533364] sunxi-wlan wlan.28: bus_index: 1
[  145.553300] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 0Hz bm PP pm UP vdd 21B
[  145.573045] sunxi-mmc 1c10000.sdmmc: no vqmmc,Check if there is regulator
[  145.592622] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[  145.622952] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 52, RTO !!
[  145.630418] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 52, RTO !!
[  145.638623] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[  145.652749] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[  145.666047] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 8, RTO !!
[  145.674336] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  145.682156] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  145.689543] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  145.696938] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  145.704941] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  145.712491] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  145.719997] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  145.727528] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  145.734272] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm OD pm ON vB
[  145.746809] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 1, RTO !!
[  145.753727] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 0Hz bm OD pm OFF vdd 0B
[  145.996088] RTL871X: module exit success
[  146.754020] sunxi-bt bt.29: set block: 1
[  146.902633] CPU2: shutdown
[  146.905640] psci: CPU2 killed.
[  146.974514] sunxi-bt bt.29: set block: 0
[  146.978987] sunxi-bt bt.29: check bluetooth io_regulator voltage: 1800000
[  147.692222] CPU2: Booted secondary processor
[  147.696936] CPU2: update cpu_power 1968128
[  149.265073] CPU3: shutdown
[  149.268130] psci: CPU3 killed.
[  150.053654] CPU3: Booted secondary processor
[  150.058347] CPU3: update cpu_power 1968128
[  150.281166] RTL871X: module init start
[  150.285266] RTL871X: rtl8723bs v4.3.16_13854.20150410_BTCOEX20150119-5844
[  150.294319] RTL871X: build time: Oct  5 2016 12:09:30
[  150.299918] RTL871X: rtl8723bs BT-Coex version = BTCOEX20150119-5844
[  150.306967] sunxi-wlan wlan.28: bus_index: 1
[  150.311946] sunxi-wlan wlan.28: check wlan io_regulator voltage: 1800000
[  150.428582] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 0Hz bm PP pm UP vdd 21B
[  150.439952] RTL871X: module init ret=0
[  150.440037] sunxi-mmc 1c10000.sdmmc: no vqmmc,Check if there is regulator
[  150.453640] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[  150.466730] init: Starting service 'p2p_supplicant'...
[  150.493832] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 52, RTO !!
[  150.501643] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 52, RTO !!
[  150.508337] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[  150.524899] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[  150.539803] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 8, RTO !!
[  150.547211] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  150.554675] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  150.562047] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  150.569865] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  150.577308] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  150.584874] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  150.592342] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  150.599802] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  150.606515] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm OD pm ON vB
[  150.619112] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 1, RTO !!
[  150.625816] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 0Hz bm OD pm OFF vdd 0B
[  150.646014] init: Service 'p2p_supplicant' (pid 9722) exited with status 255
[  151.625811] CPU3: shutdown
[  151.628802] psci: CPU3 killed.
[  152.809106] CPU3: Booted secondary processor
[  152.813856] CPU3: update cpu_power 1968128
[  155.562570] CPU3: shutdown
[  155.565539] psci: CPU3 killed.
[  155.760886] CPU3: Booted secondary processor
[  155.765602] CPU3: update cpu_power 1968128
[  156.841684] sunxi-bt bt.29: set block: 1
[  157.045894] sunxi-bt bt.29: set block: 0
[  157.051059] sunxi-bt bt.29: check bluetooth io_regulator voltage: 1800000
[  157.332975] CPU3: shutdown
[  157.335944] psci: CPU3 killed.
[  157.728941] CPU3: Booted secondary processor
[  157.733647] CPU3: update cpu_power 1968128
[  159.300884] CPU3: shutdown
[  159.303865] psci: CPU3 killed.
[  159.894325] CPU3: Booted secondary processor
[  159.899061] CPU3: update cpu_power 1968128
[  161.860728] CPU3: shutdown
[  161.864427] psci: CPU3 killed.
[  162.279727] sunxi-bt bt.29: set block: 1
[  162.482850] sunxi-bt bt.29: set block: 0
[  162.487348] sunxi-bt bt.29: check bluetooth io_regulator voltage: 1800000
[  162.845860] CPU3: Booted secondary processor
[  162.850587] CPU3: update cpu_power 1968128
[  164.417715] CPU3: shutdown
[  164.421418] psci: CPU3 killed.
[  164.617143] CPU3: Booted secondary processor
[  164.621912] CPU3: update cpu_power 1968128
[  165.509531] type=1400 audit(1475757529.794:55): avc: denied { write } for pi1
[  165.533045] type=1400 audit(1475757529.794:56): avc: denied { open } for pid1
[  165.589718] RTL871X: module exit start
[  165.594352] sunxi-wlan wlan.28: bus_index: 1
[  165.599899] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 0Hz bm PP pm UP vdd 21B
[  165.611116] sunxi-mmc 1c10000.sdmmc: no vqmmc,Check if there is regulator
[  165.636743] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[  165.667086] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 52, RTO !!
[  165.674661] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 52, RTO !!
[  165.681343] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[  165.695766] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[  165.709459] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 8, RTO !!
[  165.717062] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  165.724464] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  165.731910] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  165.739345] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  165.746776] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  165.754316] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  165.761810] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  165.769343] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  165.776073] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm OD pm ON vB
[  165.788949] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 1, RTO !!
[  165.795566] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 0Hz bm OD pm OFF vdd 0B
[  166.099328] RTL871X: module exit success
[  166.188964] CPU3: shutdown
[  166.192883] psci: CPU3 killed.
[  166.781651] CPU3: Booted secondary processor
[  166.786356] CPU3: update cpu_power 1968128
[  167.419312] sunxi-bt bt.29: set block: 1
[  167.622054] sunxi-bt bt.29: set block: 0
[  167.629393] sunxi-bt bt.29: check bluetooth io_regulator voltage: 1800000
[  169.140949] CPU3: shutdown
[  169.143931] psci: CPU3 killed.
[  169.341251] CPU3: Booted secondary processor
[  169.345975] CPU3: update cpu_power 1968128
[  170.348369] RTL871X: module init start
[  170.352549] RTL871X: rtl8723bs v4.3.16_13854.20150410_BTCOEX20150119-5844
[  170.360142] RTL871X: build time: Oct  5 2016 12:09:30
[  170.366448] RTL871X: rtl8723bs BT-Coex version = BTCOEX20150119-5844
[  170.373858] sunxi-wlan wlan.28: bus_index: 1
[  170.378776] sunxi-wlan wlan.28: check wlan io_regulator voltage: 1800000
[  170.499956] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 0Hz bm PP pm UP vdd 21B
[  170.501019] RTL871X: module init ret=0
[  170.516486] sunxi-mmc 1c10000.sdmmc: no vqmmc,Check if there is regulator
[  170.524889] init: Starting service 'p2p_supplicant'...
[  170.546906] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[  170.577227] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 52, RTO !!
[  170.585089] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 52, RTO !!
[  170.591777] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[  170.605943] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vB
[  170.619406] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 8, RTO !!
[  170.623623] init: Service 'p2p_supplicant' (pid 11414) exited with status 255
[  170.634610] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  170.642022] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  170.649446] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  170.656849] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RTO !!
[  170.664369] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  170.671870] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  170.679370] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  170.686856] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RTO !!
[  170.693568] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 400000Hz bm OD pm ON vB
[  170.707281] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 1, RTO !!
[  170.713960] sunxi-mmc 1c10000.sdmmc: sdc set ios: clk 0Hz bm OD pm OFF vdd 0B
[  171.108968] CPU3: shutdown
[  171.112154] psci: CPU3 killed.
[  172.695959] sunxi-bt bt.29: set block: 1
[  172.899510] sunxi-bt bt.29: set block: 0
[  172.904019] sunxi-bt bt.29: check bluetooth io_regulator voltage: 1800000
[  174.063500] CPU3: Booted secondary processor
[  174.068238] CPU3: update cpu_power 1968128
[  175.832202] CPU3: shutdown
[  175.835182] psci: CPU3 killed. 

 

 

 

Edit: Due to lack of time I only tested shortly with the LCD and maybe I suffered from bad PSU or anything else.

Link to comment
Share on other sites

  • 0

Also received a replacement board, but same basic problems with GbE, so unfortunately no further help from my side possible

 

Please get back to TL Lim and ask what to do. I can send you one of the working boards but need it here for some time to do a few tests before.

 

They really should start with a quick QA round at least for the replacement boards (they sent 4 boards out to us and 2 are defective -- huh?). But it seems they really don't care that much about what's happening...

 

BTW: Had a short look into pine64 forums after weeks. Unbelievable that a specific person is still moderator and now tries to tell @ssvb about Mali -- too funny (if I would ever have a question regarding Mali I would always ask Siarhei first)

Link to comment
Share on other sites

  • 0

For me this is fine, will be in hospital till beginning of November, so don't need a new board till that time.

 

Will also check with tllim the next steps, but it seems they didn't even test those boards they sent out and still they have no real idea whats wrong with their boards....

 

Its a real pain board.

Link to comment
Share on other sites

  • 0

Its a real pain board.

 

Well, a few hardware flaws (shitty Micro USB, no custom led, the GbE issue, the HDMI drama, now the LCD mess) combined with pretty careless after-sales behaviour (still no real 'getting started guide', moderators enabled to act as censors, no wiki updates, a clueless 'moderator elite' responsible for the moronic Mali hype, no QA at least for hardware replacements and so on) and Pine64 turns into Pain64. Everything as expected ;)

 

BTW: this poor guy here also suffers from the GbE issue and now the PoE adapter (from Pine64 only capable of Fast Ethernet) masks the symptoms: http://forum.pine64.org/showthread.php?tid=1068&pid=20973#pid20973(and now the poor guy buys a new PSU for no reason or let's say it more clear: since the forum over there and documentation of well known issues still so much sucks)

 

Get well soon!

Link to comment
Share on other sites

  • 0

tkaiser, I have to ask, what HDMI drama?

 

Please see post #1 here or N°4 there. Given the similarities of HDMI drivers in H3 and A64 BSP I still wonder why there were so many issues with no display output at all but maybe that's just because the majority of Pine64 users had no idea about the SBC concept at all or simply believed in the marketing claims to get a '$15 supercomputer'?

Link to comment
Share on other sites

  • 0

If I understand correctly, those issues also exists on H3, due to same HDMI IP and basically the same driver code?

 

From my experience, A64 HDMI blob can be reproduced from H3 HDMI source + one function, which I published in OrangePi forum. So if anyone would like to play with it, it's possible, but license issues still remain. Currently I'm trying to port most HDMI patches from linux-sunxi repo to H3 kernel with some of my own fixes, so EDID negotiation and non 16:9 resolutions would be possible. It will take some time, though. I imagine that it would solve most of those issues?

Link to comment
Share on other sites

  • 0

It will take some time, though. I imagine that it would solve most of those issues?

 

To be honest: while testing with A64 a few hundred hours (unattended of course) I might have connected a display to the Pine64+ I had here maybe one or two times. IIRC I tried out whether the HDMI-to-DVI fixes known from A83T and H3 also match with A64 BSP kernel.

 

So I'm definitely the wrong person to ask for display issues. But I highly appreciate that you look into. It can't be overestimated what you've done for H3 already. Do you have access to A64 hardware already?

Link to comment
Share on other sites

  • 0

Do you have access to A64 hardware already?

 

No, I was thinking about buying it, but then I said to myself that I should concentrate on one platform and try to squeeze the max. One very unatractive feature of A64 is U-Boot. I started to hate BSP U-Boot as soon as I integrated it first time in OpenELEC. While there is some mainline support for A64, AFAIK it is not meant to boot BSP kernel. I guess some work would be needed for that. Second issue is mali driver, but probably it is also solvable.

 

However, I'm looking forward for H5, despite high probability of above issues.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...