Getting UAS working on HK 4.9

Test and fix the Kernel 4.9 features

Moderators: mdrjr, odroid

Re: Getting UAS working on HK 4.9

Unread postby Kosmatik » Wed May 24, 2017 12:24 am

Odd, the drives are brand new and Ive never dropped them. Long scan in progress, results in about 7 hours.

EDIT: I'd like to add that all the ports and cables have been cleaned with anhydrous alcohol. Cables and the PCB was checked to fit 100% and the enclosure has not been moved.
Kosmatik
 
Posts: 25
Joined: Tue May 23, 2017 12:06 pm
languages_spoken: English, Russian
ODROIDs: XU4

Re: Getting UAS working on HK 4.9

Unread postby Kosmatik » Wed May 24, 2017 9:01 am

So to recap long smart scan produced no errors on both drives:

Code: Select all
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%        62         -


I also had to disable UAS for this jmicron bridge in kernel using below in unusual_uas.h as the flags from JMS567 did not alleviate the issue. If anyone knows where I need to submit lsusb -v and dmesg to have this properly looked at will be appreciated.

Code: Select all
UNUSUAL_DEV(0x152d, 0x0561, 0x0000, 0x9999,
      "JMicron",
      "JMS561",
      USB_SC_DEVICE, USB_PR_DEVICE, NULL,
      US_FL_IGNORE_UAS),


Stability testing will continue

Sadly, still happens
Code: Select all
[ 4146.728763] usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
Last edited by Kosmatik on Wed May 24, 2017 10:13 am, edited 1 time in total.
Kosmatik
 
Posts: 25
Joined: Tue May 23, 2017 12:06 pm
languages_spoken: English, Russian
ODROIDs: XU4

Re: Getting UAS working on HK 4.9

Unread postby crashoverride » Wed May 24, 2017 10:13 am

I should note that once a drive shows the type of errors you posted (ext4), it should be reformatted. It has been my experience that an EXT fs is never the same after such failures despite "recovery complete" assurances.

Also, when formatting an EXT fs, be aware of "lazy init":
https://www.thomas-krenn.com/en/wiki/Ex ... ialization

Its best to disable "lazy init" so that any errors are seen immediately and any future errors can be correlated to the operation being performed rather than something "in the background".
crashoverride
 
Posts: 3060
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1

Re: Getting UAS working on HK 4.9

Unread postby Kosmatik » Wed May 24, 2017 12:36 pm

So I formatted again, no errors

Code: Select all
root@openmediavault:/etc# mkfs.ext4 -E lazy_itable_init=0,lazy_journal_init=0 /dev/sda
mke2fs 1.42.12 (29-Aug-2014)
Creating filesystem with 976754646 4k blocks and 244195328 inodes
Filesystem UUID: 0bf04d45-b2b2-42ac-a05e-0d15aed927d1
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848, 512000000, 550731776, 644972544

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

root@openmediavault:/etc# mkfs.ext4 -E lazy_itable_init=0,lazy_journal_init=0 /dev/sdb
mke2fs 1.42.12 (29-Aug-2014)
Creating filesystem with 976754646 4k blocks and 244195328 inodes
Filesystem UUID: 83548b20-5857-44bb-917b-8c67839d688f
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848, 512000000, 550731776, 644972544

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done


Still resets though, while at it, also caught a bug, i suspect this same issue is causing samba failures.

Image

Code: Select all
[  599.113178] usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
[  733.284738] usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
[  776.142441] BUG: Bad page state in process kswapd0  pfn:98cc6
[  776.142813] page:efaa1bd8 count:0 mapcount:-2 mapping:  (null) index:0x1
[  776.143133] flags: 0x40000000()
[  776.143291] page dumped because: nonzero mapcount
[  776.143599] Modules linked in: binfmt_misc cpufreq_powersave cpufreq_conservative cpufreq_userspace cfg80211 rfkill cpufreq_ondemand uas s5p_sss exynos_gpiomem pwm_fan uio_pdrv_genirq uio fb_ili9340(C) fbtft_device(C) fbtft(C) spidev spi_s3c64xx fuse ipv6 md_mod
[  776.143671] CPU: 5 PID: 62 Comm: kswapd0 Tainted: G         C      4.9.29-odroidxu4 #17
[  776.143675] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[  776.143696] [<c010e93c>] (unwind_backtrace) from [<c010b5a4>] (show_stack+0x10/0x14)
[  776.143705] [<c010b5a4>] (show_stack) from [<c05ae538>] (dump_stack+0x84/0x98)
[  776.143715] [<c05ae538>] (dump_stack) from [<c01d1948>] (bad_page+0xf4/0x158)
[  776.143722] [<c01d1948>] (bad_page) from [<c01d23ac>] (free_pcppages_bulk+0x2ec/0x458)
[  776.143729] [<c01d23ac>] (free_pcppages_bulk) from [<c01d3868>] (free_hot_cold_page+0x1c0/0x218)
[  776.143737] [<c01d3868>] (free_hot_cold_page) from [<c01d3b3c>] (free_hot_cold_page_list+0x2c/0x48)
[  776.143743] [<c01d3b3c>] (free_hot_cold_page_list) from [<c01dfb84>] (shrink_page_list+0x2cc/0xbc8)
[  776.143750] [<c01dfb84>] (shrink_page_list) from [<c01e0b30>] (shrink_inactive_list+0x1d4/0x4dc)
[  776.143756] [<c01e0b30>] (shrink_inactive_list) from [<c01e1584>] (shrink_node_memcg+0x43c/0x6d0)
[  776.143762] [<c01e1584>] (shrink_node_memcg) from [<c01e18e0>] (shrink_node+0xc8/0x32c)
[  776.143768] [<c01e18e0>] (shrink_node) from [<c01e2620>] (kswapd+0x2f8/0x690)
[  776.143775] [<c01e2620>] (kswapd) from [<c013d3e0>] (kthread+0xf8/0x110)
[  776.143782] [<c013d3e0>] (kthread) from [<c0107838>] (ret_from_fork+0x14/0x3c)
[  776.143787] Disabling lock debugging due to kernel taint


EDIT:

Just got an email

Code: Select all
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 12106 ().

This means there was a problem with the program, such as a segfault.
However, the executable could not be found for process 12106.
It may have died unexpectedly, or you may not have permission to debug
the process.
Kosmatik
 
Posts: 25
Joined: Tue May 23, 2017 12:06 pm
languages_spoken: English, Russian
ODROIDs: XU4

Re: Getting UAS working on HK 4.9

Unread postby crashoverride » Wed May 24, 2017 12:49 pm

That may indicate a hardware issue in the XU4 itself. The HDD issues may just be a symptom of that.

To narrow the scope, you should test with the official Ubuntu Mate image. If the issue persists, you should see if the issue happens when using SD/eMMC as the source/destination instead of the HDD.
crashoverride
 
Posts: 3060
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1

Re: Getting UAS working on HK 4.9

Unread postby mad_ady » Wed May 24, 2017 1:17 pm

I'd replace/check usb cables as well.
User avatar
mad_ady
 
Posts: 2400
Joined: Wed Jul 15, 2015 5:00 pm
Location: Bucharest, Romania
languages_spoken: english
ODROIDs: XU4, C1+, C2

Re: Getting UAS working on HK 4.9

Unread postby odroid » Wed May 24, 2017 1:30 pm

I could reproduce a similar issue with a new external storage box.
The box has the ASM1153 and VID/PID is 1746/55AA.
There was no issue yesterday. But I met the issue this morning(KST) once. But I can't reproduce the issue now.
I will keep trying to reproduce the issue.

Code: Select all
[  356.315023] usb 4-1.2: new SuperSpeed USB device number 3 using xhci-hcd
[  356.335816] usb 4-1.2: New USB device found, idVendor=174c, idProduct=55aa
[  356.335822] usb 4-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[  356.335828] usb 4-1.2: Product: USB3.0 External HDD
[  356.335833] usb 4-1.2: Manufacturer: ASMedia
[  356.335837] usb 4-1.2: SerialNumber: 201401000057
[  356.375508] scsi host0: uas
[  356.376689] scsi 0:0:0:0: Direct-Access     Samsung  SSD 850 PRO 256G 0    PQ: 0 ANSI: 6
[  356.430590] sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
[  356.430598] sd 0:0:0:0: Attached scsi generic sg0 type 0
[  356.431011] usbcore: registered new interface driver uas
[  356.431087] sd 0:0:0:0: [sda] Write Protect is off
[  356.431094] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[  356.431311] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  356.433165]  sda: sda1
[  356.434808] sd 0:0:0:0: [sda] Attached SCSI disk
[  356.767958] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[  412.179675] sd 0:0:0:0: [sda] tag#0 data cmplt err -71 uas-tag 1 inflight: CMD
[  412.179687] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 04 48 00 00 04 00 00
[  412.180392] xhci-hcd xhci-hcd.2.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[  412.188473] xhci-hcd xhci-hcd.2.auto: @00000000b684eaa0 00000000 00000000 04000000 03038001
[  443.370136] sd 0:0:0:0: [sda] tag#15 uas_eh_abort_handler 0 uas-tag 16 inflight: CMD IN
[  443.370147] sd 0:0:0:0: [sda] tag#15 CDB: opcode=0x28 28 00 00 04 84 00 00 04 00 00
[  443.370544] sd 0:0:0:0: [sda] tag#14 uas_eh_abort_handler 0 uas-tag 15 inflight: CMD IN
[  443.370551] sd 0:0:0:0: [sda] tag#14 CDB: opcode=0x28 28 00 00 04 80 00 00 04 00 00
[  443.370903] sd 0:0:0:0: [sda] tag#13 uas_eh_abort_handler 0 uas-tag 14 inflight: CMD IN
[  443.370909] sd 0:0:0:0: [sda] tag#13 CDB: opcode=0x28 28 00 00 04 7c 00 00 04 00 00
[  443.371256] sd 0:0:0:0: [sda] tag#12 uas_eh_abort_handler 0 uas-tag 13 inflight: CMD IN
[  443.371263] sd 0:0:0:0: [sda] tag#12 CDB: opcode=0x28 28 00 00 04 78 00 00 04 00 00
[  443.371609] sd 0:0:0:0: [sda] tag#11 uas_eh_abort_handler 0 uas-tag 12 inflight: CMD IN
[  443.371615] sd 0:0:0:0: [sda] tag#11 CDB: opcode=0x28 28 00 00 04 74 00 00 04 00 00
[  443.371961] sd 0:0:0:0: [sda] tag#10 uas_eh_abort_handler 0 uas-tag 11 inflight: CMD IN
[  443.371967] sd 0:0:0:0: [sda] tag#10 CDB: opcode=0x28 28 00 00 04 70 00 00 04 00 00
[  443.372311] sd 0:0:0:0: [sda] tag#9 uas_eh_abort_handler 0 uas-tag 10 inflight: CMD IN
[  443.372317] sd 0:0:0:0: [sda] tag#9 CDB: opcode=0x28 28 00 00 04 6c 00 00 04 00 00
[  443.372660] sd 0:0:0:0: [sda] tag#8 uas_eh_abort_handler 0 uas-tag 9 inflight: CMD IN
[  443.372665] sd 0:0:0:0: [sda] tag#8 CDB: opcode=0x28 28 00 00 04 68 00 00 04 00 00
[  443.373009] sd 0:0:0:0: [sda] tag#7 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD IN
[  443.373015] sd 0:0:0:0: [sda] tag#7 CDB: opcode=0x28 28 00 00 04 64 00 00 04 00 00
[  443.373358] sd 0:0:0:0: [sda] tag#6 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD IN
[  443.373364] sd 0:0:0:0: [sda] tag#6 CDB: opcode=0x28 28 00 00 04 60 00 00 04 00 00
[  443.373706] sd 0:0:0:0: [sda] tag#5 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD IN
[  443.373712] sd 0:0:0:0: [sda] tag#5 CDB: opcode=0x28 28 00 00 04 5c 00 00 04 00 00
[  443.374055] sd 0:0:0:0: [sda] tag#4 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD IN
[  443.374061] sd 0:0:0:0: [sda] tag#4 CDB: opcode=0x28 28 00 00 04 58 00 00 04 00 00
[  443.374404] sd 0:0:0:0: [sda] tag#3 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD IN
[  443.374410] sd 0:0:0:0: [sda] tag#3 CDB: opcode=0x28 28 00 00 04 54 00 00 04 00 00
[  443.374754] sd 0:0:0:0: [sda] tag#2 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD IN
[  443.374761] sd 0:0:0:0: [sda] tag#2 CDB: opcode=0x28 28 00 00 04 50 00 00 04 00 00
[  443.375153] sd 0:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN
[  443.375164] sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 00 04 4c 00 00 04 00 00
[  443.375562] sd 0:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD
[  443.375572] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 04 48 00 00 04 00 00
[  443.375621] scsi host0: uas_eh_bus_reset_handler start
[  443.455218] usb 4-1.2: reset SuperSpeed USB device number 3 using xhci-hcd
[  443.477442] scsi host0: uas_eh_bus_reset_handler success
User avatar
odroid
Site Admin
 
Posts: 24367
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: Getting UAS working on HK 4.9

Unread postby crashoverride » Wed May 24, 2017 1:46 pm

odroid wrote:There was no issue yesterday. But I met the issue this morning(KST) once.

That is consistent with what I experienced with the ASM controller in my Seagate drive when I said "UAS works... until it doesn't". So far, I have not encountered issues with CloudShell2.

With regard to the previous issue discussed:
Kosmatik wrote:[ 776.143291] page dumped because: nonzero mapcount

That sounds like a memory issue if the "swap file" is z-ram. If its an actual swap file that does not reside on the HDD, this would also indicate a failure in XU4 itself.
crashoverride
 
Posts: 3060
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1

Re: Getting UAS working on HK 4.9

Unread postby odroid » Wed May 24, 2017 1:58 pm

My test was done with official Ubuntu image. I will disable the UAS if I meet the same issue again.

Good point. As far as I remember, the OMV image enabled the ZRAM driver by default.
I will double check it.
User avatar
odroid
Site Admin
 
Posts: 24367
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: Getting UAS working on HK 4.9

Unread postby odroid » Wed May 24, 2017 2:10 pm

