Receiving spinlocks KP randomly

Just a few minutes ago I saw this from my byobu remote session:
e>/-1, .owner_cpu: 152518656                                               [0/0]
Message from syslogd@nas at Nov  4 16:25:26 ...
 kernel:[66559.853169] BUG: spinlock lockup suspected on CPU#3, swapper/3/0

Message from syslogd@nas at Nov  4 16:25:26 ...
 kernel:[66559.857273]  lock: 0xffffffc0f5e27e10, .magic: 00000040, .owner: <non
e>/-1, .owner_cpu: 152518656
Message from syslogd@nas at Nov  4 16:25:26 ...
 kernel:[66552.808519] BUG: spinlock bad magic on CPU#3, swapper/3/0

Message from syslogd@nas at Nov  4 16:25:26 ...
 kernel:[66552.809119]  lock: 0xffffffc0f5e27e10, .magic: 00000040, .owner: <non
e>/-1, .owner_cpu: 152518656

Message from syslogd@nas at Nov  4 16:25:26 ...
 kernel:[66559.853169] BUG: spinlock lockup suspected on CPU#3, swapper/3/0

Message from syslogd@nas at Nov  4 16:25:26 ...
 kernel:[66559.857273]  lock: 0xffffffc0f5e27e10, .magic: 00000040, .owner: <non
e>/-1, .owner_cpu: 152518656

And then my R64 just reached a complete lockdown. Have no idea what happened, what caused this.

