29 879
modifications
Modifications
Sauter à la navigation
Sauter à la recherche
Ligne 1 :
Ligne 1 : − + − + − We ran several benchmarks to measure the computing power on the XU4. The same tests were performed on the Raspberry Pi 2 Model B, ODROID-C1, ODROID-U3 and ODROID-XU4.+ − The values of the test results were scaled uniformly for comparison purposes. The computing power of the XU4 was measured to be ~3-4 times faster than the latest Raspberry Pi 2 thanks to the 2Ghz Cortex-A15 cores and much higher memory bandwidth. Using the XU4 as a computer provides a "desktop like" experience, unlike the sluggish performance of most single-board computers!+ − Particularly for developers, compiling code on the XU4 is about 3 to 4 times faster. The high-performance 2GB DDR3 RAM is an additional advantage allowing most programs to be compiled directly on the XU4.+ Ligne 12 :
Ligne 12 : − + Ligne 48 :
Ligne 48 : − + Ligne 55 :
Ligne 55 : − + + + Ligne 65 :
Ligne 67 : − Write command: dd if=/dev/zero of=test oflag=direct bs=8M count=64+ − Read command: dd if=test of=/dev/null iflag=direct bs=8M+ − Following eMMC 5.0 test was done with 16GB model (8GB model is slower than 16GB).+ Ligne 78 :
Ligne 80 : − + − + Ligne 89 :
Ligne 91 : − + + − The XU4 has two standard-sized USB 3.0 SuperSpeed host ports.+ − To measure the USB 3.0 performance, we connected an SSD via a USB-SATA bridge. We used the Toshiba SSD HDT312 128GB model for this test. − + Ligne 100 :
Ligne 102 : − + − + − + Ligne 113 :
Ligne 115 : − + − Thanks to the advanced technology of the RTL8153 controller, the XU4's Ethernet controller easily outperforms the connectivity solutions of prior generations.+ − + Ligne 126 :
Ligne 128 : − + − + − + − + Ligne 142 :
Ligne 144 : − + − These days, network storage applications like NAS and cloud services are popular. We ran the famous OMV (Open Media Vault) OS on the XU4 to measure network storage performance.+ − An SSD was connected to the XU4 via a USB 3.0 to SATA bridge. The Gigabit Ethernet port was connected to a Windows 8 PC via a simple switching hub. − We sent a big 1.6GB file from the XU4 to the PC via a Samba connection. This resulted in a download speed of ~75-85MB/sec.+ − The upload speed was measured at ~70MB/sec. Even though this performance is great, we are working on optimizing it even further. − The XU4 is a great solution to make a DIY personal cloud storage server!+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ODroid-XU4-Performance (voir la source)
Version du 7 novembre 2016 à 11:56
, 7 novembre 2016 à 11:56→Performance USB 3.0
{{traduction}}
{{MCH-Aider}}
== CPU/RAM PERFORMANCE ==
== Performance CPU/RAM ==
HardKernel à réalisé plusieurs banc d'essais (benchmarks) pour mesurer la puissance de traitement du XU4. Les mêmes tests ont étés réalisés sur un Rapsberry-Pi 2 Modèle B, ODROID-C1, ODROID-U3 et ODROID-XU4.
Les valeurs des différents test ont étés mis-à-l'échelle pour permettre une comparaison unforme. La puissance de traitement d'un XU4 à été mesuré comme étant 3 à 4 fois plus rapide que le Raspberry Pi 2 (grâce aux coeurs Cortex-A15 à 2Ghz et à la plus grande bande passante de la mémoire). Avec le XU4, vous pouvez créer un nano ordinateur offrant une expérience "bureaux PC" confortable par rapport aux autres ordinateurs mono-carte!
Plus particulièrement, les développeurs apprécierons les performances 3 à 4 fois supérieurs lors de phase de compilation. La haute-performance des 2GB de RAM DDR3 est un avantage complémentaire permettant à la plupart des programmes d'être compilés directement sur le XU4.
[[Fichier:ODroid-XU4-Performance-01.jpg]]
[[Fichier:ODroid-XU4-Performance-01.jpg]]
{| class="wikitable" border="1"
{| class="wikitable" border="1"
|-
|-
| align="center" | Benchmarks (Index Score)
| align="center" | Benchmarks (Index du Score)
| align="center" | Raspberry Pi 2
| align="center" | Raspberry Pi 2
| align="center" | ODROID-C1
| align="center" | ODROID-C1
| align="left" | 2891.8
| align="left" | 2891.8
|- style="font-size: 90%"
|- style="font-size: 90%"
| align="left" | Memory BandWidth (mbw 100: MiB/s)
| align="left" | Bande passante mémoire (mbw 100: MiB/s)
| align="left" | 557.1
| align="left" | 557.1
| align="left" | 1069.6
| align="left" | 1069.6
|}
|}
== CPU/RAM PERFORMANCE ==
== Performance SD/eMMC ==
Vous pouvez booter depuis une carte microSD ou un module mémoire eMMC. L'interface MicroSD supporte les performances supérieures du mode UHS-1.
Vous pouvez booter depuis une carte microSD ou un module mémoire eMMC. L'interface MicroSD supporte les performances supérieures du mode UHS-1.
Vous trouverez ci-dessous les performances d'accès pour un fichier de 512MB en lecture/écriture pour les 3 supports de stockage.
Vous trouverez ci-dessous les performances d'accès pour un fichier de 512MB en lecture/écriture pour les 3 supports de stockage.
Le stockage sur eMMC 5.0 est environ 7x plus performant qu'une carte Class-10 durant le test de lecture.
Le stockage sur eMMC 5.0 est environ 7x plus performant qu'une carte Class-10 durant le test de lecture.
La carte MicroSD UHS-1 est environ 2x plus rapide qu'une MicroSD Class-10 (en test de lecture).
La carte MicroSD UHS-1 est environ 2x plus rapide qu'une MicroSD Class-10 (en test de lecture).
[[Fichier:ODroid-XU4-Performance-02.jpg]]
[[Fichier:ODroid-XU4-Performance-02.jpg]]
Commande d'écriture: dd if=/dev/zero of=test oflag=direct bs=8M count=64
Commande de lecture: dd if=test of=/dev/null iflag=direct bs=8M
Ci-dessous, les tests réalisés sur une eMMC 5.0 de 16GB (les modèles 8GB sont plus lent que les modèles 16GB).
{| class="wikitable" border="1"
{| class="wikitable" border="1"
| align="center" | eMMC 5.0
| align="center" | eMMC 5.0
|- style="font-size: 90%"
|- style="font-size: 90%"
| align="left" | Write speed (MB/s)
| align="left" | Vitesse d'écriture (MB/s)
| align="left" | 8.5
| align="left" | 8.5
| align="left" | 10.8
| align="left" | 10.8
| align="left" | 39.3
| align="left" | 39.3
|- style="font-size: 90%"
|- style="font-size: 90%"
| align="left" | Read speed (MB/s)
| align="left" | Vitesse de lecture (MB/s)
| align="left" | 18.9
| align="left" | 18.9
| align="left" | 35.9
| align="left" | 35.9
|}
|}
== USB 3.0 PERFORMANCE ==
== Performance USB 3.0 ==
Le XU4 est équipé de 2 port USB 3.0 SuperSpeed (ports Hôte).
Pour mesurer les performances USB , HardKernel à connecté un SSD via une interface USB-SATA. Le disque utilisé est un Toshiba SSD HDT312 128GB.
USB 3.0 read access speed is ~5x faster than USB 2.0 on the XU4!
La vitesse de lecture USB 3.0 est environ 5 fois supérieure à celle d'un port USB 2.0 du XU4!
[[Fichier:ODroid-XU4-Performance-03.jpg]]
[[Fichier:ODroid-XU4-Performance-03.jpg]]
{| class="wikitable" border="1"
{| class="wikitable" border="1"
|-
|-
| align="center" | USB storage performance
| align="center" | Performance du stockage USB
| align="center" | Read SSD(MB/sec)
| align="center" | Lecture SSD(MB/sec)
| align="center" | Write SSD(MB/sec)
| align="center" | Ecriture SSD(MB/sec)
|- style="font-size: 90%"
|- style="font-size: 90%"
| align="left" | USB2.0 HighSpeed
| align="left" | USB2.0 HighSpeed
|}
|}
== ETHERNET PERFORMANCE ==
== Performances Ethernet ==
The XU4 has an on-board Gigabit Ethernet controller. Our bi-directional streaming speed was measured at ~880Mbps.
The XU4 has an on-board Gigabit Ethernet controller. Our bi-directional streaming speed was measured at ~880Mbps.
Grâce à la technologie du contrôleur RTL8153, le contrôleur Ethernet du XU4 offre des solutions de connectivité ultra-performantes par rapport aux précédentes générations.
[[Fichier:ODroid-XU4-Performance-04.jpg]]
[[Fichier:ODroid-XU4-Performance-04.jpg]]
<nowiki>Test command
<nowiki>Commande de test
Server mode : iperf -s
Server mode : iperf -s
Client Mode : iperf -c [ip address] -P 10 -W 32k</nowiki>
Client Mode : iperf -c [ip address] -P 10 -W 32k</nowiki>
{| class="wikitable" border="1"
{| class="wikitable" border="1"
|-
|-
| align="center" | Ethernet performance
| align="center" | Performance Ethernet
| align="center" | XU3 On-board 100Mbps
| align="center" | Interface 100Mbps natif du XU3
| align="center" | XU3 External 1Gbps
| align="center" | Interface 1Gbps externe sur XU3
| align="center" | XU4 On-board 1Gbps
| align="center" | '''Interface 1Gbps natif du XU4'''
|- style="font-size: 90%"
|- style="font-size: 90%"
| align="left" | iperf Server on SBC (Mbit/sec)
| align="left" | iperf Server on SBC (Mbit/sec)
|}
|}
== NETWORK STORAGE PERFORMANCE ==
== Performance du stockage réseau ==
De nos jour, les services de stockage NAS et Cloud sont devenu très populaires. HardKernel à testé le fameux OS OMV (Open Media Vault) sur le XU4 afin de pouvoir mesurer les performances du stockage réseau.
Un disque SSD a été connecté sur le XU4 via le convertisseur USB 3.0 vers SATA. Le port Gigabit Ethernet était connecté sur un PC en Windows 8 par l'intermédiaire d'un Switch.
Le test consiste à envoyer un gros fichier de 1.6 GB depuis le XU4 vers le PC par l'intermédiaire d'une connexion Samba. Le résultat est une vitesse de téléchargement de 75 à 85MB/sec.
La vitesse d'upload (téléversement) est mesurée à ~70MB/sec. Et même si ces performances sont vraiment impressionnantes, HardKernel continue à travailler sur des optimisations encore plus avancées.
Le XU4 est une option de choix pour réaliser son propre serveur de stockage Cloud!
[[Fichier:ODroid-XU4-Performance-05.jpg]]
[[Fichier:ODroid-XU4-Performance-05.jpg]]
== La solution Heterogeneous Multi-Processing (HMP) ==
ODROID-XU4 est équipé de 4 gros coeurs (ARM® Cortex® -A15™ jusqu'à 2.0GHz) et 4 plus petits coeurs (ARM® Cortex® -A7™ jusqu'à 1.4 GHz) offrant un des possibilités de traitement avancés et performant tout en maintenant une consommation d'énergie la plus efficace possible.
La solution HMP de big.LITTLE™, Exynos-5422 peut utiliser le maximum de ses 8 coeurs pour pour gérer de façon optimal les traitements intensifs.
[[Fichier:ODroid-XU4-Performance-06.jpg]]
== OpenGL ES 3.0 et OpenCL 1.1 ==
Ce point concerne OpenGL ES 3.0 et OpenCL 1.1 pour les plateformes Linux et Android.
Le GPU (processeur graphique) ARM® Mali™-T628 MP6 offre les interfaces de programmation (API) clés pour le support de OpenGL ES 1.1, OpenGL ES 2.0 et OpenGL ES 3.0, OpenCL 1.1 (''Full Profile'') et Google RenderScript.
Mali-T628 est un GPU de choix pour les périphériques destinés à dominer la prochaine génération des périphériques embarqués (mobile). Il offre des optimisations permettant de réaliser des interfaces graphiques/utilisateur à couper le souffle. Ses domaines d'applications couvre le gaphique 3D, application graphique, réalité augmentée, génération de texture et reconnaissance vocale.
Vous pouvez télécharger le SDK complet pour OpenGL ES et OpenCL depuis le site développeur de MALI. C'est du libre!
La capture d'écran ci-dessous présente des applications OpenGL-ES et le media player de Kodi sous Ubuntu 15.04 Mate (avec HMP activé dans le noyau 3.10 LTS).
[[Fichier:ODroid-XU4-Performance-07.png|1024px]]
== Boot du noyau Mainline (Expérimentale) ==
La version du noyau 4.2.0 RC1 fonctionne sur le XU4. Voyez le log de démarrage ci-dessous.
Si vous voulez l'essayer, vous pouvez télécharger les sources coded du noyau depuis le Github d'ODroid.
* [https://github.com/hardkernel/linux/commits/odroidxu4-v4.2-rc1 odroidxu4-v4.2-rc1] (ODroid GitHub)
{{ambox-stop|text=Ce support expérimental du noyau 4.2 supporte SMP sur les 4 coeurs A15, USB 3.0, Gigabit Ethernet et quelques fonctionnalités de base.
Par contre HDMI, GPU, VPU(MFC) et HMP ne fonctionnent pas encore. Pour le moment, ce noyau ne sera utile que pour les applications totalement autonomes (sans connexion sur moniteur).
Le système d'exploitation OMV (Open Media Vault) fonctionnera sur la dernière version du noyau.}}
<nowiki>[ 0.000000] Booting Linux on physical CPU 0x100
[ 0.000000] Linux version 4.2.0-rc1+ (tobetter@hkxeon) (gcc version 4.9.2 20140904 (prerelease) (crosstool-NG linaro-1.13.1-4.9-2014.09 - Linaro GCC 4.9-2014.09) ) #4 SMP PREEMPT Fri Jul 10 16:45:24 KST 2015
[ 0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Hardkernel Odroid XU4
[ 0.000000] cma: Reserved 64 MiB at 0xba800000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] Samsung CPU ID: 0xe5422001
[ 0.000000] On node 0 totalpages: 514560
[ 0.000000] free_area_init_node: node 0, pgdat c07f12c0, node_mem_map ee81f000
[ 0.000000] Normal zone: 1520 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 190464 pages, LIFO batch:31
[ 0.000000] HighMem zone: 324096 pages, LIFO batch:31
[ 0.000000] Running under secure firmware.
[ 0.000000] PERCPU: Embedded 11 pages/cpu @ee78f000 s14336 r8192 d22528 u45056
[ 0.000000] pcpu-alloc: s14336 r8192 d22528 u45056 alloc=11*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 513040
[ 0.000000] Kernel command line: console=tty1 console=ttySAC2,115200n8 root=UUID=a4b494db-320a-4ce2-bb3a-841db943f9c0 rootwait ro smsc95xx.macaddr=00:1e:06:61:7a:39
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 1962856K/2058240K available (5506K kernel code, 200K rwdata, 1992K rodata, 404K init, 295K bss, 29848K reserved, 65536K cma-reserved, 1230848K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xf0000000 - 0xff000000 ( 240 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xef800000 ( 760 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc075ad74 (7500 kB)
[ 0.000000] .init : 0xc075b000 - 0xc07c0000 ( 404 kB)
[ 0.000000] .data : 0xc07c0000 - 0xc07f2220 ( 201 kB)
[ 0.000000] .bss : 0xc07f5000 - 0xc083ec6c ( 296 kB)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Additional per-CPU info printed with stalls.
[ 0.000000] Build-time adjustment of leaf fanout to 32.
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] L2C: failed to init: -19
[ 0.000000] Switching to timer-based delay loop, resolution 41ns
[ 0.000000] clocksource: mct-frc: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[ 0.000007] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[ 0.000696] Console: colour dummy device 80x30
[ 0.001447] console [tty1] enabled
[ 0.001491] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=120000)
[ 0.001549] pid_max: default: 32768 minimum: 301
[ 0.001729] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.001767] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.002658] CPU: Testing write buffer coherency: ok
[ 0.003184] CPU0: update cpu_capacity 448
[ 0.003222] CPU0: thread -1, cpu 0, socket 1, mpidr 80000100
[ 0.003491] Setting up static identity map for 0x40008280 - 0x400082d8
[ 0.003865] ARM CCI driver probed
[ 0.004152] Exynos MCPM support installed
[ 0.020519] CPU1: update cpu_capacity 1535
[ 0.020527] CPU1: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.025503] CPU2: update cpu_capacity 1535
[ 0.025510] CPU2: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.030522] CPU3: update cpu_capacity 1535
[ 0.030529] CPU3: thread -1, cpu 2, socket 0, mpidr 80000002
[ 0.035509] CPU4: update cpu_capacity 1535
[ 0.035517] CPU4: thread -1, cpu 3, socket 0, mpidr 80000003
[ 0.040602] CPU5: update cpu_capacity 448
[ 0.040610] CPU5: thread -1, cpu 1, socket 1, mpidr 80000101
[ 0.045599] CPU6: update cpu_capacity 448
[ 0.045607] CPU6: thread -1, cpu 2, socket 1, mpidr 80000102
[ 0.050588] CPU7: update cpu_capacity 448
[ 0.050596] CPU7: thread -1, cpu 3, socket 1, mpidr 80000103
[ 0.050702] Brought up 8 CPUs
[ 0.051039] SMP: Total of 8 processors activated (384.00 BogoMIPS).
[ 0.051072] CPU: WARNING: CPU(s) started in wrong/inconsistent modes (primary CPU mode 0x1a)
[ 0.051115] CPU: This may indicate a broken bootloader or firmware.
[ 0.052135] devtmpfs: initialized
[ 0.080775] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 3
[ 0.082343] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302231375000 ns
[ 0.086012] pinctrl core: initialized pinctrl subsystem
[ 0.086799] regulator-dummy: no parameters
[ 0.087610] NET: Registered protocol family 16
[ 0.089703] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.104988] cpuidle: using governor ladder
[ 0.124978] cpuidle: using governor menu
[ 0.129700] gpiochip_add: registered GPIOs 0 to 7 on device: gpy7
[ 0.129898] gpiochip_add: registered GPIOs 8 to 15 on device: gpx0
[ 0.130131] gpiochip_add: registered GPIOs 16 to 23 on device: gpx1
[ 0.130335] gpiochip_add: registered GPIOs 24 to 31 on device: gpx2
[ 0.130529] gpiochip_add: registered GPIOs 32 to 39 on device: gpx3
[ 0.132024] gpiochip_add: registered GPIOs 40 to 47 on device: gpc0
[ 0.132237] gpiochip_add: registered GPIOs 48 to 55 on device: gpc1
[ 0.132430] gpiochip_add: registered GPIOs 56 to 62 on device: gpc2
[ 0.132628] gpiochip_add: registered GPIOs 63 to 66 on device: gpc3
[ 0.132842] gpiochip_add: registered GPIOs 67 to 68 on device: gpc4
[ 0.133049] gpiochip_add: registered GPIOs 69 to 76 on device: gpd1
[ 0.133243] gpiochip_add: registered GPIOs 77 to 82 on device: gpy0
[ 0.133436] gpiochip_add: registered GPIOs 83 to 86 on device: gpy1
[ 0.133643] gpiochip_add: registered GPIOs 87 to 92 on device: gpy2
[ 0.133839] gpiochip_add: registered GPIOs 93 to 100 on device: gpy3
[ 0.134034] gpiochip_add: registered GPIOs 101 to 108 on device: gpy4
[ 0.134232] gpiochip_add: registered GPIOs 109 to 116 on device: gpy5
[ 0.134439] gpiochip_add: registered GPIOs 117 to 124 on device: gpy6
[ 0.135672] gpiochip_add: registered GPIOs 125 to 132 on device: gpe0
[ 0.135867] gpiochip_add: registered GPIOs 133 to 134 on device: gpe1
[ 0.136055] gpiochip_add: registered GPIOs 135 to 140 on device: gpf0
[ 0.136239] gpiochip_add: registered GPIOs 141 to 148 on device: gpf1
[ 0.136426] gpiochip_add: registered GPIOs 149 to 156 on device: gpg0
[ 0.136615] gpiochip_add: registered GPIOs 157 to 164 on device: gpg1
[ 0.136799] gpiochip_add: registered GPIOs 165 to 166 on device: gpg2
[ 0.136986] gpiochip_add: registered GPIOs 167 to 170 on device: gpj4
[ 0.138109] gpiochip_add: registered GPIOs 171 to 178 on device: gpa0
[ 0.138297] gpiochip_add: registered GPIOs 179 to 184 on device: gpa1
[ 0.138485] gpiochip_add: registered GPIOs 185 to 192 on device: gpa2
[ 0.138679] gpiochip_add: registered GPIOs 193 to 197 on device: gpb0
[ 0.138865] gpiochip_add: registered GPIOs 198 to 202 on device: gpb1
[ 0.139049] gpiochip_add: registered GPIOs 203 to 206 on device: gpb2
[ 0.139232] gpiochip_add: registered GPIOs 207 to 214 on device: gpb3
[ 0.139427] gpiochip_add: registered GPIOs 215 to 216 on device: gpb4
[ 0.139615] gpiochip_add: registered GPIOs 217 to 224 on device: gph0
[ 0.140878] gpiochip_add: registered GPIOs 225 to 231 on device: gpz
[ 0.143298] exynos-audss-clk 3810000.audss-clock-controller:: setup completed
[ 0.152608] EXYNOS5420 PMU initialized
[ 0.194093] SCSI subsystem initialized
[ 0.194706] usbcore: registered new interface driver usbfs
[ 0.194861] usbcore: registered new interface driver hub
[ 0.195150] usbcore: registered new device driver usb
[ 0.196236] s3c-i2c 12c80000.i2c:: slave address 0x00
[ 0.196282] s3c-i2c 12c80000.i2c:: bus frequency set to 65 KHz
[ 0.196935] s3c-i2c 12c80000.i2c:: i2c-2: S3C I2C adapter
[ 0.200745] clocksource: Switched to clocksource mct-frc
[ 0.201244] FS-Cache: Loaded
[ 0.224210] NET: Registered protocol family 2
[ 0.225113] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.225279] TCP bind hash table entries: 8192 (order: 5, 163840 bytes)
[ 0.225691] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.225940] UDP hash table entries: 512 (order: 2, 24576 bytes)
[ 0.226043] UDP-Lite hash table entries: 512 (order: 2, 24576 bytes)
[ 0.226446] NET: Registered protocol family 1
[ 0.226966] RPC: Registered named UNIX socket transport module.
[ 0.227007] RPC: Registered udp transport module.
[ 0.227036] RPC: Registered tcp transport module.
[ 0.227065] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.227430] Trying to unpack rootfs image as initramfs...
[ 0.537926] Freeing initrd memory: 3876K (c2000000 - c23c9000)
[ 0.540696] futex hash table entries: 2048 (order: 5, 131072 bytes)
[ 0.564313] ntfs: driver 2.1.32 [Flags: R/W].
[ 0.565053] romfs: ROMFS MTD (C) 2007 Red Hat, Inc.
[ 0.565411] fuse init (API version 7.23)
[ 0.567241] bounce: pool size: 64 pages
[ 0.567280] io scheduler noop registered
[ 0.567310] io scheduler deadline registered
[ 0.567690] io scheduler cfq registered (default)
[ 0.568071] phy phy-video-phy@10040728:.0: Looking up phy-supply from device tree
[ 0.568087] phy phy-video-phy@10040728:.0: Looking up phy-supply property in node /video-phy@10040728 failed
[ 0.568695] phy phy-video-phy@10040714:.1: Looking up phy-supply from device tree
[ 0.568711] phy phy-video-phy@10040714:.1: Looking up phy-supply property in node /video-phy@10040714 failed
[ 0.568890] phy phy-video-phy@10040714:.2: Looking up phy-supply from device tree
[ 0.568904] phy phy-video-phy@10040714:.2: Looking up phy-supply property in node /video-phy@10040714 failed
[ 0.569067] phy phy-video-phy@10040714:.3: Looking up phy-supply from device tree
[ 0.569081] phy phy-video-phy@10040714:.3: Looking up phy-supply property in node /video-phy@10040714 failed
[ 0.569245] phy phy-video-phy@10040714:.4: Looking up phy-supply from device tree
[ 0.569259] phy phy-video-phy@10040714:.4: Looking up phy-supply property in node /video-phy@10040714 failed
[ 0.570242] phy phy-12130000.phy:.5: Looking up phy-supply from device tree
[ 0.570258] phy phy-12130000.phy:.5: Looking up phy-supply property in node /phy@12130000 failed
[ 0.570435] phy phy-12130000.phy:.6: Looking up phy-supply from device tree
[ 0.570450] phy phy-12130000.phy:.6: Looking up phy-supply property in node /phy@12130000 failed
[ 0.570613] phy phy-12130000.phy:.7: Looking up phy-supply from device tree
[ 0.570627] phy phy-12130000.phy:.7: Looking up phy-supply property in node /phy@12130000 failed
[ 0.570856] phy phy-12130000.phy:.8: Looking up phy-supply from device tree
[ 0.570874] phy phy-12130000.phy:.8: Looking up phy-supply property in node /phy@12130000 failed
[ 0.571623] exynos5_usb3drd_phy 12100000.phy:: Looking up vbus-supply from device tree
[ 0.571639] exynos5_usb3drd_phy 12100000.phy:: Looking up vbus-supply property in node /phy@12100000 failed
[ 0.571651] 12100000.phy: supply vbus not found, using dummy regulator
[ 0.571762] exynos5_usb3drd_phy 12100000.phy:: Looking up vbus-boost-supply from device tree
[ 0.571777] exynos5_usb3drd_phy 12100000.phy:: Looking up vbus-boost-supply property in node /phy@12100000 failed
[ 0.571787] 12100000.phy: supply vbus-boost not found, using dummy regulator
[ 0.571888] phy phy-12100000.phy:.9: Looking up phy-supply from device tree
[ 0.571902] phy phy-12100000.phy:.9: Looking up phy-supply property in node /phy@12100000 failed
[ 0.572089] phy phy-12100000.phy:.10: Looking up phy-supply from device tree
[ 0.572104] phy phy-12100000.phy:.10: Looking up phy-supply property in node /phy@12100000 failed
[ 0.572402] exynos5_usb3drd_phy 12500000.phy:: Looking up vbus-supply from device tree
[ 0.572417] exynos5_usb3drd_phy 12500000.phy:: Looking up vbus-supply property in node /phy@12500000 failed
[ 0.572428] 12500000.phy: supply vbus not found, using dummy regulator
[ 0.572521] exynos5_usb3drd_phy 12500000.phy:: Looking up vbus-boost-supply from device tree
[ 0.572536] exynos5_usb3drd_phy 12500000.phy:: Looking up vbus-boost-supply property in node /phy@12500000 failed
[ 0.572546] 12500000.phy: supply vbus-boost not found, using dummy regulator
[ 0.572645] phy phy-12500000.phy:.11: Looking up phy-supply from device tree
[ 0.572660] phy phy-12500000.phy:.11: Looking up phy-supply property in node /phy@12500000 failed
[ 0.572850] phy phy-12500000.phy:.12: Looking up phy-supply from device tree
[ 0.572864] phy phy-12500000.phy:.12: Looking up phy-supply property in node /phy@12500000 failed
[ 0.578092] dma-pl330 3880000.adma: Loaded driver for PL330 DMAC-241330
[ 0.578128] dma-pl330 3880000.adma: DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6
[ 0.583870] dma-pl330 121a0000.pdma: Loaded driver for PL330 DMAC-241330
[ 0.583905] dma-pl330 121a0000.pdma: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[ 0.589678] dma-pl330 121b0000.pdma: Loaded driver for PL330 DMAC-241330
[ 0.589714] dma-pl330 121b0000.pdma: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[ 0.591378] dma-pl330 10800000.mdma: Loaded driver for PL330 DMAC-241330
[ 0.591413] dma-pl330 10800000.mdma: DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32
[ 0.702141] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 0.704902] 12c00000.serial:: ttySAC0 at MMIO 0x12c00000 (irq = 58, base_baud = 0) is a S3C6400/10
[ 0.705626] 12c10000.serial:: ttySAC1 at MMIO 0x12c10000 (irq = 59, base_baud = 0) is a S3C6400/10
[ 0.706383] 12c20000.serial:: ttySAC2 at MMIO 0x12c20000 (irq = 60, base_baud = 0) is a S3C6400/10
[ 1.434038] console [ttySAC2] enabled
[ 1.438403] 12c30000.serial:: ttySAC3 at MMIO 0x12c30000 (irq = 61, base_baud = 0) is a S3C6400/10
[ 1.448653] [drm] Initialized drm 1.1.0 20060810
[ 1.455635] of_get_named_gpiod_flags: parsed 'hpd-gpio' property of node '/hdmi@14530000[0]' - status (0)
[ 1.455829] exynos-hdmi 14530000.hdmi:: Looking up vdd-supply from device tree
[ 1.455856] exynos-hdmi 14530000.hdmi:: Failed to get supply 'vdd': -517
[ 1.461132] [drm:hdmi_probe] *ERROR* failed to get regulators
[ 1.466837] [drm:hdmi_probe] *ERROR* hdmi_resources_init failed
[ 1.491261] brd: module loaded
[ 1.503212] loop: module loaded
[ 1.507360] exynos-dwc3 usb@12000000:: Looking up vdd33-supply from device tree
[ 1.507937] exynos-dwc3 usb@12400000:: Looking up vdd33-supply from device tree
[ 1.508503] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.513604] ehci-exynos: EHCI EXYNOS driver
[ 1.517993] of_get_named_gpiod_flags: can't parse 'samsung,vbus-gpio' property of node '/usb@12110000[0]'
[ 1.518260] exynos-ehci 12110000.usb:: EHCI Host Controller
[ 1.523378] exynos-ehci 12110000.usb:: new USB bus registered, assigned bus number 1
[ 1.531258] exynos-ehci 12110000.usb:: irq 115, io mem 0x12110000
[ 1.545805] exynos-ehci 12110000.usb:: USB 2.0 started, EHCI 1.00
[ 1.550662] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.557221] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.564423] usb usb1: Product: EHCI Host Controller
[ 1.569260] usb usb1: Manufacturer: Linux 4.2.0-rc1+ ehci_hcd
[ 1.574985] usb usb1: SerialNumber: 12110000.usb:
[ 1.580689] hub 1-0:1.0: USB hub found
[ 1.583428] hub 1-0:1.0: 3 ports detected
[ 1.588474] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.593555] ohci-exynos: OHCI EXYNOS driver
[ 1.598048] exynos-ohci 12120000.usb:: USB Host Controller
[ 1.603185] exynos-ohci 12120000.usb:: new USB bus registered, assigned bus number 2
[ 1.611003] exynos-ohci 12120000.usb:: irq 115, io mem 0x12120000
[ 1.675022] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.680378] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.688108] usb usb2: Product: USB Host Controller
[ 1.692332] usb usb2: Manufacturer: Linux 4.2.0-rc1+ ohci_hcd
[ 1.698049] usb usb2: SerialNumber: 12120000.usb:
[ 1.703692] hub 2-0:1.0: USB hub found
[ 1.706495] hub 2-0:1.0: 3 ports detected
[ 1.712062] mousedev: PS/2 mouse device common for all mice
[ 1.717695] s3c-rtc 101e0000.rtc:: failed to find rtc source clock
[ 1.723006] i2c /dev entries driver
[ 1.731283] vdd_ldo1: 1000 mV
[ 1.732496] LDO2: at 1800 mV
[ 1.734168] vdd_ldo3: 1800 mV
[ 1.735379] LDO4: at 1800 mV
[ 1.737158] vdd_ldo5: 1800 mV
[ 1.738937] vdd_ldo6: 1000 mV
[ 1.740711] vdd_ldo7: 1800 mV
[ 1.742531] vdd_ldo8: 1800 mV
[ 1.744305] vdd_ldo9: 3000 mV
[ 1.746082] vdd_ldo10: 1800 mV
[ 1.747865] vdd_ldo11: 1000 mV
[ 1.749637] vdd_ldo12: 1800 mV
[ 1.753198] vdd_ldo13: ramp_delay not set
[ 1.756267] vdd_ldo13: 2800 mV
[ 1.757544] LDO14: at 3000 mV
[ 1.759317] vdd_ldo15: 3100 mV
[ 1.761113] vdd_ldo16: 2200 mV
[ 1.762892] tsp_avdd: 3300 mV
[ 1.764169] LDO18: at 1800 mV
[ 1.767727] vdd_sd: ramp_delay not set
[ 1.770503] vdd_sd: 2800 mV
[ 1.771774] LDO20: at 1800 mV
[ 1.773064] LDO21: at 1800 mV
[ 1.774329] LDO22: at 1200 mV
[ 1.775615] LDO23: at 1100 mV
[ 1.777431] tsp_io: 2800 mV
[ 1.778705] LDO25: at 1800 mV
[ 1.780498] vdd_ldo26: 3000 mV
[ 1.781770] LDO27: at 1000 mV
[ 1.783052] LDO28: at 3300 mV
[ 1.784327] LDO29: at 1800 mV
[ 1.785607] LDO30: at 1800 mV
[ 1.786920] LDO31: at 1800 mV
[ 1.788197] LDO32: at 1800 mV
[ 1.789476] LDO33: at 1800 mV
[ 1.790770] LDO34: at 3000 mV
[ 1.792051] LDO35: at 1600 mV
[ 1.793336] LDO36: at 1800 mV
[ 1.794602] LDO37: at 1800 mV
[ 1.795873] LDO38: at 2800 mV
[ 1.797651] vdd_mif: 800 <--> 1300 mV at 1100 mV
[ 1.799434] vdd_arm: 800 <--> 1500 mV at 1000 mV
[ 1.801258] vdd_int: 800 <--> 1400 mV at 1000 mV
[ 1.803039] vdd_g3d: 800 <--> 1400 mV at 1000 mV
[ 1.804814] vdd_mem: 800 <--> 1400 mV at 1200 mV
[ 1.806539] vdd_kfc: 800 <--> 1500 mV at 1025 mV
[ 1.808215] vdd_1.0v_ldo: 800 <--> 1500 mV at 900 mV
[ 1.809902] vdd_1.8v_ldo: 800 <--> 1500 mV at 1225 mV
[ 1.811729] vdd_2.8v_ldo: 3000 <--> 3750 mV at 5000 mV
[ 1.813507] vdd_vmem: 2850 mV
[ 1.820105] s5m-rtc s2mps14-rtc: rtc core: registered s5m-rtc as rtc0
[ 1.830198] thermal thermal_zone0: failed to read out thermal zone (-22)
[ 1.835485] exynos-tmu 10060000.tmu:: Looking up vtmu-supply from device tree
[ 1.836376] thermal thermal_zone1: failed to read out thermal zone (-22)
[ 1.842155] exynos-tmu 10064000.tmu:: Looking up vtmu-supply from device tree
[ 1.843035] thermal thermal_zone2: failed to read out thermal zone (-22)
[ 1.848827] exynos-tmu 10068000.tmu:: Looking up vtmu-supply from device tree
[ 1.849747] thermal thermal_zone3: failed to read out thermal zone (-22)
[ 1.855507] exynos-tmu 1006c000.tmu:: Looking up vtmu-supply from device tree
[ 1.856433] thermal thermal_zone4: failed to read out thermal zone (-22)
[ 1.862172] exynos-tmu 100a0000.tmu:: Looking up vtmu-supply from device tree
[ 1.864055] s3c2410-wdt 101d0000.watchdog:: watchdog inactive, reset disabled, irq disabled
[ 1.871854] device-mapper: ioctl: 4.32.0-ioctl (2015-6-26) initialised: dm-devel@redhat.com
[ 1.879713] cpu cpu0: Looking up cpu-cluster.1-supply from device tree
[ 1.882215] cpu cpu0: bL_cpufreq_init: CPU 0 initialized
[ 1.889137] cpu cpu1: Looking up cpu-cluster.0-supply from device tree
[ 1.891982] cpu cpu1: bL_cpufreq_init: CPU 1 initialized
[ 1.898865] arm_big_little: bL_cpufreq_register: Registered platform driver: dt-bl
[ 1.905237] sdhci: Secure Digital Host Controller Interface driver
[ 1.911122] sdhci: Copyright(c) Pierre Ossman
[ 1.915612] Synopsys Designware Multimedia Card Interface Driver
[ 1.921911] dwmmc_exynos 12200000.mmc:: num-slots property not found, assuming 1 slot is available
[ 1.930415] dwmmc_exynos 12200000.mmc:: IDMAC supports 32-bit address mode.
[ 1.937333] dwmmc_exynos 12200000.mmc:: Using internal DMA controller.
[ 1.943798] dwmmc_exynos 12200000.mmc:: Version ID is 250a
[ 1.949276] dwmmc_exynos 12200000.mmc:: DW MMC controller at irq 90, 64 bit host data width, 64 deep fifo
[ 1.958804] dwmmc_exynos 12200000.mmc:: Looking up vmmc-supply from device tree
[ 1.958812] dwmmc_exynos 12200000.mmc:: Looking up vmmc-supply property in node /mmc@12200000 failed
[ 1.958825] dwmmc_exynos 12200000.mmc:: Looking up vqmmc-supply from device tree
[ 1.958833] dwmmc_exynos 12200000.mmc:: Looking up vqmmc-supply property in node /mmc@12200000 failed
[ 1.958842] dwmmc_exynos 12200000.mmc:: No vmmc regulator found
[ 1.964671] dwmmc_exynos 12200000.mmc:: No vqmmc regulator found
[ 1.970661] dwmmc_exynos 12200000.mmc:: GPIO lookup for consumer cd
[ 1.970668] dwmmc_exynos 12200000.mmc:: using device tree for GPIO lookup
[ 1.970680] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/mmc@12200000[0]' - status (0)
[ 1.970697] dwmmc_exynos 12200000.mmc:: Got CD GPIO
[ 1.975503] dwmmc_exynos 12200000.mmc:: GPIO lookup for consumer wp
[ 1.975510] dwmmc_exynos 12200000.mmc:: using device tree for GPIO lookup
[ 1.975517] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@12200000[0]'
[ 1.975524] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@12200000[0]'
[ 1.975530] dwmmc_exynos 12200000.mmc:: using lookup tables for GPIO lookup
[ 1.975538] dwmmc_exynos 12200000.mmc:: lookup for GPIO wp failed
[ 1.975630] platform pwrseq:: GPIO lookup for consumer reset
[ 1.975636] platform pwrseq:: using device tree for GPIO lookup
[ 1.975647] of_get_named_gpiod_flags: parsed 'reset-gpios' property of node '/pwrseq[0]' - status (0)
[ 1.975664] dwmmc_exynos 12200000.mmc:: allocated mmc-pwrseq
[ 2.011000] dwmmc_exynos 12200000.mmc:: 1 slots initialized
[ 2.015286] dwmmc_exynos 12220000.mmc:: num-slots property not found, assuming 1 slot is available
[ 2.024099] dwmmc_exynos 12220000.mmc:: IDMAC supports 32-bit address mode.
[ 2.031009] dwmmc_exynos 12220000.mmc:: Using internal DMA controller.
[ 2.037486] dwmmc_exynos 12220000.mmc:: Version ID is 250a
[ 2.042967] dwmmc_exynos 12220000.mmc:: DW MMC controller at irq 91, 64 bit host data width, 64 deep fifo
[ 2.052483] dwmmc_exynos 12220000.mmc:: Looking up vmmc-supply from device tree
[ 2.052491] dwmmc_exynos 12220000.mmc:: Looking up vmmc-supply property in node /mmc@12220000 failed
[ 2.052503] dwmmc_exynos 12220000.mmc:: Looking up vqmmc-supply from device tree
[ 2.052510] dwmmc_exynos 12220000.mmc:: Looking up vqmmc-supply property in node /mmc@12220000 failed
[ 2.052519] dwmmc_exynos 12220000.mmc:: No vmmc regulator found
[ 2.058364] dwmmc_exynos 12220000.mmc:: No vqmmc regulator found
[ 2.064348] dwmmc_exynos 12220000.mmc:: GPIO lookup for consumer cd
[ 2.064354] dwmmc_exynos 12220000.mmc:: using device tree for GPIO lookup
[ 2.064361] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/mmc@12220000[0]'
[ 2.064368] of_get_named_gpiod_flags: can't parse 'cd-gpio' property of node '/mmc@12220000[0]'
[ 2.064374] dwmmc_exynos 12220000.mmc:: using lookup tables for GPIO lookup
[ 2.064382] dwmmc_exynos 12220000.mmc:: lookup for GPIO cd failed
[ 2.064390] dwmmc_exynos 12220000.mmc:: GPIO lookup for consumer wp
[ 2.064396] dwmmc_exynos 12220000.mmc:: using device tree for GPIO lookup
[ 2.064402] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@12220000[0]'
[ 2.064409] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@12220000[0]'
[ 2.064415] dwmmc_exynos 12220000.mmc:: using lookup tables for GPIO lookup
[ 2.064422] dwmmc_exynos 12220000.mmc:: lookup for GPIO wp failed
[ 2.090826] dwmmc_exynos 12220000.mmc:: 1 slots initialized
[ 2.096053] of_get_named_gpiod_flags: parsed 'gpios' property of node '/gpioleds/redled[0]' - status (0)
[ 2.097110] usbcore: registered new interface driver usbhid
[ 2.101308] usbhid: USB HID core driver
[ 2.106430] NET: Registered protocol family 17
[ 2.109456] NET: Registered protocol family 15
[ 2.114180] Registering SWP/SWPB emulation handler
[ 2.120103] of_get_named_gpiod_flags: parsed 'hpd-gpio' property of node '/hdmi@14530000[0]' - status (0)
[ 2.120184] exynos-hdmi 14530000.hdmi:: Looking up vdd-supply from device tree
[ 2.120715] exynos-hdmi 14530000.hdmi:: Looking up vdd_osc-supply from device tree
[ 2.121266] exynos-hdmi 14530000.hdmi:: Looking up vdd_pll-supply from device tree
[ 2.121782] exynos-hdmi 14530000.hdmi:: Looking up hdmi-en-supply from device tree
[ 2.121790] exynos-hdmi 14530000.hdmi:: Looking up hdmi-en-supply property in node /hdmi@14530000 failed
[ 2.121800] 14530000.hdmi: supply hdmi-en not found, using dummy regulator
[ 2.128183] exynos-drm exynos-drm: bound 14400000.fimd: (ops fimd_component_ops)
[ 2.134663] exynos-drm exynos-drm: bound 14450000.mixer: (ops mixer_component_ops)
[ 2.142311] exynos-drm exynos-drm: bound 14530000.hdmi: (ops hdmi_component_ops)
[ 2.149488] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 2.156067] [drm] No driver support for vblank timestamp query.
[ 2.159665] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[ 2.159871] mmc1: new high speed SDHC card at address aaaa
[ 2.162128] mmcblk0: mmc1:aaaa SU08G 7.40 GiB
[ 2.164505] mmcblk0: p1 p2
[ 2.184319] [drm] Initialized exynos 1.0.0 20110530 on minor 0
[ 2.190715] exynos-dwc3 usb@12000000:: Looking up vdd33-supply from device tree
[ 2.191285] exynos-dwc3 usb@12000000:: Looking up vdd10-supply from device tree
[ 2.394680] xhci-hcd xhci-hcd.6.auto: xHCI Host Controller
[ 2.398728] xhci-hcd xhci-hcd.6.auto: new USB bus registered, assigned bus number 3
[ 2.406606] xhci-hcd xhci-hcd.6.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x00010010
[ 2.415034] xhci-hcd xhci-hcd.6.auto: irq 137, io mem 0x12000000
[ 2.421113] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[ 2.427738] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.434936] usb usb3: Product: xHCI Host Controller
[ 2.439780] usb usb3: Manufacturer: Linux 4.2.0-rc1+ xhci-hcd
[ 2.445503] usb usb3: SerialNumber: xhci-hcd.6.auto
[ 2.450972] hub 3-0:1.0: USB hub found
[ 2.454080] hub 3-0:1.0: 1 port detected
[ 2.458357] xhci-hcd xhci-hcd.6.auto: xHCI Host Controller
[ 2.463449] xhci-hcd xhci-hcd.6.auto: new USB bus registered, assigned bus number 4
[ 2.471218] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[ 2.477825] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.485022] usb usb4: Product: xHCI Host Controller
[ 2.489867] usb usb4: Manufacturer: Linux 4.2.0-rc1+ xhci-hcd
[ 2.495582] usb usb4: SerialNumber: xhci-hcd.6.auto
[ 2.501027] hub 4-0:1.0: USB hub found
[ 2.504163] hub 4-0:1.0: 1 port detected
[ 2.508975] exynos-dwc3 usb@12400000:: Looking up vdd33-supply from device tree
[ 2.509466] exynos-dwc3 usb@12400000:: Looking up vdd10-supply from device tree
[ 2.712823] xhci-hcd xhci-hcd.9.auto: xHCI Host Controller
[ 2.716872] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 5
[ 2.724756] xhci-hcd xhci-hcd.9.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x00010010
[ 2.733176] xhci-hcd xhci-hcd.9.auto: irq 138, io mem 0x12400000
[ 2.739245] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
[ 2.745880] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.753078] usb usb5: Product: xHCI Host Controller
[ 2.757922] usb usb5: Manufacturer: Linux 4.2.0-rc1+ xhci-hcd
[ 2.763785] usb usb5: SerialNumber: xhci-hcd.9.auto
[ 2.768503] usb 3-1: new high-speed USB device number 2 using xhci-hcd
[ 2.775659] hub 5-0:1.0: USB hub found
[ 2.778738] hub 5-0:1.0: 1 port detected
[ 2.783026] xhci-hcd xhci-hcd.9.auto: xHCI Host Controller
[ 2.788091] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 6
[ 2.795897] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003
[ 2.802466] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.809656] usb usb6: Product: xHCI Host Controller
[ 2.814508] usb usb6: Manufacturer: Linux 4.2.0-rc1+ xhci-hcd
[ 2.820240] usb usb6: SerialNumber: xhci-hcd.9.auto
[ 2.825094] usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd
[ 2.832216] hub 6-0:1.0: USB hub found
[ 2.835303] hub 6-0:1.0: 1 port detected
[ 2.840532] s3c-rtc 101e0000.rtc:: rtc core: registered s3c as rtc1
[ 2.847584] s5m-rtc s2mps14-rtc: setting system clock to 2015-07-14 01:08:25 UTC (1436836105)
[ 2.855481] usb 4-1: New USB device found, idVendor=05e3, idProduct=0616
[ 2.861321] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.868415] usb 4-1: Product: USB3.0 Hub
[ 2.872317] usb 4-1: Manufacturer: GenesysLogic
[ 2.887803] hub 4-1:1.0: USB hub found
[ 2.890455] hub 4-1:1.0: 2 ports detected
[ 2.901940] Freeing unused kernel memory: 404K (c075b000 - c07c0000)
[ 2.906992] usb 3-1: New USB device found, idVendor=05e3, idProduct=0610
[ 2.913513] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.920612] usb 3-1: Product: USB2.0 Hub
[ 2.924514] usb 3-1: Manufacturer: GenesysLogic
[ 2.952009] hub 3-1:1.0: USB hub found
[ 2.954924] hub 3-1:1.0: 2 ports detected
[ 2.970064] random: systemd-udevd urandom read with 80 bits of entropy available
[ 3.215994] usb 6-1: new SuperSpeed USB device number 2 using xhci-hcd
[ 3.237723] usb 6-1: New USB device found, idVendor=0bda, idProduct=8153
[ 3.243129] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[ 3.250172] usb 6-1: Product: USB 10/100/1000 LAN
[ 3.254846] usb 6-1: Manufacturer: Realtek
[ 3.258914] usb 6-1: SerialNumber: 000001000000
[ 3.322067] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 3.386033] usb 4-1.2: new SuperSpeed USB device number 3 using xhci-hcd
[ 3.408811] usb 4-1.2: New USB device found, idVendor=05e3, idProduct=0735
[ 3.414239] usb 4-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.421539] usb 4-1.2: Product: USB3.0 SATA Bridge
[ 3.426275] usb 4-1.2: Manufacturer: USB Storage
[ 3.430862] usb 4-1.2: SerialNumber: 0000000000000033
[ 4.105635] udevd[1746]: starting version 175
[ 4.379721] random: nonblocking pool is initialized
[ 4.476677] samsung-pwm 12dd0000.pwm:: tried to request PWM channel 1 without output
[ 4.483029] leds_pwm pwmleds:: unable to request PWM for green:mmc0: -22
[ 4.490794] leds_pwm: probe of pwmleds: failed with error -22
[ 4.576076] usb_phy_generic.0.auto supply vcc not found, using dummy regulator
[ 4.582190] usb_phy_generic.1.auto supply vcc not found, using dummy regulator
[ 4.589654] usb_phy_generic.2.auto supply vcc not found, using dummy regulator
[ 4.597056] usb_phy_generic.3.auto supply vcc not found, using dummy regulator
[ 4.603756] usb_phy_generic.4.auto supply vcc not found, using dummy regulator
[ 4.611029] usb_phy_generic.5.auto supply vcc not found, using dummy regulator
[ 4.621414] usb_phy_generic.7.auto supply vcc not found, using dummy regulator
[ 4.628822] usb_phy_generic.8.auto supply vcc not found, using dummy regulator
[ 4.657950] usbcore: registered new interface driver r8152
[ 4.669980] usb-storage 4-1.2:1.0: USB Mass Storage device detected
[ 4.675842] scsi host0: usb-storage 4-1.2:1.0
[ 4.680144] usbcore: registered new interface driver usb-storage
[ 4.700543] usbcore: registered new interface driver cdc_ether
[ 4.812164] usb 6-1: reset SuperSpeed USB device number 2 using xhci-hcd
[ 4.870365] r8152 6-1:1.0 eth0: v2.04.0 (2015/03/06)
[ 4.873898] r8152 6-1:1.0 eth0: This product is covered by one or more of the following patents:
[ 4.873898] US6,570,884, US6,115,776, and US6,327,625.
[ 4.873898]
[ 5.668463] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 5.676463] scsi 0:0:0:0: Direct-Access Samsung SSD 850 EVO 120G 1003 PQ: 0 ANSI: 6
[ 5.684417] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 5.684666] sd 0:0:0:0: [sda] 234441632 512-byte logical blocks: (120 GB/111 GiB)
[ 5.685461] sd 0:0:0:0: [sda] Write Protect is off
[ 5.685471] sd 0:0:0:0: [sda] Mode Sense: 5f 00 10 08
[ 5.686169] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[ 5.690823] sda: sda1
[ 5.702201] sd 0:0:0:0: [sda] Attached SCSI disk
[ 6.807014] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: data=ordered
[ 7.678428] NET: Registered protocol family 10
[ 7.800947] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 10.348978] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
[....] Starting enhanced syslogd: rsyslogd. ok
[....] Starting periodic command scheduler: cron. ok
[....] Starting system message bus: dbus. ok
[....] Starting OpenBSD Secure Shell server: sshd. ok
[....] Starting Samba daemons: nmbd smbd. ok
Debian GNU/Linux 7 odroid ttySAC2
odroid login: root
Password:
Last login: Tue Jul 14 10:27:15 KST 2015 on tty1
Linux odroid 4.2.0-rc1+ #4 SMP PREEMPT Fri Jul 10 16:45:24 KST 2015 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@odroid:~# uname -a
Linux odroid 4.2.0-rc1+ #4 SMP PREEMPT Fri Jul 10 16:45:24 KST 2015 armv7l
GNU/Linux</nowiki>