I was wrong. There was no zram in OMV OS. I was confused with folder2ram. Sorry. :oops:
Code: Select all
root@odroidxu4:~# dmesg
[    0.000000] Booting Linux on physical CPU 0x100
[    0.000000] Linux version 4.9.28-odroidxu4 (root@opennms) (gcc version 6.3.1 20170109 (Linaro GCC 6.3-2017.02) ) #8 SMP PREEMPT Fri May 19 09:25:51 CEST 2017
[    0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=10c5387d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt:Machine model: Hardkernel Odroid XU4
[    0.000000] cma: Reserved 128 MiB at 0xb6800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] Samsung CPU ID: 0xe5422001
[    0.000000] On node 0 totalpages: 518656
[    0.000000] free_area_init_node: node 0, pgdat c0e56640, node_mem_map eee25000
[    0.000000]   Normal zone: 1728 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 196608 pages, LIFO batch:31
[    0.000000]   HighMem zone: 322048 pages, LIFO batch:31
[    0.000000] Running under secure firmware.
[    0.000000] percpu: Embedded 14 pages/cpu @eed7f000 s26700 r8192 d22452 u57344
[    0.000000] pcpu-alloc: s26700 r8192 d22452 u57344 alloc=14*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: 516928
[    0.000000] Kernel command line: console=tty1 vt.global_cursor_default=0 consoleblank=0 loglevel=1 root=UUID=b137c027-10cf-41d5-8a72-fd546b628157 rootwait rw fsck.repair=yes smsc95xx.macaddr=00:1e:06:61:7a:55 governor=performance hdmi_tx_amp_lvl=31 hdmi_tx_lvl_ch0=3 hdmi_tx_lvl_ch1=3 hdmi_tx_lvl_ch2=3 hdmi_tx_emp_lvl=6 hdmi_clk_amp_lvl=31 hdmi_tx_res=0 HPD=true vout=hdmi s5p_mfc.mem=16M
[    0.000000] hdmi: using HDMI mode
[    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: 1904540K/2074624K available (9216K kernel code, 348K rwdata, 2336K rodata, 1024K init, 341K bss, 39012K reserved, 131072K cma-reserved, 1157120K highmem)
[    0.000000] Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
    lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc0a00000   (10208 kB)
      .init : 0xc0d00000 - 0xc0e00000   (1024 kB)
      .data : 0xc0e00000 - 0xc0e572a0   ( 349 kB)
       .bss : 0xc0e59000 - 0xc0eae5bc   ( 342 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[    0.000000] hperf_hmp: fast CPUs mask: 000000F0
[    0.000000] hperf_hmp: slow CPUs mask: 0000000F
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]    Build-time adjustment of leaf fanout to 32.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    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.001431] Console: colour dummy device 80x30
[    0.001448] console [tty1] enabled
[    0.001471] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=120000)
[    0.001487] pid_max: default: 32768 minimum: 301
[    0.001693] Security Framework initialized
[    0.001704] AppArmor: AppArmor disabled by boot time parameter
[    0.001762] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001771] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.002724] CPU: Testing write buffer coherency: ok
[    0.003530] CPU0: update cpu_capacity 551
[    0.003540] CPU0: thread -1, cpu 0, socket 1, mpidr 80000100
[    0.003675] Setting up static identity map for 0x40100000 - 0x40100058
[    0.004336] ARM CCI driver probed
[    0.004554] Exynos MCPM support installed
[    0.085327] CPU1: update cpu_capacity 551
[    0.085335] CPU1: thread -1, cpu 1, socket 1, mpidr 80000101
[    0.086295] CPU2: update cpu_capacity 551
[    0.086302] CPU2: thread -1, cpu 2, socket 1, mpidr 80000102
[    0.087178] CPU3: update cpu_capacity 551
[    0.087185] CPU3: thread -1, cpu 3, socket 1, mpidr 80000103
[    0.088080] CPU4: update cpu_capacity 1496
[    0.088088] CPU4: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.089213] CPU5: update cpu_capacity 1496
[    0.089220] CPU5: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.090208] CPU6: update cpu_capacity 1496
[    0.090215] CPU6: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.091129] CPU7: update cpu_capacity 1496
[    0.091135] CPU7: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.091252] Brought up 8 CPUs
[    0.091264] SMP: Total of 8 processors activated (384.00 BogoMIPS).
[    0.091272] CPU: WARNING: CPU(s) started in wrong/inconsistent modes (primary CPU mode 0x1a)
[    0.091277] CPU: This may indicate a broken bootloader or firmware.
[    0.092792] devtmpfs: initialized
[    0.118599] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
[    0.118801] hperf_hmp: registered cpufreq transition notifier
[    0.118982] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302231375000 ns
[    0.118997] futex hash table entries: 2048 (order: 5, 131072 bytes)
[    0.121384] xor: measuring software checksum speed
[    0.169964]    arm4regs  :  1516.800 MB/sec
[    0.219965]    8regs     :  1126.400 MB/sec
[    0.269966]    32regs    :  1173.600 MB/sec
[    0.319965]    neon      :  2199.200 MB/sec
[    0.319973] xor: using function: neon (2199.200 MB/sec)
[    0.320063] pinctrl core: initialized pinctrl subsystem
[    0.321941] NET: Registered protocol family 16
[    0.323713] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.339244] cpuidle: using governor menu
[    0.355423] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.355431] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.365928] exynos-audss-clk 3810000.audss-clock-controller:: epll 180633609
[    0.368058] iommu: Adding device 10850000.g2d: to group 0
[    0.373322] iommu: Adding device 11000000.codec: to group 1
[    0.403299] iommu: Adding device 14450000.mixer: to group 2
[    0.403784] iommu: Adding device 11c00000.rotator: to group 3
[    0.407186] random: fast init done
[    0.408294] iommu: Adding device 13e00000.video-scaler: to group 4
[    0.408777] iommu: Adding device 13e10000.video-scaler: to group 5
[    0.409263] iommu: Adding device 11f50000.jpeg: to group 6
[    0.409751] iommu: Adding device 11f60000.jpeg: to group 7
[    0.410080] EXYNOS5420 PMU initialized
[    0.525144] raid6: int32x1  gen()   178 MB/s
[    0.610100] raid6: int32x1  xor()   218 MB/s
[    0.695089] raid6: int32x2  gen()   253 MB/s
[    0.780077] raid6: int32x2  xor()   264 MB/s
[    0.865035] raid6: int32x4  gen()   342 MB/s
[    0.950041] raid6: int32x4  xor()   265 MB/s
[    1.034997] raid6: int32x8  gen()   372 MB/s
[    1.120039] raid6: int32x8  xor()   262 MB/s
[    1.205010] raid6: neonx1   gen()   717 MB/s
[    1.289998] raid6: neonx1   xor()   628 MB/s
[    1.375009] raid6: neonx2   gen()  1061 MB/s
[    1.459987] raid6: neonx2   xor()   942 MB/s
[    1.545014] raid6: neonx4   gen()  1357 MB/s
[    1.630011] raid6: neonx4   xor()   992 MB/s
[    1.715016] raid6: neonx8   gen()  1309 MB/s
[    1.800017] raid6: neonx8   xor()   980 MB/s
[    1.800024] raid6: using algorithm neonx4 gen() 1357 MB/s
[    1.800031] raid6: .... xor() 992 MB/s, rmw enabled
[    1.800037] raid6: using intx1 recovery algorithm
[    1.801753] SCSI subsystem initialized
[    1.802019] usbcore: registered new interface driver usbfs
[    1.802098] usbcore: registered new interface driver hub
[    1.802267] usbcore: registered new device driver usb
[    1.803007] s3c-i2c 12c70000.i2c:: slave address 0x00
[    1.803020] s3c-i2c 12c70000.i2c:: bus frequency set to 378 KHz
[    1.803337] s3c-i2c 12c70000.i2c:: i2c-1: S3C I2C adapter
[    1.803491] s3c-i2c 12c80000.i2c:: slave address 0x00
[    1.803503] s3c-i2c 12c80000.i2c:: bus frequency set to 65 KHz
[    1.803962] s3c-i2c 12c80000.i2c:: i2c-2: S3C I2C adapter
[    1.804365] media: Linux media interface: v0.10
[    1.804421] Linux video capture interface: v2.00
[    1.804874] Advanced Linux Sound Architecture Driver Initialized.
[    1.806165] clocksource: Switched to clocksource mct-frc
[    1.806351] VFS: Disk quotas dquot_6.6.0
[    1.806416] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.823729] NET: Registered protocol family 2
[    1.824372] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    1.824446] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    1.824600] TCP: Hash tables configured (established 8192 bind 8192)
[    1.824648] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    1.824683] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    1.824897] NET: Registered protocol family 1
[    1.825538] RPC: Registered named UNIX socket transport module.
[    1.825545] RPC: Registered udp transport module.
[    1.825551] RPC: Registered tcp transport module.
[    1.825558] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.825770] Trying to unpack rootfs image as initramfs...
[    2.116657] Freeing initrd memory: 5188K (c2000000 - c2511000)
[    2.119790] audit: initializing netlink subsys (disabled)
[    2.119833] audit: type=2000 audit(2.115:1): initialized
[    2.120129] Initialise system trusted keyrings
[    2.120656] workingset: timestamp_bits=14 max_order=19 bucket_order=5
[    2.135210] NFS: Registering the id_resolver key type
[    2.135231] Key type id_resolver registered
[    2.135238] Key type id_legacy registered
[    2.135254] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    2.135266] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    2.136495] romfs: ROMFS MTD (C) 2007 Red Hat, Inc.
[    2.137502] JFS: nTxBlock = 8192, nTxLock = 65536
[    2.142558] SGI XFS with ACLs, security attributes, realtime, no debug enabled
[    2.152762] Key type asymmetric registered
[    2.152818] bounce: pool size: 64 pages
[    2.153050] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)
[    2.153239] io scheduler noop registered
[    2.153247] io scheduler deadline registered
[    2.153481] io scheduler cfq registered (default)
[    2.156740] 12130000.phy: supply vbus not found, using dummy regulator
[    2.157857] 12100000.phy: supply vbus not found, using dummy regulator
[    2.157929] 12100000.phy: supply vbus-boost not found, using dummy regulator
[    2.158367] 12500000.phy: supply vbus not found, using dummy regulator
[    2.158438] 12500000.phy: supply vbus-boost not found, using dummy regulator
[    2.163902] dma-pl330 3880000.adma: Loaded driver for PL330 DMAC-241330
[    2.163913] dma-pl330 3880000.adma:    DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6
[    2.168029] dma-pl330 121a0000.pdma: Loaded driver for PL330 DMAC-241330
[    2.168040] dma-pl330 121a0000.pdma:    DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    2.172208] dma-pl330 121b0000.pdma: Loaded driver for PL330 DMAC-241330
[    2.172219] dma-pl330 121b0000.pdma:    DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    2.173383] dma-pl330 10800000.mdma: Loaded driver for PL330 DMAC-241330
[    2.173393] dma-pl330 10800000.mdma:    DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32
[    2.261330] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    2.264104] 12c00000.serial:: ttySAC0 at MMIO 0x12c00000 (irq = 76, base_baud = 0) is a S3C6400/10
[    2.264580] 12c10000.serial:: ttySAC1 at MMIO 0x12c10000 (irq = 77, base_baud = 0) is a S3C6400/10
[    2.265029] 12c20000.serial:: ttySAC2 at MMIO 0x12c20000 (irq = 78, base_baud = 0) is a S3C6400/10
[    2.265478] 12c30000.serial:: ttySAC3 at MMIO 0x12c30000 (irq = 79, base_baud = 0) is a S3C6400/10
[    2.266958] [drm] Initialized
[    2.268560] exynos-hdmi 14530000.hdmi:: Failed to get supply 'vdd': -517
[    2.269792] exynos-rot 11c00000.rotator:: The exynos rotator is probed successfully
[    2.270513] exynos-drm-ipp exynos-drm-ipp: drm ipp registered successfully.
[    2.275017] mali 11800000.mali:: GPU identified as 0x0620 r0p1 status 0
[    2.275947] devfreq 11800000.mali:: Couldn't update frequency transition information.
[    2.275959] mali 11800000.mali:: could not find power_model node
[    2.276747] mali 11800000.mali:: Probed as mali0
[    2.292661] brd: module loaded
[    2.302325] loop: module loaded
[    2.303210] libphy: Fixed MDIO Bus: probed
[    2.303583] usbcore: registered new interface driver r8152
[    2.303635] usbcore: registered new interface driver cdc_ether
[    2.303687] usbcore: registered new interface driver cdc_subset
[    2.304228] exynos-dwc3 soc:usb3-0:: no suspend clk specified
[    2.304327] exynos-dwc3 soc:usb3-1:: no suspend clk specified
[    2.305588] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.305595] ehci-exynos: EHCI EXYNOS driver
[    2.305990] exynos-ehci 12110000.usb:: EHCI Host Controller
[    2.306019] exynos-ehci 12110000.usb:: new USB bus registered, assigned bus number 1
[    2.306294] exynos-ehci 12110000.usb:: irq 91, io mem 0x12110000
[    2.321208] exynos-ehci 12110000.usb:: USB 2.0 started, EHCI 1.00
[    2.321430] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.321441] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.321449] usb usb1: Product: EHCI Host Controller
[    2.321458] usb usb1: Manufacturer: Linux 4.9.28-odroidxu4 ehci_hcd
[    2.321466] usb usb1: SerialNumber: 12110000.usb:
[    2.322247] hub 1-0:1.0: USB hub found
[    2.322289] hub 1-0:1.0: 3 ports detected
[    2.323350] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    2.323369] ohci-exynos: OHCI EXYNOS driver
[    2.323626] exynos-ohci 12120000.usb:: USB Host Controller
[    2.323653] exynos-ohci 12120000.usb:: new USB bus registered, assigned bus number 2
[    2.323768] exynos-ohci 12120000.usb:: irq 91, io mem 0x12120000
[    2.385427] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[    2.385438] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.385446] usb usb2: Product: USB Host Controller
[    2.385454] usb usb2: Manufacturer: Linux 4.9.28-odroidxu4 ohci_hcd
[    2.385462] usb usb2: SerialNumber: 12120000.usb:
[    2.386248] hub 2-0:1.0: USB hub found
[    2.386291] hub 2-0:1.0: 3 ports detected
[    2.387931] usbcore: registered new interface driver cdc_wdm
[    2.388040] usbcore: registered new interface driver usb-storage
[    2.388858] mousedev: PS/2 mouse device common for all mice
[    2.390454] i2c /dev entries driver
[    2.394038] LDO27: mapping for mode 1 not defined
[    2.394075] LDO28: mapping for mode 1 not defined
[    2.394111] LDO30: mapping for mode 1 not defined
[    2.406449] vdd_ldo9: Bringing 3300000uV into 3000000-3000000uV
[    2.418591] vdd_ldo15: Bringing 3300000uV into 3100000-3100000uV
[    2.427517] vdd_sd: Bringing 3300000uV into 2800000-2800000uV
[    2.446384] vdd_ldo30: Bringing 1800000uV into 3300000-3300000uV
[    2.488712] s5m-rtc s2mps14-rtc: rtc core: registered s5m-rtc as rtc0
[    2.491886] IR NEC protocol handler initialized
[    2.491893] IR RC5(x/sz) protocol handler initialized
[    2.491900] IR RC6 protocol handler initialized
[    2.491906] IR JVC protocol handler initialized
[    2.491913] IR Sony protocol handler initialized
[    2.491919] IR SANYO protocol handler initialized
[    2.491925] IR Sharp protocol handler initialized
[    2.491932] IR MCE Keyboard/mouse protocol handler initialized
[    2.491938] IR XMP protocol handler initialized
[    2.492979] s5p-jpeg 11f50000.jpeg:: encoder device registered as /dev/video0
[    2.493220] s5p-jpeg 11f50000.jpeg:: decoder device registered as /dev/video1
[    2.493227] s5p-jpeg 11f50000.jpeg:: Samsung S5P JPEG codec
[    2.493598] s5p-jpeg 11f60000.jpeg:: encoder device registered as /dev/video2
[    2.493823] s5p-jpeg 11f60000.jpeg:: decoder device registered as /dev/video3
[    2.493830] s5p-jpeg 11f60000.jpeg:: Samsung S5P JPEG codec
[    2.511986] s5p-mfc 11000000.codec:: preallocated 16 MiB buffer for the firmware and context buffers
[    2.512262] s5p-mfc 11000000.codec:: decoder registered as /dev/video10
[    2.512485] s5p-mfc 11000000.codec:: encoder registered as /dev/video11
[    2.522366] s3c2410-wdt 101d0000.watchdog:: watchdog inactive, reset disabled, irq disabled
[    2.523024] device-mapper: uevent: version 1.0.3
[    2.523500] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised: dm-devel@redhat.com
[    2.525849] core: _opp_supported_by_regulators: OPP minuV: 1135000 maxuV: 1135000, not supported by regulator
[    2.525859] cpu cpu0: _opp_add: OPP not supported by regulators (1100000000)
[    2.537273] sdhci: Secure Digital Host Controller Interface driver
[    2.537277] sdhci: Copyright(c) Pierre Ossman
[    2.537486] Synopsys Designware Multimedia Card Interface Driver
[    2.538047] dwmmc_exynos 12200000.mmc:: IDMAC supports 32-bit address mode.
[    2.538099] dwmmc_exynos 12200000.mmc:: Using internal DMA controller.
[    2.538109] dwmmc_exynos 12200000.mmc:: Version ID is 250a
[    2.538141] dwmmc_exynos 12200000.mmc:: DW MMC controller at irq 94,64 bit host data width,64 deep fifo
[    2.538283] dwmmc_exynos 12200000.mmc:: Got CD GPIO
[    2.538342] dwmmc_exynos 12200000.mmc:: allocated mmc-pwrseq
[    2.561838] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    2.581414] dwmmc_exynos 12200000.mmc:: 1 slots initialized
[    2.581637] dwmmc_exynos 12220000.mmc:: IDMAC supports 32-bit address mode.
[    2.581663] dwmmc_exynos 12220000.mmc:: Using internal DMA controller.
[    2.581673] dwmmc_exynos 12220000.mmc:: Version ID is 250a
[    2.581702] dwmmc_exynos 12220000.mmc:: DW MMC controller at irq 95,64 bit host data width,64 deep fifo
[    2.606645] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    2.626229] dwmmc_exynos 12220000.mmc:: 1 slots initialized
[    2.626957] hidraw: raw HID events driver (C) Jiri Kosina
[    2.627186] usbcore: registered new interface driver usbhid
[    2.627189] usbhid: USB HID core driver
[    2.643169] exynos-nocp: new NoC Probe device registered: 10ca1000.nocp:
[    2.643285] exynos-nocp: new NoC Probe device registered: 10ca1400.nocp:
[    2.643407] exynos-nocp: new NoC Probe device registered: 10ca1800.nocp:
[    2.643523] exynos-nocp: new NoC Probe device registered: 10ca1c00.nocp:
[    2.648301] odroid-audio sound:: dit-hifi <-> 3830000.i2s: mapping ok
[    2.649366] NET: Registered protocol family 17
[    2.649386] NET: Registered protocol family 15
[    2.649434] Key type dns_resolver registered
[    2.649880] Registering SWP/SWPB emulation handler
[    2.650342] registered taskstats version 1
[    2.650346] Loading compiled-in X.509 certificates
[    2.651332] Btrfs loaded, crc32c=crc32c-generic
[    2.660307] Key type encrypted registered
[    2.679675] [drm] Exynos DRM: using 14450000.mixer: device for DMA mapping operations
[    2.679836] exynos-drm exynos-drm: bound 14450000.mixer: (ops 0xc0a6a6b4)
[    2.679970] exynos-drm exynos-drm: bound 14530000.hdmi: (ops 0xc0a6a85c)
[    2.679975] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    2.679978] [drm] No driver support for vblank timestamp query.
[    2.738253] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[    2.812117] Console: switching to colour frame buffer device 240x67
[    2.821593] exynos-drm exynos-drm: fb0:  frame buffer device
[    2.841334] mmc1: new ultra high speed DDR50 SDHC card at address aaaa
[    2.846960] mmcblk1: mmc1:aaaa SL16G 14.8 GiB
[    2.847850]  mmcblk1: p1 p2
[    2.851183] [drm] Initialized exynos 1.0.0 20110530 on minor 0
[    2.851359] exynos-dwc3 soc:usb3-0:: no suspend clk specified
[    2.855300] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[    2.855316] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 3
[    2.855606] xhci-hcd xhci-hcd.2.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x00010010
[    2.855641] xhci-hcd xhci-hcd.2.auto: irq 143, io mem 0x12000000
[    2.855771] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    2.855776] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.855781] usb usb3: Product: xHCI Host Controller
[    2.855786] usb usb3: Manufacturer: Linux 4.9.28-odroidxu4 xhci-hcd
[    2.855790] usb usb3: SerialNumber: xhci-hcd.2.auto
[    2.856222] hub 3-0:1.0: USB hub found
[    2.856245] hub 3-0:1.0: 1 port detected
[    2.856502] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[    2.856511] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 4
[    2.856566] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.856656] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[    2.856661] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.856666] usb usb4: Product: xHCI Host Controller
[    2.856670] usb usb4: Manufacturer: Linux 4.9.28-odroidxu4 xhci-hcd
[    2.856675] usb usb4: SerialNumber: xhci-hcd.2.auto
[    2.857051] hub 4-0:1.0: USB hub found
[    2.857072] hub 4-0:1.0: 1 port detected
[    2.857529] exynos-dwc3 soc:usb3-1:: no suspend clk specified
[    2.859334] xhci-hcd xhci-hcd.5.auto: xHCI Host Controller
[    2.859347] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 5
[    2.859637] xhci-hcd xhci-hcd.5.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x00010010
[    2.859665] xhci-hcd xhci-hcd.5.auto: irq 144, io mem 0x12400000
[    2.859780] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
[    2.859786] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.859790] usb usb5: Product: xHCI Host Controller
[    2.859795] usb usb5: Manufacturer: Linux 4.9.28-odroidxu4 xhci-hcd
[    2.859799] usb usb5: SerialNumber: xhci-hcd.5.auto
[    2.860170] hub 5-0:1.0: USB hub found
[    2.860191] hub 5-0:1.0: 1 port detected
[    2.860442] xhci-hcd xhci-hcd.5.auto: xHCI Host Controller
[    2.860451] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 6
[    2.860503] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.860588] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003
[    2.860594] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.860598] usb usb6: Product: xHCI Host Controller
[    2.860603] usb usb6: Manufacturer: Linux 4.9.28-odroidxu4 xhci-hcd
[    2.860607] usb usb6: SerialNumber: xhci-hcd.5.auto
[    2.860987] hub 6-0:1.0: USB hub found
[    2.861008] hub 6-0:1.0: 1 port detected
[    2.862002] s3c-rtc 101e0000.rtc:: rtc disabled, re-enabling
[    2.862055] s3c-rtc 101e0000.rtc:: warning: invalid RTC value so initializing it
[    2.862105] rtc rtc1: invalid alarm value: 1900-1-2 0:0:0
[    2.862241] s3c-rtc 101e0000.rtc:: rtc core: registered s3c as rtc1
[    2.863505] exynos-bus: new bus device registered: soc:bus_wcore: ( 84000 KHz ~ 400000 KHz)
[    2.864032] exynos-bus: new bus device registered: soc:bus_noc: ( 67000 KHz ~ 100000 KHz)
[    2.864428] exynos-bus: new bus device registered: soc:bus_fsys_apb: (100000 KHz ~ 200000 KHz)
[    2.864695] exynos-bus: new bus device registered: soc:bus_fsys: (100000 KHz ~ 200000 KHz)
[    2.865148] exynos-bus: new bus device registered: soc:bus_fsys2: ( 75000 KHz ~ 150000 KHz)
[    2.865719] exynos-bus: new bus device registered: soc:bus_mfc: ( 96000 KHz ~ 333000 KHz)
[    2.866260] exynos-bus: new bus device registered: soc:bus_gen: ( 89000 KHz ~ 267000 KHz)
[    2.866603] exynos-bus: new bus device registered: soc:bus_peri: ( 67000 KHz ~  67000 KHz)
[    2.867169] exynos-bus: new bus device registered: soc:bus_g2d: ( 84000 KHz ~ 333000 KHz)
[    2.867680] exynos-bus: new bus device registered: soc:bus_g2d_acp: ( 67000 KHz ~ 267000 KHz)
[    2.868186] exynos-bus: new bus device registered: soc:bus_jpeg: ( 75000 KHz ~ 300000 KHz)
[    2.868704] exynos-bus: new bus device registered: soc:bus_jpeg_apb: ( 84000 KHz ~ 167000 KHz)
[    2.869100] exynos-bus: new bus device registered: soc:bus_disp1_fimd: (120000 KHz ~ 200000 KHz)
[    2.869553] exynos-bus: new bus device registered: soc:bus_disp1: (120000 KHz ~ 300000 KHz)
[    2.870003] exynos-bus: new bus device registered: soc:bus_gscl_scaler: (150000 KHz ~ 300000 KHz)
[    2.870567] exynos-bus: new bus device registered: soc:bus_mscl: ( 84000 KHz ~ 400000 KHz)
[    2.871123] input: gpio_keys: as /devices/platform/gpio_keys:/input/input0
[    2.872527] Power domain power-domain@10044120 disable failed
[    2.873224] s5m-rtc s2mps14-rtc: setting system clock to 2000-01-01 00:00:08 UTC (946684808)
[    2.875611] ALSA device list:
[    2.875615]   #0: odroid-snd
[    2.876294] Freeing unused kernel memory: 1024K (c0d00000 - c0e00000)
[    2.899981] systemd-udevd[193]: starting version 215
[    2.976233] usb 2-1: new full-speed USB device number 2 using exynos-ohci
[    3.191213] usb 3-1: new high-speed USB device number 2 using xhci-hcd
[    3.218250] usb 2-1: New USB device found, idVendor=046d, idProduct=c52b
[    3.218259] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.218265] usb 2-1: Product: USB Receiver
[    3.218270] usb 2-1: Manufacturer: Logitech
[    3.242360] logitech-djreceiver 0003:046D:C52B.0003: hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-12120000.usb:-1/input2
[    3.335981] usb 3-1: New USB device found, idVendor=05e3, idProduct=0610
[    3.335987] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.335992] usb 3-1: Product: USB2.0 Hub
[    3.335996] usb 3-1: Manufacturer: GenesysLogic
[    3.369072] hub 3-1:1.0: USB hub found
[    3.369517] hub 3-1:1.0: 2 ports detected
[    3.372656] input: Logitech K400 as /devices/platform/soc:/12120000.usb:/usb2/2-1/2-1:1.2/0003:046D:C52B.0003/0003:046D:4024.0004/input/input1
[    3.373477] logitech-hidpp-device 0003:046D:4024.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech K400] on usb-12120000.usb:-1:1
[    3.451347] usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd
[    3.474028] usb 4-1: New USB device found, idVendor=05e3, idProduct=0616
[    3.474034] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.474038] usb 4-1: Product: USB3.0 Hub
[    3.474043] usb 4-1: Manufacturer: GenesysLogic
[    3.481216] hub 4-1:1.0: USB hub found
[    3.481515] hub 4-1:1.0: 2 ports detected
[    3.860502] EXT4-fs (mmcblk1p1): mounted filesystem with writeback data mode. Opts: (null)
[    3.941277] usb 6-1: new SuperSpeed USB device number 2 using xhci-hcd
[    3.962103] usb 6-1: New USB device found, idVendor=0bda, idProduct=8153
[    3.962110] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[    3.962116] usb 6-1: Product: USB 10/100/1000 LAN
[    3.962121] usb 6-1: Manufacturer: Realtek
[    3.962126] usb 6-1: SerialNumber: 000001000000
[    4.080507] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
[    4.080667] systemd[1]: Detected architecture 'arm'.
[    4.108201] NET: Registered protocol family 10
[    4.108841] systemd[1]: Inserted module 'ipv6'
[    4.110140] systemd[1]: Set hostname to <odroidxu4>.
[    4.124589] usb 6-1: reset SuperSpeed USB device number 2 using xhci-hcd
[    4.202392] r8152 6-1:1.0 eth0: v2.08.0 (2016/12/09)
[    4.202402] r8152 6-1:1.0 eth0: This product is covered by one or more of the following patents:
      US6,570,884, US6,115,776, and US6,327,625.

