Menion

December 13, 2018

Hi

It is better if you report everything to U-Boot mailing list: https://lists.denx.de/listinfo/u-boot

December 9, 2018

16 minutes ago, svts said:

Hello everybody!

I've bought recently OrangePi PC2 to develop a small data gathering machine but got stuck with some difficulties with Armbian.

Board is OrangePi PC2 v 1.1.

The problem is random crashes (kernel oops and kernel panics then sometimes).

What I have done: made SD card with Armbian "next" 5.65 distro (kernel 4.14.78-sunxi64). No changes, no overlays etc.

What happens: the system crashes randomly. It happens never during initial kernel boot but it starts happening after systemd load.

Sometimes (like 1-2 of 10) system cannot boot at all without crash. When system boots okay I use a script to test:

Reveal hidden contents

#!/bin/sh

while true; do
date
for I in `seq 1 4`; do
    timeout $I cat /dev/zero > /dev/null &
    cat /var/log/syslog | grep 123 > /dev/null &
done
wait
sleep 1
done

The script runs well for a while (like 5-15 mins) and then crash appears in system console and dmesg. Sometimes system hangs immediately but sometimes it works then. I check then the state of the system using ambianmonitor -m (temp and cpu freq) and also top (f -> P to watch CPU id of the process)

When there's no direct oops crash in system log, some local crashes can occur, i.e. it can be segfault of some tool (ssh, top, sudo etc).

What I have already tried: updated kernel to dev-version (4.19) but got the same random crashes.

Downgraded to 4.10.0 and got the same things.

Tried to upgrade u-boot to dev version, tried to downgrade u-boot.

Uploaded u-boot to NOR flash and used USB for armbian (no SD card at all) - random crashes appear.

"Official" distro (Debian 8, kernel 3.10) works with no issue. But it's too old to use with 1-wire, I2C and other sensors.

Then I spent hours to check PC and LR values, also checked processes which was involved to crash issue but nothing common.

I tried to downclock CPU (to 480 MHz min and max) - no luck. Checked voltages (1.1 Vcore, 1.2Vdram) - everything is okay. Changed PSU - no effect.

Changed the board to another OPI PC2 one - no effect, same crashes.

Then I tried to run the system on a single core by kernel parameter maxcpus=1. And everything was FINE. No crashes for 24h.

Then I made CPU1 online (echo 1 > /sys/bus/cpu/devices/cpu1/online) and got crash after like 5 minutes of running the script (non stop).

Then I tried to play with kernel parameter isolcpus=1-3. I saw then some interrupts (cat /proc/interrupts) got served by all CPU cores, but all software were running at CPU0 core. Then no crash for like 12h. Then I started the same script on CPU2 using taskset -c 4 ./test.sh, saw it running on CPU2 (using top) and then got a crash again in 15 minutes.

Then I tried isolcpus=0,2-3, saw systemd and all services running at CPU1, run test.sh for like 4 hours on CPU1 (as well) with no problem, then run it on CPU2 taskset -c 4 ./test.sh and got crash in like 10 minutes.

Also I tried memtester on both boards I have - everything is fine.

Conclusion: it seems it's not hardware issue, something prevents apps work normally when there's high I/O load when multiple cores are used. And it seems it's not kernel itself as kernel processes work and serve interrupts during isolcpus parameter used.

Could it be an issue with systemd? There's no option in repo to update it and check.

Please help me to figure out what's happening. Thank you so much.

Some crash oops logs are below.

Reveal hidden contents

[ OK ] Started Serial Getty on ttyS0.
[ OK ] Started Set console scheme.
[ OK ] Created slice system-getty.slice.
[ OK ] Started Getty on tty1.
[ OK ] Reached target Login Prompts.
[ OK ] Started OpenBSD Secure Shell server.
[ OK ] Reached target Multi-User System.
[ OK ] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
[ OK ] Started Update UTMP about System Runlevel Changes.

Ubuntu 18.04.1 LTS orangepipc2 ttyS0