I've been hitting similar on a RockPro64 running Open Media Vault 0.8.3-1141. Every time I try to initialize a raid1 volume I hit this after just a couple minutes.
`                _                     __   _  _
_ __ ___   | | ___ __  _ __ ___  / / | || |
| '/ _ \ / | |/ / ' | '/ _ | '_ | || |_
| | | (_) | (|   <| |) | | | () | (_) |_   |
||  _/ _||_\ .__/||  _/ _/   ||
||
Linux rockpro64 4.4.167-1213-rockchip-ayufan-g34ae07687fce #1 SMP Tue Jun 18 20:44:49 UTC 2019 aarch64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@rockpro64:~# mdadm --readwrite /dev/md0
root@rockpro64:~# tail -f /var/log/kern.log
Jul  6 23:17:08 rockpro64 kernel: [   18.870817] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
Jul  6 23:17:14 rockpro64 kernel: [   25.226971] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Jul  6 23:17:18 rockpro64 kernel: [   29.324141] NFSD: starting 90-second grace period (net ffffff80093a2f40)
Jul  6 23:17:24 rockpro64 kernel: [   34.886722] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
Jul  7 00:24:13 rockpro64 kernel: [   62.621049] md: md0 switched to read-write mode.
Jul  7 00:24:13 rockpro64 kernel: [   62.639974] md: resync of RAID array md0
Jul  7 00:24:13 rockpro64 kernel: [   62.640460] md: minimum guaranteed  speed: 1000 KB/sec/disk.
Jul  7 00:24:13 rockpro64 kernel: [   62.641129] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync.
Jul  7 00:24:13 rockpro64 kernel: [   62.642201] md: using 128k window, over a total of<PHONE_NUMBER>k.
Jul  7 00:24:17 rockpro64 kernel: [   66.891480] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
Jul  7 00:25:21 rockpro64 kernel: [  130.896639] cdn-dp fec00000.dp: [drm:cdn_dp_request_firmware] ERROR Timed out trying to load firmware
Message from syslogd@rockpro64 at Jul  7 00:27:08 ...
kernel:[  233.001921] Internal error: : 96000210 [#1] SMP
Jul  7 00:27:08 rockpro64 kernel: [  233.001042] Unhandled fault: synchronous external abort (0x96000210) at 0xffffff80096c61b0
Jul  7 00:27:08 rockpro64 kernel: [  233.001921] Internal error: : 96000210 [#1] SMP
Jul  7 00:27:08 rockpro64 kernel: [  233.002397] Modules linked in: midgard_kbase dw_hdmi_i2s_audio rockchip_saradc ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid0 multipath linear raid1 md_mod
Jul  7 00:27:08 rockpro64 kernel: [  233.004571] CPU: 0 PID: 143 Comm: scsi_eh_1 Not tainted 4.4.167-1213-rockchip-ayufan-g34ae07687fce #1
Jul  7 00:27:08 rockpro64 kernel: [  233.005524] Hardware name: Pine64 RockPro64 (DT)
Jul  7 00:27:08 rockpro64 kernel: [  233.006007] task: ffffffc0efcb8000 task.stack: ffffffc0efcb4000
Jul  7 00:27:08 rockpro64 kernel: [  233.006631] PC is at ahci_scr_read+0x70/0x98
Jul  7 00:27:08 rockpro64 kernel: [  233.007081] LR is at sata_scr_read+0x88/0x94
Jul  7 00:27:08 rockpro64 kernel: [  233.007528] pc : [] lr : [] pstate: 80000145
Jul  7 00:27:08 rockpro64 kernel: [  233.008292] sp : ffffffc0efcb7a50
Jul  7 00:27:08 rockpro64 kernel: [  233.008640] x29: ffffffc0efcb7a50 x28:<PHONE_NUMBER>000000
Jul  7 00:27:08 rockpro64 kernel: [  233.009211] x27: ffffffc0efc49e80 x26:<PHONE_NUMBER>000001
Jul  7 00:27:08 rockpro64 kernel: [  233.009781] x25: ffffffc0efc4a258 x24: ffffffc0efc48000
Jul  7 00:27:08 rockpro64 kernel: [  233.010352] x23:<PHONE_NUMBER>000000 x22: ffffffc0efcb7b28
Jul  7 00:27:08 rockpro64 kernel: [  233.010923] x21: ffffffc0efc49e80 x20: ffffffc0efcb7b28
Jul  7 00:27:08 rockpro64 kernel: [  233.011493] x19:<PHONE_NUMBER>000001 x18:<PHONE_NUMBER>d00800
Jul  7 00:27:08 rockpro64 kernel: [  233.012063] x17:<PHONE_NUMBER>000000 x16:<PHONE_NUMBER>000000
Jul  7 00:27:08 rockpro64 kernel: [  233.012633] x15:<PHONE_NUMBER>000000 x14:<PHONE_NUMBER>000000
Jul  7 00:27:08 rockpro64 kernel: [  233.013203] x13:<PHONE_NUMBER>000000 x12:<PHONE_NUMBER>000000
Jul  7 00:27:08 rockpro64 kernel: [  233.013772] x11:<PHONE_NUMBER>000000 x10:<PHONE_NUMBER>000000
Jul  7 00:27:08 rockpro64 kernel: [  233.014343] x9 :<PHONE_NUMBER>000000 x8 : ffffffc0efc4a258
Jul  7 00:27:08 rockpro64 kernel: [  233.014914] x7 :<PHONE_NUMBER>000000 x6 : ffffffc0efc4a2d0
Jul  7 00:27:08 rockpro64 kernel: [  233.018973] x5 :<PHONE_NUMBER>000000 x4 : ffffff8008d9af94
Jul  7 00:27:08 rockpro64 kernel: [  233.022971] x3 :<PHONE_NUMBER>0001b0 x2 : ffffffc0efcb7b28
Jul  7 00:27:08 rockpro64 kernel: [  233.026914] x1 :<PHONE_NUMBER>000030 x0 : ffffff80096c61b0
Jul  7 00:27:08 rockpro64 kernel: [  233.030806]
Jul  7 00:27:08 rockpro64 kernel: [  233.030806] PC: 0xffffff800877cb0c:
Jul  7 00:27:08 rockpro64 kernel: [  233.037877] cb0c  52800013 912c1821 97fe23cd 17ffffe2 a9bd7bfd 910003fd a90153f3 f90013f5
Jul  7 00:27:08 rockpro64 kernel: [  233.042148] cb2c  aa0003f5 2a0103f3 aa1e03e0 aa0203f4 d503201f f94002a3 7100127f f959dc60
Jul  7 00:27:08 rockpro64 kernel: [  233.046485] cb4c  b9402c63 f9401801 53196063 91040063 f9400820 54000268 54000061 b9401821
Jul  7 00:27:08 rockpro64 kernel: [  233.050838] cb6c  36e80201 d00030e4 913de084 91007084 b8735881 34000161 8b21c063 8b030000
Jul  7 00:27:08 rockpro64 kernel: [  233.055199] cb8c  b9400000 d5033d9f b9000280 52800000 a94153f3 f94013f5 a8c37bfd d65f03c0
Jul  7 00:27:08 rockpro64 kernel: [  233.059567] cbac  128002a0 17fffffb a9be7bfd 910003fd f9000bf3 aa0003f3 aa1e03e0 d503201f
Jul  7 00:27:08 rockpro64 kernel: [  233.063939] cbcc  f9400260 f9400000 f959dc00 f9401800 b9400000 36400120 52801fe0 b9038660
Jul  7 00:27:08 rockpro64 kernel: [  233.068322] cbec  f0004482 90004061 912c8842 911dbc21 aa1303e0 97ff9d72 f9400bf3 a8c27bfd
Jul  7 00:27:08 rockpro64 kernel: [  233.072786]
Jul  7 00:27:08 rockpro64 kernel: [  233.072786] LR: 0xffffff8008763424:
Jul  7 00:27:08 rockpro64 kernel: [  233.080343] 3424  a90153f3 a9025bf5 aa0003f3 2a0103f5 aa1e03e0 aa0203f6 d503201f f9400274
Jul  7 00:27:08 rockpro64 kernel: [  233.084836] 3444  d283d000 8b000280 eb00027f 54000180 f959c280 eb00027f 54000120 aa1603e2
Jul  7 00:27:08 rockpro64 kernel: [  233.089268] 3464  2a1503e1 aa1303e0 9400572a a94153f3 a9425bf5 a8c37bfd d65f03c0 aa1303e0
Jul  7 00:27:08 rockpro64 kernel: [  233.093647] 3484  97fffb19 34000100 f9400680 aa1603e2 2a1503e1 f9406c03 aa1303e0 d63f0060
Jul  7 00:27:08 rockpro64 kernel: [  233.098065] 34a4  17fffff3 12800bc0 17fffff1 a9ba7bfd 910003fd a90153f3 a9025bf5 a90363f7
Jul  7 00:27:08 rockpro64 kernel: [  233.102501] 34c4  a9046bf9 aa0103f5 aa0203f6 aa0003f7 aa1e03e0 d503201f d0005813 b94012a0
Jul  7 00:27:08 rockpro64 kernel: [  233.106912] 34e4  f940e274 a94066b8 97e6e656 8b000280 cb160001 910173a2 f100003f 52800001
Jul  7 00:27:08 rockpro64 kernel: [  233.111301] 3504  9a80a2d6 aa1703e0 97ffffc4 2a0003f5 350003c0 b9405fb4 f940e27a 12000e94
Jul  7 00:27:08 rockpro64 kernel: [  233.115658]
Jul  7 00:27:08 rockpro64 kernel: [  233.115658] SP: 0xffffffc0efcb79d0:
Jul  7 00:27:08 rockpro64 kernel: [  233.122908] 79d0  efcb7b28 ffffffc0 00000000 00000000 efc48000 ffffffc0 efc4a258 ffffffc0
Jul  7 00:27:08 rockpro64 kernel: [  233.127166] 79f0  00000001 00000000 efc49e80 ffffffc0 00000000 00000000 efcb7a50 ffffffc0
Jul  7 00:27:08 rockpro64 kernel: [  233.131340] 7a10  087634a4 ffffff80 efcb7a50 ffffffc0 0877cb8c ffffff80 80000145 00000000
Jul  7 00:27:08 rockpro64 kernel: [  233.135428] 7a30  08cbe644 ffffff80 f2bb60a0 ffffffc0 ffffffff ffffffff 00000000 00000000
Jul  7 00:27:08 rockpro64 kernel: [  233.139426] 7a50  efcb7a80 ffffffc0 087634a4 ffffff80 efc49e80 ffffffc0 efc48000 ffffffc0
Jul  7 00:27:08 rockpro64 kernel: [  233.143368] 7a70  00000001 00000000 00000000 00000000 efcb7ab0 ffffffc0 08770374 ffffff80
Jul  7 00:27:08 rockpro64 kernel: [  233.147307] 7a90  efc4a258 ffffffc0 efc49e80 ffffffc0 efc4b858 ffffffc0 00003008 00000000
Jul  7 00:27:08 rockpro64 kernel: [  233.151252] 7ab0  efcb7b60 ffffffc0 08770b34 ffffff80 efc48000 ffffffc0 efc49e80 ffffffc0
Jul  7 00:27:08 rockpro64 kernel: [  233.155230]
Jul  7 00:27:08 rockpro64 kernel: [  233.155230] X0: 0xffffff80096c6130:
Jul  7 00:27:08 rockpro64 kernel: [  233.161788] 6130
Jul  7 00:27:08 rockpro64 kernel: [  233.211980] Unhandled fault: synchronous external abort (0x96000210) at 0xffffff80096c6130
Jul  7 00:27:08 rockpro64 kernel: [  237.987191] rk3x-i2c ff3c0000.i2c: timeout, ipd: 0x10, state: 1
Message from syslogd@rockpro64 at Jul  7 00:27:47 ...
kernel:[  240.218948] BUG: spinlock lockup suspected on CPU#0, scsi_eh_1/143
Message from syslogd@rockpro64 at Jul  7 00:27:47 ...
kernel:[  240.222849]  lock: 0xffffff800926fdf0, .magic: dead4ead, .owner: scsi_eh_1/143, .owner_cpu: 0
Jul  7 00:27:47 rockpro64 kernel: [  240.218948] BUG: spinlock lockup suspected on CPU#0, scsi_eh_1/143
Jul  7 00:27:47 rockpro64 kernel: [  240.222849]  lock: 0xffffff800926fdf0, .magic: dead4ead, .owner: scsi_eh_1/143, .owner_cpu: 0
Jul  7 00:27:47 rockpro64 kernel: [  240.227026] CPU: 0 PID: 143 Comm: scsi_eh_1 Not tainted 4.4.167-1213-rockchip-ayufan-g34ae07687fce #1
Jul  7 00:27:47 rockpro64 kernel: [  240.231336] Hardware name: Pine64 RockPro64 (DT)
Jul  7 00:27:47 rockpro64 kernel: [  240.235282] Call trace:
Jul  7 00:27:47 rockpro64 kernel: [  240.239056] [] dump_backtrace+0x0/0x220
Jul  7 00:27:47 rockpro64 kernel: [  240.243183] [] show_stack+0x24/0x30
Jul  7 00:27:47 rockpro64 kernel: [  240.247311] [] dump_stack+0x98/0xc0
Jul  7 00:27:47 rockpro64 kernel: [  240.251429] [] spin_dump+0x84/0xa4
Jul  7 00:27:47 rockpro64 kernel: [  240.255566] [] do_raw_spin_lock+0xdc/0x164
Jul  7 00:27:47 rockpro64 kernel: [  240.259802] [] _raw_spin_lock_irq+0x24/0x30
Jul  7 00:27:47 rockpro64 kernel: [  240.264071] [] die+0x38/0x1ac
Jul  7 00:27:47 rockpro64 kernel: [  240.268241] [] arm64_notify_die+0x6c/0x70
Jul  7 00:27:47 rockpro64 kernel: [  240.272502] [] do_mem_abort+0x9c/0xac
Jul  7 00:27:47 rockpro64 kernel: [  240.276743] Exception stack(0xffffffc0efcb7560 to 0xffffffc0efcb7690)
Jul  7 00:27:47 rockpro64 kernel: [  240.281086] 7560: ffffffc0efcb8000<PHONE_NUMBER>000000 ffffffc0efcb7730 ffffff80085a0dc4
Jul  7 00:27:47 rockpro64 kernel: [  240.285566] 7580:<PHONE_NUMBER>000007<PHONE_NUMBER>000000 ffffff80096c6130<PHONE_NUMBER>000000
Jul  7 00:27:47 rockpro64 kernel: [  240.290013] 75a0: ffffff800941f2fc<PHONE_NUMBER>000000 ffffffc0efcb75d0 ffffff800810b7f8
Jul  7 00:27:47 rockpro64 kernel: [  240.294437] 75c0:<PHONE_NUMBER>000005<PHONE_NUMBER>000000 ffffffc0efcb7670 ffffff800810b958
Jul  7 00:27:47 rockpro64 kernel: [  240.298807] 75e0: ffffffc0efcb76f0 ffffff8008f8816c ffffff8008f8816c ffffff8008fed582
Jul  7 00:27:47 rockpro64 kernel: [  240.303163] 7600: ffffffc0efcb77bc ffffff80096c6130<PHONE_NUMBER>000004<PHONE_NUMBER>000010
Jul  7 00:27:47 rockpro64 kernel: [  240.307501] 7620:<PHONE_NUMBER>000000 ffffffc0efcb77c0 ffffffc0efcb77bc<PHONE_NUMBER>000000
Jul  7 00:27:47 rockpro64 kernel: [  240.311810] 7640:<PHONE_NUMBER>001000<PHONE_NUMBER>aaaaaa<PHONE_NUMBER>000008 00000000ffffffff
Jul  7 00:27:47 rockpro64 kernel: [  240.316081] 7660: ffffffc0f29dbf10 ffffff800ba002a0 ffffff800ba002a0<PHONE_NUMBER>000000
Jul  7 00:27:47 rockpro64 kernel: [  240.320398] 7680:<PHONE_NUMBER>000000<PHONE_NUMBER>000000
Jul  7 00:27:47 rockpro64 kernel: [  240.324397] [] el1_da+0x24/0x84
Jul  7 00:27:47 rockpro64 kernel: [  240.328343] [] show_data.constprop.3+0xa4/0xf8
Jul  7 00:27:47 rockpro64 kernel: [  240.332391] [] __show_regs+0x154/0x1a8
Jul  7 00:27:47 rockpro64 kernel: [  240.336332] [] die+0xb4/0x1ac
Jul  7 00:27:47 rockpro64 kernel: [  240.340152] [] arm64_notify_die+0x6c/0x70
Jul  7 00:27:47 rockpro64 kernel: [  240.344030] [] do_mem_abort+0x9c/0xac
Jul  7 00:27:47 rockpro64 kernel: [  240.347831] Exception stack(0xffffffc0efcb7880 to 0xffffffc0efcb79b0)
Jul  7 00:27:47 rockpro64 kernel: [  240.351752] 7880:<PHONE_NUMBER>000001<PHONE_NUMBER>000000 ffffffc0efcb7a50 ffffff800877cb8c
Jul  7 00:27:47 rockpro64 kernel: [  240.355798] 78a0:<PHONE_NUMBER>000007<PHONE_NUMBER>000000 ffffff80096c61b0 ffffffc0efc4a258
Jul  7 00:27:47 rockpro64 kernel: [  240.359850] 78c0:<PHONE_NUMBER>000001 ffffffc0efc49e80 ffffffc0efcb8000 ffffffc0efcb7a50
Jul  7 00:27:47 rockpro64 kernel: [  240.363846] 78e0: ffffff80087634a4 ffffffc0efcb7920 ffffff80080825b8<PHONE_NUMBER>000145
Jul  7 00:27:47 rockpro64 kernel: [  240.367838] 7900:<PHONE_NUMBER>000000 ffffffc0f298eb80<PHONE_NUMBER>000000 ffffff80080e92b8
Jul  7 00:27:47 rockpro64 kernel: [  240.371828] 7920: ffffff80096c61b0<PHONE_NUMBER>000030 ffffffc0efcb7b28<PHONE_NUMBER>0001b0
Jul  7 00:27:47 rockpro64 kernel: [  240.375860] 7940: ffffff8008d9af94<PHONE_NUMBER>000000 ffffffc0efc4a2d0<PHONE_NUMBER>000000
Jul  7 00:27:47 rockpro64 kernel: [  240.379858] 7960: ffffffc0efc4a258<PHONE_NUMBER>000000<PHONE_NUMBER>000000<PHONE_NUMBER>000000
Jul  7 00:27:47 rockpro64 kernel: [  240.383830] 7980:<PHONE_NUMBER>000000<PHONE_NUMBER>000000<PHONE_NUMBER>000000<PHONE_NUMBER>000000
Jul  7 00:27:47 rockpro64 kernel: [  240.387754] 79a0:<PHONE_NUMBER>000000<PHONE_NUMBER>000000
Jul  7 00:27:47 rockpro64 kernel: [  240.391371] [] el1_da+0x24/0x84
Jul  7 00:27:47 rockpro64 kernel: [  240.394929] [] sata_scr_read+0x88/0x94
Jul  7 00:27:47 rockpro64 kernel: [  240.398563] [] ata_eh_link_autopsy+0x4c/0x740
Jul  7 00:27:47 rockpro64 kernel: [  240.402271] [] ata_eh_autopsy+0xcc/0xdc
Jul  7 00:27:47 rockpro64 kernel: [  240.405862] [] sata_pmp_error_handler+0x34/0x7b8
Jul  7 00:27:47 rockpro64 kernel: [  240.409476] [] ahci_error_handler+0x44/0x70
Jul  7 00:27:47 rockpro64 kernel: [  240.413018] [] ata_scsi_port_error_handler+0xe0/0x550
Jul  7 00:27:47 rockpro64 kernel: [  240.416597] [] ata_scsi_error+0x84/0xa4
Jul  7 00:27:47 rockpro64 kernel: [  240.419986] [] scsi_error_handler+0x130/0x6d4
Jul  7 00:27:47 rockpro64 kernel: [  240.423359] [] kthread+0xe0/0xf0
Jul  7 00:27:47 rockpro64 kernel: [  240.426620] [] ret_from_fork+0x10/0x20
Jul  7 00:27:47 rockpro64 kernel: [  276.141323] Watchdog detected hard LOCKUP on cpu 0
Jul  7 00:27:47 rockpro64 kernel: [  276.141898] ------------[ cut here ]------------
Jul  7 00:27:47 rockpro64 kernel: [  276.151042] WARNING: at kernel/watchdog.c:352
Jul  7 00:27:47 rockpro64 kernel: [  276.155862] Modules linked in: midgard_kbase dw_hdmi_i2s_audio rockchip_saradc ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid0 multipath linear raid1 md_mod
Jul  7 00:27:47 rockpro64 kernel: [  276.167535]
Jul  7 00:27:47 rockpro64 kernel: [  276.172480] CPU: 5 PID: 0 Comm: swapper/5 Not tainted 4.4.167-1213-rockchip-ayufan-g34ae07687fce #1
Jul  7 00:27:47 rockpro64 kernel: [  276.178353] Hardware name: Pine64 RockPro64 (DT)
Jul  7 00:27:47 rockpro64 kernel: [  276.183844] task: ffffffc0f2af4600 task.stack: ffffffc0f2b0c000
Jul  7 00:27:47 rockpro64 kernel: [  276.189486] PC is at watchdog_timer_fn+0x190/0x2e8
Jul  7 00:27:47 rockpro64 kernel: [  276.194978] LR is at watchdog_timer_fn+0x190/0x2e8
Jul  7 00:27:47 rockpro64 kernel: [  276.200389] pc : [] lr : [] pstate: 600001c5
Jul  7 00:27:47 rockpro64 kernel: [  276.206136] sp : ffffffc0f7f43d00
Jul  7 00:27:47 rockpro64 kernel: [  276.211514] x29: ffffffc0f7f43d00 x28:<PHONE_NUMBER>000000
Jul  7 00:27:47 rockpro64 kernel: [  276.217097] x27: ffffff80092678a0 x26: ffffff800922b238
Jul  7 00:27:47 rockpro64 kernel: [  276.222643] x25: ffffffc0f7f46250 x24: ffffffc0f2b0fda0
Jul  7 00:27:47 rockpro64 kernel: [  276.228150] x23:<PHONE_NUMBER>000000 x22:<PHONE_NUMBER>0000fd
Jul  7 00:27:47 rockpro64 kernel: [  276.233638] x21: ffffff8009266000 x20: ffffff800922b2b0
Jul  7 00:27:47 rockpro64 kernel: [  276.239072] x19: ffffff800922b000 x18:<PHONE_NUMBER>000005
Jul  7 00:27:47 rockpro64 kernel: [  276.244427] x17:<PHONE_NUMBER>000000 x16:<PHONE_NUMBER>000000
Jul  7 00:27:47 rockpro64 kernel: [  276.249745] x15:<PHONE_NUMBER>000000 x14: ffffff800ba006c0
Jul  7 00:27:47 rockpro64 kernel: [  276.255025] x13: ffffff800ba006c0 x12: ffffffc0f29dac20
Jul  7 00:27:47 rockpro64 kernel: [  276.260287] x11: 00000000ffffffff x10:<PHONE_NUMBER>000008
Jul  7 00:27:47 rockpro64 kernel: [  276.265567] x9 :<PHONE_NUMBER>aaaaaa x8 :<PHONE_NUMBER>001000
Jul  7 00:27:47 rockpro64 kernel: [  276.270820] x7 :<PHONE_NUMBER>000000 x6 :<PHONE_NUMBER>000001
Jul  7 00:27:47 rockpro64 kernel: [  276.276040] x5 :<PHONE_NUMBER>000000 x4 :<PHONE_NUMBER>000000
Jul  7 00:27:47 rockpro64 kernel: [  276.281157] x3 : 00000040eed1b000 x2 : 00000040eed1b000
Jul  7 00:27:47 rockpro64 kernel: [  276.286200] x1 :<PHONE_NUMBER>000005 x0 :<PHONE_NUMBER>000026
Jul  7 00:27:47 rockpro64 kernel: [  276.291240]
Jul  7 00:27:47 rockpro64 kernel: [  276.291240] PC: 0xffffff800815629c:
Jul  7 00:27:47 rockpro64 kernel: [  276.300567] 629c  91022694 d538d080 38746801 34000041 3834681f 97ffff7a a94153f3 52800020
Jul  7 00:27:47 rockpro64 kernel: [  276.306060] 62bc  a9425bf5 a94363f7 a9446bf9 a94573fb a8c77bfd d65f03c0 91020282 f87a6860
Jul  7 00:27:47 rockpro64 kernel: [  276.311564] 62dc  f8626865 91022294 eb05001f 54000101 38746860 35fffb80 b9403082 90007200
Jul  7 00:27:47 rockpro64 kernel: [  276.317155] 62fc  910de000 340000c2 9400dfb4 f8226860 f87c7b60 3834681f 17ffffd3 9400e03e
Jul  7 00:27:47 rockpro64 kernel: [  276.322821] 631c  d4210000 f87c7b60 52800021 38346801 17ffffcd 97fe4698 f9444ea1 36080941
Jul  7 00:27:47 rockpro64 kernel: [  276.328584] 633c  b9401341 910003e2 340008e1 531f7821 d35efc00 8b21c2c1 cb000021 b6f80841
Jul  7 00:27:47 rockpro64 kernel: [  276.334401] 635c  6b160016 54000800 91022a99 d538d080 38606b21 34000101 91024294 f8746802
Jul  7 00:27:47 rockpro64 kernel: [  276.340277] 637c  d5384101 eb01005f 54fff980 3839681f 17ffffc9 34000157 90009981 52800000
Jul  7 00:27:47 rockpro64 kernel: [  276.346226]
Jul  7 00:27:47 rockpro64 kernel: [  276.346226] LR: 0xffffff800815629c:
Jul  7 00:27:47 rockpro64 kernel: [  276.356609] 629c  91022694 d538d080 38746801 34000041 3834681f 97ffff7a a94153f3 52800020
Jul  7 00:27:47 rockpro64 kernel: [  276.362696] 62bc  a9425bf5 a94363f7 a9446bf9 a94573fb a8c77bfd d65f03c0 91020282 f87a6860
Jul  7 00:27:47 rockpro64 kernel: [  276.368843] 62dc  f8626865 91022294 eb05001f 54000101 38746860 35fffb80 b9403082 90007200
Jul  7 00:27:47 rockpro64 kernel: [  276.375029] 62fc  910de000 340000c2 9400dfb4 f8226860 f87c7b60 3834681f 17ffffd3 9400e03e
Jul  7 00:27:47 rockpro64 kernel: [  276.381277] 631c  d4210000 f87c7b60 52800021 38346801 17ffffcd 97fe4698 f9444ea1 36080941
Jul  7 00:27:47 rockpro64 kernel: [  276.387587] 633c  b9401341 910003e2 340008e1 531f7821 d35efc00 8b21c2c1 cb000021 b6f80841
Jul  7 00:27:47 rockpro64 kernel: [  276.393943] 635c  6b160016 54000800 91022a99 d538d080 38606b21 34000101 91024294 f8746802
Jul  7 00:27:47 rockpro64 kernel: [  276.400375] 637c  d5384101 eb01005f 54fff980 3839681f 17ffffc9 34000157 90009981 52800000
Jul  7 00:27:47 rockpro64 kernel: [  276.406846]
Jul  7 00:27:47 rockpro64 kernel: [  276.406846] SP: 0xffffffc0f7f43c80:
Jul  7 00:27:47 rockpro64 kernel: [  276.418255] 3c80  000000fd 00000000 00000000 00000000 f2b0fda0 ffffffc0 f7f46250 ffffffc0
Jul  7 00:27:47 rockpro64 kernel: [  276.424700] 3ca0  0922b238 ffffff80 092678a0 ffffff80 00000000 00000000 f7f43d00 ffffffc0
Jul  7 00:27:47 rockpro64 kernel: [  276.430999] 3cc0  0815631c ffffff80 f7f43d00 ffffffc0 0815631c ffffff80 600001c5 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.437238] 3ce0  09266898 ffffff80 0000003a 00000000 00000000 00000080 f2400028 ffffffc0
Jul  7 00:27:47 rockpro64 kernel: [  276.443416] 3d00  f7f43d70 ffffffc0 08120dbc ffffff80 f7f46250 ffffffc0 f7f45c00 ffffffc0
Jul  7 00:27:47 rockpro64 kernel: [  276.449523] 3d20  4639b2b9 00000040 f7f45c80 ffffffc0 09225000 ffffff80 00000003 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.455638] 3d40  093d9290 ffffff80 4639b2b9 00000040 0815618c ffffff80 4639a1a2 00000040
Jul  7 00:27:47 rockpro64 kernel: [  276.461755] 3d60  f7f46250 ffffffc0 09266898 ffffff80 f7f43de0 ffffffc0 081213a0 ffffff80
Jul  7 00:27:47 rockpro64 kernel: [  276.467984]
Jul  7 00:27:47 rockpro64 kernel: [  276.467984] X12: 0xffffffc0f29daba0:
Jul  7 00:27:47 rockpro64 kernel: [  276.478731] aba0  30303030 3030c630 30303030 787878c6 7c787878 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.484976] abc0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.491248] abe0  06600606 06c00606 c6c6c60c 7cfe7c78 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.497530] ac00  c6060006 c606c606 c6067c06 c606c606 7c0cc60c 7c0c7c0c c618c018 c618c618
Jul  7 00:27:47 rockpro64 kernel: [  276.503868] ac20  00000000 00000000 00000000 00000000 00000000 00000000 00000000 38380000
Jul  7 00:27:47 rockpro64 kernel: [  276.510270] ac40  d6d6d6d6 d6d6d6d6 d6d6d6d6 d6d6d6d6 c6c6c6c6 c6c6c6c6 c6c6c6c6 c6c6c6c6
Jul  7 00:27:47 rockpro64 kernel: [  276.516765] ac60  d6d6d6cc c6ccc6cc cc00c0c0 ccc6ccc6 00c6c6c6 7c767c76 7c7c7c76 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.523335] ac80  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.529992]
Jul  7 00:27:47 rockpro64 kernel: [  276.529992] X13: 0xffffff800ba00640:
Jul  7 00:27:47 rockpro64 kernel: [  276.541821] 0640  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.548650] 0660  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.555451] 0680  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.562248] 06a0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.569016] 06c0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.575741] 06e0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.582395] 0700  00000000 00000000 00000000 00000000 00aaaaaa 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.589027] 0720  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.595526]
Jul  7 00:27:47 rockpro64 kernel: [  276.595526] X14: 0xffffff800ba00640:
Jul  7 00:27:47 rockpro64 kernel: [  276.606832] 0640  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.613276] 0660  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.619592] 0680  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.625788] 06a0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.631856] 06c0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.637803] 06e0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.643607] 0700  00000000 00000000 00000000 00000000 00aaaaaa 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.649395] 0720  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.655058]
Jul  7 00:27:47 rockpro64 kernel: [  276.655058] X19: 0xffffff800922af80:
Jul  7 00:27:47 rockpro64 kernel: [  276.664674] af80  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.670280] afa0  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.675762] afc0  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.681108] afe0  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.686326] b000  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.691420] b020  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.696375] b040  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.701298] b060  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.706079]
Jul  7 00:27:47 rockpro64 kernel: [  276.706079] X20: 0xffffff800922b230:
Jul  7 00:27:47 rockpro64 kernel: [  276.714064] b230  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.718868] b250  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.723572] b270  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.728173] b290  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.732673] b2b0  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.737087] b2d0  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.741361] b2f0  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.745578] b310  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.749673]
Jul  7 00:27:47 rockpro64 kernel: [  276.749673] X21: 0xffffff8009265f80:
Jul  7 00:27:47 rockpro64 kernel: [  276.756322] 5f80  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.760484] 5fa0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.764520] 5fc0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.768417] 5fe0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.772209] 6000  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.775895] 6020  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.779436] 6040  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.782944] 6060  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.786312]
Jul  7 00:27:47 rockpro64 kernel: [  276.786312] X24: 0xffffffc0f2b0fd20:
Jul  7 00:27:47 rockpro64 kernel: [  276.791734] fd20  00000000 00000000 f2af4600 ffffffc0 000001c0 00000000 089708c0 ffffff80
Jul  7 00:27:47 rockpro64 kernel: [  276.795422] fd40  00000002 00000000 08092188 ffffff80 f2b0fd60 ffffffc0 0809227c ffffff80
Jul  7 00:27:47 rockpro64 kernel: [  276.799179] fd60  f2b0fda0 ffffffc0 089efbbc ffffff80 f1d32210 ffffffc0 f1d31e10 ffffffc0
Jul  7 00:27:47 rockpro64 kernel: [  276.803012] fd80  f2b0fda0 ffffffc0 089efc0c ffffff80 f1d32000 ffffffc0 085d0a14 ffffff80
Jul  7 00:27:47 rockpro64 kernel: [  276.806863] fda0  00000000 00000000 00000005 00000000 eed1b000 00000040 00000020 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.810814] fdc0  ffffffff 00ffffff 5d6e6ac3 00000001 00013240 00000000 00000005 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.814696] fde0  b5593519 00000034 08081800 ffffff80 00001000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.818622] fe00  34d5d91d 00000000 eed1b000 00000040 f2af4600 ffffffc0 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.822484]
Jul  7 00:27:47 rockpro64 kernel: [  276.822484] X25: 0xffffffc0f7f461d0:
Jul  7 00:27:47 rockpro64 kernel: [  276.828883] 61d0  ffffffff 00000000 ffffffff ffffffff 00000001 00000000 f7f461e8 ffffffc0
Jul  7 00:27:47 rockpro64 kernel: [  276.833044] 61f0  f7f461e8 ffffffc0 f7f461f8 ffffffc0 f7f461f8 ffffffc0 0814a210 ffffff80
Jul  7 00:27:47 rockpro64 kernel: [  276.837304] 6210  f2aa7cf8 ffffffc0 f2aa7c50 ffffffc0 00020002 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.841659] 6230  00000001 00000000 00000045 00000000 00000044 00000000 f2b87000 ffffffc0
Jul  7 00:27:47 rockpro64 kernel: [  276.846093] 6250  f7f46250 ffffffc0 00000000 00000000 00000000 00000000 46384600 00000040
Jul  7 00:27:47 rockpro64 kernel: [  276.850589] 6270  46384600 00000040 0815618c ffffff80 f7f45c80 ffffffc0 00000000 0000001f
Jul  7 00:27:47 rockpro64 kernel: [  276.855051] 6290  08156160 ffffff80 63746177 676f6468 0000352f 00000000 00000044 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.859579] 62b0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.864041]
Jul  7 00:27:47 rockpro64 kernel: [  276.864041] X26: 0xffffff800922b1b8:
Jul  7 00:27:47 rockpro64 kernel: [  276.871664] b1b8  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.876458] b1d8  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.881255] b1f8  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.886048] b218  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.890843] b238  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.895635] b258  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.900283] b278  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.904883] b298  ******** ******** ******** ******** ******** ******** ******** ********
Jul  7 00:27:47 rockpro64 kernel: [  276.909336]
Jul  7 00:27:47 rockpro64 kernel: [  276.909336] X27: 0xffffff8009267820:
Jul  7 00:27:47 rockpro64 kernel: [  276.916932] 7820  00000001 00000000 00000001 00000000 000000fa 00000000 f7f55480 ffffffc0
Jul  7 00:27:47 rockpro64 kernel: [  276.921706] 7840  00000015 00000000 f7f55440 ffffffc0 00000001 00000006 00000060 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.926579] 7860  00015000 00001000 00000001 00000000 f7f554c0 ffffffc0 f7f578c0 ffffffc0
Jul  7 00:27:47 rockpro64 kernel: [  276.931567] 7880  00000000 00000005 00000010 00000000 f7f55340 ffffffc0 f7ed7000 ffffffc0
Jul  7 00:27:47 rockpro64 kernel: [  276.936570] 78a0  eecb2000 00000040 eecc7000 00000040 eecdc000 00000040 eecf1000 00000040
Jul  7 00:27:47 rockpro64 kernel: [  276.941666] 78c0  eed06000 00000040 eed1b000 00000040 00000000 00000000 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.946663] 78e0  00000002 00000000 0000341a 00000000 00010000 00000000 000f7fff 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.951672] 7900  0001e26f 00000000 00002000 00000000 00000000 0000fffa 00000000 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.956584]
Jul  7 00:27:47 rockpro64 kernel: [  276.956584] X29: 0xffffffc0f7f43c80:
Jul  7 00:27:47 rockpro64 kernel: [  276.965091] 3c80  000000fd 00000000 00000000 00000000 f2b0fda0 ffffffc0 f7f46250 ffffffc0
Jul  7 00:27:47 rockpro64 kernel: [  276.970327] 3ca0  0922b238 ffffff80 092678a0 ffffff80 00000000 00000000 f7f43d00 ffffffc0
Jul  7 00:27:47 rockpro64 kernel: [  276.975652] 3cc0  0815631c ffffff80 f7f43d00 ffffffc0 0815631c ffffff80 600001c5 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.981076] 3ce0  09266898 ffffff80 0000003a 00000000 00000000 00000080 f2400028 ffffffc0
Jul  7 00:27:47 rockpro64 kernel: [  276.986605] 3d00  f7f43d70 ffffffc0 08120dbc ffffff80 f7f46250 ffffffc0 f7f45c00 ffffffc0
Jul  7 00:27:47 rockpro64 kernel: [  276.992229] 3d20  4639b2b9 00000040 f7f45c80 ffffffc0 09225000 ffffff80 00000003 00000000
Jul  7 00:27:47 rockpro64 kernel: [  276.997814] 3d40  093d9290 ffffff80 4639b2b9 00000040 0815618c ffffff80 4639a1a2 00000040
Jul  7 00:27:47 rockpro64 kernel: [  277.003464] 3d60  f7f46250 ffffffc0 09266898 ffffff80 f7f43de0 ffffffc0 081213a0 ffffff80
Jul  7 00:27:47 rockpro64 kernel: [  277.009073]
Jul  7 00:27:47 rockpro64 kernel: [  277.013844] ---[ end trace 8ad4400a27e2532b ]---
Jul  7 00:27:47 rockpro64 kernel: [  277.018940] Call trace:
Jul  7 00:27:47 rockpro64 kernel: [  277.023832] Exception stack(0xffffffc0f7f43b30 to 0xffffffc0f7f43c60)
Jul  7 00:27:47 rockpro64 kernel: [  277.029162] 3b20:                                   ffffff800922b000<PHONE_NUMBER>000000
Jul  7 00:27:47 rockpro64 kernel: [  277.034695] 3b40: ffffffc0f7f43d00 ffffff800815631c<PHONE_NUMBER>000026<PHONE_NUMBER>000000
Jul  7 00:27:47 rockpro64 kernel: [  277.040252] 3b60: ffffffc0f7f43c00 ffffff800810b958 ffffffc0f7f43c80 ffffff8008f96378
Jul  7 00:27:47 rockpro64 kernel: [  277.045809] 3b80: ffffff8009266000<PHONE_NUMBER>0000fd<PHONE_NUMBER>000000 ffffffc0f2b0fda0
Jul  7 00:27:47 rockpro64 kernel: [  277.051316] 3ba0: ffffffc0f7f46250 ffffff800922b238 ffffff80092678a0<PHONE_NUMBER>000000
Jul  7 00:27:47 rockpro64 kernel: [  277.056895] 3bc0: ffffffc0f7f43be0 ffffff8009225000<PHONE_NUMBER>000026<PHONE_NUMBER>000005
Jul  7 00:27:47 rockpro64 kernel: [  277.062391] 3be0: 00000040eed1b000 00000040eed1b000<PHONE_NUMBER>000000<PHONE_NUMBER>000000
Jul  7 00:27:47 rockpro64 kernel: [  277.067850] 3c00:<PHONE_NUMBER>000001<PHONE_NUMBER>000000<PHONE_NUMBER>001000<PHONE_NUMBER>aaaaaa
Jul  7 00:27:47 rockpro64 kernel: [  277.073271] 3c20:<PHONE_NUMBER>000008 00000000ffffffff ffffffc0f29dac20 ffffff800ba006c0
Jul  7 00:27:47 rockpro64 kernel: [  277.078672] 3c40: ffffff800ba006c0<PHONE_NUMBER>000000<PHONE_NUMBER>000000<PHONE_NUMBER>000000
Jul  7 00:27:47 rockpro64 kernel: [  277.084108] [] watchdog_timer_fn+0x190/0x2e8
Jul  7 00:27:47 rockpro64 kernel: [  277.089350] [] __hrtimer_run_queues+0x1bc/0x284
Jul  7 00:27:47 rockpro64 kernel: [  277.094585] [] hrtimer_interrupt+0xac/0x1bc
Jul  7 00:27:47 rockpro64 kernel: [  277.099778] [] tick_handle_oneshot_broadcast+0x144/0x1c0
Jul  7 00:27:47 rockpro64 kernel: [  277.105045] [] rk_timer_interrupt+0x4c/0x5c
Jul  7 00:27:47 rockpro64 kernel: [  277.110241] [] handle_irq_event_percpu+0xf4/0x1f0
Jul  7 00:27:47 rockpro64 kernel: [  277.115419] [] handle_irq_event+0x50/0x80
Jul  7 00:27:47 rockpro64 kernel: [  277.120565] [] handle_fasteoi_irq+0xcc/0x134
Jul  7 00:27:47 rockpro64 kernel: [  277.125794] [] generic_handle_irq+0x2c/0x44
Jul  7 00:27:47 rockpro64 kernel: [  277.131064] [] __handle_domain_irq+0xb4/0xb8
Jul  7 00:27:47 rockpro64 kernel: [  277.136404] [] gic_handle_irq+0xc8/0x180
Jul  7 00:27:47 rockpro64 kernel: [  277.141769] Exception stack(0xffffffc0f2b0fda0 to 0xffffffc0f2b0fed0)
Jul  7 00:27:47 rockpro64 kernel: [  277.147335] fda0:<PHONE_NUMBER>000000<PHONE_NUMBER>000005 00000040eed1b000<PHONE_NUMBER>000020
Jul  7 00:27:47 rockpro64 kernel: [  277.153195] fdc0: 00ffffffffffffff 000000015d6e6ac3<PHONE_NUMBER>013240<PHONE_NUMBER>000005
Jul  7 00:27:47 rockpro64 kernel: [  277.158984] fde0: 00000034b5593519 ffffff8008081800<PHONE_NUMBER>001000<PHONE_NUMBER>000000
Jul  7 00:27:47 rockpro64 kernel: [  277.164811] fe00:<PHONE_NUMBER>d5d91d 00000040eed1b000 ffffffc0f2af4600<PHONE_NUMBER>000000
Jul  7 00:27:47 rockpro64 kernel: [  277.170576] fe20:<PHONE_NUMBER>000000<PHONE_NUMBER>000000<PHONE_NUMBER>d00800<PHONE_NUMBER>3979c2
Jul  7 00:27:47 rockpro64 kernel: [  277.176342] fe40:<PHONE_NUMBER>000002 ffffffc0efd9b400<PHONE_NUMBER>000002 ffffff80093d97b8
Jul  7 00:27:47 rockpro64 kernel: [  277.182075] fe60:<PHONE_NUMBER>000001<PHONE_NUMBER>fd1bb7 ffffff80093720c0<PHONE_NUMBER>c9d234
Jul  7 00:27:47 rockpro64 kernel: [  277.187875] fe80:<PHONE_NUMBER>000000 ffffffc0f2b0fed0 ffffff8008948f34 ffffffc0f2b0fed0
Jul  7 00:27:47 rockpro64 kernel: [  277.193661] fea0: ffffff8008948f38<PHONE_NUMBER>000145 ffffffc0f2b0fed0 ffffff8008948f34
Jul  7 00:27:47 rockpro64 kernel: [  277.199506] fec0: ffffffffffffffff<PHONE_NUMBER>000002
Jul  7 00:27:47 rockpro64 kernel: [  277.205075] [] el1_irq+0xb4/0x140
Jul  7 00:27:47 rockpro64 kernel: [  277.210676] [] cpuidle_enter_state+0x1fc/0x254
Jul  7 00:27:47 rockpro64 kernel: [  277.216358] [] cpuidle_enter+0x34/0x44
Jul  7 00:27:47 rockpro64 kernel: [  277.221947] [] call_cpuidle+0x70/0x78
Jul  7 00:27:47 rockpro64 kernel: [  277.227432] [] cpu_startup_entry+0x29c/0x2ac
Jul  7 00:27:47 rockpro64 kernel: [  277.232944] [] secondary_start_kernel+0x190/0x1bc
Jul  7 00:27:47 rockpro64 kernel: [  277.238509] [<0000000002c9d178>] 0x2c9d178
john@FrankenDell:~$
`