[    4.227733] random: crng init done
[    4.373138] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
[    4.374544] systemd[1]: Expecting device dev-ttySAC2.device...
[    4.374838] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[    4.374968] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    4.374993] systemd[1]: Starting Remote File Systems (Pre).
[    4.375152] systemd[1]: Reached target Remote File Systems (Pre).
[    4.498457] fuse init (API version 7.26)
[    4.528566] fbtft: module is from the staging directory, the quality is unknown, you have been warned.
[    4.533151] fbtft_device: module is from the staging directory, the quality is unknown, you have been warned.
[    4.533878] spidev spi1.0: spidev spi1.0 1000kHz 8 bits mode=0x00
[    4.533891] spi spi1.1: ads7846 spi1.1 1000kHz 8 bits mode=0x00
[    4.534135] spidev spi1.0: Deleting spi1.0
[    4.534955] fbtft_device: GPIOS used by 'hktft9340':
[    4.534964] fbtft_device: 'reset' = GPIO21
[    4.534970] fbtft_device: 'dc' = GPIO22
[    4.534977] fbtft_device: 'led' = GPIO18
[    4.534989] spi spi1.1: ads7846 spi1.1 1000kHz 8 bits mode=0x00
[    4.535000] spi spi1.0: fb_ili9340 spi1.0 35000kHz 8 bits mode=0x00
[    4.655669] systemd-udevd[349]: starting version 215
[    4.814544] gpiomem-exynos 13400000.gpiomem:: Initialised: GPIO register area is 2
[    4.817818] gpiomem-exynos 13400000.gpiomem:: Initialised: Registers at 0x13400000
[    4.817832] gpiomem-exynos 13400000.gpiomem:: Initialised: Registers at 0x14010000
[    4.824244] fb_ili9340: module is from the staging directory, the quality is unknown, you have been warned.
[    5.251347] graphics fb1: fb_ili9340 frame buffer, 320x240, 150 KiB video memory, 4 KiB DMA buffer memory, fps=20, spi1.0 at 35 MHz
[    5.260093] s5p-secss 10830000.sss:: s5p-sss driver registered
[    5.284213] s5p-mfc 11000000.codec:: Direct firmware load for s5p-mfc-v8.fw failed with error -2
[    5.284228] s5p_mfc_load_firmware:70: Firmware is not present in the /lib/firmware directory nor compiled in kernel
[    5.287013] s5p-mfc 11000000.codec:: Direct firmware load for s5p-mfc-v8.fw failed with error -2
[    5.287024] s5p_mfc_load_firmware:70: Firmware is not present in the /lib/firmware directory nor compiled in kernel
[    5.453533] r8152 6-1:1.0 eth1: renamed from eth0
[    5.476476] systemd-udevd[377]: renamed network interface eth0 to eth1
[    5.521060] EXT4-fs (mmcblk1p1): re-mounted. Opts: commit=600,errors=remount-ro
[    5.654367] Adding 131068k swap on /var/swap.  Priority:-1 extents:1 across:131068k SS
[    8.566290] usb 4-1.1: new SuperSpeed USB device number 3 using xhci-hcd
[    8.587393] usb 4-1.1: New USB device found, idVendor=152d, idProduct=0561
[    8.587401] usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[    8.587407] usb 4-1.1: Product: External Disk 3.0
[    8.587412] usb 4-1.1: Manufacturer: JMicron
[    8.587418] usb 4-1.1: SerialNumber: RANDOM__7AD758C4668B
[    8.601995] scsi host0: uas
[    8.603045] scsi 0:0:0:0: Direct-Access     JMicron  0                8037 PQ: 0 ANSI: 6
[    8.646785] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    9.354436] sd 0:0:0:0: [sda] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB)
[    9.355210] scsi 0:0:0:1: Direct-Access     JMicron  1                8037 PQ: 0 ANSI: 6
[    9.355885] sd 0:0:0:0: [sda] Write Protect is off
[    9.355892] sd 0:0:0:0: [sda] Mode Sense: 67 00 10 08
[    9.356364] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    9.398501]  sda: sda1
[    9.401118] sd 0:0:0:0: [sda] Attached SCSI disk
[    9.416726] sd 0:0:0:1: Attached scsi generic sg1 type 0
[    9.416894] sd 0:0:0:1: [sdb] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB)
[    9.416922] usbcore: registered new interface driver uas
[    9.418042] sd 0:0:0:1: [sdb] Write Protect is off
[    9.418049] sd 0:0:0:1: [sdb] Mode Sense: 67 00 10 08
[    9.418518] sd 0:0:0:1: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    9.464870]  sdb: sdb1
[    9.467425] sd 0:0:0:1: [sdb] Attached SCSI disk
[   94.642214] systemd-journald[308]: Received request to flush runtime journal from PID 1
[  133.385108] usb 4-1.1: USB disconnect, device number 3
[  133.387315] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  133.691502] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=0x00
[  133.762987] sd 0:0:0:1: [sdb] Synchronizing SCSI cache
[  134.061476] sd 0:0:0:1: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=0x00
[  162.060336] logitech-hidpp-device 0003:046D:4024.0004: HID++ 2.0 device connected.
root@odroidxu4:~# dmesg
[    0.000000] Booting Linux on physical CPU 0x100
[    0.000000] Linux version 4.9.28-odroidxu4 (root@opennms) (gcc version 6.3.1 20170109 (Linaro GCC 6.3-2017.02) ) #8 SMP PREEMPT Fri May 19 09:25:51 CEST 2017
[    0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=10c5387d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt:Machine model: Hardkernel Odroid XU4
[    0.000000] cma: Reserved 128 MiB at 0xb6800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] Samsung CPU ID: 0xe5422001
[    0.000000] On node 0 totalpages: 518656
[    0.000000] free_area_init_node: node 0, pgdat c0e56640, node_mem_map eee25000
[    0.000000]   Normal zone: 1728 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 196608 pages, LIFO batch:31
[    0.000000]   HighMem zone: 322048 pages, LIFO batch:31
[    0.000000] Running under secure firmware.
[    0.000000] percpu: Embedded 14 pages/cpu @eed7f000 s26700 r8192 d22452 u57344
[    0.000000] pcpu-alloc: s26700 r8192 d22452 u57344 alloc=14*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: 516928
[    0.000000] Kernel command line: console=tty1 vt.global_cursor_default=0 consoleblank=0 loglevel=1 root=UUID=b137c027-10cf-41d5-8a72-fd546b628157 rootwait rw fsck.repair=yes smsc95xx.macaddr=00:1e:06:61:7a:55 governor=performance hdmi_tx_amp_lvl=31 hdmi_tx_lvl_ch0=3 hdmi_tx_lvl_ch1=3 hdmi_tx_lvl_ch2=3 hdmi_tx_emp_lvl=6 hdmi_clk_amp_lvl=31 hdmi_tx_res=0 HPD=true vout=hdmi s5p_mfc.mem=16M
[    0.000000] hdmi: using HDMI mode
[    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: 1904540K/2074624K available (9216K kernel code, 348K rwdata, 2336K rodata, 1024K init, 341K bss, 39012K reserved, 131072K cma-reserved, 1157120K highmem)
[    0.000000] Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
    lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc0a00000   (10208 kB)
      .init : 0xc0d00000 - 0xc0e00000   (1024 kB)
      .data : 0xc0e00000 - 0xc0e572a0   ( 349 kB)
       .bss : 0xc0e59000 - 0xc0eae5bc   ( 342 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[    0.000000] hperf_hmp: fast CPUs mask: 000000F0
[    0.000000] hperf_hmp: slow CPUs mask: 0000000F
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]    Build-time adjustment of leaf fanout to 32.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    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.001431] Console: colour dummy device 80x30
[    0.001448] console [tty1] enabled
[    0.001471] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=120000)
[    0.001487] pid_max: default: 32768 minimum: 301
[    0.001693] Security Framework initialized
[    0.001704] AppArmor: AppArmor disabled by boot time parameter
[    0.001762] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001771] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.002724] CPU: Testing write buffer coherency: ok
[    0.003530] CPU0: update cpu_capacity 551
[    0.003540] CPU0: thread -1, cpu 0, socket 1, mpidr 80000100
[    0.003675] Setting up static identity map for 0x40100000 - 0x40100058
[    0.004336] ARM CCI driver probed
[    0.004554] Exynos MCPM support installed
[    0.085327] CPU1: update cpu_capacity 551
[    0.085335] CPU1: thread -1, cpu 1, socket 1, mpidr 80000101
[    0.086295] CPU2: update cpu_capacity 551
[    0.086302] CPU2: thread -1, cpu 2, socket 1, mpidr 80000102
[    0.087178] CPU3: update cpu_capacity 551
[    0.087185] CPU3: thread -1, cpu 3, socket 1, mpidr 80000103
[    0.088080] CPU4: update cpu_capacity 1496
[    0.088088] CPU4: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.089213] CPU5: update cpu_capacity 1496
[    0.089220] CPU5: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.090208] CPU6: update cpu_capacity 1496
[    0.090215] CPU6: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.091129] CPU7: update cpu_capacity 1496
[    0.091135] CPU7: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.091252] Brought up 8 CPUs
[    0.091264] SMP: Total of 8 processors activated (384.00 BogoMIPS).
[    0.091272] CPU: WARNING: CPU(s) started in wrong/inconsistent modes (primary CPU mode 0x1a)
[    0.091277] CPU: This may indicate a broken bootloader or firmware.
[    0.092792] devtmpfs: initialized
[    0.118599] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
[    0.118801] hperf_hmp: registered cpufreq transition notifier
[    0.118982] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302231375000 ns
[    0.118997] futex hash table entries: 2048 (order: 5, 131072 bytes)
[    0.121384] xor: measuring software checksum speed
[    0.169964]    arm4regs  :  1516.800 MB/sec
[    0.219965]    8regs     :  1126.400 MB/sec
[    0.269966]    32regs    :  1173.600 MB/sec
[    0.319965]    neon      :  2199.200 MB/sec
[    0.319973] xor: using function: neon (2199.200 MB/sec)
[    0.320063] pinctrl core: initialized pinctrl subsystem
[    0.321941] NET: Registered protocol family 16
[    0.323713] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.339244] cpuidle: using governor menu
[    0.355423] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.355431] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.365928] exynos-audss-clk 3810000.audss-clock-controller:: epll 180633609
[    0.368058] iommu: Adding device 10850000.g2d: to group 0
[    0.373322] iommu: Adding device 11000000.codec: to group 1
[    0.403299] iommu: Adding device 14450000.mixer: to group 2
[    0.403784] iommu: Adding device 11c00000.rotator: to group 3
[    0.407186] random: fast init done
[    0.408294] iommu: Adding device 13e00000.video-scaler: to group 4
[    0.408777] iommu: Adding device 13e10000.video-scaler: to group 5
[    0.409263] iommu: Adding device 11f50000.jpeg: to group 6
[    0.409751] iommu: Adding device 11f60000.jpeg: to group 7
[    0.410080] EXYNOS5420 PMU initialized
[    0.525144] raid6: int32x1  gen()   178 MB/s
[    0.610100] raid6: int32x1  xor()   218 MB/s
[    0.695089] raid6: int32x2  gen()   253 MB/s
[    0.780077] raid6: int32x2  xor()   264 MB/s
[    0.865035] raid6: int32x4  gen()   342 MB/s
[    0.950041] raid6: int32x4  xor()   265 MB/s
[    1.034997] raid6: int32x8  gen()   372 MB/s
[    1.120039] raid6: int32x8  xor()   262 MB/s
[    1.205010] raid6: neonx1   gen()   717 MB/s
[    1.289998] raid6: neonx1   xor()   628 MB/s
[    1.375009] raid6: neonx2   gen()  1061 MB/s
[    1.459987] raid6: neonx2   xor()   942 MB/s
[    1.545014] raid6: neonx4   gen()  1357 MB/s
[    1.630011] raid6: neonx4   xor()   992 MB/s
[    1.715016] raid6: neonx8   gen()  1309 MB/s
[    1.800017] raid6: neonx8   xor()   980 MB/s
[    1.800024] raid6: using algorithm neonx4 gen() 1357 MB/s
[    1.800031] raid6: .... xor() 992 MB/s, rmw enabled
[    1.800037] raid6: using intx1 recovery algorithm
[    1.801753] SCSI subsystem initialized
[    1.802019] usbcore: registered new interface driver usbfs
[    1.802098] usbcore: registered new interface driver hub
[    1.802267] usbcore: registered new device driver usb
[    1.803007] s3c-i2c 12c70000.i2c:: slave address 0x00
[    1.803020] s3c-i2c 12c70000.i2c:: bus frequency set to 378 KHz
[    1.803337] s3c-i2c 12c70000.i2c:: i2c-1: S3C I2C adapter
[    1.803491] s3c-i2c 12c80000.i2c:: slave address 0x00
[    1.803503] s3c-i2c 12c80000.i2c:: bus frequency set to 65 KHz
[    1.803962] s3c-i2c 12c80000.i2c:: i2c-2: S3C I2C adapter
[    1.804365] media: Linux media interface: v0.10
[    1.804421] Linux video capture interface: v2.00
[    1.804874] Advanced Linux Sound Architecture Driver Initialized.
[    1.806165] clocksource: Switched to clocksource mct-frc
[    1.806351] VFS: Disk quotas dquot_6.6.0
[    1.806416] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.823729] NET: Registered protocol family 2
[    1.824372] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    1.824446] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    1.824600] TCP: Hash tables configured (established 8192 bind 8192)
[    1.824648] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    1.824683] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    1.824897] NET: Registered protocol family 1
[    1.825538] RPC: Registered named UNIX socket transport module.
[    1.825545] RPC: Registered udp transport module.
[    1.825551] RPC: Registered tcp transport module.
[    1.825558] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.825770] Trying to unpack rootfs image as initramfs...
[    2.116657] Freeing initrd memory: 5188K (c2000000 - c2511000)
[    2.119790] audit: initializing netlink subsys (disabled)
[    2.119833] audit: type=2000 audit(2.115:1): initialized
[    2.120129] Initialise system trusted keyrings
[    2.120656] workingset: timestamp_bits=14 max_order=19 bucket_order=5
[    2.135210] NFS: Registering the id_resolver key type
[    2.135231] Key type id_resolver registered
[    2.135238] Key type id_legacy registered
[    2.135254] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    2.135266] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    2.136495] romfs: ROMFS MTD (C) 2007 Red Hat, Inc.
[    2.137502] JFS: nTxBlock = 8192, nTxLock = 65536
[    2.142558] SGI XFS with ACLs, security attributes, realtime, no debug enabled
[    2.152762] Key type asymmetric registered
[    2.152818] bounce: pool size: 64 pages
[    2.153050] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)
[    2.153239] io scheduler noop registered
[    2.153247] io scheduler deadline registered
[    2.153481] io scheduler cfq registered (default)
[    2.156740] 12130000.phy: supply vbus not found, using dummy regulator
[    2.157857] 12100000.phy: supply vbus not found, using dummy regulator
[    2.157929] 12100000.phy: supply vbus-boost not found, using dummy regulator
[    2.158367] 12500000.phy: supply vbus not found, using dummy regulator
[    2.158438] 12500000.phy: supply vbus-boost not found, using dummy regulator
[    2.163902] dma-pl330 3880000.adma: Loaded driver for PL330 DMAC-241330
[    2.163913] dma-pl330 3880000.adma:    DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6
[    2.168029] dma-pl330 121a0000.pdma: Loaded driver for PL330 DMAC-241330
[    2.168040] dma-pl330 121a0000.pdma:    DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    2.172208] dma-pl330 121b0000.pdma: Loaded driver for PL330 DMAC-241330
[    2.172219] dma-pl330 121b0000.pdma:    DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    2.173383] dma-pl330 10800000.mdma: Loaded driver for PL330 DMAC-241330
[    2.173393] dma-pl330 10800000.mdma:    DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32
[    2.261330] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    2.264104] 12c00000.serial:: ttySAC0 at MMIO 0x12c00000 (irq = 76, base_baud = 0) is a S3C6400/10
[    2.264580] 12c10000.serial:: ttySAC1 at MMIO 0x12c10000 (irq = 77, base_baud = 0) is a S3C6400/10
[    2.265029] 12c20000.serial:: ttySAC2 at MMIO 0x12c20000 (irq = 78, base_baud = 0) is a S3C6400/10
[    2.265478] 12c30000.serial:: ttySAC3 at MMIO 0x12c30000 (irq = 79, base_baud = 0) is a S3C6400/10
[    2.266958] [drm] Initialized
[    2.268560] exynos-hdmi 14530000.hdmi:: Failed to get supply 'vdd': -517
[    2.269792] exynos-rot 11c00000.rotator:: The exynos rotator is probed successfully
[    2.270513] exynos-drm-ipp exynos-drm-ipp: drm ipp registered successfully.
[    2.275017] mali 11800000.mali:: GPU identified as 0x0620 r0p1 status 0
[    2.275947] devfreq 11800000.mali:: Couldn't update frequency transition information.
[    2.275959] mali 11800000.mali:: could not find power_model node
[    2.276747] mali 11800000.mali:: Probed as mali0
[    2.292661] brd: module loaded
[    2.302325] loop: module loaded
[    2.303210] libphy: Fixed MDIO Bus: probed
[    2.303583] usbcore: registered new interface driver r8152
[    2.303635] usbcore: registered new interface driver cdc_ether
[    2.303687] usbcore: registered new interface driver cdc_subset
[    2.304228] exynos-dwc3 soc:usb3-0:: no suspend clk specified
[    2.304327] exynos-dwc3 soc:usb3-1:: no suspend clk specified
[    2.305588] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.305595] ehci-exynos: EHCI EXYNOS driver
[    2.305990] exynos-ehci 12110000.usb:: EHCI Host Controller
[    2.306019] exynos-ehci 12110000.usb:: new USB bus registered, assigned bus number 1
[    2.306294] exynos-ehci 12110000.usb:: irq 91, io mem 0x12110000
[    2.321208] exynos-ehci 12110000.usb:: USB 2.0 started, EHCI 1.00
[    2.321430] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.321441] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.321449] usb usb1: Product: EHCI Host Controller
[    2.321458] usb usb1: Manufacturer: Linux 4.9.28-odroidxu4 ehci_hcd
[    2.321466] usb usb1: SerialNumber: 12110000.usb:
[    2.322247] hub 1-0:1.0: USB hub found
[    2.322289] hub 1-0:1.0: 3 ports detected
[    2.323350] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    2.323369] ohci-exynos: OHCI EXYNOS driver
[    2.323626] exynos-ohci 12120000.usb:: USB Host Controller
[    2.323653] exynos-ohci 12120000.usb:: new USB bus registered, assigned bus number 2
[    2.323768] exynos-ohci 12120000.usb:: irq 91, io mem 0x12120000
[    2.385427] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[    2.385438] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.385446] usb usb2: Product: USB Host Controller
[    2.385454] usb usb2: Manufacturer: Linux 4.9.28-odroidxu4 ohci_hcd
[    2.385462] usb usb2: SerialNumber: 12120000.usb:
[    2.386248] hub 2-0:1.0: USB hub found
[    2.386291] hub 2-0:1.0: 3 ports detected
[    2.387931] usbcore: registered new interface driver cdc_wdm
[    2.388040] usbcore: registered new interface driver usb-storage
[    2.388858] mousedev: PS/2 mouse device common for all mice
[    2.390454] i2c /dev entries driver
[    2.394038] LDO27: mapping for mode 1 not defined
[    2.394075] LDO28: mapping for mode 1 not defined
[    2.394111] LDO30: mapping for mode 1 not defined
[    2.406449] vdd_ldo9: Bringing 3300000uV into 3000000-3000000uV
[    2.418591] vdd_ldo15: Bringing 3300000uV into 3100000-3100000uV
[    2.427517] vdd_sd: Bringing 3300000uV into 2800000-2800000uV
[    2.446384] vdd_ldo30: Bringing 1800000uV into 3300000-3300000uV
[    2.488712] s5m-rtc s2mps14-rtc: rtc core: registered s5m-rtc as rtc0
[    2.491886] IR NEC protocol handler initialized
[    2.491893] IR RC5(x/sz) protocol handler initialized
[    2.491900] IR RC6 protocol handler initialized
[    2.491906] IR JVC protocol handler initialized
[    2.491913] IR Sony protocol handler initialized
[    2.491919] IR SANYO protocol handler initialized
[    2.491925] IR Sharp protocol handler initialized
[    2.491932] IR MCE Keyboard/mouse protocol handler initialized
[    2.491938] IR XMP protocol handler initialized
[    2.492979] s5p-jpeg 11f50000.jpeg:: encoder device registered as /dev/video0
[    2.493220] s5p-jpeg 11f50000.jpeg:: decoder device registered as /dev/video1
[    2.493227] s5p-jpeg 11f50000.jpeg:: Samsung S5P JPEG codec
[    2.493598] s5p-jpeg 11f60000.jpeg:: encoder device registered as /dev/video2
[    2.493823] s5p-jpeg 11f60000.jpeg:: decoder device registered as /dev/video3
[    2.493830] s5p-jpeg 11f60000.jpeg:: Samsung S5P JPEG codec
[    2.511986] s5p-mfc 11000000.codec:: preallocated 16 MiB buffer for the firmware and context buffers
[    2.512262] s5p-mfc 11000000.codec:: decoder registered as /dev/video10
[    2.512485] s5p-mfc 11000000.codec:: encoder registered as /dev/video11
[    2.522366] s3c2410-wdt 101d0000.watchdog:: watchdog inactive, reset disabled, irq disabled
[    2.523024] device-mapper: uevent: version 1.0.3
[    2.523500] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised: dm-devel@redhat.com
[    2.525849] core: _opp_supported_by_regulators: OPP minuV: 1135000 maxuV: 1135000, not supported by regulator
[    2.525859] cpu cpu0: _opp_add: OPP not supported by regulators (1100000000)
[    2.537273] sdhci: Secure Digital Host Controller Interface driver
[    2.537277] sdhci: Copyright(c) Pierre Ossman
[    2.537486] Synopsys Designware Multimedia Card Interface Driver
[    2.538047] dwmmc_exynos 12200000.mmc:: IDMAC supports 32-bit address mode.
[    2.538099] dwmmc_exynos 12200000.mmc:: Using internal DMA controller.
[    2.538109] dwmmc_exynos 12200000.mmc:: Version ID is 250a
[    2.538141] dwmmc_exynos 12200000.mmc:: DW MMC controller at irq 94,64 bit host data width,64 deep fifo
[    2.538283] dwmmc_exynos 12200000.mmc:: Got CD GPIO
[    2.538342] dwmmc_exynos 12200000.mmc:: allocated mmc-pwrseq
[    2.561838] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    2.581414] dwmmc_exynos 12200000.mmc:: 1 slots initialized
[    2.581637] dwmmc_exynos 12220000.mmc:: IDMAC supports 32-bit address mode.
[    2.581663] dwmmc_exynos 12220000.mmc:: Using internal DMA controller.
[    2.581673] dwmmc_exynos 12220000.mmc:: Version ID is 250a
[    2.581702] dwmmc_exynos 12220000.mmc:: DW MMC controller at irq 95,64 bit host data width,64 deep fifo
[    2.606645] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    2.626229] dwmmc_exynos 12220000.mmc:: 1 slots initialized
[    2.626957] hidraw: raw HID events driver (C) Jiri Kosina
[    2.627186] usbcore: registered new interface driver usbhid
[    2.627189] usbhid: USB HID core driver
[    2.643169] exynos-nocp: new NoC Probe device registered: 10ca1000.nocp:
[    2.643285] exynos-nocp: new NoC Probe device registered: 10ca1400.nocp:
[    2.643407] exynos-nocp: new NoC Probe device registered: 10ca1800.nocp:
[    2.643523] exynos-nocp: new NoC Probe device registered: 10ca1c00.nocp:
[    2.648301] odroid-audio sound:: dit-hifi <-> 3830000.i2s: mapping ok
[    2.649366] NET: Registered protocol family 17
[    2.649386] NET: Registered protocol family 15
[    2.649434] Key type dns_resolver registered
[    2.649880] Registering SWP/SWPB emulation handler
[    2.650342] registered taskstats version 1
[    2.650346] Loading compiled-in X.509 certificates
[    2.651332] Btrfs loaded, crc32c=crc32c-generic
[    2.660307] Key type encrypted registered
[    2.679675] [drm] Exynos DRM: using 14450000.mixer: device for DMA mapping operations
[    2.679836] exynos-drm exynos-drm: bound 14450000.mixer: (ops 0xc0a6a6b4)
[    2.679970] exynos-drm exynos-drm: bound 14530000.hdmi: (ops 0xc0a6a85c)
[    2.679975] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    2.679978] [drm] No driver support for vblank timestamp query.
[    2.738253] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[    2.812117] Console: switching to colour frame buffer device 240x67
[    2.821593] exynos-drm exynos-drm: fb0:  frame buffer device
[    2.841334] mmc1: new ultra high speed DDR50 SDHC card at address aaaa
[    2.846960] mmcblk1: mmc1:aaaa SL16G 14.8 GiB
[    2.847850]  mmcblk1: p1 p2
[    2.851183] [drm] Initialized exynos 1.0.0 20110530 on minor 0
[    2.851359] exynos-dwc3 soc:usb3-0:: no suspend clk specified
[    2.855300] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[    2.855316] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 3
[    2.855606] xhci-hcd xhci-hcd.2.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x00010010
[    2.855641] xhci-hcd xhci-hcd.2.auto: irq 143, io mem 0x12000000
[    2.855771] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    2.855776] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.855781] usb usb3: Product: xHCI Host Controller
[    2.855786] usb usb3: Manufacturer: Linux 4.9.28-odroidxu4 xhci-hcd
[    2.855790] usb usb3: SerialNumber: xhci-hcd.2.auto
[    2.856222] hub 3-0:1.0: USB hub found
[    2.856245] hub 3-0:1.0: 1 port detected
[    2.856502] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[    2.856511] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 4
[    2.856566] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.856656] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[    2.856661] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.856666] usb usb4: Product: xHCI Host Controller
[    2.856670] usb usb4: Manufacturer: Linux 4.9.28-odroidxu4 xhci-hcd
[    2.856675] usb usb4: SerialNumber: xhci-hcd.2.auto
[    2.857051] hub 4-0:1.0: USB hub found
[    2.857072] hub 4-0:1.0: 1 port detected
[    2.857529] exynos-dwc3 soc:usb3-1:: no suspend clk specified
[    2.859334] xhci-hcd xhci-hcd.5.auto: xHCI Host Controller
[    2.859347] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 5
[    2.859637] xhci-hcd xhci-hcd.5.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x00010010
[    2.859665] xhci-hcd xhci-hcd.5.auto: irq 144, io mem 0x12400000
[    2.859780] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
[    2.859786] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.859790] usb usb5: Product: xHCI Host Controller
[    2.859795] usb usb5: Manufacturer: Linux 4.9.28-odroidxu4 xhci-hcd
[    2.859799] usb usb5: SerialNumber: xhci-hcd.5.auto
[    2.860170] hub 5-0:1.0: USB hub found
[    2.860191] hub 5-0:1.0: 1 port detected
[    2.860442] xhci-hcd xhci-hcd.5.auto: xHCI Host Controller
[    2.860451] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 6
[    2.860503] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.860588] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003
[    2.860594] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.860598] usb usb6: Product: xHCI Host Controller
[    2.860603] usb usb6: Manufacturer: Linux 4.9.28-odroidxu4 xhci-hcd
[    2.860607] usb usb6: SerialNumber: xhci-hcd.5.auto
[    2.860987] hub 6-0:1.0: USB hub found
[    2.861008] hub 6-0:1.0: 1 port detected
[    2.862002] s3c-rtc 101e0000.rtc:: rtc disabled, re-enabling
[    2.862055] s3c-rtc 101e0000.rtc:: warning: invalid RTC value so initializing it
[    2.862105] rtc rtc1: invalid alarm value: 1900-1-2 0:0:0
[    2.862241] s3c-rtc 101e0000.rtc:: rtc core: registered s3c as rtc1
[    2.863505] exynos-bus: new bus device registered: soc:bus_wcore: ( 84000 KHz ~ 400000 KHz)
[    2.864032] exynos-bus: new bus device registered: soc:bus_noc: ( 67000 KHz ~ 100000 KHz)
[    2.864428] exynos-bus: new bus device registered: soc:bus_fsys_apb: (100000 KHz ~ 200000 KHz)
[    2.864695] exynos-bus: new bus device registered: soc:bus_fsys: (100000 KHz ~ 200000 KHz)
[    2.865148] exynos-bus: new bus device registered: soc:bus_fsys2: ( 75000 KHz ~ 150000 KHz)
[    2.865719] exynos-bus: new bus device registered: soc:bus_mfc: ( 96000 KHz ~ 333000 KHz)
[    2.866260] exynos-bus: new bus device registered: soc:bus_gen: ( 89000 KHz ~ 267000 KHz)
[    2.866603] exynos-bus: new bus device registered: soc:bus_peri: ( 67000 KHz ~  67000 KHz)
[    2.867169] exynos-bus: new bus device registered: soc:bus_g2d: ( 84000 KHz ~ 333000 KHz)
[    2.867680] exynos-bus: new bus device registered: soc:bus_g2d_acp: ( 67000 KHz ~ 267000 KHz)
[    2.868186] exynos-bus: new bus device registered: soc:bus_jpeg: ( 75000 KHz ~ 300000 KHz)
[    2.868704] exynos-bus: new bus device registered: soc:bus_jpeg_apb: ( 84000 KHz ~ 167000 KHz)
[    2.869100] exynos-bus: new bus device registered: soc:bus_disp1_fimd: (120000 KHz ~ 200000 KHz)
[    2.869553] exynos-bus: new bus device registered: soc:bus_disp1: (120000 KHz ~ 300000 KHz)
[    2.870003] exynos-bus: new bus device registered: soc:bus_gscl_scaler: (150000 KHz ~ 300000 KHz)
[    2.870567] exynos-bus: new bus device registered: soc:bus_mscl: ( 84000 KHz ~ 400000 KHz)
[    2.871123] input: gpio_keys: as /devices/platform/gpio_keys:/input/input0
[    2.872527] Power domain power-domain@10044120 disable failed
[    2.873224] s5m-rtc s2mps14-rtc: setting system clock to 2000-01-01 00:00:08 UTC (946684808)
[    2.875611] ALSA device list:
[    2.875615]   #0: odroid-snd
[    2.876294] Freeing unused kernel memory: 1024K (c0d00000 - c0e00000)
[    2.899981] systemd-udevd[193]: starting version 215
[    2.976233] usb 2-1: new full-speed USB device number 2 using exynos-ohci
[    3.191213] usb 3-1: new high-speed USB device number 2 using xhci-hcd
[    3.218250] usb 2-1: New USB device found, idVendor=046d, idProduct=c52b
[    3.218259] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.218265] usb 2-1: Product: USB Receiver
[    3.218270] usb 2-1: Manufacturer: Logitech
[    3.242360] logitech-djreceiver 0003:046D:C52B.0003: hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-12120000.usb:-1/input2
[    3.335981] usb 3-1: New USB device found, idVendor=05e3, idProduct=0610
[    3.335987] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.335992] usb 3-1: Product: USB2.0 Hub
[    3.335996] usb 3-1: Manufacturer: GenesysLogic
[    3.369072] hub 3-1:1.0: USB hub found
[    3.369517] hub 3-1:1.0: 2 ports detected
[    3.372656] input: Logitech K400 as /devices/platform/soc:/12120000.usb:/usb2/2-1/2-1:1.2/0003:046D:C52B.0003/0003:046D:4024.0004/input/input1
[    3.373477] logitech-hidpp-device 0003:046D:4024.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech K400] on usb-12120000.usb:-1:1
[    3.451347] usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd
[    3.474028] usb 4-1: New USB device found, idVendor=05e3, idProduct=0616
[    3.474034] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.474038] usb 4-1: Product: USB3.0 Hub
[    3.474043] usb 4-1: Manufacturer: GenesysLogic
[    3.481216] hub 4-1:1.0: USB hub found
[    3.481515] hub 4-1:1.0: 2 ports detected
[    3.860502] EXT4-fs (mmcblk1p1): mounted filesystem with writeback data mode. Opts: (null)
[    3.941277] usb 6-1: new SuperSpeed USB device number 2 using xhci-hcd
[    3.962103] usb 6-1: New USB device found, idVendor=0bda, idProduct=8153
[    3.962110] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[    3.962116] usb 6-1: Product: USB 10/100/1000 LAN
[    3.962121] usb 6-1: Manufacturer: Realtek
[    3.962126] usb 6-1: SerialNumber: 000001000000
[    4.080507] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
[    4.080667] systemd[1]: Detected architecture 'arm'.
[    4.108201] NET: Registered protocol family 10
[    4.108841] systemd[1]: Inserted module 'ipv6'
[    4.110140] systemd[1]: Set hostname to <odroidxu4>.
[    4.124589] usb 6-1: reset SuperSpeed USB device number 2 using xhci-hcd
[    4.202392] r8152 6-1:1.0 eth0: v2.08.0 (2016/12/09)
[    4.202402] r8152 6-1:1.0 eth0: This product is covered by one or more of the following patents:
      US6,570,884, US6,115,776, and US6,327,625.