orangepipc2 login: [   38.155840] Unable to handle kernel NULL pointer dereference at virtual address 00000077
[   38.163950] pgd = ffff000008bef000
[   38.167350] [00000077] *pgd=000000007effe003, *pud=000000007effd003, *pmd=0000000000000000
[   38.175639] Internal error: Oops: 96000044 [#1] SMP
[   38.180518] Modules linked in: tun sun8i_codec_analog sun4i_codec snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer sch_fq_codel
[   38.192001] CPU: 1 PID: 7 Comm: rcu_sched Not tainted 4.10.0-sun50iw2 #7
[   38.198692] Hardware name: Xunlong Orange Pi PC 2 (DT)
[   38.203824] task: ffff80003d864b00 task.stack: ffff80003d898000
[   38.209741] PC is at rcu_gp_kthread+0x3c8/0x7c8
[   38.214263] LR is at rcu_gp_kthread+0x394/0x7c8
[   38.218792] pc : [<ffff0000080ff3c8>] lr : [<ffff0000080ff394>] pstate: 20000145
[   38.226175] sp : ffff80003d89bdd0
[   38.229483] x29: 0000000000000000 x28: 0000000000000000
[   38.234786] x27: 0000000000000000 x26: ffff000008b32000
[   38.240092] x25: 0000000000000003 x24: ffff80003d89be50
[   38.245407] x23: 0000000000000001 x22: 0000000000000004
[   38.250713] x21: ffff000008b16000 x20: ffff000008b32b20
[   38.256015] x19: ffff000008b32800 x18: ffff000008ba7a00
[   38.261330] x17: 0000ffff9d099010 x16: ffff0000080ad170
[   38.266639] x15: fffffffffffffc68 x14: 000000000000024d
[   38.271947] x13: ffff000008a3c000 x12: dead000000000100
[   38.277252] x11: ffff7e0000000000 x10: 0000000000000860
[   38.282564] x9 : ffff80003d89bcb0 x8 : ffff80003d8653c0
[   38.287871] x7 : ffff80003ef99c80 x6 : 00000008e2435045
[   38.293174] x5 : 0000000000000000 x4 : 0000000000000000
[   38.298476] x3 : 0000000000000078 x2 : 0000000000000077
[   38.303778] x1 : 00000000ffff004b x0 : 00000000000005f2
[   38.309088]
[   38.310581] Process rcu_sched (pid: 7, stack limit = 0xffff80003d898000)
[   38.317269] Stack: (0xffff80003d89bdd0 to 0xffff80003d89c000)
[   38.323015] bdc0:                                   ffff80003d89be60 ffff0000080c5a28
[   38.330847] bde0: ffff80003d831300 ffff80003d831200 ffff000008ba5860 ffff80003d864b00
[   38.338669] be00: ffff0000089ca578 ffff000008b32800 ffff0000080ff000 ffff80003d831338
[   38.346484] be20: ffff80003d857ce0 0000000000000000 ffff000008b37d0d ffff80003d864b00
[   38.354301] be40: 00ff80003d831300 ffff80003d864b00 ffff80003d89be50 ffff80003d89be50
[   38.362118] be60: 0000000000000000 ffff0000080826c0 ffff0000080c5938 ffff80003d831200
[   38.369934] be80: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[   38.377751] bea0: 0000000000000000 0000000000000000 0000000000000000 ffffffffffffffff
[   38.385566] bec0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[   38.393381] bee0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[   38.401196] bf00: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[   38.409011] bf20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[   38.416826] bf40: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[   38.424641] bf60: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[   38.432457] bf80: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[   38.440272] bfa0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[   38.448087] bfc0: 0000000000000000 0000000000000005 0000000000000000 0000000000000000
[   38.455901] bfe0: 0000000000000000 0000000000000000 ffffffffffffffff ffffffffffffffff
[   38.463715] Call trace:
[   38.466156] Exception stack(0xffff80003d89bc00 to 0xffff80003d89bd30)
[   38.472585] bc00: ffff000008b32800 0001000000000000 ffff80003d89bdd0 ffff0000080ff3c8
[   38.480400] bc20: ffff80003d89bc30 ffff0000080df768 ffff80003d89bcd0 ffff000008811d7c
[   38.488214] bc40: ffff80003ef9f900 ffff000008b18000 ffff000008af1000 ffff80003d864b00
[   38.496031] bc60: ffff80003d89bc90 ffff0000080db368 ffff80003d864b80 ffff000008b18000
[   38.503845] bc80: 0000000000000001 0000000000000000 ffff80003d89bcd0 ffff000008811e30
[   38.511660] bca0: 00000000000005f2 00000000ffff004b 0000000000000077 0000000000000078
[   38.519475] bcc0: 0000000000000000 0000000000000000 00000008e2435045 ffff80003ef99c80
[   38.527291] bce0: ffff80003d8653c0 ffff80003d89bcb0 0000000000000860 ffff7e0000000000
[   38.535106] bd00: dead000000000100 ffff000008a3c000 000000000000024d fffffffffffffc68
[   38.542920] bd20: ffff0000080ad170 0000ffff9d099010
[   38.547795] [<ffff0000080ff3c8>] rcu_gp_kthread+0x3c8/0x7c8
[   38.553359] Code: 9101e3a3 f94542a1 9101dfa2 91000400 (3901dfbf)
[   38.559577] ---[ end trace f49e754a16b6761c ]---
[   43.200819] fuse init (API version 7.26)
Sun Dec 9 08:21:06 MSK 2018
Sun Dec 9 08:21:11 MSK 2018
Sun Dec 9 08:21:16 MSK 2018
[   59.156035] INFO: rcu_sched detected stalls on CPUs/tasks:
[   59.161537] (detected by 2, t=5253 jiffies, g=1185, c=1184, q=6363)
[   59.167896] All QSes seen, last rcu_sched kthread activity 5254 (4294907087-4294901833), jiffies_till_next_fqs=1, root ->qsmask 0x0
[   59.179697] cat             R running task        0 1638   1637 0x00000000
[   59.186736] Call trace:
[   59.189189] [<ffff000008087a20>] dump_backtrace+0x0/0x220
[   59.194579] [<ffff000008087c54>] show_stack+0x14/0x20
[   59.199624] [<ffff0000080d0c84>] sched_show_task+0x10c/0x170
[   59.205279] [<ffff0000081002e4>] rcu_check_callbacks+0x854/0x858
[   59.211277] [<ffff000008102c74>] update_process_times+0x2c/0x58
[   59.217189] [<ffff00000811205c>] tick_sched_handle.isra.7+0x24/0x70
[   59.223444] [<ffff0000081120ec>] tick_sched_timer+0x44/0x90
[   59.229029] [<ffff0000081037a8>] __hrtimer_run_queues+0xf0/0x178
[   59.235034] [<ffff000008103ae8>] hrtimer_interrupt+0xa0/0x220
[   59.240774] [<ffff00000869b970>] arch_timer_handler_phys+0x30/0x40
[   59.246946] [<ffff0000080f61b8>] handle_percpu_devid_irq+0x78/0x130
[   59.253204] [<ffff0000080f0eac>] generic_handle_irq+0x24/0x38
[   59.258943] [<ffff0000080f152c>] __handle_domain_irq+0x5c/0xb8
[   59.264768] [<ffff000008080d24>] gic_handle_irq+0x54/0xa8
[   59.270157] Exception stack(0xffff80003c423be0 to 0xffff80003c423d10)
[   59.276586] 3be0: 0000ffffa7556d40 00000000000002c0 0000000000001000 0000000000000001
[   59.284418] 3c00: 0000000000020000 0001000000000000 0000000000000020 0000ffffa753d000
[   59.292240] 3c20: 000000000000003f 0000ffffa78742a0 0000000000000840 0000000000000000
[   59.300057] 3c40: 0000000000000001 000000000000270f 0000000000000002 0000000000000000
[   59.307874] 3c60: ffff0000081cb7b0 0000ffffa77bba78 0000ffffa784ca70 0000000000001000
[   59.315689] 3c80: 0000000000019000 ffff80003c423de0 ffff80003c8a0000 ffff80003c423eb8
[   59.323503] 3ca0: 0000000000000015 0000000000000123 000000000000003f ffff80003c423e18
[   59.331320] 3cc0: 0000000000001000 ffff80003c423d10 ffff0000084c7fa0 ffff80003c423d10
[   59.339136] 3ce0: ffff0000084b2388 0000000020000145 ffff80003c0f5780 ffff80003c8a0000
[   59.346951] 3d00: 0001000000000000 ffff000008812500
[   59.351825] [<ffff000008081ff4>] el1_irq+0xb4/0x140
[   59.356700] [<ffff0000084b2388>] __clear_user+0x18/0x90
[   59.361919] [<ffff00000856882c>] read_iter_zero+0x4c/0xc0
[   59.367312] [<ffff0000081c9064>] __vfs_read+0xac/0xf8
[   59.372354] [<ffff0000081ca2fc>] vfs_read+0x84/0x140
[   59.377310] [<ffff0000081cb7f4>] SyS_read+0x44/0xa0
[   59.382179] [<ffff000008082730>] el0_svc_naked+0x24/0x28
[   59.387484] rcu_sched kthread starved for 5309 jiffies! g1185 c1184 f0x2 RCU_GP_DOING_FQS(4) ->state=0x40

Reveal hidden contents

[ 100.848748] Unable to handle kernel NULL pointer dereference at virtual address 000000d0
[ 100.856945] pgd = ffff80003c641000
[ 100.860346] [000000d0] *pgd=0000000000000000
[ 100.864667] Internal error: Oops: 96000044 [#1] SMP
[ 100.869541] Modules linked in: fuse tun sun4i_codec sun8i_codec_analog snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer sch_fq_codel
[ 100.881456] CPU: 2 PID: 1439 Comm: test.sh Not tainted 4.10.0-sun50iw2 #7
[ 100.888232] Hardware name: Xunlong Orange Pi PC 2 (DT)
[ 100.893362] task: ffff80003ca0d780 task.stack: ffff80003c614000
[ 100.899281] PC is at copy_process.isra.5.part.6+0x150/0x1470
[ 100.904934] LR is at copy_process.isra.5.part.6+0x134/0x1470
[ 100.910584] pc : [<ffff0000080a6bd8>] lr : [<ffff0000080a6bbc>] pstate: 40000145
[ 100.917965] sp : ffff80003c617d50
[ 100.921273] x29: 0000000000000000 x28: 0000000001200011
[ 100.926579] x27: ffff80003c880000 x26: ffff80003c810c80
[ 100.931883] x25: 0000000000000000 x24: 0000000000000000
[ 100.937186] x23: 0000000000000000 x22: 0000000000000000
[ 100.942490] x21: 0000000000000000 x20: 0000ffff8d4cac80
[ 100.947793] x19: 0000000000000000 x18: 0000000000000000
[ 100.953098] x17: 0000ffff8d3f27c0 x16: ffff0000080a8370
[ 100.958402] x15: 0000000000000000 x14: 0000000000000000
[ 100.963705] x13: 0000000000000000 x12: 0000000000000000
[ 100.969009] x11: 0000000000000000 x10: 0000000000000000
[ 100.974312] x9 : 0000000000000000 x8 : 0000000000000000
[ 100.979614] x7 : 0000000000000000 x6 : ffff80003c811900
[ 100.984916] x5 : 0000000000000000 x4 : 0000000000000000
[ 100.990221] x3 : ffff000008af5739 x2 : 0000000000000001
[ 100.995524] x1 : ffff80003c810c80 x0 : 0000000000000001
[ 101.000826]
[ 101.002315] Process test.sh (pid: 1439, stack limit = 0xffff80003c614000)
[ 101.009093] Stack: (0xffff80003c617d50 to 0xffff80003c618000)
[ 101.014831] 7d40:                                   ffff80003c617e40 ffff0000080a8058
[ 101.022648] 7d60: 0000000001200011 0000000000000000 ffffffffffffffff 0000000000000000
[ 101.030465] 7d80: 0000000040000000 0000000000000015 0000000000000123 00000000000000dc
[ 101.038281] 7da0: ffff000008822000 ffff80003ca0d780 ffff000008828178 000000009200004f
[ 101.046098] 7dc0: 0000aaaab2f5c908 ffff80003c617ec0 0000000000000000 0000000000000024
[ 101.053914] 7de0: 000000009200004f 0000aaaab2f5c908 0000aaaac955f8b0 ffff80003ca0d780
[ 101.061730] 7e00: 0000000001200011 0000000000000002 0000000000000000 ffff00000808236c
[ 101.069547] 7e20: 0000000000000000 ffff000008ba4000 ffffffffffffffff 0000aaaab2f39ac4
[ 101.077363] 7e40: ffff80003c617eb0 ffff0000080a8388 0000000000000000 00008000364c5000
[ 101.085180] 7e60: ffffffffffffffff 0000ffff8d3f28a4 0000000040000000 0000000000000015
[ 101.092998] 7e80: 0000000000000123 00000000000000dc ffff80003c617eb0 ffff0000081c75d0
[ 101.100817] 7ea0: 0000000000000000 00008000364c5000 0000000000000000 ffff000008082730
[ 101.108634] 7ec0: 0000000001200011 0000000000000000 0000000000000000 0000000000000000
[ 101.116451] 7ee0: 0000ffff8d4cac80 0000ffff8d4cabb0 0000aaaac9561120 000000000003e9a3
[ 101.124269] 7f00: 00000000000000dc 0000aaaab2f5c000 0101010101010101 0000000000000000
[ 101.132085] 7f20: 0101010101010101 000000000000270f 0000000000000001 0000000000000020
[ 101.139901] 7f40: 0000aaaab2f5baf0 0000ffff8d3f27c0 0000ffff8d4a3a70 0000000000000000
[ 101.147716] 7f60: 0000000000000000 0000ffff8d4a2000 0000aaaac955f8b0 0000ffff8d4caaa0
[ 101.155532] 7f80: 0000ffff8d4cb2a0 0000000000000000 0000aaaab2f5c0d8 0000aaaac955f8b0
[ 101.163348] 7fa0: 0000ffffc0c044a0 0000ffffc0c04390 0000aaaab2f3f480 0000ffffc0c04390
[ 101.171165] 7fc0: 0000ffff8d3f28a4 0000000040000000 0000000001200011 00000000000000dc
[ 101.178981] 7fe0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[ 101.186796] Call trace:
[ 101.189239] Exception stack(0xffff80003c617b80 to 0xffff80003c617cb0)
[ 101.195672] 7b80: 0000000000000000 0001000000000000 ffff80003c617d50 ffff0000080a6bd8
[ 101.203488] 7ba0: ffff80003c617c20 ffff000008184af8 ffff7e00017000c0 ffff7e000074fb80
[ 101.211305] 7bc0: ffff80003c617d08 0000000000000180 000000003ca07840 ffff000008b9b600
[ 101.219122] 7be0: 0000000000000000 0000000000000140 ffff800000000001 ffff000008184b6c
[ 101.226937] 7c00: ffff80003c617d50 ffff0000080a6ba4 0000000000000000 0000ffff8d4cac80
[ 101.234754] 7c20: 0000000000000001 ffff80003c810c80 0000000000000001 ffff000008af5739
[ 101.242569] 7c40: 0000000000000000 0000000000000000 ffff80003c811900 0000000000000000
[ 101.250385] 7c60: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[ 101.258201] 7c80: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[ 101.266016] 7ca0: ffff0000080a8370 0000ffff8d3f27c0
[ 101.270890] [<ffff0000080a6bd8>] copy_process.isra.5.part.6+0x150/0x1470
[ 101.277583] Code: 350019a0 2a0203e0 aa1a03e1 f903435f (b900d3a2)
[ 101.283806] ---[ end trace 2625318557f33a56 ]---

Reveal hidden contents

[    3.319363] sun8i-emac 1c30000.ethernet: PHY regulator found
[    3.325754] input: r_gpio_keys as /devices/platform/r_gpio_keys/input/input0
[    3.333011] of_cfs_init
[    3.335489] of_cfs_init: OK
[    3.338387] gmac-3v3: disabling
[    3.341539] ALSA device list:
[    3.344505]   No soundcards found.
[    3.348283] Freeing unused kernel memory: 448K
Loading, please wait...
starting version 237
[    3.417575] systemd-udevd[203]: unhandled level 0 translation fault (11) at 0x00000038, esr 0x92000004
[    3.426960] pgd = ffff80003be82000
[    3.430373] [00000038] *pgd=0000000000000000
[    3.434643]
[    3.436140] CPU: 1 PID: 203 Comm: systemd-udevd Not tainted 4.10.0-sun50iw2 #7
[    3.443356] Hardware name: Xunlong Orange Pi PC 2 (DT)
[    3.448490] task: ffff80003c19f080 task.stack: ffff80003bec4000
[    3.454409] PC is at 0xaaaad4fce1c8
[    3.457896] LR is at 0xaaaad4fce1b0
[    3.461382] pc : [<0000aaaad4fce1c8>] lr : [<0000aaaad4fce1b0>] pstate: 60000000
[    3.468768] sp : 0000ffffeba07510
[    3.472080] x29: 0000000000000000 x28: 000000000000000e
[    3.477389] x27: 0000aaaaeca4a140 x26: 00000000000002ea
[    3.482697] x25: 0000aaaaeca6a180 x24: 0000000000000054
[    3.488006] x23: 0000aaaaeca6a4a0 x22: 0000aaaaeca66b80
[    3.493340] x21: 0000aaaaeca6b2d0 x20: 000000000000007c
[    3.498655] x19: 0000aaaad5036000 x18: 0000ffff9d690a70
[    3.503963] x17: 0000ffff9d60e5f8 x16: 0000aaaad5036a58
[    3.509269] x15: 0000000000000000 x14: 0000000000000002
[    3.514574] x13: 000000000000270f x12: 0000000000000001
[    3.519880] x11: 0000000000000000 x10: 0000000000000001
[    3.525186] x9 : 0000ffff9d6b9c90 x8 : 00000000000000d3
[    3.530492] x7 : 7f7fffffff7f7fff x6 : fefffefe9c6809cf

Reveal hidden contents

[ OK ] Started LSB: Load kernel modules needed to enable cpufreq scaling.
         Starting LSB: set CPUFreq kernel parameters...
[   11.379399] Unable to handle kernel NULL pointer dereference at virtual address 00000038
[   11.379403] Unable to handle kernel NULL pointer dereference at virtual address 00000038
[   11.379406] Unable to handle kernel NULL pointer dereference at virtual address 00000038
[   11.379409] Unable to handle kernel NULL pointer dereference at virtual address 00000038
[   11.379417] Mem abort info:
[   11.379418] Mem abort info:
[   11.379419] Mem abort info:
[   11.379422]   Exception class = DABT (current EL), IL = 32 bits
[   11.379424]   Exception class = DABT (current EL), IL = 32 bits
[   11.379426]   Exception class = DABT (current EL), IL = 32 bits
[   11.379428]   SET = 0, FnV = 0
[   11.379429]   SET = 0, FnV = 0
[   11.379431]   SET = 0, FnV = 0
[   11.379432]   EA = 0, S1PTW = 0
[   11.379433]   EA = 0, S1PTW = 0
[   11.379434]   EA = 0, S1PTW = 0
[   11.379435] Data abort info:
[   11.379436] Data abort info:
[   11.379437] Data abort info:
[   11.379438]   ISV = 0, ISS = 0x00000006
[   11.379439]   ISV = 0, ISS = 0x00000004
[   11.379440]   ISV = 0, ISS = 0x00000004
[   11.379442]   CM = 0, WnR = 0
[   11.379443]   CM = 0, WnR = 0
[   11.379444]   CM = 0, WnR = 0
[   11.379448] user pgtable: 4k pages, 48-bit VAs, pgd = ffff80003508c000
[   11.379451] user pgtable: 4k pages, 48-bit VAs, pgd = ffff8000351b8000
[   11.379454] user pgtable: 4k pages, 48-bit VAs, pgd = ffff800034572000
[   11.379456] [0000000000000038] *pgd=000000007568b003
[   11.379458] [0000000000000038] *pgd=0000000000000000
[   11.379460] [0000000000000038] *pgd=0000000000000000
[   11.379461] , *pud=0000000075699003
[   11.379464] , *pmd=0000000000000000
[   11.379467] Internal error: Oops: 96000004 [#1] SMP
[   11.379469] Modules linked in: sun8i_codec_analog sun4i_i2s ir_lirc_codec lirc_dev snd_soc_hdmi_codec sun4i_codec snd_soc_simple_card snd_soc_simple_card_utils snd_soc_core sunxi_cir sun4i_gpadc_iio snd_pcm_dmaengine snd_pcm snd_timer iio_hwmon industrialio zram sch_fq_codel dw_hdmi_cec dw_hdmi_i2s_audio sy8106a_regulator sun8i_dw_hdmi dw_hdmi cec rc_core uas sunxi musb_hdrc sun4i_tcon sun8i_mixer sun4i_drm
[   11.379524] CPU: 3 PID: 724 Comm: armbian-hardwar Not tainted 4.14.78-sunxi64 #416
[   11.379526] Hardware name: Xunlong Orange Pi PC 2 (DT)
[   11.379528] task: ffff80003539db00 task.stack: ffff00000a5d8000
[   11.379541] PC is at cpu_load_update_active+0x4c/0xa8
[   11.379546] LR is at cpu_load_update_active+0x9c/0xa8
[   11.379549] pc : [<ffff0000080e3064>] lr : [<ffff0000080e30b4>] pstate: 800001c5
[   11.379550] sp : ffff00000801bd90
[   11.379551] x29: 0000000000000000 x28: ffff80003539db00
[   11.379556] x27: ffff800037fb6dc0 x26: ffff800037fb6dc0
[   11.379560] x25: ffff800037fb6dd0 x24: 00000002a600d616
[   11.379563] x23: ffff80003539db00 x22: 0000000000000003
[   11.379567] x21: 0000000000000404 x20: ffff800037fbb000
[   11.379571] x19: ffff000008c68d88 x18: 0000ffffbc77fa70
[   11.379575] x17: 0000ffffbc6ceb60 x16: ffff0000081ff200
[   11.379579] x15: 0000000000000406 x14: 0000000000000000
[   11.379582] x13: ffff000008998918 x12: 0000000000000001
[   11.379586] x11: ffff000008998920 x10: 0000000000000406
[   11.379590] x9 : 0000000000000004 x8 : ffff800037fbb030
[   11.379594] x7 : 0000000000000020 x6 : 0000000000000404
[   11.379597] x5 : 00000002a6438871 x4 : 000000000000000f
[   11.379601] x3 : 000000001dcd6500 x2 : 0000000016349bec
[   11.379604] x1 : 00000002900eec85 x0 : ffff800037fbb000
[   11.379610] Process armbian-hardwar (pid: 724, stack limit = 0xffff00000a5d8000)
[   11.379612] Call trace:
[   11.379616] Exception stack(0xffff00000801bc50 to 0xffff00000801bd90)
[   11.379620] bc40:                                   ffff800037fbb000 00000002900eec85
[   11.379624] bc60: 0000000016349bec 000000001dcd6500 000000000000000f 00000002a6438871
[   11.379628] bc80: 0000000000000404 0000000000000020 ffff800037fbb030 0000000000000004
[   11.379633] bca0: 0000000000000406 ffff000008998920 0000000000000001 ffff000008998918
[   11.379637] bcc0: 0000000000000000 0000000000000406 ffff0000081ff200 0000ffffbc6ceb60
[   11.379641] bce0: 0000ffffbc77fa70 ffff000008c68d88 ffff800037fbb000 0000000000000404
[   11.379645] bd00: 0000000000000003 ffff80003539db00 00000002a600d616 ffff800037fb6dd0
[   11.379649] bd20: ffff800037fb6dc0 ffff800037fb6dc0 ffff80003539db00 0000000000000000
[   11.379653] bd40: ffff0000080e30b4 ffff00000801bd90 ffff0000080e3064 00000000800001c5
[   11.379657] bd60: ffff800037fbb000 ffff80003539db80 0000ffffffffffff ffff0000080e1a84
[   11.379660] bd80: 0000000000000000 ffff0000080e3064
[   11.379666] [<ffff0000080e3064>] cpu_load_update_active+0x4c/0xa8
[   11.379672] Code: f9454000 eb020002 54000141 91362273 (f9401fa1)
[   11.379676] ---[ end trace a5890dadb94a76a7 ]---
[   11.379679] Kernel panic - not syncing: Fatal exception in interrupt
[   11.379684] SMP: stopping secondary CPUs
[   11.812830] Mem abort info:
[   11.815620]   Exception class = DABT (current EL), IL = 32 bits
[   11.821531]   SET = 0, FnV = 0
[   11.824581]   EA = 0, S1PTW = 0
[   11.827716] Data abort info:
[   11.830592]   ISV = 0, ISS = 0x00000006
[   11.834422]   CM = 0, WnR = 0
[   11.837386] user pgtable: 4k pages, 48-bit VAs, pgd = ffff8000350b9000
[   11.843904] [0000000000000038] *pgd=0000000075795003, *pud=00000000757a4003, *pmd=0000000000000000
f[   12.422302] SMP: failed to stop secondary CPUs 0-3
[   12.427089] Kernel Offset: disabled
[   12.430574] CPU features: 0x0802004
[   12.434058] Memory Limit: none
[   12.437110] Rebooting in 10 seconds..
[   22.441187] SMP: stopping secondary CPUs
[   23.487718] SMP: failed to stop secondary CPUs 0-3

This looks like to be a flaw in kernel internals. Please report it in linux-sunxi mainlining effort newsgroup

August 16, 2018

Hi all

After having used a lot the OPiPC2 with Armbian, I am now adding support for this board in openwrt.

The first add board patch, has been merged recently in snapshot branch and works ok.

For the first implementation I set the MUSB port role to host, but now my goal is to set it in OTG, making this port available for usb serial console, connecting a host PC to it.

So, I built the needed support for g_serial in kernel and give a try, but I cannot make it work

The host PC detects just nothing, as the OpiPC2 does not detect a USB host being connected to it

Checking the dmesg I see something suspicious:

[    0.614423] sun4i-usb-phy 1c19400.phy: Couldn't request ID GPIO

The only gpio managed by this USB phy (that is the one attached to the MUSB 1c19000) is the role switch PIN, as far as I understand:

usb0_id_det-gpios = <&pio 6 12 GPIO_ACTIVE_HIGH>; /* PG12 */

The dts are the mailine ones of kernel 4.14.x, the OTG support for H5 has been added in 4.12.x but I think I remember that I had the same dmesg log also in Armbian (I run it till 4.15.x)

PG12 is not taken by other nodes, so I really don't understand the problem here, IF this is a problem and not a warning that I shall just ignore

Thanks, bye

February 9, 2018

JMS567 should not be amongst them so in your situation most probably you should check the cable and USB3-A receptacle which is known to be utter crap (the low end storage world will be a better place once we have USB-C everywhere).

Folks, if you see 'uas' in your logs then it's often just the uas driver reporting problems happening one layer below. Don't shoot the messenger even if it seems 'fun' to blame software and a protocol for hardware issues.

It is not the cable. In BOT mode (with quirks in modules.d) works perfectly

Inviato dal mio SM-G955F utilizzando Tapatalk

February 9, 2018

alright thanks@edupv

Oh, and one another problem that bugs me once every one or two week in armbian 5.27, but in 5.40 it's almost everyday,
The UASP stopped responding requests, it freeze entire system for several minutes, and every I/O to my hard drive makes the OS unresponsive.

I was using ASMedia ASM1153E a years ago, and it show much problem. So I switch to JMicron JMS578, which doesn't error as often like ASMedia 1153E.
I already read here (http://linux-sunxi.org/USB/UAS) and found out both ASM1153E and JMS578 is listed as OK right now.

below is dmesg output when it started to freeze when I'm copying a file from my PC to OrangePi via Windows 10 SMB. Most of the time, I'm just unplug & plug it again, followed by reboot if the problem still occured.
Spoiler

[47768.032826] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [47768.032841] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 58 3d e0 00 00 20 00[47768.032871] scsi host1: uas_eh_device_reset_handler start[47768.160815] usb 5-1: reset high-speed USB device number 2 using ehci-platform[47768.317930] scsi host1: uas_eh_device_reset_handler success[50330.163432] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [50330.163447] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 6b 33 a0 00 00 20 00[50330.163479] scsi host1: uas_eh_device_reset_handler start[50330.291422] usb 5-1: reset high-speed USB device number 2 using ehci-platform[50330.448545] scsi host1: uas_eh_device_reset_handler success[50526.777755] sd 1:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD [50526.777769] sd 1:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 03 6c d9 c0 00 00 20 00[50526.777801] scsi host1: uas_eh_device_reset_handler start[50526.905758] usb 5-1: reset high-speed USB device number 2 using ehci-platform[50527.062920] scsi host1: uas_eh_device_reset_handler success[51663.454466] sd 1:0:0:0: [sda] tag#2 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD [51663.454481] sd 1:0:0:0: [sda] tag#2 CDB: opcode=0x28 28 00 03 75 30 e0 00 00 20 00[51663.454493] sd 1:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD [51663.454499] sd 1:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 03 75 30 c0 00 00 20 00[51663.454509] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [51663.454515] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 75 30 a0 00 00 20 00[51663.454546] scsi host1: uas_eh_device_reset_handler start[51663.590458] usb 5-1: reset high-speed USB device number 2 using ehci-platform[51663.747660] scsi host1: uas_eh_device_reset_handler success[51845.732387] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [51845.732402] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 76 72 60 00 00 20 00[51845.732432] scsi host1: uas_eh_device_reset_handler start[51845.860374] usb 5-1: reset high-speed USB device number 2 using ehci-platform[51846.017539] scsi host1: uas_eh_device_reset_handler success[51894.886013] sd 1:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD [51894.886029] sd 1:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 03 76 c3 00 00 00 20 00[51894.886042] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [51894.886048] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 76 c2 e0 00 00 20 00[51894.886077] scsi host1: uas_eh_device_reset_handler start[51895.018012] usb 5-1: reset high-speed USB device number 2 using ehci-platform[51895.175164] scsi host1: uas_eh_device_reset_handler success[52292.211152] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [52292.211167] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 79 32 40 00 00 20 00[52292.211198] scsi host1: uas_eh_device_reset_handler start[52292.339142] usb 5-1: reset high-speed USB device number 2 using ehci-platform[52292.496285] scsi host1: uas_eh_device_reset_handler success[52404.854865] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [52404.854879] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 7a f4 a0 00 00 20 00[52404.854911] scsi host1: uas_eh_device_reset_handler start[52404.982872] usb 5-1: reset high-speed USB device number 2 using ehci-platform[52405.140037] scsi host1: uas_eh_device_reset_handler success[54092.463588] sd 1:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD [54092.463602] sd 1:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 03 8c 92 a0 00 00 20 00[54092.463615] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [54092.463621] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 8c 92 00 00 00 20 00[54092.463651] scsi host1: uas_eh_device_reset_handler start[54092.595592] usb 5-1: reset high-speed USB device number 2 using ehci-platform[54092.752780] scsi host1: uas_eh_device_reset_handler success[54538.942597] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [54538.942612] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 8f 2d c0 00 00 20 00[54538.942644] scsi host1: uas_eh_device_reset_handler start[54539.070600] usb 5-1: reset high-speed USB device number 2 using ehci-platform[54539.227780] scsi host1: uas_eh_device_reset_handler success[55057.103819] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [55057.103834] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 91 fa 20 00 00 20 00[55057.103865] scsi host1: uas_eh_device_reset_handler start[55057.231835] usb 5-1: reset high-speed USB device number 2 using ehci-platform[55057.389024] scsi host1: uas_eh_device_reset_handler success[55653.090860] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [55653.090874] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 96 59 80 00 00 20 00[55653.090906] scsi host1: uas_eh_device_reset_handler start[55653.218859] usb 5-1: reset high-speed USB device number 2 using ehci-platform[55653.376021] scsi host1: uas_eh_device_reset_handler success[56503.038029] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [56503.038044] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 9b eb e0 00 00 20 00[56503.038074] scsi host1: uas_eh_device_reset_handler start[56503.166015] usb 5-1: reset high-speed USB device number 2 using ehci-platform[56503.323149] scsi host1: uas_eh_device_reset_handler success[56711.940696] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [56711.940711] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 9d 57 20 00 00 20 00[56711.940743] scsi host1: uas_eh_device_reset_handler start[56712.068695] usb 5-1: reset high-speed USB device number 2 using ehci-platform[56712.225894] scsi host1: uas_eh_device_reset_handler success[56845.065067] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [56845.065081] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 9e 28 c0 00 00 20 00[56845.065113] scsi host1: uas_eh_device_reset_handler start[56845.193056] usb 5-1: reset high-speed USB device number 2 using ehci-platform[56845.350268] scsi host1: uas_eh_device_reset_handler success[56945.420365] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [56945.420379] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 9e ca 60 00 00 20 00[56945.420410] scsi host1: uas_eh_device_reset_handler start[56945.548357] usb 5-1: reset high-speed USB device number 2 using ehci-platform[56945.705523] scsi host1: uas_eh_device_reset_handler success[57299.736002] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [57299.736016] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 a1 59 80 00 00 20 00[57299.736048] scsi host1: uas_eh_device_reset_handler start[57299.863990] usb 5-1: reset high-speed USB device number 2 using ehci-platform[57300.021139] scsi host1: uas_eh_device_reset_handler success[57723.685896] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [57723.685910] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 a4 37 20 00 00 20 00[57723.685941] scsi host1: uas_eh_device_reset_handler start[57723.813885] usb 5-1: reset high-speed USB device number 2 using ehci-platform[57723.971011] scsi host1: uas_eh_device_reset_handler success[57890.349013] sd 1:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08[57890.349040] sd 1:0:0:0: [sda] tag#0 Sense Key : 0xb [current] [57890.349047] sd 1:0:0:0: [sda] tag#0 ASC=0x47 ASCQ=0x3 [57890.349058] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 a5 bb c0 00 00 20 00[57890.349065] print_req_error: I/O error, dev sda, sector 61193152[57938.732871] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [57938.732885] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 a6 03 60 00 00 20 00[57938.732916] scsi host1: uas_eh_device_reset_handler start[57938.860865] usb 5-1: reset high-speed USB device number 2 using ehci-platform[57939.018019] scsi host1: uas_eh_device_reset_handler success[92577.642693] EXT4-fs (sda1): error count since last fsck: 1[92577.642712] EXT4-fs (sda1): initial error at time 1517862148: ext4_find_entry:1436: inode 2113537[92577.642729] EXT4-fs (sda1): last error at time 1517862148: ext4_find_entry:1436: inode 2113537[97339.405484] sd 1:0:0:0: [sda] tag#4 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD [97339.405498] sd 1:0:0:0: [sda] tag#4 CDB: opcode=0x2a 2a 00 03 f2 f8 00 00 04 00 00[97339.405512] sd 1:0:0:0: [sda] tag#3 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD [97339.405518] sd 1:0:0:0: [sda] tag#3 CDB: opcode=0x2a 2a 00 03 f2 f4 00 00 04 00 00[97339.405527] sd 1:0:0:0: [sda] tag#2 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD [97339.405533] sd 1:0:0:0: [sda] tag#2 CDB: opcode=0x2a 2a 00 03 f2 f0 00 00 04 00 00[97339.405543] sd 1:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD [97339.405549] sd 1:0:0:0: [sda] tag#1 CDB: opcode=0x2a 2a 00 03 f2 ec 00 00 04 00 00[97339.405558] sd 1:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [97339.405564] sd 1:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 03 f2 e8 00 00 04 00 00[97339.405576] sd 1:0:0:0: [sda] tag#27 uas_eh_abort_handler 0 uas-tag 28 inflight: CMD [97339.405582] sd 1:0:0:0: [sda] tag#27 CDB: opcode=0x2a 2a 00 03 f2 e4 00 00 04 00 00[97339.405591] sd 1:0:0:0: [sda] tag#26 uas_eh_abort_handler 0 uas-tag 27 inflight: CMD [97339.405597] sd 1:0:0:0: [sda] tag#26 CDB: opcode=0x2a 2a 00 03 f2 e0 00 00 04 00 00[97339.405606] sd 1:0:0:0: [sda] tag#25 uas_eh_abort_handler 0 uas-tag 26 inflight: CMD [97339.405612] sd 1:0:0:0: [sda] tag#25 CDB: opcode=0x2a 2a 00 03 f2 dc 00 00 04 00 00[97339.405621] sd 1:0:0:0: [sda] tag#24 uas_eh_abort_handler 0 uas-tag 25 inflight: CMD [97339.405627] sd 1:0:0:0: [sda] tag#24 CDB: opcode=0x2a 2a 00 03 f2 d8 00 00 04 00 00[97339.405637] sd 1:0:0:0: [sda] tag#23 uas_eh_abort_handler 0 uas-tag 24 inflight: CMD [97339.405642] sd 1:0:0:0: [sda] tag#23 CDB: opcode=0x2a 2a 00 03 f2 d4 00 00 04 00 00[97339.405652] sd 1:0:0:0: [sda] tag#22 uas_eh_abort_handler 0 uas-tag 23 inflight: CMD OUT [97339.405658] sd 1:0:0:0: [sda] tag#22 CDB: opcode=0x2a 2a 00 03 f2 d0 00 00 04 00 00[97366.030292] sd 1:0:0:0: tag#5 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD [97366.030305] sd 1:0:0:0: tag#5 CDB: opcode=0x0 00 00 00 00 00 00[97366.030341] scsi host1: uas_eh_device_reset_handler start[97366.194294] usb 5-1: reset high-speed USB device number 2 using ehci-platform[97366.351493] scsi host1: uas_eh_device_reset_handler success[97374.990566] sd 1:0:0:0: [sda] tag#22 uas_eh_abort_handler 0 uas-tag 23 inflight: CMD [97374.990581] sd 1:0:0:0: [sda] tag#22 CDB: opcode=0x12 12 00 00 00 24 00[97398.799307] sd 1:0:0:0: [sda] tag#28 uas_eh_abort_handler 0 uas-tag 29 inflight: CMD [97398.799322] sd 1:0:0:0: [sda] tag#28 CDB: opcode=0x28 28 00 03 c0 08 68 00 00 08 00[97398.799337] sd 1:0:0:0: [sda] tag#21 uas_eh_abort_handler 0 uas-tag 22 inflight: CMD [97398.799343] sd 1:0:0:0: [sda] tag#21 CDB: opcode=0x2a 2a 00 03 f4 04 00 00 04 00 00[97398.799353] sd 1:0:0:0: [sda] tag#20 uas_eh_abort_handler 0 uas-tag 21 inflight: CMD [97398.799359] sd 1:0:0:0: [sda] tag#20 CDB: opcode=0x2a 2a 00 03 f4 00 00 00 04 00 00[97398.799368] sd 1:0:0:0: [sda] tag#19 uas_eh_abort_handler 0 uas-tag 20 inflight: CMD [97398.799374] sd 1:0:0:0: [sda] tag#19 CDB: opcode=0x2a 2a 00 03 f3 fc 00 00 04 00 00[97398.799384] sd 1:0:0:0: [sda] tag#18 uas_eh_abort_handler 0 uas-tag 19 inflight: CMD [97398.799389] sd 1:0:0:0: [sda] tag#18 CDB: opcode=0x2a 2a 00 03 f3 f8 00 00 04 00 00[97398.799398] sd 1:0:0:0: [sda] tag#17 uas_eh_abort_handler 0 uas-tag 18 inflight: CMD [97398.799404] sd 1:0:0:0: [sda] tag#17 CDB: opcode=0x2a 2a 00 03 f3 f4 00 00 04 00 00[97398.799414] sd 1:0:0:0: [sda] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: CMD [97398.799419] sd 1:0:0:0: [sda] tag#16 CDB: opcode=0x2a 2a 00 03 f3 f0 00 00 04 00 00[97398.799452] scsi host1: uas_eh_device_reset_handler start[97398.951299] usb 5-1: reset high-speed USB device number 2 using ehci-platform[97399.108489] scsi host1: uas_eh_device_reset_handler success[97406.927546] sd 1:0:0:0: [sda] tag#7 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD [97406.927560] sd 1:0:0:0: [sda] tag#7 CDB: opcode=0x12 12 00 00 00 24 00[97431.568309] sd 1:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [97431.568323] sd 1:0:0:0: tag#0 CDB: opcode=0x0 00 00 00 00 00 00[97431.568353] scsi host1: uas_eh_device_reset_handler start[97431.583653] sd 1:0:0:0: [sda] tag#5 uas_zap_pending 0 uas-tag 6 inflight: CMD [97431.583665] sd 1:0:0:0: [sda] tag#5 CDB: opcode=0x2a 2a 00 03 f4 04 00 00 04 00 00[97431.583674] sd 1:0:0:0: [sda] tag#6 uas_zap_pending 0 uas-tag 7 inflight: CMD [97431.583680] sd 1:0:0:0: [sda] tag#6 CDB: opcode=0x28 28 00 03 c0 08 68 00 00 08 00[97431.708296] usb 5-1: reset high-speed USB device number 2 using ehci-platform[97431.865490] scsi host1: uas_eh_device_reset_handler success______@orangepipc2:~$

I have the same problem with a multi bay enclosure with JMS567 and Intel Atom running Ubuntu 16.04 with any kind of kernels. It is not a problem with armbian or power, the UAS just have several problems with some chipsets

Inviato dal mio SM-G955F utilizzando Tapatalk

January 15, 2018

Hi all

I would like to start this topic to discuss on the best approach for having some degree of data integrity using ARM SBC (aarch64 SoC in primis)

My goal is to set a big archive, I have in program to build 5x8TB HD, scheme TBD

The goal is to have at least one hard drive failure tolerance, it is acceptable that some data is lost during rebuild, since the main goal of the archive is to store picture and video, so it is tolerable that few pictures or video get corrupted, but the rebuild shall not stop in this case

The write performances are not so important, but read performances shall sustain some video streaming, roughly at least 25 Mbytes/s

My enclosure leverage on JMicron JMB394 which has RAID hardware support (apparently it is a real HW RAID, not a fake SW RAID such Intel iw) up to RAID5

Nevertheless, I have verified that unfortunately, it does not produce any metadata that mdadm can understand, so in case the enclosure fails, I don't know how recover the array, if I cannot get another identical enclosure

So I am investigating the possibility of a software RAID.

I have read about the URE statistic during RAID5 rebuild for large single disk storages, it is still not clear to me if in this case, such URE during RAID5 (and also RAID6) rebuild, the array rebuild will just stop or if it gets rebuilt but with the corresponding files corrupted (first questions)

So, I was more focusing on RAID6 but also investigating ZFS RAID-Z and BTRFS

@tkaiser I have read your post about ZFS, if I understand correctly you reach 4-5Mbyte per seconds in write, while more that 200Mbyte/s in read, on a x64 system, is that correct?

Do you have some figures about MDADM RAID5 or RAID6 and perhaps BRFS that it should work more reliable in kernel > 4.12.x since the problem in RAID5/6 have been fixed (at least the most critical one)?

Let's put some idea on the table, I think it would be valuable for most of us!

Bye

Advanced users - Development · December 14, 2017

Hi @zador.blood.stained

There is something strange with one of the overlay, the red led.

The overlay is:

Quote

/dts-v1/;
/plugin/;

/ {
   compatible = "allwinner,sun50i-h5";

   fragment@0 {
       target-path = "/leds";

       __overlay__ {

           status {
               linux,default-trigger = "mmc0";
           };
       };
   };
};

According to the ftdoverlay output (including all the overlay I use) the parameter seems to be inserted:

Quote

   leds {
       compatible = "gpio-leds";

       pwr {
           label = "orangepi:green:pwr";
           gpios = <0x34 0x0 0xa 0x0>;
           default-state = "on";
       };

       status {
           linux,default-trigger = "mmc0";
           label = "orangepi:red:status";
           gpios = <0x15 0x0 0x14 0x0>;
       };
   };

parameter added, and nothing is changed compared to the original

But then if I go in /proc/device-tree/leds/status/ I see the attribute:

Quote

menion@orangepipc2:/proc/device-tree/leds/status$ ls
gpios label linux,default-trigger name
menion@orangepipc2:/proc/device-tree/leds/status$

correct value also:

Quote

menion@orangepipc2:/proc/device-tree/leds/status$ cat linux,default-trigger
mmc0menion@orangepipc2:/proc/device-tree/leds/status$

But the result now is that the green led is blinking!

When I added manually the parameter in the dts it worked. The only thing is that the parameter was added as last in sub-node status

Maybe you have some idea here

Bye

Advanced users - Development · December 12, 2017

I see also that in the rootfs there is an utility named "armbian-add-overlay" that takes as parameter an overlay dts

Is something that automagically compile, put the dtbo in /boot/overlay-user and add the entry in armbianEnv.txt?

Advanced users - Development · December 12, 2017

You are right!

The soc node is very long!

Thanks!!!!

Anyhow, if it may be of any little interest, two overlay I think are usefull for orangepipc2: one set the red led to mmc activity, the other one set the power switch to issue an acpi shutdown event, so you can gracefully shutdown the board without having to log in the console

Bye

Advanced users - Development · December 12, 2017

I have also tried to remove the "/delete-property/ dr_mode", same problem

It can be a problem with fdtoverlay, but what happens to the boot process if I put a failing overlay?

Advanced users - Development · December 12, 2017

So, I need to list somewhere which overlay uboot shall pick up in overlay-user or all of them are loaded?

Also, sorry, but I need another quick help.

I want to set musb to host mode only, so I did this:

Quote

/dts-v1/;
/plugin/;

/ {
compatible = "allwinner,sun50i-h5";
fragment@0 {

target-path = "/usb@01c19000";
__overlay__ {
/delete-property/ dr_mode;
dr_mode = "host";
};
};
};

In the original dtb, the node is:

Quote

usb@01c19000 {
compatible = "allwinner,sun8i-h3-musb";
reg = <0x1c19000 0x400>;
clocks = <0x6 0x20>;
resets = <0x6 0x11>;
interrupts = <0x0 0x47 0x4>;
interrupt-names = "mc";
phys = <0x16 0x0>;
phy-names = "usb";
extcon = <0x16 0x0>;
status = "okay";
dr_mode = "otg";
linux,phandle = <0x44>;
phandle = <0x44>;
};

The dts compile fine, but ftdoverlay return error -1 applying the fragment.... Do you know why?

Thanks!

Advanced users - Development · December 12, 2017

Thanks @zador.blood.stained

Apparently the dtbo I have made works, I have tested them merging everything with fdtoverlay tool

One question: the overlay under /boot/overlay-user are loaded matching the name with overlay_prefix variable in /boot/armbianEnv.txt, or they are just all loaded?

Advanced users - Development · December 12, 2017

Hi all

Maybe someone can help

I want to change node: r-gpio-keys

but the syntax:

fragment@0 {
target = <&r-gpio-keys>;

prompt a syntax error. The problem are the "-" in the node name. Something like target = <&leds> is accepted.

So how can select such node?

Advanced users - Development · December 11, 2017

Thanks. Do you know if it is possible to perform a sort of "dry run" of the dtb+overlay combination in order to check the final results without having to load it on the real target?

Advanced users - Development · December 9, 2017

Yes, but the armbia-release under /etc is delivered with linux-xenial-root-next- that must follow the image userland arch. So if this is armhf and you install it on a aarch64 kernel, the uintrd image will be generated as armhf and the system will fail to boot. So, in very general case, the UINTRD variable in armbia-release shall be set according to kernel and/or uboot arch

Advanced users - Development · December 7, 2017

@zador.blood.stained It has been a while that I am running my "hybrid" image, the results are very very positive from both performances and most important memory footprint.

Also, adding the arm64 architecture and replacing the kernel dtb and uboot images, permits to ugprade everything directly by apt-get. But there is one little problem here: the package linux-xenial-root-next- must follow the userland version, so to say. In my case it is orangepi. But in this package there is also a new armbian-release file, that is set to generate initramfs for armhf instead of aarch64.

So, I don't know what are the plans for the 32 bit userland on 64 bit kernel official Armbian release, but maybe in the meawhile you may think to add a postinstall script that adapt the initrd architecture based on the kernel type?

Bye

Advanced users - Development · December 7, 2017

Hi all

Can you suggest some online resource for learning the dts overlay syntax?

I am ok with adding things, I have found something about deleting things, but what if I want to change something? Is it delete and add in the same fragment? One fragment to delete and the next one to add?

Thanks!

November 9, 2017

http://linux-sunxi.org/Linux_mainlining_effort got updated. There is a link to a lima kernel driver plus MESA OpenGL Lima for Mali400

So apparently the things are moving underground

November 3, 2017

Ahhhhh ok Next time I will recompile the kernel I will enable one then

November 3, 2017

But the usb gadgets, aren't ment to be used for having the SBC acting like a serial, mass storage, etc...?

My goal is just to use the OTG port in host mode

November 3, 2017

Mmmm I am afraid I don't know what this gadget module are. But I did nothing, so I guess no

November 3, 2017

With original dtb, dr_mode='otg' I plugged an USB key but it doesn't get recognized. I changed the dr_mode='host', rebooted with the new dtb and then it worked fine. USB key is connected with a micro USB to USB A female cable, also named OTG cable, can this be the problem?

November 3, 2017

Is it possible to change on the fly the MUSB from OTG<->HOST without having to do so in the dts?

Advanced users - Development · November 2, 2017

Ok, I have reinstalled all the services I had and make a mem usage check:

64bit userland

menion@orangepipc2:~$ egrep --color 'Mem|Cache|Swap' /proc/meminfo
MemTotal:        1018536 kB
MemFree:           33660 kB
MemAvailable:     235864 kB
Cached:           249024 kB
SwapCached:         9252 kB
SwapTotal:       2111484 kB
SwapFree:        1969148 kB

32 bit userland

menion@orangepipc2:~$  egrep --color 'Mem|Cache|Swap' /proc/meminfo
MemTotal:        1018572 kB
MemFree:          157292 kB
MemAvailable:     465496 kB
Cached:           346984 kB
SwapCached:            0 kB
SwapTotal:       2111484 kB
SwapFree:        2111484 kB

relevant services active,: apache2, amule, deluge, freeradius, php-fpm, mysql, 2xopenvpn server, shellinabox, nfs sharing, samba, tvheadend (64bit)

I think the difference is important, and most important physical swap never run

Advanced users - Development · November 2, 2017

They should have implemented the structure this way (even if it is a little bit more memory hungry, but normally this is a temporary stack memory usage):

struct dtv_properties {
__u32 num;
struct dtv_property props[DTV_IOCTL_MAX_MSGS];
};

but there are two problem, the first one is that the structure is copied from user two time, the latter with the former pointer and it would not work with the array. The modifications are simple, but it would break the ioctl compatibility, it would require a new DVB API major.

I have written an email to the linux-tv mailing list, I think this is something definitely needed to be fixed.

Of course it is still possible tu run an arm64 bit version of the DVB app, which is what I am doing using a precompiled ppa (since otherwise I should cross-compile) and fixing some stupid dependencies problem in multi-arch (with package dtv-scan-tables)

Sign In

Forums

Store

Crowdfunding

Applications

Events

Raffles

Community Map

Posts posted by Menion

Important Information