Are you sure that you don't have underpower issue? This clearly seems to be the one. Maybe too weak power adapter?

Are you sure that you don't have underpower issue? This clearly seems to be the one. Maybe too weak power adapter?

I don't think 3A 5V with my R64 4GB is underpowered

I'm running the 12v 5A adapter on the RockPro64.

I actually figured out that I had a bad PCI card. I picked up the one at the link below, and added the "pci=nomsi" boot parameter as outlined in the following forum post and was able to initialize raid1 on 2x white label HGST as well as 2x older intel SSDs I had laying around at the same time while also running "stress -c4 -m16" then further could run dd of /dev/urandom to both raid devices and all is stable.
https://www.amazon.com/gp/product/B07KNXZFRH/ref=ppx_yo_dt_b_asin_title_o04_s00?ie=UTF8&psc=1
https://forum.pine64.org/showthread.php?tid=6496

I have the same issue.
My configuration:
ROCKPro64 4GB Single Board Computer
ROCKPro64 PCI-e to Dual SATA-II Interface Card
ROCKPro64 Metal Desktop/NAS Casing with fan
ROCKPro64 12V 5A EU Power Supply
2x Seagate IronWolf NAS HDD, 4TB each
Installed 0.9.14 (tried both armhf and arm64) first, updated all packages, activated SMART monitoring, quick-wiped both disks, created RAID1 via the OMV web interface. Server crashes at random times, web interface not reachable, SSH doesn't work. No dmesg output (via SSH) before the crash. Sometimes still responds to iCMP pings, sometimes doesn't. After a power cycle, RAID is in "sync pending" state, nothing suspicious in kern.log.
Then tried a vanilla armbian (stretch), updated all packages, installed OMV via armbian-config, created RAID1 via the OMV web interface as before. This time received a kernel panic while connected via SSH:
Message from syslogd@localhost at Nov 18 10:01:47 ...
kernel:[ 75.976355] Internal error: : 96000210 [#1] SMP

Message from syslogd@localhost at Nov 18 10:01:47 ...
kernel:[ 83.247622] BUG: spinlock lockup suspected on CPU#2, scsi_eh_1/284

Message from syslogd@localhost at Nov 18 10:01:47 ...
kernel:[ 83.251260] lock: 0xffffff8009121870, .magic: dead4ead, .owner: scsi_eh_1/284, .owner_cpu: 2

Message from syslogd@localhost at Nov 18 10:03:59 ...
kernel:[ 240.428491] Kernel panic - not syncing: hung_task: blocked tasks

Finally tried booting the armbian-setup with pci=nomsi, resulting in the same behavior as with the 0.9.14 image (no error message, just crashed).
Any updates on this issue?

Can you try to force downclock RAM to 400MHz? I would assume that this is
due to this (this was usually thing in the past). Is not that RAM is bad,
but maybe some setting is off somewhere.
On Mon, Nov 18, 2019 at 12:22 PM Jonas Windhager<EMAIL_ADDRESS>wrote:

I have the same issue.
My configuration:
ROCKPro64 4GB Single Board Computer
ROCKPro64 PCI-e to Dual SATA-II Interface Card
ROCKPro64 Metal Desktop/NAS Casing with fan
ROCKPro64 12V 5A EU Power Supply
2x Seagate IronWolf NAS HDD, 4TB each
Installed 0.9.14 (tried both armhf and arm64) first, updated all packages,
activated SMART monitoring, quick-wiped both disks, created RAID1 via the
OMV web interface. Server crashes at random times, web interface not
reachable, SSH doesn't work. No dmesg output (via SSH) before the crash.
Sometimes still responds to iCMP pings, sometimes doesn't. After a power
cycle, RAID is in "sync pending" state, nothing suspicious in kern.log.
Then tried a vanilla armbian (stretch), updated all packages, installed
OMV via armbian-config, created RAID1 via the OMV web interface as before.
This time received a kernel panic while connected via SSH:
Message from syslogd@localhost at Nov 18 10:01:47 ...
kernel:[ 75.976355] Internal error: : 96000210 [#1] SMP
Message from syslogd@localhost at Nov 18 10:01:47 ...
kernel:[ 83.247622] BUG: spinlock lockup suspected on CPU#2, scsi_eh_1/284
Message from syslogd@localhost at Nov 18 10:01:47 ...
kernel:[ 83.251260] lock: 0xffffff8009121870, .magic: dead4ead, .owner: scsi_eh_1/284, .owner_cpu: 2
Message from syslogd@localhost at Nov 18 10:03:59 ...
kernel:[ 240.428491] Kernel panic - not syncing: hung_task: blocked tasks
Finally tried booting the armbian-setup with pci=nomsi, resulting in the
same behavior as with the 0.9.14 image (no error message, just crashed).
Any updates on this issue?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ayufan-rock64/linux-build/issues/299?email_source=notifications&email_token=AASOSQNZAVHYAOKOC2HOG63QUJ3IBA5CNFSM4GBUZLP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEKDR3I#issuecomment-554973421,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASOSQP57VJPCZJV63UYAY3QUJ3IBANCNFSM4GBUZLPQ
.

Hi ayufan! Thanks for your reply. How can I force the RAM clock down to 400MHz?

Look in /sys/class/devfreq/dmc

Unfortunately, setting /sys/class/devfreq/dmc/max_freq to 400000000 didn't help. This time, however, dmesg recorded the problem "on time":
[Nov18 23:22] Unhandled fault: synchronous external abort (0x96000210) at 0xffffff80093e6130
[  +0.008153] Internal error: : 96000210 [#1] SMP

Message from syslogd@localhost at Nov 18 23:22:09 ...
 kernel:[ 2234.999648] Internal error: : 96000210 [#1] SMP
[  +0.007787] Modules linked in: softdog af_packet lz4hc lz4hc_compress zlib snd_soc_rockchip_hdmi_dp rk_vcodec lzo zram ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid1 raid0 multipath linear md_mod phy_rockchip_pcie
[  +0.026297] CPU: 0 PID: 275 Comm: scsi_eh_0 Not tainted 4.4.192-rockchip64 #1
[  +0.008800] Hardware name: Pine64 RockPro64 (DT)
[  +0.008527] task: ffffffc0dfb2f000 task.stack: ffffffc0f13c8000
[  +0.008705] PC is at ahci_scr_read+0x70/0x98
[  +0.008534] LR is at sata_scr_read+0x88/0x94
[  +0.008413] pc : [<ffffff800875bf08>] lr : [<ffffff80087427cc>] pstate: 80000145
[  +0.008847] sp : ffffffc0f13cba50
[  +0.008375] x29: ffffffc0f13cba50 x28:<PHONE_NUMBER>000000
[  +0.008557] x27: ffffffc0f111de80 x26:<PHONE_NUMBER>000001
[  +0.008501] x25: ffffffc0f111e258 x24: ffffffc0f111c000
[  +0.008404] x23:<PHONE_NUMBER>000000 x22: ffffffc0f13cbb28
[  +0.008362] x21: ffffffc0f111de80 x20: ffffffc0f13cbb28
[  +0.008370] x19:<PHONE_NUMBER>000001 x18:<PHONE_NUMBER>d00800
[  +0.008406] x17:<PHONE_NUMBER>000000 x16:<PHONE_NUMBER>000000
[  +0.008354] x15:<PHONE_NUMBER>000000 x14:<PHONE_NUMBER>000000
[  +0.008249] x13:<PHONE_NUMBER>000000 x12:<PHONE_NUMBER>000000
[  +0.008137] x11:<PHONE_NUMBER>000000 x10:<PHONE_NUMBER>000000
[  +0.007989] x9 :<PHONE_NUMBER>000000 x8 : ffffffc0f111e258
[  +0.007940] x7 :<PHONE_NUMBER>000000 x6 : ffffffc0f111e2d0
[  +0.007889] x5 :<PHONE_NUMBER>000000 x4 : ffffff8008caa2fc
[  +0.007881] x3 :<PHONE_NUMBER>000130 x2 : ffffffc0f13cbb28
[  +0.007871] x1 :<PHONE_NUMBER>000030 x0 : ffffff80093e6130
[  +0.007827]
              PC: 0xffffff800875be88:
[  +0.014995] be88  52800013 91392821 97fe24e0 17ffffe2 a9bd7bfd 910003fd a90153f3 f90013f5
[  +0.008527] bea8  aa0003f5 2a0103f3 aa1e03e0 aa0203f4 d503201f f94002a3 7100127f f959dc60
[  +0.008603] bec8  b9402c63 f9401801 53196063 91040063 f9400820 54000268 54000061 b9401821
[  +0.008668] bee8  36e80201 f0002a64 910b8084 91007084 b8735881 34000161 8b21c063 8b030000
[  +0.008674] bf08  b9400000 d5033d9f b9000280 52800000 a94153f3 f94013f5 a8c37bfd d65f03c0
[  +0.008708] bf28  128002a0 17fffffb a9be7bfd 910003fd f9000bf3 aa0003f3 aa1e03e0 d503201f
[  +0.008725] bf48  f9400260 f9400000 f959dc00 f9401800 b9400000 36400120 52801fe0 b9038660
[  +0.008736] bf68  f0003c22 900038a1 91399842 912ff421 aa1303e0 97ff9d5d f9400bf3 a8c27bfd
[  +0.008855]
              LR: 0xffffff800874274c:
[  +0.016111] 274c  a90153f3 a9025bf5 aa0003f3 2a0103f5 aa1e03e0 aa0203f6 d503201f f9400274
[  +0.008943] 276c  d283d000 8b000280 eb00027f 54000180 f959c280 eb00027f 54000120 aa1603e2
[  +0.008966] 278c  2a1503e1 aa1303e0 9400573d a94153f3 a9425bf5 a8c37bfd d65f03c0 aa1303e0
[  +0.008985] 27ac  97fffb19 34000100 f9400680 aa1603e2 2a1503e1 f9406c03 aa1303e0 d63f0060
[  +0.009029] 27cc  17fffff3 12800bc0 17fffff1 a9ba7bfd 910003fd a90153f3 a9025bf5 a90363f7
[  +0.009210] 27ec  a9046bf9 aa0103f5 aa0203f6 aa0003f7 aa1e03e0 d503201f f0004e93 b94012a0
[  +0.009226] 280c  f940e274 a94066b8 97e76ebe 8b000280 cb160001 910173a2 f100003f 52800001
[  +0.009244] 282c  9a80a2d6 aa1703e0 97ffffc4 2a0003f5 350003c0 b9405fb4 f940e27a 12000e94
[  +0.009336]
              SP: 0xffffffc0f13cb9d0:
[  +0.016472] b9d0  f13cbb28 ffffffc0 00000000 00000000 f111c000 ffffffc0 f111e258 ffffffc0
[  +0.008879] b9f0  00000001 00000000 f111de80 ffffffc0 00000000 00000000 f13cba50 ffffffc0
[  +0.008658] ba10  087427cc ffffff80 f13cba50 ffffffc0 0875bf08 ffffff80 80000145 00000000
[  +0.008461] ba30  091178a0 ffffff80 f7ede200 ffffffc0 ffffffff ffffffff 080f0094 ffffff80
[  +0.008373] ba50  f13cba80 ffffffc0 087427cc ffffff80 f111de80 ffffffc0 f111c000 ffffffc0
[  +0.008306] ba70  00000001 00000000 f2aa4680 ffffffc0 f13cbab0 ffffffc0 0874f6ac ffffff80
[  +0.008282] ba90  f111e258 ffffffc0 f111de80 ffffffc0 f111f858 ffffffc0 00003008 00000000
[  +0.008266] bab0  f13cbb60 ffffffc0 0874fe6c ffffff80 f111c000 ffffffc0 f111de80 ffffffc0
[  +0.008353]
              X0: 0xffffff80093e60b0:
[  +0.014831] 60b0
[  +0.050245] Unhandled fault: synchronous external abort (0x96000210) at 0xffffff80093e60b0
[  +0.961736] rk3x-i2c ff3c0000.i2c: timeout, ipd: 0x10, state: 1

Hi,
Is there some person who has this setup with HDD disk and this works correctly?
ROCKPro64 4GB Single Board Computer
ROCKPro64 PCI-e to Dual SATA-II Interface Card
ROCKPro64 Metal Desktop/NAS Casing with fan
ROCKPro64 12V 5A EU Power Supply
Thanks in advance.

@romanczukiewiczs Please ask in https://forum.pine64.org/index.php
I have massiv problems with pine64 pcie-to-sata adapter. Now i use Marvell 88SE9230 without problems.

@bullet64 do You use this with pine64rockpro? You did on this setup something with mdadm?

Yes. Please read about it in my forum. My forum profile https://forum.pine64.org/member.php?action=profile&uid=8601

Hi
Any news on that ?
I had the same issue on manjaro and debian buster.
But the issue is not only on PCIe to sata card:
I can get, like you, the issue in 5 minutes with PCIe and SATA disk if I use syncthing and let it scan my files or if I use dd command.
But I have the same issue if I remove the PCIe card and if I do hexdump /dev/eMMC disk or sdcard and wait 10 to 40 minutes. I would have never noticed that if I didn't decided to do more test on my eMMC and sd card driver.
When I use the sdcard I can see that when I have the issue, it is always after 10 seconds of DMA failure (DMA is started but we dont get the DMA done interruption).
So I first though it was an issue on sdcard driver but no:
If I remove the sdcard and use eMMC only, I will also get the same (a)synchronous external abort oops
Note: When adding debug messages in the kernel driver, I was taking more time to get the oops, but you will get it
It is unlikely that we have similar BUG in eMMC, sdcard and PCIe so I think it is a hardware issue.
But why some people dont have this issue ?
Maybe only some devices have this BUG ?

I couldn't make it work with the Pine64 card. Now using a Marvell-based one (88SE9128) without a single dmesg error for 3 weeks already.

FYI - I have the same configuration and same problem as @jwindhager reported.

+1, same hardware
OMV5 runs at Armbian
Crashes with Creating a File System:
 ____            _    ____               __   _  _
|  _ \ ___   ___| | _|  _ \ _ __ ___    / /_ | || |
| |_) / _ \ / __| |/ / |_) | '__/ _ \  | '_ \| || |_
|  _ < (_) | (__|   <|  __/| | | (_) | | (_) |__   _|
|_| \_\___/ \___|_|\_\_|   |_|  \___/   \___/   |_|

Welcome to Armbian buster with Linux 4.4.210-rockchip64

System load:   2.13 0.66 0.23  	Up time:       0 min
Memory usage:  10 % of 3874MB 	IP:            <IP_ADDRESS>
CPU temp:      51°C
Usage of /:    17% of 15G

Last login: Sun Feb  2 19:08:55 2020 from <IP_ADDRESS>

root@NAS-rockpro64:~# mkfs.ext4 /dev/sda
mke2fs 1.44.5 (15-Dec-2018)
Creating filesystem with 732566646 4k blocks and 183148544 inodes
Filesystem UUID: 21668c66-fbee-4fd2-8e1f-2127a8c48970
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 (262144 blocks):
Message from syslogd@NAS-rockpro64 at Feb  3 18:04:10 ...
 kernel:[  121.843550] Internal error: : 96000210 [#1] SMP

Message from syslogd@NAS-rockpro64 at Feb  3 18:04:10 ...
 kernel:[  129.131405] BUG: spinlock lockup suspected on CPU#0, scsi_eh_0/274

Message from syslogd@NAS-rockpro64 at Feb  3 18:04:10 ...
 kernel:[  129.135057]  lock: 0xffffff8009321870, .magic: dead4ead, .owner: scsi_eh_0/274, .owner_cpu: 0

@hemertje Can you check if you get the same results on DietPi?

OK, Stable or Testing image?

Testing, as linked.

OK, Wil try
DietPi_RockPro64-ARMv8-Buster.7z | 2020-01-22 01:31 | 98M
Can it run OMV?
Do you have a link to a Howto?

OK, Wil try
DietPi_RockPro64-ARMv8-Buster.7z | 2020-01-22 01:31 | 98M
Can it run OMV?
Do you have a link to a Howto?

Here's how to get started: https://forum.openmediavault.org/index.php/Thread/25062-Install-OMV5-on-Debian-10-Buster/
Try formatting the disk(s) first just to test and please share the results.

 He suggests too small of a power supply at beginning. Probably an issue with the kernel. I'm running Bionic on mine and have no issues. I would try one of the armbian images (those come from ayufan's work too) - dl.armbian.com/rockpro64/archive/. I have had better luck with the 4.x kernels over the 5.x kernels.

Well, I've tried Armbian, Ayufan's OMV and Manjaro and all of those just kernel panic for me. The only one that has worked so far is DietPi. Others might get other results, but that seems doubtable as long as the identical hardware is used.
root@DietPi:~# uptime
 21:20:11 up 4 days,  3:29,  1 user,  load average: 0.07, 0.03, 0.01
root@DietPi:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sdb[1] sda[0]
<PHONE_NUMBER> blocks super 1.2 [2/2] [UU]
      bitmap: 0/30 pages [0KB], 65536KB chunk

unused devices: <none>

https://dietpi.com/phpbb/viewtopic.php?p=5#p5
Open Media Vault - NOT available anymore due to incompatibilities!
Installed Dietpi as minimal with OMV as stated here  https://forum.openmediavault.org/index.php/Thread/25062-Install-OMV5-on-Debian-10-Buster/
Errors were encountered while processing:
openssh-server
openmediavault
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@DietPi:~# cat /etc/issue
Armbian 20.02.0-rc0 Buster \l

on the WebIf
Welcome to nginx!
If you see this page, the nginx web server is successfully installed and working. Further configuration is required.
For online documentation and support please refer to nginx.org.
Commercial support is available at nginx.com.
Thank you for using nginx.

Feb 03 21:12:00 DietPi systemd[1]: Starting OpenBSD Secure Shell server...
Feb 03 21:12:00 DietPi sshd[20297]: error: Bind to port 22 on <IP_ADDRESS> failed: Address already in use.
Feb 03 21:12:00 DietPi sshd[20297]: error: Bind to port 22 on :: failed: Address already in use.
Feb 03 21:12:00 DietPi sshd[20297]: fatal: Cannot bind any address.
Feb 03 21:12:00 DietPi systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION
Feb 03 21:12:00 DietPi systemd[1]: ssh.service: Failed with result 'exit-code'.
Feb 03 21:12:00 DietPi systemd[1]: Failed to start OpenBSD Secure Shell server.
dpkg: error processing package openssh-server (--configure):
installed openssh-server package post-installation script subprocess returned error exit status 1
Setting up php7.3-fpm (7.3.11-1~deb10u1) ...
Creating config file /etc/php/7.3/fpm/php.ini with new version
Created symlink /etc/systemd/system/multi-user.target.wants/php7.3-fpm.service → /lib/systemd/system/php7.3-fpm.service.
Setting up php-pam (1.0.3-1+deb10u1) ...
Setting up collectd (5.8.1-1.3) ...
dpkg: dependency problems prevent configuration of openmediavault:
openmediavault depends on openssh-server; however:
Package openssh-server is not configured yet.

dpkg: error processing package openmediavault (--configure):
dependency problems - leaving unconfigured
Setting up rrdcached (1.7.1-2) ...
Setting up libnginx-mod-http-image-filter (1.14.2-2+deb10u1) ...
Setting up libjavascript-minifier-xs-perl (0.11-1+b5) ...
Setting up libbind9-161:arm64 (1:9.11.5.P4+dfsg-5.1) ...
Setting up samba-libs:arm64 (2:4.9.5+dfsg-5+deb10u1) ...
Setting up php-yaml (2.0.2+1.3.1-4) ...
Setting up nginx-full (1.14.2-2+deb10u1) ...
Setting up salt-minion (2019.2.2+ds-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/salt-minion.service → /lib/systemd/system/salt-minion.service.
Setting up liblocale-po-perl (0.27-2) ...
Setting up php-fpm (2:7.3+69) ...
Setting up rrdtool (1.7.1-2) ...
Setting up bind9-host (1:9.11.5.P4+dfsg-5.1) ...
Setting up php-cgi (2:7.3+69) ...
Setting up python-samba (2:4.9.5+dfsg-5+deb10u1) ...
Setting up nginx (1.14.2-2+deb10u1) ...
Setting up samba-vfs-modules:arm64 (2:4.9.5+dfsg-5+deb10u1) ...
Setting up samba-common-bin (2:4.9.5+dfsg-5+deb10u1) ...
Checking smb.conf with testparm
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Server role: ROLE_STANDALONE
Done
Setting up avahi-daemon (0.7-4+b1) ...
Created symlink /etc/systemd/system/dbus-org.freedesktop.Avahi.service → /lib/systemd/system/avahi-daemon.service.
Created symlink /etc/systemd/system/multi-user.target.wants/avahi-daemon.service → /lib/systemd/system/avahi-daemon.service.
Created symlink /etc/systemd/system/sockets.target.wants/avahi-daemon.socket → /lib/systemd/system/avahi-daemon.socket.
Setting up libnss-mdns:arm64 (0.14.1-1) ...
First installation detected...
Checking NSS setup...
Setting up samba (2:4.9.5+dfsg-5+deb10u1) ...
Adding group `sambashare' (GID 120) ...
Done.
Samba is not being run as an AD Domain Controller: Masking samba-ad-dc.service
Please ignore the following error about deb-systemd-helper not finding those services.
(samba-ad-dc.service masked)
Created symlink /etc/systemd/system/multi-user.target.wants/nmbd.service → /lib/systemd/system/nmbd.service.
Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.
/usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory
Created symlink /etc/systemd/system/multi-user.target.wants/smbd.service → /lib/systemd/system/smbd.service.
Setting up wsdd (0.5-1) ...
wsdd.service is a disabled or a static unit, not starting it.
Setting up liblvm2cmd2.03:arm64 (2.03.02-3) ...
Setting up dmeventd (2:1.02.155-3) ...
Created symlink /etc/systemd/system/sockets.target.wants/dm-event.socket → /lib/systemd/system/dm-event.socket.
dm-event.service is a disabled or a static unit, not starting it.
Setting up lvm2 (2.03.02-3) ...
update-initramfs: deferring update (trigger activated)
Created symlink /etc/systemd/system/sysinit.target.wants/blk-availability.service → /lib/systemd/system/blk-availability.service.
Created symlink /etc/systemd/system/sysinit.target.wants/lvm2-monitor.service → /lib/systemd/system/lvm2-monitor.service.
Created symlink /etc/systemd/system/sysinit.target.wants/lvm2-lvmpolld.socket → /lib/systemd/system/lvm2-lvmpolld.socket.
Processing triggers for mime-support (3.62) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-5.4.13-rockchip64
update-initramfs: Converting to u-boot format
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for systemd (241-7~deb10u2) ...
Processing triggers for rsyslog (8.1901.0-1) ...
Processing triggers for dbus (1.12.16-1) ...
Errors were encountered while processing:
openssh-server
openmediavault
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@DietPi:~# omv-confdbadm populate
[WARNING ] /usr/lib/python3/dist-packages/salt/utils/path.py:265: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
if not isinstance(exes, collections.Iterable):
Traceback (most recent call last):
File "/usr/sbin/omv-confdbadm", line 74, in
sys.exit(main())
File "/usr/sbin/omv-confdbadm", line 70, in main
return cmd_inst.execute(*sys.argv)
File "/usr/share/openmediavault/confdbadm/commands.d/update.py", line 59, in execute
db.set(obj)
File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 294, in set
query = openmediavault.config.DatabaseSetQuery(obj)
File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 757, in init
super().init(obj.model.id)
File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 305, in init
self._database_file = openmediavault.getenv("OMV_CONFIG_FILE")
File "/usr/lib/python3/dist-packages/openmediavault/init.py", line 56, in getenv
value = openmediavault.settings.Environment.get_str(key, default)
File "/usr/lib/python3/dist-packages/openmediavault/settings.py", line 77, in get_str
value = Environment.get(key, default)
File "/usr/lib/python3/dist-packages/openmediavault/settings.py", line 71, in get
% (key, DEFAULT_FILE)
KeyError: "The environment variable 'OMV_CONFIG_FILE' does not exist in '/etc/default/openmediavault'"
Traceback (most recent call last):
File "/usr/sbin/omv-confdbadm", line 74, in
sys.exit(main())
File "/usr/sbin/omv-confdbadm", line 70, in main
return cmd_inst.execute(*sys.argv)
File "/usr/share/openmediavault/confdbadm/commands.d/populate.py", line 48, in execute
openmediavault.subprocess.check_call([script_path])
File "/usr/lib/python3/dist-packages/openmediavault/subprocess.py", line 58, in check_call
return subprocess.check_call(*popenargs, **kwargs)
File "/usr/lib/python3.7/subprocess.py", line 347, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/share/openmediavault/confdb/populate.d/20hostname.sh']' returned non-zero exit status 1.
root@DietPi:~# cat /etc/issue
Armbian 20.02.0-rc0 Buster \l

Please don't clutter this thread with issues that aren't related directly to the issue. Try formatting the disk(s) instead and see if that works without the kernel panicking. Regarding your current issue, try the stable version of DietPi and then install OMV. Any issues should be reported on their forums.

OK, Wil try
DietPi_RockPro64-ARMv8-Buster.7z | 2020-01-22 01:31 | 98M
Can it run OMV?
Do you have a link to a Howto?

Here's how to get started: https://forum.openmediavault.org/index.php/Thread/25062-Install-OMV5-on-Debian-10-Buster/
Try formatting the disk(s) first just to test and please share the results.

Above instruction won't work anymore on Stable DietPi...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
openmediavault : Depends: php-pam but it is not going to be installed
Depends: monit but it is not going to be installed
Depends: salt-minion but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
root@DietPi:~#
Sorry can't test for you...

Put the 3TB WD Red HDD in an external case with his own power supply
Connected via USB3 between RockPro64 and the external case
Now it formats without problems, see screenshot
Never came this far...

Which rom are you using? DietPi or something else? The issue in this thread was also specifically reported for the pcie-adapter from pine64 and hence should be discussed around that but thanks for reporting back of the success.

Armbian_19.11.7_Rockpro64_buster_legacy_<IP_ADDRESS>z from
https://dl.armbian.com/rockpro64/archive/
My Pine64 PCI card
root@rockpro64:~# lspci
00:00.0 PCI bridge: Fuzhou Rockchip Electronics Co., Ltd RK3399 PCI Express Root Port
01:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)
root@rockpro64:~#

I found at my computing stuff a WD 1TB Green Caviar HDD and tried it without the external power supply, similar like before with the 3TB WD Red HDD
Got the same errors as before , but it took a little longer before the system crashed
`Creating the file system, please wait ...
===== Wipe signatures from device =====
===== Create partition =====
Creating new GPT entries.
Disk /dev/sda:<PHONE_NUMBER> sectors, 931.5 GiB
Model: WDC WD10EADS-00L
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 1E8AE397-E393-4A56-8835-5F9A81FA53CB
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is<PHONE_NUMBER>
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number  Start (sector)    End (sector)  Size       Code  Name
1            2048<PHONE_NUMBER>   931.5 GiB   8300
The operation has completed successfully.
===== Create file system =====
mke2fs 1.44.5 (15-Dec-2018)
Creating filesystem with 244190385 4k blocks and 61054976 inodes
Filesystem UUID: 88b18685-3bde-4609-99d8-539883efb79f
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
Allocating group tables:    0/7453         done
Writing inode tables:    0/7453  45/7453 241/7453 317/7453 366/7453 414/7453 463/7453 511/7453 557/7453 600/7453 641/7453 680/7453 720/7453 759/7453 798/7453 838/7453 863/7453 871/7453 874/7453`
` ____            _    ____               __   _  _
|  _ \ ___   | | |  _ \ _ __ ___    / / | || |
| |) / _ \ / __| |/ / |) | '/ _ \  | '_ | || |_
|  _ < (_) | (|   <|  /| | | () | | () | |
|| __/ _||__|   ||  _/   __/   |_|
Welcome to Armbian buster with Linux 4.4.208-rockchip64
System load:   0.11 0.07 0.02  	Up time:       2:41 hours
Memory usage:  5 % of 3874MB 	Zram usage:    2 % of 1937Mb 	IP:            <IP_ADDRESS>
CPU temp:      36°C
Usage of /:    7% of 29G
[ General system configuration (beta): armbian-config ]
Last login: Wed Feb  5 17:21:39 2020 from <IP_ADDRESS>
root@rockpro64:~#
Message from syslogd@localhost at Feb  5 19:57:03 ...
kernel:[ 9735.004750] Internal error: : 96000210 [#1] SMP
Message from syslogd@localhost at Feb  5 19:57:10 ...
kernel:[ 9742.274127] BUG: spinlock lockup suspected on CPU#0, scsi_eh_2/264
Message from syslogd@localhost at Feb  5 19:57:10 ...
kernel:[ 9742.277966]  lock: 0xffffff8009321870, .magic: dead4ead, .owner: scsi_eh_2/264, .owner_cpu: 0
Message from syslogd@localhost at Feb  5 19:58:48 ...
kernel:[ 9840.525926] Kernel panic - not syncing: hung_task: blocked tasks`

How to bring it down to the specific cause?
Power supply or PCI-SATA card or ?
Faulty hardware or caused by software?

Which rom are you using? DietPi or something else? The issue in this thread was also specifically reported for the pcie-adapter from pine64 and hence should be discussed around that but thanks for reporting back of the success.

I installed bionic-minimal-rockpro64-0.9.16-1163-armhf.img.xz from https://github.com/ayufan-rock64/linux-build/releases/tag/0.9.16
with the updates:
sudo apt-get update -y && sudo apt-get install linux-rockpro64-0.9 -y
sudo apt-get update -y && sudo apt-get dist-upgrade -y
I opened a second ssh session with the command:
tail -f /var/log/syslog
and did some debugging with the command:
mkfs.ext4 /dev/sda
here is the log:
Welcome to Ubuntu 18.04.4 LTS (GNU/Linux 4.4.197-1236-rockchip-ayufan-g30faab37e339 aarch64)
                _                     __   _  _
 _ __ ___   | | ___ __  _ __ ___  / / | || |
| '/ _ \ / | |/ / ' | '/ _ | '_ | || |_
| | | (_) | (|   <| |) | | | () | (_) |_   |
||  _/ _||_\ .__/||  _/ _/   ||
                    ||
* Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage
System information as of Sun Feb 16 15:20:07 UTC 2020
System load:  0.14              Processes:           168
  Usage of /:   5.3% of 28.42GB   Users logged in:     1
  Memory usage: 2%                IP address for eth0: <IP_ADDRESS>
  Swap usage:   0%
* Multipass 1.0 is out!  Supports cloud-init for fast, local, cloud devops simulation.
https://multipass.run/
Last login: Sun Feb 16 15:17:51 2020 from <IP_ADDRESS>
rock64@rockpro64:~$ tail -f /var/log/syslog
Feb 16 15:17:49 rockpro64 systemd[774]: Reached target Sockets.
Feb 16 15:17:49 rockpro64 systemd[774]: Reached target Timers.
Feb 16 15:17:49 rockpro64 systemd[774]: Reached target Basic System.
Feb 16 15:17:49 rockpro64 systemd[774]: Reached target Default.
Feb 16 15:17:49 rockpro64 systemd[774]: Startup finished in 184ms.
Feb 16 15:17:49 rockpro64 systemd[1]: Started User Manager for UID 1000.
Feb 16 15:18:01 rockpro64 CRON[830]: (root) CMD (for i in pgrep "ftpd|nfsiod|smbd|afpd|cnid" ; do ionice -c1 -p $i ${XU4_HMP_Fix}; done &>/dev/null)
Feb 16 15:19:01 rockpro64 CRON[835]: (root) CMD (for i in pgrep "ftpd|nfsiod|smbd|afpd|cnid" ; do ionice -c1 -p $i ${XU4_HMP_Fix}; done &>/dev/null)
Feb 16 15:20:01 rockpro64 CRON[842]: (root) CMD (for i in pgrep "ftpd|nfsiod|smbd|afpd|cnid" ; do ionice -c1 -p $i ${XU4_HMP_Fix}; done &>/dev/null)
Feb 16 15:20:07 rockpro64 systemd[1]: Started Session 11 of user rock64.
Feb 16 15:21:01 rockpro64 CRON[897]: (root) CMD (for i in pgrep "ftpd|nfsiod|smbd|afpd|cnid" ; do ionice -c1 -p $i ${XU4_HMP_Fix}; done &>/dev/null)
Feb 16 15:21:30 rockpro64 kernel: [  410.987554] ata2.00: exception Emask 0x0 SAct 0x7effffff SErr 0x0 action 0x6 frozen
Feb 16 15:21:30 rockpro64 kernel: [  410.988489] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  410.989238] ata2.00: cmd 61/40:00:40:e8:85/05:00:ae:00:00/40 tag 0 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  410.989238]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  410.990973] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  410.991420] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  410.992056] ata2.00: cmd 61/40:08:80:ed:85/05:00:ae:00:00/40 tag 1 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  410.992056]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  410.993900] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  410.994359] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  410.994995] ata2.00: cmd 61/40:10:c0:f2:85/05:00:ae:00:00/40 tag 2 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  410.994995]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  410.996811] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  410.997272] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  410.997908] ata2.00: cmd 61/40:18:00:f8:85/05:00:ae:00:00/40 tag 3 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  410.997908]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  410.999625] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.000068] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.000795] ata2.00: cmd 61/40:20:40:fd:85/05:00:ae:00:00/40 tag 4 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.000795]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.002530] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.002974] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.003609] ata2.00: cmd 61/40:28:80:02:86/05:00:ae:00:00/40 tag 5 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.003609]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.005431] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.005879] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.006514] ata2.00: cmd 61/40:30:c0:07:86/05:00:ae:00:00/40 tag 6 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.006514]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.008022] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.008403] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.008968] ata2.00: cmd 61/40:38:00:0d:86/05:00:ae:00:00/40 tag 7 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.008968]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.010471] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.010852] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.011395] ata2.00: cmd 61/40:40:40:12:86/05:00:ae:00:00/40 tag 8 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.011395]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.012943] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.013326] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.013870] ata2.00: cmd 61/40:48:80:17:86/05:00:ae:00:00/40 tag 9 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.013870]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.015371] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.015751] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.016295] ata2.00: cmd 61/40:50:c0:1c:86/05:00:ae:00:00/40 tag 10 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.016295]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.017851] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.021465] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.025255] ata2.00: cmd 61/40:58:00:22:86/05:00:ae:00:00/40 tag 11 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.025255]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.033208] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.036768] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.040422] ata2.00: cmd 61/40:60:40:27:86/05:00:ae:00:00/40 tag 12 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.040422]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.048219] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.051419] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.054501] ata2.00: cmd 61/40:68:80:2c:86/05:00:ae:00:00/40 tag 13 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.054501]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.061055] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.063968] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.067066] ata2.00: cmd 61/40:70:c0:31:86/05:00:ae:00:00/40 tag 14 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.067066]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.073633] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.076588] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.079646] ata2.00: cmd 61/40:78:00:37:86/05:00:ae:00:00/40 tag 15 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.079646]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.086228] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.089029] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.091678] ata2.00: cmd 61/40:80:40:3c:86/05:00:ae:00:00/40 tag 16 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.091678]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.097416] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.099930] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.102607] ata2.00: cmd 61/40:88:80:41:86/05:00:ae:00:00/40 tag 17 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.102607]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.108357] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.110774] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.113115] ata2.00: cmd 61/40:90:c0:46:86/05:00:ae:00:00/40 tag 18 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.113115]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.118185] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.120369] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.122711] ata2.00: cmd 61/40:98:00:4c:86/05:00:ae:00:00/40 tag 19 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.122711]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.127790] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.130003] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.132327] ata2.00: cmd 61/40:a0:40:51:86/05:00:ae:00:00/40 tag 20 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.132327]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.137407] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.139600] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.141946] ata2.00: cmd 61/40:a8:80:56:86/05:00:ae:00:00/40 tag 21 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.141946]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.147043] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.149225] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.151329] ata2.00: cmd 61/40:b0:c0:5b:86/05:00:ae:00:00/40 tag 22 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.151329]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.155970] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.157968] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.160073] ata2.00: cmd 61/40:b8:00:61:86/05:00:ae:00:00/40 tag 23 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.160073]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.164719] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.166698] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.168824] ata2.00: cmd 61/40:c8:c0:c8:85/05:00:ae:00:00/40 tag 25 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.168824]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.173477] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.175449] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.177578] ata2.00: cmd 61/40:d0:00:ce:85/05:00:ae:00:00/40 tag 26 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.177578]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.182221] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.184195] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.186336] ata2.00: cmd 61/40:d8:40:d3:85/05:00:ae:00:00/40 tag 27 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.186336]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.190676] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.192481] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.194438] ata2.00: cmd 61/40:e0:80:d8:85/05:00:ae:00:00/40 tag 28 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.194438]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.198734] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.200553] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.202490] ata2.00: cmd 61/40:e8:c0:dd:85/05:00:ae:00:00/40 tag 29 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.202490]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.206798] ata2.00: status: { DRDY }
Feb 16 15:21:30 rockpro64 kernel: [  411.208615] ata2.00: failed command: WRITE FPDMA QUEUED
Feb 16 15:21:30 rockpro64 kernel: [  411.210414] ata2.00: cmd 61/40:f0:00:e3:85/05:00:ae:00:00/40 tag 30 ncq 688128 out
Feb 16 15:21:30 rockpro64 kernel: [  411.210414]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 16 15:21:30 rockpro64 kernel: [  411.214423] ata2.00: status: { DRDY }
Feb 16 15:21:31 rockpro64 kernel: [  411.216102] ata2: hard resetting link
packet_write_wait: Connection to <IP_ADDRESS> port 22: Broken pipe
ATA controller:
rock64@rockpro64:~$ lspci |grep ATA
01:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)
and this hard drive:
rock64@rockpro64:~$ sudo smartctl -a /dev/sda |grep Model
Model Family:     Western Digital Red
Device Model:     WDC WD30EFRX-68EUZN0
here's the HDD's SMART report:
rock64@rockpro64:~$ sudo smartctl -a /dev/sda
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-4.4.197-1236-rockchip-ayufan-g30faab37e339] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD30EFRX-68EUZN0
Serial Number:    WD-WCC4N6JZS316
LU WWN Device Id: 5 0014ee 2111b9f23
Firmware Version: 82.00A82
User Capacity:    3,000,592,982,016 bytes [3.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:    Sun Feb 16 15:42:12 2020 UTC
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:  (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
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: (42420) 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:  ( 425) 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   185   176   021    Pre-fail  Always       -       5750
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       525
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   098   098   000    Old_age   Always       -       1808
 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       -       469
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       48
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       590
194 Temperature_Celsius     0x0022   122   113   000    Old_age   Always       -       28
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   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   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  Extended offline    Completed without error       00%      1335         -
2  Extended offline    Completed without error       00%      1187         -
3  Extended offline    Completed without error       00%      1062         -
4  Extended offline    Completed without error       00%       862         -
5  Extended offline    Completed without error       00%       696         -
6  Extended offline    Completed without error       00%       549         -
7  Extended offline    Completed without error       00%       411         -
8  Extended offline    Completed without error       00%       267         -
9  Extended offline    Completed without error       00%       121         -
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.
As a layman myself, I see some "errors" with the dmesg command:
[    1.479161] vcc5v0_host: no parameters
[    1.479325] reg-fixed-voltage vcc5v0-host-regulator: vcc5v0_host supplying 0uV
[    1.479966] iommu: Adding device ff650000.vpu_service to group 0
[    1.480069] iommu: Adding device ff660000.rkvdec to group 1
[    1.480166] iommu: Adding device ff670000.iep to group 2
[    1.480293] iommu: Adding device ff8f0000.vop to group 3
[    1.480388] platform ff8f0000.vop: iommu /iommu@ff8f3f00 not found
[    1.480408] iommu: Removing device ff8f0000.vop from group 3
[    1.480471] iommu: Adding device ff900000.vop to group 3
[    1.480993] rk_iommu ff650800.iommu: can't get sclk
[    1.481295] rk_iommu ff660480.iommu: can't get sclk
[    1.481408] rk_iommu ff670800.iommu: can't get aclk
[    1.481432] rk_iommu ff670800.iommu: can't get hclk
[    1.481453] rk_iommu ff670800.iommu: can't get sclk
[    1.481655] rk_iommu ff903f00.iommu: can't get sclk
[    1.482036] SCSI subsystem initialized
[    1.845571] phy<EMAIL_ADDRESS>Failed to get VBUS supply regulator
[    1.851160] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
[    1.851268] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
[    1.851279] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed
[    1.851294] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
[    1.851321] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
[    1.851331] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed
[    1.851343] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
[    1.851367] rockchip-pcie f8000000.pcie: bus-scan-delay-ms in device tree is 1000 ms
[    1.851400] rockchip-pcie f8000000.pcie: missing "memory-region" property
[    1.851438] PCI host bridge /pcie@f8000000 ranges:
[    1.851472]   MEM 0xfa000000..0xfbdfffff -> 0xfa000000
[    1.851495]    IO 0xfbe00000..0xfbefffff -> 0xfbe00000
[    1.898676] rockchip-pcie f8000000.pcie: invalid power supply
[    1.935126] rockchip-pcie f8000000.pcie: wait 1000 ms (from device tree) before bus scan
[    2.938931] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[    3.135818] rockchip-spi ff1d0000.spi: no high_speed pinctrl state
[    3.946085] i2c i2c-10: of_i2c: modalias failure on /dp@fec00000/ports
[    3.947872] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
[    4.132784] xhci-hcd xhci-hcd.9.auto: Host not halted after 16000 microseconds.
[    4.137214] xhci-hcd xhci-hcd.9.auto: Host controller not halted, aborting reset.
[    4.951028] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
[   14.382190] ff100000.saradc supply vref not found, using dummy regulator
[   14.382297] rockchip-saradc ff100000.saradc: failed to get voltage
[   14.386073] rockchip-saradc: probe of ff100000.saradc failed with error -22
[   14.694857] FAT-fs (mmcblk0p6): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[   14.706800] [BT_RFKILL]: DISABLE UART_RTS
[   14.706867] [BT_RFKILL]: bt turn on power
[   14.712323] FAT-fs (mmcblk0p6): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Questions:

I see many driver failures in de dmesg?

Is this an incompatibility between the WD RED firmware and either the SATA Chipset and/or the mainboard it's self?

How to be fixed?


Adjust Rust version so that hax can translate it into fstar

Applied the changes that were previously documented in #80.

This PR contains the changes that we could do on our side to be compatible with hax fstar generation. It's not a lot, so I will be merging them soon.


Update z2ui5_cl_xml_view.clas.abap

Visible Property to Label

no worries, i fixed the issues, now its green and i can merge this one and delete the other pull request.
i think you created accidentally two branches, thats why both changes were in different branches. next time just delete the other branch and try to commit all changes in one branch, then also the PR gets automatically updated.
Thank you for your PR!


load model error

When I try to load model by model = DepthAnything.from_pretrained("depth_anything_{:}14".format(args.encoder)), it occurs that
Traceback (most recent call last):
  File "./models/depth_anything/dpt.py", line 183, in <module>
    model = DepthAnything.from_pretrained("depth_anything_{:}14".format(args.encoder))
  File "/home/aokiji/anaconda3/envs/go-slam/lib/python3.8/site-packages/huggingface_hub/utils/_validators.py", line 118, in _inner_fn
    return fn(*args, **kwargs)
  File "/home/aokiji/anaconda3/envs/go-slam/lib/python3.8/site-packages/huggingface_hub/hub_mixin.py", line 277, in from_pretrained
    instance = cls._from_pretrained(
  File "/home/aokiji/anaconda3/envs/go-slam/lib/python3.8/site-packages/huggingface_hub/hub_mixin.py", line 485, in _from_pretrained
    model = cls(**model_kwargs)
TypeError: __init__() missing 1 required positional argument: 'config'

I'm sure that the pth in the right path.

sorry for this, I make a mistake


pkg/shelf: io.serve() should accept a secure parameter for SSL

This issue was originally filed by<EMAIL_ADDRESS>
io.serve(handler, 'localhost', 8080) - does not allow binding using SSL.
It would be convenient to be able to pass an (optional) secure parameter:
io.serve(handler, 'localhost', 443, secure:true)

This issue has been moved to dart-lang/shelf#23.


Consts where val is a LogicValue have unsanitary names

Describe the bug
If you create a Const where val is a LogicValue (or some other legal val whose toString produces an invalid variable name), then the generated name for the Logic can be invalid since it is not sanitized.  The name of the signal should be sanitized.
To Reproduce
Const(LogicValue.ofString('10xz'))

Expected behavior
Constant is created without exception.
Actual behavior
Exception due to unsanitary name.

Will start working on this


Enabled syntax highlighting in README

Updated the readme with syntax highlighting for the code example

Is the email public for the CLA?

Is the email public for the CLA?

I'm afraid I don't understand your question

For the CLA I have to enter an email address. Is that email adres publicly visible then ?

For the CLA I have to enter an email address. Is that email adres publicly visible then ?

No, we do not make it publicly visible. It is collected so that if we update the CLA we have a concrete way to contact you (perhaps to resign, or to make you aware of changes), because GH ID is not the best way to contact someone after the fact :)


can not use "~" with mkdir

can not use "~" with mkdir
1 In powershell, the following functions are normal: (command with "~")
test-path ~/xxx
cd ~/xxx
2 i foud powershell's mkdir is linked to /usr/bin/mkdir:
mkdir --help     #    return gnu
3 can use 【mkdir ~/xxx】in bash,but can't use that command in powershell,i think it is a bug.
Steps to reproduce
mkdir ~/xxx
Expected behavior
support ~
Actual behavior
Environment data
linux:
centos 7.3 1611
Name                           Value

PSVersion                      6.0.0-alpha
PSEdition                      Core
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   <IP_ADDRESS>
GitCommitId                    v6.0.0-alpha.14
CLRVersion
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
reporter
By the chinese powershell study & research group. QQ group No. is 183173532
in 'vscode' or other open source project,in version release notes,bug reporter should be thank.
So I left a group name.

hi @SteveL-MSFT    This problem has been fixed,close it please.
Name                           Value

PSVersion                      6.0.0-beta
PSEdition                      Core
BuildVersion                   <IP_ADDRESS>
CLRVersion
GitCommitId                    v6.0.0-beta.1
OS                             Linux 3.10.0-514.16.1.el7.x86_64 #1 SMP Wed Apr 12 15:04:24 UTC 2017
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

I'm not repro'ing this with Ubuntu16.04 and beta.1.  mkdir ~/test2 created a folder called test2 in my home directory.
I'll try with CentOS.


Wrong usage of application symbol

I'm not sure if this is NOT a Capistrano issue. But since everything used to work fine in staging before implementing scm-gitcopy into production I will post it here.
In my deploy.rb my application symbol is set to:
set :application, 'Semcoglas'
set :deploy_to, '/var/www/semcoweb'

I always regarded application as App name.
When I run cap production deploy everything works fine so far. All paths are used correctly based on the deploy_to symbol.
But then, when Composer is supposed to run, the path suddenly changes to /var/www/Semcoglas <- name of the :application symbol.
Of course I get a Could not open file: /var/www/Semcoglas/shared/composer.phar error.
I tried without defining :application and indeed the wrong path will become /var/www/shared/....
Any idea what is happening here?

Have you come across this issue before @leehambley? Maybe you can confirm if this issue is directly related to @capistrano? Thanks

I've not seen this one before @webdevilopers - Sounds like the capistrano-composer Gem has a problem?

Okay, since there is no other feedback by @xuwupeng2000 I'm gonna move this issue there. Thanks for the feedback @leehambley !


alternate-current

Mod name
alternate-current
Curseforge link
No response
Other links
https://modrinth.com/mod/alternate-current
https://github.com/SpaceWalkerRS/alternate-current
What it does
Alternate Current is an efficient and non-locational redstone dust implementation. Its main focus lies in reducing the lag caused by redstone dust, by optimizing the power calculations and reducing the number of shape and block updates emitted. As a side effect of these changes the block update order of redstone dust networks is predictable and intuitive rather than locational and chaotic.
MSPT contributions of redstone dust are up to 20 times lower with Alternate Current, all the while maintaining a high level of Vanilla parity. Its low number of code modifications make it minimally invasive, so it's an easy drop-in replacement for Vanilla redstone dust.
Why should it be in the modpack
10 times faster than Lithium
Why shouldn't it be in the modpack
it changes the redstone update order
Categories
Performance optimization
Additional details
No response

it changes the redstone update order

It may be faster and more efficient, but it still changes overall redstone behavior, so unfortunately I cannot include it. See also: #44

it changes the redstone update order

It may be faster and more efficient, but it still changes overall redstone behavior, so unfortunately I cannot include it. See also: #44

Basically it wont break any thing, it just make the redstone wire more predictable, or just fix some broken or locational machine which broke by the vanilla redstone wire. Vanilla redstone wire update order just worse

*While Lithium can boast 100% Vanilla parity, Alternate Current cannot.


allow copying only parts of the output

the solution here could be 2 parts:

add hints as copy sources
additionally add a json command that allows saying something like "copy value quench" which will copy the surrounding value of a word that is preceded by q:

first bullet point done by #35


Create Issues For July/August Items

Look at SoW

Done, some of the items I added may be completed already, but oh well


add uber h3 hexagonal hierarchical spatial index example

🚀 Pull Request
Description

This pull-request adds an Uber H3 example, which demonstrates the relationship between the underlying icosahedron and the base resolution, and the next 3 child resolutions of this hexagonal hierarchical spatial index.
This hierarchical index is of particular interest as it may potentially provide an approach/framework for sharding, aggregating and rendering higher-resolution meshes in a scalable way; certainly an exciting space worth exploring further.
https://github.com/bjlittle/geovista/assets/2051656/f042d927-54a5-4e76-9640-5884b708a349

Hmmmm soooo tempted to drop support for py39 ... been tiptoeing around it for a while now.
The NEP29 Drop Schedule for py39 is 5 Apr 2024, so that's ballpark and close enough for me 🤔

pre-commit.ci autofix