[    4.227733] random: crng init done
[    4.373138] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
[    4.374544] systemd[1]: Expecting device dev-ttySAC2.device...
[    4.374838] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[    4.374968] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    4.374993] systemd[1]: Starting Remote File Systems (Pre).
[    4.375152] systemd[1]: Reached target Remote File Systems (Pre).
[    4.498457] fuse init (API version 7.26)
[    4.528566] fbtft: module is from the staging directory, the quality is unknown, you have been warned.
[    4.533151] fbtft_device: module is from the staging directory, the quality is unknown, you have been warned.
[    4.533878] spidev spi1.0: spidev spi1.0 1000kHz 8 bits mode=0x00
[    4.533891] spi spi1.1: ads7846 spi1.1 1000kHz 8 bits mode=0x00
[    4.534135] spidev spi1.0: Deleting spi1.0
[    4.534955] fbtft_device: GPIOS used by 'hktft9340':
[    4.534964] fbtft_device: 'reset' = GPIO21
[    4.534970] fbtft_device: 'dc' = GPIO22
[    4.534977] fbtft_device: 'led' = GPIO18
[    4.534989] spi spi1.1: ads7846 spi1.1 1000kHz 8 bits mode=0x00
[    4.535000] spi spi1.0: fb_ili9340 spi1.0 35000kHz 8 bits mode=0x00
[    4.655669] systemd-udevd[349]: starting version 215
[    4.814544] gpiomem-exynos 13400000.gpiomem:: Initialised: GPIO register area is 2
[    4.817818] gpiomem-exynos 13400000.gpiomem:: Initialised: Registers at 0x13400000
[    4.817832] gpiomem-exynos 13400000.gpiomem:: Initialised: Registers at 0x14010000
[    4.824244] fb_ili9340: module is from the staging directory, the quality is unknown, you have been warned.
[    5.251347] graphics fb1: fb_ili9340 frame buffer, 320x240, 150 KiB video memory, 4 KiB DMA buffer memory, fps=20, spi1.0 at 35 MHz
[    5.260093] s5p-secss 10830000.sss:: s5p-sss driver registered
[    5.284213] s5p-mfc 11000000.codec:: Direct firmware load for s5p-mfc-v8.fw failed with error -2
[    5.284228] s5p_mfc_load_firmware:70: Firmware is not present in the /lib/firmware directory nor compiled in kernel
[    5.287013] s5p-mfc 11000000.codec:: Direct firmware load for s5p-mfc-v8.fw failed with error -2
[    5.287024] s5p_mfc_load_firmware:70: Firmware is not present in the /lib/firmware directory nor compiled in kernel
[    5.453533] r8152 6-1:1.0 eth1: renamed from eth0
[    5.476476] systemd-udevd[377]: renamed network interface eth0 to eth1
[    5.521060] EXT4-fs (mmcblk1p1): re-mounted. Opts: commit=600,errors=remount-ro
[    5.654367] Adding 131068k swap on /var/swap.  Priority:-1 extents:1 across:131068k SS
[    8.566290] usb 4-1.1: new SuperSpeed USB device number 3 using xhci-hcd
[    8.587393] usb 4-1.1: New USB device found, idVendor=152d, idProduct=0561
[    8.587401] usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[    8.587407] usb 4-1.1: Product: External Disk 3.0
[    8.587412] usb 4-1.1: Manufacturer: JMicron
[    8.587418] usb 4-1.1: SerialNumber: RANDOM__7AD758C4668B
[    8.601995] scsi host0: uas
[    8.603045] scsi 0:0:0:0: Direct-Access     JMicron  0                8037 PQ: 0 ANSI: 6
[    8.646785] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    9.354436] sd 0:0:0:0: [sda] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB)
[    9.355210] scsi 0:0:0:1: Direct-Access     JMicron  1                8037 PQ: 0 ANSI: 6
[    9.355885] sd 0:0:0:0: [sda] Write Protect is off
[    9.355892] sd 0:0:0:0: [sda] Mode Sense: 67 00 10 08
[    9.356364] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    9.398501]  sda: sda1
[    9.401118] sd 0:0:0:0: [sda] Attached SCSI disk
[    9.416726] sd 0:0:0:1: Attached scsi generic sg1 type 0
[    9.416894] sd 0:0:0:1: [sdb] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB)
[    9.416922] usbcore: registered new interface driver uas
[    9.418042] sd 0:0:0:1: [sdb] Write Protect is off
[    9.418049] sd 0:0:0:1: [sdb] Mode Sense: 67 00 10 08
[    9.418518] sd 0:0:0:1: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    9.464870]  sdb: sdb1
[    9.467425] sd 0:0:0:1: [sdb] Attached SCSI disk
[   94.642214] systemd-journald[308]: Received request to flush runtime journal from PID 1
[  133.385108] usb 4-1.1: USB disconnect, device number 3
[  133.387315] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  133.691502] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=0x00
[  133.762987] sd 0:0:0:1: [sdb] Synchronizing SCSI cache
[  134.061476] sd 0:0:0:1: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=0x00
[  162.060336] logitech-hidpp-device 0003:046D:4024.0004: HID++ 2.0 device connected.


Code: Select all
root@odroidxu4:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev             10M     0   10M   0% /dev
tmpfs           399M  6.9M  392M   2% /run
/dev/mmcblk1p1  3.7G  1.4G  2.3G  38% /
tmpfs           997M     0  997M   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           997M     0  997M   0% /sys/fs/cgroup
tmpfs           997M     0  997M   0% /tmp
folder2ram      997M  4.2M  993M   1% /var/log
folder2ram      997M     0  997M   0% /var/tmp
folder2ram      997M  344K  997M   1% /var/lib/openmediavault/rrd
folder2ram      997M  724K  997M   1% /var/spool
folder2ram      997M   14M  984M   2% /var/lib/rrdcached
folder2ram      997M  8.0K  997M   1% /var/lib/monit
folder2ram      997M     0  997M   0% /var/lib/php5
folder2ram      997M     0  997M   0% /var/lib/netatalk/CNID
tmpfs           200M     0  200M   0% /run/user/0
User avatar
odroid
Site Admin
 
Posts: 24367
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: Getting UAS working on HK 4.9

Unread postby crashoverride » Wed May 24, 2017 2:28 pm

Code: Select all
[    5.654367] Adding 131068k swap on /var/swap.  Priority:-1 extents:1 across:131068k SS

Since there is no mount for /var or /var/swap. I guess its using the SD/eMMC card for swap (on /).

This implies the issue affecting the HDD is also affecting the SD/eMMC. If correct, this implies a XU4 fault. There should be some way to "stress test" the XU4 without involving USB/HDD. Perhaps someone has some suggestions?
crashoverride
 
Posts: 3060
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1

Re: Getting UAS working on HK 4.9

Unread postby Kosmatik » Wed May 24, 2017 11:55 pm

My install was on an eMMC card.

I did a little more tests today, this is what happens when cloudshell2 is plugged into the top USB port:

Code: Select all
[    7.038747] usb 4-1.2: UAS is blacklisted for this device, using usb-storage instead
[    7.038756] usb-storage 4-1.2:1.0: USB Mass Storage device detected
[    7.039000] usb-storage 4-1.2:1.0: Quirks match for vid 152d pid 0561: 800000
[    7.039064] scsi host0: usb-storage 4-1.2:1.0
[    7.045788] usbcore: registered new interface driver uas
[    8.616309] usb 4-1.2: Device not responding to setup address.
[    8.826254] usb 4-1.2: Device not responding to setup address.
[    9.036171] usb 4-1.2: device not accepting address 3, error -71
[    9.996302] usb 4-1.2: Device not responding to setup address.
[   10.206259] usb 4-1.2: Device not responding to setup address.
[   10.416172] usb 4-1.2: device not accepting address 3, error -71
[   11.557371] usb 4-1-port2: Cannot enable. Maybe the USB cable is bad?
[   11.736192] usb 4-1.2: USB disconnect, device number 3
[   12.656270] usb 4-1.2: Device not responding to setup address.
[   12.866258] usb 4-1.2: Device not responding to setup address.
[   13.076192] usb 4-1.2: device not accepting address 4, error -71
[   14.036256] usb 4-1.2: new SuperSpeed USB device number 5 using xhci-hcd
[   14.057314] usb 4-1.2: New USB device found, idVendor=152d, idProduct=0561
[   14.057322] usb 4-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[   14.057328] usb 4-1.2: Product: External Disk 3.0
[   14.057334] usb 4-1.2: Manufacturer: JMicron
[   14.057339] usb 4-1.2: SerialNumber: DB01234567D2
[   14.058248] usb 4-1.2: UAS is blacklisted for this device, using usb-storage instead
[   14.058256] usb-storage 4-1.2:1.0: USB Mass Storage device detected
[   14.058429] usb-storage 4-1.2:1.0: Quirks match for vid 152d pid 0561: 800000
[   14.058491] scsi host0: usb-storage 4-1.2:1.0
[   15.406291] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[   15.446508] scsi 0:0:0:0: Direct-Access     JMicron  0                8037 PQ: 0 ANSI: 6
[   15.447446] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   15.447615] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[   15.447930] sd 0:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[   15.448391] sd 0:0:0:0: [sda] Write Protect is off
[   15.448401] sd 0:0:0:0: [sda] Mode Sense: 47 00 10 08
[   15.448873] sd 0:0:0:0: [sda] No Caching mode page found
[   15.448880] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   15.449842] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[   15.481382] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[   15.482542] sd 0:0:0:0: [sda] Attached SCSI disk
[   47.321314] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[   47.341589] usb 4-1.2: device descriptor read/8, error -71
[   47.451175] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[   47.471598] usb 4-1.2: device descriptor read/8, error -71
[   48.331302] usb 4-1.2: Device not responding to setup address.
[   48.541222] usb 4-1.2: Device not responding to setup address.
[   48.751173] usb 4-1.2: device not accepting address 5, error -71
[   49.516304] usb 4-1.2: Device not responding to setup address.
[   49.726253] usb 4-1.2: Device not responding to setup address.
[   49.936170] usb 4-1.2: device not accepting address 5, error -71
[   50.266318] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[   50.426303] usb 4-1.2: Device not responding to setup address.
[   50.636254] usb 4-1.2: Device not responding to setup address.
[   50.846158] usb 4-1.2: device not accepting address 5, error -71
[   51.386295] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[   55.396319] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[   55.471197] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[   55.543933] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[   58.816301] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[   58.887599] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[   59.255070] EXT4-fs (sda): mounted filesystem with ordered data mode. Opts: user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl
[   94.146303] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[   94.273282] systemd-journald[335]: Received request to flush runtime journal from PID 1
[   99.831408] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[   99.851579] usb 4-1.2: device descriptor read/8, error -71
[   99.966243] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[   99.991557] usb 4-1.2: device descriptor read/8, error -71
[  100.661388] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[  101.101422] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[  105.956346] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[  106.791390] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[  111.426420] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[  111.846381] usb 4-1.2: Device not responding to setup address.
[  112.056340] usb 4-1.2: Device not responding to setup address.
[  112.266247] usb 4-1.2: device not accepting address 5, error -71
[  112.601386] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[  112.626685] usb 4-1.2: device descriptor read/8, error -71
[  112.736267] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[  112.756614] usb 4-1.2: device descriptor read/8, error -71
[  113.206416] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[  113.226652] usb 4-1.2: device descriptor read/8, error -71
[  113.336256] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[  113.356556] usb 4-1.2: device descriptor read/8, error -71
[  114.011390] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[  116.366399] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[  116.386726] usb 4-1.2: device descriptor read/8, error -71
[  116.496269] usb 4-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[  116.516684] usb 4-1.2: device descriptor read/8, error -71
[  117.171381] usb 4-1.2: Device not responding to setup address.
[  117.381321] usb 4-1.2: Device not responding to setup address.
[  117.591267] usb 4-1.2: device not accepting address 5, error -71
[  117.921434] usb 4-1.2: Device not responding to setup address.
[  118.131399] usb 4-1.2: Device not responding to setup address.
[  118.341307] usb 4-1.2: device not accepting address 5, error -71
[  119.101395] usb 4-1.2: Device not responding to setup address.
[  119.311342] usb 4-1.2: Device not responding to setup address.
[  119.526271] usb 4-1.2: device not accepting address 5, error -71
[  119.706339] usb 4-1.2: USB disconnect, device number 5
[  119.811408] usb 4-1.2: Device not responding to setup address.
[  120.021353] usb 4-1.2: Device not responding to setup address.
[  120.231273] usb 4-1.2: device not accepting address 6, error -71
[  120.771356] usb 4-1.2: new SuperSpeed USB device number 7 using xhci-hcd
[  120.792522] usb 4-1.2: New USB device found, idVendor=152d, idProduct=0561
[  120.792536] usb 4-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[  120.792547] usb 4-1.2: Product: External Disk 3.0
[  120.792554] usb 4-1.2: Manufacturer: JMicron
[  120.792562] usb 4-1.2: SerialNumber: DB01234567D2
[  120.793824] usb 4-1.2: UAS is blacklisted for this device, using usb-storage instead
[  120.793838] usb-storage 4-1.2:1.0: USB Mass Storage device detected
[  120.794194] usb-storage 4-1.2:1.0: Quirks match for vid 152d pid 0561: 800000
[  120.794331] scsi host0: usb-storage 4-1.2:1.0
[  122.907500] usb 4-1-port2: Cannot enable. Maybe the USB cable is bad?
[  123.086356] usb 4-1.2: USB disconnect, device number 7
[  123.166402] usb 4-1.2: Device not responding to setup address.
[  123.376385] usb 4-1.2: Device not responding to setup address.
[  123.586302] usb 4-1.2: device not accepting address 8, error -71
[  124.697544] usb 4-1-port2: Cannot enable. Maybe the USB cable is bad?
[  139.356435] usb 4-1.2: new SuperSpeed USB device number 10 using xhci-hcd
[  139.377535] usb 4-1.2: New USB device found, idVendor=152d, idProduct=0561
[  139.377545] usb 4-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[  139.377551] usb 4-1.2: Product: External Disk 3.0
[  139.377555] usb 4-1.2: Manufacturer: JMicron
[  139.377560] usb 4-1.2: SerialNumber: DB01234567D2
[  139.378663] usb 4-1.2: UAS is blacklisted for this device, using usb-storage instead
[  139.378671] usb-storage 4-1.2:1.0: USB Mass Storage device detected
[  139.383889] usb-storage 4-1.2:1.0: Quirks match for vid 152d pid 0561: 800000
[  139.383962] scsi host0: usb-storage 4-1.2:1.0
[  140.731476] usb 4-1.2: Device not responding to setup address.
[  140.941441] usb 4-1.2: Device not responding to setup address.
[  141.151374] usb 4-1.2: device not accepting address 10, error -71
[  142.116547] usb 4-1.2: reset SuperSpeed USB device number 10 using xhci-hcd
[  142.156698] scsi 0:0:0:0: Direct-Access     JMicron  0                8037 PQ: 0 ANSI: 6
[  142.157628] sd 0:0:0:0: Attached scsi generic sg0 type 0
[  142.157768] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[  142.158086] sd 0:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[  142.158581] sd 0:0:0:0: [sda] Write Protect is off
[  142.158594] sd 0:0:0:0: [sda] Mode Sense: 47 00 10 08
[  142.159093] sd 0:0:0:0: [sda] No Caching mode page found
[  142.159102] sd 0:0:0:0: [sda] Assuming drive cache: write through
[  142.159934] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[  142.163767] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[  142.165093] sd 0:0:0:0: [sda] Attached SCSI disk
root@openmediavault:~#


and bottom, which seems okay at first, but produces the reset as before:

Code: Select all
[    4.396733] usb 4-1.1: new SuperSpeed USB device number 3 using xhci-hcd
[    4.417356] usb 4-1.1: New USB device found, idVendor=152d, idProduct=0561
[    4.417368] usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[    4.417374] usb 4-1.1: Product: External Disk 3.0
[    4.417379] usb 4-1.1: Manufacturer: JMicron
[    4.417385] usb 4-1.1: SerialNumber: DB01234567D2
[    4.418731] usb 4-1.1: UAS is blacklisted for this device, using usb-storage instead
[    4.418741] usb-storage 4-1.1:1.0: USB Mass Storage device detected
[    4.418989] usb-storage 4-1.1:1.0: Quirks match for vid 152d pid 0561: 800000
[    4.419061] scsi host0: usb-storage 4-1.1:1.0
[    4.579201] Console: switching to colour frame buffer device 40x15
[    4.579418] graphics fb0: fb_ili9340 frame buffer, 320x240, 150 KiB video memory, 4 KiB DMA buffer memory, fps=20, spi1.0 at 35 MHz
[    4.589382] s5p-secss 10830000.sss:: s5p-sss driver registered
[    4.614736] s5p-mfc 11000000.codec:: Direct firmware load for s5p-mfc-v8.fw failed with error -2
[    4.614756] s5p_mfc_load_firmware:70: Firmware is not present in the /lib/firmware directory nor compiled in kernel
[    4.616399] s5p-mfc 11000000.codec:: Direct firmware load for s5p-mfc-v8.fw failed with error -2
[    4.616413] s5p_mfc_load_firmware:70: Firmware is not present in the /lib/firmware directory nor compiled in kernel
[    4.735001] usbcore: registered new interface driver uas
[    4.850249] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro
[    4.954426] Adding 131068k swap on /var/swap.  Priority:-1 extents:2 across:163836k SS
[    5.442029] scsi 0:0:0:0: Direct-Access     JMicron  0                8037 PQ: 0 ANSI: 6
[    5.443002] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    5.443156] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[    5.443447] sd 0:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[    5.443968] sd 0:0:0:0: [sda] Write Protect is off
[    5.443978] sd 0:0:0:0: [sda] Mode Sense: 47 00 10 08
[    5.444264] scsi 0:0:0:1: Direct-Access     JMicron  1                8037 PQ: 0 ANSI: 6
[    5.444748] sd 0:0:0:0: [sda] No Caching mode page found
[    5.444759] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    5.446389] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[    5.446424] sd 0:0:0:1: Attached scsi generic sg1 type 0
[    5.448907] sd 0:0:0:1: [sdb] Very big device. Trying to use READ CAPACITY(16).
[    5.449243] sd 0:0:0:1: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[    5.449929] sd 0:0:0:1: [sdb] Write Protect is off
[    5.449942] sd 0:0:0:1: [sdb] Mode Sense: 47 00 10 08
[    5.450185] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[    5.450634] sd 0:0:0:1: [sdb] No Caching mode page found
[    5.450642] sd 0:0:0:1: [sdb] Assuming drive cache: write through
[    5.452065] sd 0:0:0:0: [sda] Attached SCSI disk
[    5.452480] sd 0:0:0:1: [sdb] Very big device. Trying to use READ CAPACITY(16).
[    5.455234] sd 0:0:0:1: [sdb] Very big device. Trying to use READ CAPACITY(16).
[    5.456547] sd 0:0:0:1: [sdb] Attached SCSI disk
[    9.098384] sd 0:0:0:1: [sdb] Very big device. Trying to use READ CAPACITY(16).
[    9.102515] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[    9.510980] EXT4-fs (sdb): mounted filesystem with ordered data mode. Opts: user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl
[    9.533564] EXT4-fs (sda): mounted filesystem with ordered data mode. Opts: user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl
[    9.621951] systemd-journald[359]: Received request to flush runtime journal from PID 1
[  238.712303] usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
[  268.882414] usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd


Faulty cable or XU4? Does anyone know where I can find a proper quality USB 3.0 cable for the cloudshell2 quickly stateside?
Kosmatik
 
Posts: 25
Joined: Tue May 23, 2017 12:06 pm
languages_spoken: English, Russian
ODROIDs: XU4

Re: Getting UAS working on HK 4.9

Unread postby crashoverride » Thu May 25, 2017 1:20 am

There should be nothing special about the cable. You can try using any other known good USB3 cable. Even a USB2 cable should work, just slower. Either would be helpful in reducing the problem set.
Image
crashoverride
 
Posts: 3060
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1

Re: Getting UAS working on HK 4.9

Unread postby Kosmatik » Thu May 25, 2017 7:16 am

I've replaced the cable with a working one from a WD enclosure. So far no issues and I've removed the blacklisting of the bridge from the kernel as well. UAS seems stable (preliminary results)

Could someone point me to where I can buy a quality L shaped USB 3.0 cable ~20cm long in USA.

Code: Select all
[    4.153854] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro
[    4.411285] usb 4-1.1: new SuperSpeed USB device number 3 using xhci-hcd
[    4.432419] usb 4-1.1: New USB device found, idVendor=152d, idProduct=0561
[    4.432428] usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[    4.432436] usb 4-1.1: Product: External Disk 3.0
[    4.432441] usb 4-1.1: Manufacturer: JMicron
[    4.432450] usb 4-1.1: SerialNumber: DB01234567D2
[    4.483443] Console: switching to colour frame buffer device 40x15
[    4.483663] graphics fb0: fb_ili9340 frame buffer, 320x240, 150 KiB video memory, 4 KiB DMA buffer memory, fps=20, spi1.0 at 35 MHz
[    4.499668] s5p-secss 10830000.sss:: s5p-sss driver registered
[    4.500284] s5p-mfc 11000000.codec:: Direct firmware load for s5p-mfc-v8.fw failed with error -2
[    4.500293] s5p_mfc_load_firmware:70: Firmware is not present in the /lib/firmware directory nor compiled in kernel
[    4.500442] s5p-mfc 11000000.codec:: Direct firmware load for s5p-mfc-v8.fw failed with error -2
[    4.500452] s5p_mfc_load_firmware:70: Firmware is not present in the /lib/firmware directory nor compiled in kernel
[    4.533866] Adding 131068k swap on /var/swap.  Priority:-1 extents:2 across:163836k SS
[    4.644190] scsi host0: uas
[    4.645502] scsi 0:0:0:0: Direct-Access     JMicron  0                8037 PQ: 0 ANSI: 6
[    4.701862] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    4.702073] sd 0:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[    4.703088] scsi 0:0:0:1: Direct-Access     JMicron  1                8037 PQ: 0 ANSI: 6
[    4.703518] sd 0:0:0:0: [sda] Write Protect is off
[    4.703525] sd 0:0:0:0: [sda] Mode Sense: 67 00 10 08
[    4.704156] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    4.711216] sd 0:0:0:0: [sda] Attached SCSI disk
[    4.776727] sd 0:0:0:1: Attached scsi generic sg1 type 0
[    4.776902] usbcore: registered new interface driver uas
[    4.776944] sd 0:0:0:1: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[    4.778333] sd 0:0:0:1: [sdb] Write Protect is off
[    4.778340] sd 0:0:0:1: [sdb] Mode Sense: 67 00 10 08
[    4.778905] sd 0:0:0:1: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    4.785598] sd 0:0:0:1: [sdb] Attached SCSI disk
[    8.645386] EXT4-fs (sdb): mounted filesystem with ordered data mode. Opts: user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl
[    8.717402] EXT4-fs (sda): mounted filesystem with ordered data mode. Opts: user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl
[    8.813711] systemd-journald[339]: Received request to flush runtime journal from PID 1
Kosmatik
 
Posts: 25
Joined: Tue May 23, 2017 12:06 pm
languages_spoken: English, Russian
ODROIDs: XU4

Re: Getting UAS working on HK 4.9

Unread postby odroid » Thu May 25, 2017 8:31 am

I think the bundled cable in your CloudShell2 package seems to be defective. Really sorry about that.
I will talk to a director in our US office. Give me 1~2 days.
https://odroidinc.com/
User avatar
odroid
Site Admin
 
Posts: 24367
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: Getting UAS working on HK 4.9

Unread postby rncwnd » Tue May 30, 2017 7:06 pm

I am now getting this with my Cloudshell (1).
sda is the external disk. Is it the cable? Is it the disk? Is it the kernel? This behaviour started yesterday after a week without any usb-related problems (about a week ago I changed the cable to a very short one with angular plugs to avoid bending).

Code: Select all
[   20.827170] BTRFS info (device sdb1): checking UUID tree
[  102.890601] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
[  102.890640] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 03 c8 80 00 04 00 00
[  102.891375] scsi host1: uas_eh_bus_reset_handler start
[  102.970794] usb 4-1.2: reset SuperSpeed USB device number 4 using xhci-hcd
[  102.997032] scsi host1: uas_eh_bus_reset_handler success
[  143.850671] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
[  143.850713] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 20 68 00 00 04 00 00
[  143.851454] scsi host1: uas_eh_bus_reset_handler start
[  143.930796] usb 4-1.2: reset SuperSpeed USB device number 4 using xhci-hcd
[  143.957233] scsi host1: uas_eh_bus_reset_handler success
[  177.130621] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
[  177.130661] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 27 45 80 00 04 00 00
[  177.131393] scsi host1: uas_eh_bus_reset_handler start
[  177.210808] usb 4-1.2: reset SuperSpeed USB device number 4 using xhci-hcd
[  177.238231] scsi host1: uas_eh_bus_reset_handler success
[  225.770697] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
[  225.770737] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 5f b7 00 00 04 00 00
[  225.771487] scsi host1: uas_eh_bus_reset_handler start
[  225.850892] usb 4-1.2: reset SuperSpeed USB device number 4 using xhci-hcd
[  225.878448] scsi host1: uas_eh_bus_reset_handler success
[  271.850697] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
[  271.850754] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 8d b7 f8 00 04 00 00
[  271.851744] scsi host1: uas_eh_bus_reset_handler start
[  271.935902] usb 4-1.2: reset SuperSpeed USB device number 4 using xhci-hcd
[  271.963695] scsi host1: uas_eh_bus_reset_handler success
[  356.970520] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
[  356.970531] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 01 32 69 10 00 04 00 00


A btrfs-scrub run reported errors (what I excepected after the errors above).

Code: Select all
root@odroid:~# dmesg | grep ":0:0:0"
[    1.988644] scsi 1:0:0:0: Direct-Access     ASMedia  ASM1153E         0    PQ: 0 ANSI: 6
[    2.061034] sd 1:0:0:0: Attached scsi generic sg0 type 0
[    2.061361] sd 1:0:0:0: [sda] Spinning up disk...
[    2.915379] scsi 0:0:0:0: Direct-Access     Genesys  USB3/SATA Bridge 1003 PQ: 0 ANSI: 6
[    2.916022] sd 0:0:0:0: Attached scsi generic sg1 type 0
[    4.715619] sd 0:0:0:0: [sdb] Spinning up disk...
[    5.281266] sd 1:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[    5.281293] sd 1:0:0:0: [sda] 4096-byte physical blocks
[    5.282046] sd 1:0:0:0: [sda] Write Protect is off
[    5.282061] sd 1:0:0:0: [sda] Mode Sense: 43 00 00 00
[    5.282420] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    5.307174] sd 1:0:0:0: [sda] Attached SCSI disk
[    5.836032] sd 0:0:0:0: [sdb] 1953525152 512-byte logical blocks: (1.00 TB/932 GiB)
[    5.836782] sd 0:0:0:0: [sdb] Write Protect is off
[    5.836798] sd 0:0:0:0: [sdb] Mode Sense: 5f 00 10 08
[    5.837539] sd 0:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    5.854435] sd 0:0:0:0: [sdb] Attached SCSI disk


Code: Select all
root@odroid:~# lsusb -t
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 5000M
        |__ Port 1: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
        |__ Port 2: Dev 4, If 0, Class=Mass Storage, Driver=uas, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=exynos-ohci/3p, 12M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=exynos-ehci/3p, 480M


Code: Select all
root@odroid:~# smartctl -d sat -a /dev/sda
smartctl 6.4 2014-10-07 r4002 [armv7l-linux-4.9.29+] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red (AF)
Device Model:     WDC WD10JFCX-68N6GN0
Serial Number:    WD-WX21A46H48RA
LU WWN Device Id: 5 0014ee 6b15070d1
Firmware Version: 82.00A82
User Capacity:    1.000.204.886.016 bytes [1,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Tue May 30 11:42:32 2017 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (18960) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 212) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x703d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   207   170   021    Pre-fail  Always       -       650
  4 Start_Stop_Count        0x0032   098   098   000    Old_age   Always       -       2625
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   095   095   000    Old_age   Always       -       4345
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       243
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       204
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       2878
194 Temperature_Celsius     0x0022   102   098   000    Old_age   Always       -       45
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Conveyance offline  Completed without error       00%      3994         -
# 2  Short offline       Completed without error       00%      3994         -
# 3  Short offline       Completed without error       00%      3875         -
# 4  Short offline       Completed without error       00%      3725         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
rncwnd
 
Posts: 22
Joined: Tue Apr 11, 2017 11:18 pm
languages_spoken: english, german
ODROIDs: XU4

Re: Getting UAS working on HK 4.9

Unread postby odroid » Tue May 30, 2017 7:31 pm

Do you use two HDDs with the original CloudShell 1 ?
The primary disk seems to be UAS one and the secondary seems to be non-UAS.
The issue is occurring only on the primary disk. Right?
User avatar
odroid
Site Admin
 
Posts: 24367
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: Getting UAS working on HK 4.9

Unread postby rncwnd » Tue May 30, 2017 10:55 pm

I use 2 HDDs (WD Red 1TB). One is internal and connected to the cloudshell SATA port (sdb in my post), the other one (sda) is in an USB3 enclosure (LogiLink UA0115 sporting a ASM1153E).
The problem occurs only in the external disk (sda) which is connected to the ASM1153E (uas).

As I said, it worked stable without problems for the last week and suddenly started yesterday.
Seems like BTRFS is a lifesaver here...
rncwnd
 
Posts: 22
Joined: Tue Apr 11, 2017 11:18 pm
languages_spoken: english, german
ODROIDs: XU4

Re: Getting UAS working on HK 4.9

Unread postby Kosmatik » Wed May 31, 2017 7:14 am

odroid wrote:I think the bundled cable in your CloudShell2 package seems to be defective. Really sorry about that.
I will talk to a director in our US office. Give me 1~2 days.
https://odroidinc.com/


Cable arrived today and works the same as my WD one, thanks!

Now a little more testing and everything looks stable, however! this is what happens when Smart information is pulled from OMV.

Code: Select all
[  158.571802] sd 0:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
[  158.571812] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 08 0e 00 d5 00 08 00 04 00 4f 00 c2 00 b0 00
[  179.676925] sd 0:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN
[  179.676934] sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x85 85 08 0e 00 00 00 01 00 00 00 00 00 00 00 ec 00
[  179.677015] scsi host0: uas_eh_bus_reset_handler start
[  179.677686] sd 0:0:0:1: [sdb] tag#2 uas_zap_pending 0 uas-tag 3 inflight: CMD
[  179.677693] sd 0:0:0:1: [sdb] tag#2 CDB: opcode=0x8a 8a 00 00 00 00 00 09 e8 6c 18 00 00 02 00 00 00
[  179.677700] sd 0:0:0:1: [sdb] tag#3 uas_zap_pending 0 uas-tag 4 inflight: CMD
[  179.677706] sd 0:0:0:1: [sdb] tag#3 CDB: opcode=0x8a 8a 00 00 00 00 00 09 f2 9e 18 00 00 02 00 00 00
[  179.677713] sd 0:0:0:1: [sdb] tag#4 uas_zap_pending 0 uas-tag 5 inflight: CMD
[  179.677719] sd 0:0:0:1: [sdb] tag#4 CDB: opcode=0x8a 8a 00 00 00 00 00 09 f7 b9 38 00 00 02 00 00 00
[  179.757029] usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
[  179.779206] scsi host0: uas_eh_bus_reset_handler success


Any ideas?
Kosmatik
 
Posts: 25
Joined: Tue May 23, 2017 12:06 pm
languages_spoken: English, Russian
ODROIDs: XU4

Re: Getting UAS working on HK 4.9

Unread postby odroid » Wed May 31, 2017 10:57 am

Please disable the "UAS" function for testing to narrow down the root causes.
http://odroid.com/dokuwiki/doku.php?id= ... s_and_tips
User avatar
odroid
Site Admin
 
Posts: 24367
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: Getting UAS working on HK 4.9

Unread postby Kosmatik » Thu Jun 01, 2017 8:49 am

With UAS disabled and checking the Devices tab of SMART.

Code: Select all
[   38.336481] usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
[   38.481485] usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
[   65.866589] usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
[   82.316607] usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
[   82.461633] usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
Kosmatik
 
Posts: 25
Joined: Tue May 23, 2017 12:06 pm
languages_spoken: English, Russian
ODROIDs: XU4

Re: Getting UAS working on HK 4.9

Unread postby odroid » Thu Jun 01, 2017 11:35 am

I think SMART seems not be compatible with ASM1153E chipset.
Can you check the version of smartmontools in your OMV image?
User avatar
odroid
Site Admin
 
Posts: 24367
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: Getting UAS working on HK 4.9

Unread postby Kosmatik » Thu Jun 01, 2017 10:29 pm

This is getting a bit off topic, but I am able to do smartctl -a /dev/sda without issues, this seems to only happen when I either enable monitoring or check the devices in SMART section in OMV.

smartctl 6.4 2014-10-07 r4002 [armv7l-linux-4.9.30-odroidxu4] (local build)

Any ideas?
Kosmatik
 
Posts: 25
Joined: Tue May 23, 2017 12:06 pm
languages_spoken: English, Russian
ODROIDs: XU4

Re: Getting UAS working on HK 4.9

Unread postby odroid » Fri Jun 02, 2017 10:24 am

We've used only smartctl 6.5 (revision 4132 or higher) on our Ubuntu images.
http://odroid.com/dokuwiki/doku.php?id= ... rtmontools

I have no idea how SMART monitoring works on OMV.
But it seems to be worth to build & install the latest stable version of smartmontools if there is no negative side effect against OMV.
https://www.smartmontools.org/wiki/Down ... rcetarball
User avatar
odroid
Site Admin
 
Posts: 24367
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: Getting UAS working on HK 4.9

Unread postby Kosmatik » Fri Jun 02, 2017 11:48 am

Well, I've built it, but there are libraries that are old. It complains about libstdc++6 being incompatible. Then it becomes a rabbit hole after that as that library depends on something else.

I'll see what the Armbian folks say. I'll create a new thread if I have any more issues as this no longer relates to UAS.

Code: Select all
The following packages have unmet dependencies:
 smartmontools : Depends: libstdc++6 (>= 5.2) but 4.9.2-10 is installed.
Kosmatik
 
Posts: 25
Joined: Tue May 23, 2017 12:06 pm
languages_spoken: English, Russian
ODROIDs: XU4

Re: Getting UAS working on HK 4.9

Unread postby ard » Wed Jun 07, 2017 6:48 pm

Kosmatik wrote:Well, I've built it, but there are libraries that are old. It complains about libstdc++6 being incompatible. Then it becomes a rabbit hole after that as that library depends on something else.

I'll see what the Armbian folks say. I'll create a new thread if I have any more issues as this no longer relates to UAS.

Code: Select all
The following packages have unmet dependencies:
 smartmontools : Depends: libstdc++6 (>= 5.2) but 4.9.2-10 is installed.

ard@odroid3:/etc/network/interfaces.d$ apt-cache show smartmontools
Package: smartmontools
Version: 6.5+svn4324-1~bpo8+1
This is plain jessie with jessie-backports. Jessie itself contains:
Version: 6.3+svn4002-2+b2
So I suggest just installing the jessie-backport unless armbian is not based on debian/jessie.
There is some stuff I had to backport myself, but I think that most of that has already been officially backported.
Anyway: I usually use plain debian and I usually install it using debootstrap, no matter what platform.
I only made a single exception and that was ubuntu 14.04 and I still regret it everyday. Backports on ubuntu are a dependency hell, especially if you use PPA's, since PPA's usually are inconsistent "to build this you need version X of package Y. To help you I have the source of version X-1 of package Y that needs version (DIST)=1 of package Y to build itself". Oh, and no you can't get that version anywhere. Have fun!
The only way to overcome ubuntu backport dependency hell is to never ever backport from an ubuntu PPA, but always backport from either debian backports or debian testing/unstable.
Oh boy, I am ranting again. Please excuse me.
ard
 
Posts: 55
Joined: Tue Jul 09, 2013 2:12 am
languages_spoken: english, dutch, german
ODROIDs: ODROID-U2

Re: Getting UAS working on HK 4.9

Unread postby linuxest » Sat Jun 10, 2017 11:42 am

The cheap $180 Seagate 8TB USB storage (Expansion-Desktop model) works well with Kernel 4.9 UAS driver.
Image
VID:PID is 0bc2:3322 Seagate RSS LLC
Read & Write speed is around 170MB/s and it is more than enough to build my home NAS.
Samba access speed is 90~100MB/s with EXT4 file format. Our family is very satisfied with the huge amount of storage for their videos and photos. :D
Time to say goodbye to the expensive google drive. I had to pay $100 for 1TB every year.
linuxest
 
Posts: 31
Joined: Tue Nov 08, 2016 6:35 pm
languages_spoken: english
ODROIDs: 1 x HC1 and 2 x C2s with HiFi-Shield 2
And some RPi3 boards

Re: Getting UAS working on HK 4.9

Unread postby odroid » Tue Jun 20, 2017 3:38 pm

linuxest wrote:The cheap $180 Seagate 8TB USB storage (Expansion-Desktop model) works well with Kernel 4.9 UAS driver.
Image
VID:PID is 0bc2:3322 Seagate RSS LLC
Read & Write speed is around 170MB/s and it is more than enough to build my home NAS.
Samba access speed is 90~100MB/s with EXT4 file format. Our family is very satisfied with the huge amount of storage for their videos and photos. :D
Time to say goodbye to the expensive google drive. I had to pay $100 for 1TB every year.


Thank you for the report.
The Seagate 8TB external drive seems to be the most affordable storage.
I've ordered one from Amazon to play with it.
If it works well, I will write an article "Very affordable High-Performance DIY NAS" :D
BTW, I need a good idea how to attach the XU4 + official case on the storage.
User avatar
odroid
Site Admin
 
Posts: 24367
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: Getting UAS working on HK 4.9

Unread postby crossover » Tue Jun 20, 2017 9:21 pm

odroid wrote:If it works well, I will write an article "Very affordable High-Performance DIY NAS" :D
BTW, I need a good idea how to attach the XU4 + official case on the storage.


How about using a couple of velcro strips between the XU4 case and the HDD enclosure?
https://www.amazon.com/VELCRO-Brand-Sti ... B000TGSPV6
crossover
 
Posts: 105
Joined: Wed Jul 22, 2015 2:23 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, USB-IO, Tinkering kits

Re: Getting UAS working on HK 4.9

Unread postby odroid » Tue Jun 20, 2017 9:31 pm

@crossover
Thank you for the idea. :) I will try it.
User avatar
odroid
Site Admin
 
Posts: 24367
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: Getting UAS working on HK 4.9

Unread postby Snk » Thu Jun 22, 2017 9:48 am

odroid wrote:@crossover
Thank you for the idea. :) I will try it.


Hello .. Good evening! Will you use any solution for this case (using Seagate Expansion Plus 8TB) or will it just put an XU4 in the case and attach it to the external HD and make the connection using USB 3.0? I plan to make a NAS that way (if you get it) XU4 + official case nailed with a Velcro + Seagate Backup Plus Slim 2TB. When you get your external HD and the mount according to your project, could you post here in the forum?
User avatar
Snk
 
Posts: 211
Joined: Sun Jul 31, 2016 6:43 am
languages_spoken: Portuguese
ODROIDs: XU4 + eMMC 32GB + UART

Re: Getting UAS working on HK 4.9

Unread postby odroid » Thu Jun 22, 2017 10:01 am

@Snk
I will post some pictures in this forum when I make it.
I think I can receive the Seagate 8TB External storage within a week.
User avatar
odroid
Site Admin
 
Posts: 24367
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: Getting UAS working on HK 4.9

Unread postby Snk » Thu Jun 22, 2017 10:30 am

@odroid
Thank you my friend!
I am quite looking forward to seeing pictures of your project!
It will be my inspiration for my project here at home.
User avatar
Snk
 
Posts: 211
Joined: Sun Jul 31, 2016 6:43 am
languages_spoken: Portuguese
ODROIDs: XU4 + eMMC 32GB + UART

Re: Getting UAS working on HK 4.9

Unread postby Snk » Tue Jun 27, 2017 11:54 am

Hey guys ...
How do I know if my external hard drive is UAS compliant? I bought a Seagate Expansion STEA1000400 1TB and I do not know if it is compatible. Haha
I'm looking forward to @odroid for inspiration in making a mini-NAS here at home.
User avatar
Snk
 
Posts: 211
Joined: Sun Jul 31, 2016 6:43 am
languages_spoken: Portuguese
ODROIDs: XU4 + eMMC 32GB + UART

Re: Getting UAS working on HK 4.9

Unread postby odroid » Tue Jun 27, 2017 12:35 pm

Boot your XU4 and connect the storage.
And check "dmesg" output with "dmesg | grep -i uas" command.

If its VID:PID is 0bc2:2322, it should be in the black-list of UAS driver.
But it still gets 90~100MB/sec of Samba performance probably.
User avatar
odroid
Site Admin
 
Posts: 24367
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: Getting UAS working on HK 4.9

Unread postby crashoverride » Wed Jun 28, 2017 9:26 pm

crashoverride wrote:When Armbian begins testing other USB3+UAS boards, they will inevitably see the same issues.

I have confirmed this issue is also present on a different ARM board from a different manufacturer using a different SoC. Testing was done with a new HDD fresh out of the box.
[ 5290.859306] sd 0:0:0:0: [sda] tag#27 uas_eh_abort_handler 0 uas-tag 28 inflight: CMD OUT
[ 5290.859349] sd 0:0:0:0: [sda] tag#27 CDB: opcode=0x2a 2a 00 03 22 fc 00 00 04 00 00
[ 5290.859498] xhci-hcd xhci-hcd.7.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 5290.860356] xhci-hcd xhci-hcd.7.auto: @00000000781057f0 00000000 00000000 1b000000 01088001


This should put to rest any speculation/claims about the issue being XU4 related. It is entirely a Linux kernel issue.
crashoverride
 
Posts: 3060
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1

Re: Getting UAS working on HK 4.9

Unread postby mad_ady » Thu Jun 29, 2017 3:23 am

If anyone is keeping track, please add usb-storage.quirks=0x174c:0x1153:u to the faulty UAS ASMedia controllers.
It gave me quite a scare until I disabled UAS.
User avatar
mad_ady
 
Posts: 2400
Joined: Wed Jul 15, 2015 5:00 pm
Location: Bucharest, Romania
languages_spoken: english
ODROIDs: XU4, C1+, C2

Re: Getting UAS working on HK 4.9

Unread postby Snk » Thu Jun 29, 2017 9:15 am

Hello

After executing the command, I get the following information:


Odroid @ odroid: ~ $ dmesg | Grep -i uas
[4.998567] USB 4-1.1: UAS is blacklisted for this device, using usb-storage instead
[11.340813] usbcore: registered new interface driver uas
Odroid @ odroid: ~ $

In case my external HD is not compatible with UAS, correct?
User avatar
Snk
 
Posts: 211
Joined: Sun Jul 31, 2016 6:43 am
languages_spoken: Portuguese
ODROIDs: XU4 + eMMC 32GB + UART

Re: Getting UAS working on HK 4.9

Unread postby joaofl » Fri Jun 30, 2017 2:33 am

I actually have a similar problem with my External USB3 WD MyBook 8TB running on my XU4 with the odroid 4.9.29+ kernel. The smartctl tools works fines, but whenever there is a high simultaneous load on ethernet+usb3 (like when streaming a video high-res from another machine), I keep on getting numerous errors like below (every second more or less):
Code: Select all
    [Thu Jun 29 02:51:36 2017] usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
    [Thu Jun 29 02:51:36 2017] usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
    [Thu Jun 29 02:51:37 2017] usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
    [Thu Jun 29 02:51:38 2017] usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
    [Thu Jun 29 02:51:38 2017] usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
    [Thu Jun 29 02:51:40 2017] usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd

and sometimes this (which concerns me about data integrity):
Code: Select all
    [Thu Jun 29 02:22:39 2017] usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
    [Thu Jun 29 02:22:39 2017] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
    [Thu Jun 29 02:22:39 2017] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x88 88 00 00 00 00 02 a6 40 0a 10 00 00 00 f0 00 00
    [Thu Jun 29 02:22:39 2017] blk_update_request: I/O error, dev sda, sector 11379149328


The HD is new, and tested with different cables and computers.. Work fine, except on my XU4... Dont know what to do to be honest... I still have not tried disabling the UAS function...

Have also commented something on another thread here: viewtopic.php?f=147&t=27246&p=194647#p194647
joaofl
 
Posts: 28
Joined: Sat Feb 27, 2016 2:29 am
Location: Portugal, Brasil
languages_spoken: english, portuguese, spanish
ODROIDs: XU4

Re: Getting UAS working on HK 4.9

Unread postby odroid » Fri Jun 30, 2017 11:36 am

Snk wrote:Hello

After executing the command, I get the following information:


Odroid @ odroid: ~ $ dmesg | Grep -i uas
[4.998567] USB 4-1.1: UAS is blacklisted for this device, using usb-storage instead
[11.340813] usbcore: registered new interface driver uas
Odroid @ odroid: ~ $

In case my external HD is not compatible with UAS, correct?

Unfortunately, it is correct.
User avatar
odroid
Site Admin
 
Posts: 24367
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: Getting UAS working on HK 4.9

Unread postby crashoverride » Fri Jun 30, 2017 10:59 pm

joaofl wrote:whenever there is a high simultaneous load on ethernet+usb3 (like when streaming a video high-res from another machine), I keep on getting numerous errors like below (every second more or less):

The most common symptom I have seen on the drives I have tested is that everything works fine until you perform a high rate, sustained transfer. For me, this fails reliably on Linux only (windows, macOS works) on PC (x86/64) and ARM.

joaofl wrote:Dont know what to do to be honest... I still have not tried disabling the UAS function...

Disable UAS. There is no performance difference for mechanical drives that I have observed.
crashoverride
 
Posts: 3060
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1

Re: Getting UAS working on HK 4.9

Unread postby odroid » Sat Jul 01, 2017 11:44 am

crashoverride wrote:There is no performance difference for mechanical drives that I have observed.


Good observation.
I will compare the performance with my Seagate 8TB HDD box early next week.
viewtopic.php?f=98&t=27466

Update:
Here is my test result.

Mass Storage driver with JMS561 + EVO 256GB SSD
Write : 218MB/sec
Read : 220MB/sec
UAS driver with JMS561 + EVO 256GB SSD
Write : 271MB/sec
Read : 289MB/sec

Mass Storage driver with Seagate Expansion Desktop Drive 8TB HDD
Write : 157MB/sec
Read : 158MB/sec
UAS driver with Seagate Expansion Desktop Drive 8TB HDD
Write : 165MB/sec
Read : 168MB/sec

Yes! The performance difference for mechanical drives is negligible (less than 5~7%).
So HDD users can disable the UAS driver if they meet any stability issue of UAS.
User avatar
odroid
Site Admin
 
Posts: 24367
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: Getting UAS working on HK 4.9

Unread postby odroid » Sat Jul 01, 2017 2:15 pm

Snk wrote:@odroid
Thank you my friend!
I am quite looking forward to seeing pictures of your project!
It will be my inspiration for my project here at home.


I've uploaded some pictures with performance data.
viewtopic.php?f=98&t=27466
User avatar
odroid
Site Admin
 
Posts: 24367
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: Getting UAS working on HK 4.9

Unread postby joaofl » Thu Jul 06, 2017 7:47 am

crashoverride wrote:
joaofl wrote:whenever there is a high simultaneous load on ethernet+usb3 (like when streaming a video high-res from another machine), I keep on getting numerous errors like below (every second more or less):

The most common symptom I have seen on the drives I have tested is that everything works fine until you perform a high rate, sustained transfer. For me, this fails reliably on Linux only (windows, macOS works) on PC (x86/64) and ARM.

joaofl wrote:Dont know what to do to be honest... I still have not tried disabling the UAS function...

Disable UAS. There is no performance difference for mechanical drives that I have observed.


Thats true. But more specifically, I think that this issue is related to this hardkernel odroid kernel 4.9. I dont remember having this problem on previous kernel 3, and with the same external HD I dont get the same problem neither on my PC (usb3), nor on my RPi (usb2, arm, kernel 4).

Have tried replacing cables and other things more and nothing helped. I actually believe this is related to some USB3 drivers issue.

My test is simple: I simultaneously copy and transfer (r/w) a file from/to the board's external HD (on usb3), through SFTP from another Gigabit client on the network. This puts the ethernet and USB3 demands very high. Noticing that the gigabit ethernet on the odroid board is actually behind another USB3 port.

It seems to me that one crashes the other one, since if I perform simultaneous r/w locally, everything runs fine. The Ethernet on its own also seems to work fine.
I wonder if this is only happening to me.

Thank you all for the support.
joaofl
 
Posts: 28
Joined: Sat Feb 27, 2016 2:29 am
Location: Portugal, Brasil
languages_spoken: english, portuguese, spanish
ODROIDs: XU4

Re: Getting UAS working on HK 4.9

Unread postby crashoverride » Fri Jul 07, 2017 4:21 am

joaofl wrote:I dont remember having this problem on previous kernel 3, and with the same external HD I dont get the same problem neither on my PC (usb3), nor on my RPi (usb2, arm, kernel 4).

The previous kernel (3.x) did not have UAS support. The RPi does not have USB3 (it even uses different physical wires on the USB port). The issue is not present on a PC unless it runs Linux.

The issue is present on my PC running Ubuntu 16.04 with a 4.4 kernel as shown earlier in this thread. It has also been reproduced on PC by others as shown earlier in this thread. I have reproduced it on a PC using an Intel USB3 controller, a PC using an AMD USB3 controller, and a PC using a ASMedia controller. Now that other USB3+UAS capable ARM boards are becoming available, I also see the issue there.

While I am open to the premise of the issue being XU4 related, there simply is no evidence supporting that. The most compelling evidence is that the JMicron USB3 controller works flawlessly on all of the above machines where the issue is reproduceable.
crashoverride
 
Posts: 3060
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1

Re: Getting UAS working on HK 4.9

Unread postby theodoiq » Mon Jul 10, 2017 3:31 pm

Pliss.. how can I get my Seagate expansion 5TB working on?

This is what I have for now:
Code: Select all
odroid@odroid:~$ sudo lsusb | grep Seagate
Bus 004 Device 003: ID 0bc2:331a Seagate RSS LLC


# lsusb | grep -i uas

Had no result

odroid@odroid:~$ sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk1 179:0 0 7.4G 0 disk
├─mmcblk1p1 179:1 0 128M 0 part /media/boot
└─mmcblk1p2 179:2 0 7.3G 0 part /
sda 8:0 0 149.1G 0 disk
└─sda1 8:1 0 149.1G 0 part

There is no 4,6T disk here :-(

I've added on boot.ini a kernel argument:
Code: Select all
# Basic Ubuntu Setup. Don't touch unless you know what you are doing.
# --------------------------------
setenv bootrootfs "usb-storage.quirks=0bc2:331a console=tty1 console=ttySAC2,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro fsck$



I really don't know what I have to do for get the seagate working...

Any help will be very apreciated!

Tks in advance!
theodoiq
 
Posts: 25
Joined: Wed Sep 03, 2014 9:42 am
languages_spoken: english
ODROIDs: Odroid U3

Re: Getting UAS working on HK 4.9

Unread postby crashoverride » Mon Jul 10, 2017 6:03 pm

theodoiq wrote:usb-storage.quirks=0bc2:331a

that should have ":u" at the end:
Code: Select all
usb-storage.quirks=0bc2:331a:u


Also, the command to display the usb tree is
Code: Select all
lsusb -t

The output of the command will show whether the USB device is detected.

Ensure you have updated recently, there is another report of missing drives due to a previous update.
Code: Select all
sudo apt update
sudo apt upgrade
crashoverride
 
Posts: 3060
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1

Re: Getting UAS working on HK 4.9

Unread postby theodoiq » Wed Jul 12, 2017 12:04 pm

Hi,
It works!! Tks a lot!!! (SOLVED)
:D :D :D
__________________
crashoverride wrote:
theodoiq wrote:usb-storage.quirks=0bc2:331a

that should have ":u" at the end:
Code: Select all
usb-storage.quirks=0bc2:331a:u


Also, the command to display the usb tree is
Code: Select all
lsusb -t

The output of the command will show whether the USB device is detected.

Ensure you have updated recently, there is another report of missing drives due to a previous update.
Code: Select all
sudo apt update
sudo apt upgrade

__________________
theodoiq
 
Posts: 25
Joined: Wed Sep 03, 2014 9:42 am
languages_spoken: english
ODROIDs: Odroid U3

Re: Getting UAS working on HK 4.9

Unread postby odroid » Wed Jul 26, 2017 5:00 pm

A couple of users reported the Jmicron JMS578 USB-SATA bridge IC has a critical issue when they formatted an HDD with "mkfs.ext4 -b 4096 -m 0 -E lazy_itable_init=0,lazy_journal_init=0 /dev/sda1".
That command is also used in the OpenMediaVault and we could reproduce the issue a few days ago.

When a bunch of sequential data(inode) is being sent to the UAS driver, the UAS driver is increasing the DMA block memory allocation dynamically for more efficient ring-buffer management.
But the Kernel coherent-pool memory size was limited at 256KB by default and it was not sufficient for the UAS drivers.
So we could meet a lot of following kernel errors and it prevented the disk formatting.
Code: Select all
xhci-hcd xhci-hcd.2.auto: Ring expansion failed
tag#19 data out submit err -12 uas-tag 19 inflight: s-out a-cmd s-cmd work
tag#19 CDB: opcode=0x2a 2a 00 4c 00 d9 00 00 04 00 00


To fix this issue, we needed to increase the coherent-memory size to 1MB.
We will release a kernel update within a couple of days and report this patch to OMV maintainers (@tkasier and @ryecoaaron).
Meanwhile, you can add this item coherent_pool=1M on the bootargs in boot.ini file as a workaround.

setenv bootargs "${bootrootfs} ${videoconfig} smsc95xx.macaddr=${macaddr} governor=${governor} ${hdmi_phy_control} ${extraargs} coherent_pool=1M"

We tested this solution with a Seagate 8TB HDD box as well as a JMS578 included enclosure.
Both external USB 3.0 storages had the same issue when we formatted the HDD on the OMV GUI menu.
They work well with UAS now. :)
User avatar
odroid
Site Admin
 
Posts: 24367
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: Getting UAS working on HK 4.9

Unread postby crashoverride » Thu Jul 27, 2017 12:22 am

Great work, HardKernel! Thanks for putting in the time and effort for this.
crashoverride
 
Posts: 3060
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1

PreviousNext

Return to Linux Kernel 4.9 Debugging Party

Who is online

Users browsing this forum: No registered users and 1 guest