maracuja
-
Posts
26 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by maracuja
-
-
I changed the swappiness from 100 (=aggressive swapping) to 20.
sysctl -w vm.swappiness=20
System seemed more responsive first but it got stuck again when installing php7.3
I set up the led to blink when accessing the sd card:
echo "mmc0" > /sys/class/leds/orangepi\:red\:status/trigger
It's fully on now. System only responds to pings. Guess the system is so busy that it doesn't even switch the LED.
-
Did an "apt-get install mosquitto" and while "Setting up mosquitto" it said "Killed"
Dmesg gives me:
Oct 12 11:31:32 etj-55555555 systemd[1]: Reloading. Oct 12 11:31:33 etj-55555555 systemd[1]: /lib/systemd/system/nginx.service:8: PIDFile= references path below legacy directory /var/run/, updating /var/run/nginx.pid → /run/nginx.pid; please update the unit file accordingly. Oct 12 11:31:34 etj-55555555 systemd[1]: Reloading. Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711235] systemd-bless-b invoked oom-killer: gfp_mask=0x40cc0(GFP_KERNEL|__GFP_COMP), order=2, oom_score_adj=0 Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711260] CPU: 1 PID: 5174 Comm: systemd-bless-b Not tainted 5.4.8-sunxi #19.11.6 Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711265] Hardware name: Allwinner sun8i Family Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711308] [<c010da8d>] (unwind_backtrace) from [<c010a0b1>] (show_stack+0x11/0x14) Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711326] [<c010a0b1>] (show_stack) from [<c093634f>] (dump_stack+0x6f/0x7c) Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711345] [<c093634f>] (dump_stack) from [<c01fc515>] (dump_header+0x41/0x172) Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711359] [<c01fc515>] (dump_header) from [<c01fbcfb>] (oom_kill_process+0xfb/0x104) Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711369] [<c01fbcfb>] (oom_kill_process) from [<c01fc3f7>] (out_of_memory+0x19f/0x228) Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711383] [<c01fc3f7>] (out_of_memory) from [<c022eb0f>] (__alloc_pages_nodemask+0xaff/0xc9c) Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711400] [<c022eb0f>] (__alloc_pages_nodemask) from [<c0213e95>] (kmalloc_order+0x19/0x38) Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711412] [<c0213e95>] (kmalloc_order) from [<c0213ecd>] (kmalloc_order_trace+0x19/0x94) Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711430] [<c0213ecd>] (kmalloc_order_trace) from [<c015d37b>] (devkmsg_open+0x3f/0xc0) Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711445] [<c015d37b>] (devkmsg_open) from [<c0256975>] (chrdev_open+0x91/0x11c) Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711459] [<c0256975>] (chrdev_open) from [<c0250051>] (do_dentry_open+0xd5/0x2e8) Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711477] [<c0250051>] (do_dentry_open) from [<c025e2b5>] (path_openat+0x1ed/0xe14) Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711487] [<c025e2b5>] (path_openat) from [<c025fabf>] (do_filp_open+0x4f/0x90) Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711500] [<c025fabf>] (do_filp_open) from [<c0251081>] (do_sys_open+0x125/0x194) Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711513] [<c0251081>] (do_sys_open) from [<c0101001>] (ret_fast_syscall+0x1/0x62) Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711518] Exception stack(0xc0e91fa8 to 0xc0e91ff0) Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711529] 1fa0: b6edd000 b6f09968 ffffff9c b6d7385c 000a0101 00000000 Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711539] 1fc0: b6edd000 b6f09968 bef46ce4 00000142 00000000 00000000 0044af8c 00000000 Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711545] 1fe0: 00000142 bef46b00 b6e7525d b6dfe746 Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711550] Mem-Info: Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711572] active_anon:1329 inactive_anon:1532 isolated_anon:85 Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711572] active_file:1404 inactive_file:1017 isolated_file:22 Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711572] unevictable:4 dirty:0 writeback:0 unstable:0 Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711572] slab_reclaimable:4526 slab_unreclaimable:8663 Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711572] mapped:1787 shmem:53 pagetables:528 bounce:0 Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711572] free:32149 free_pcp:51 free_cma:31941 Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711586] Node 0 active_anon:5316kB inactive_anon:6128kB active_file:5616kB inactive_file:4068kB unevictable:16kB isolated(anon):340kB isolated(file):88kB mapped:7148kB dirty:0kB writeback:0kB shmem:212kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711613] Normal free:128596kB min:5388kB low:5708kB high:6028kB active_anon:5288kB inactive_anon:6144kB active_file:5556kB inactive_file:4152kB unevictable:16kB writepending:0kB present:262144kB managed:243968kB mlocked:16kB kernel_stack:1304kB pagetables:2112kB bounce:0kB free_pcp:212kB local_pcp:0kB free_cma:127764kB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711616] lowmem_reserve[]: 0 0 0 Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711625] Normal: 149*4kB (UMEC) 74*8kB (UMEC) 6*16kB (C) 5*32kB (C) 6*64kB (C) 4*128kB (C) 2*256kB (C) 2*512kB (C) 2*1024kB (C) 2*2048kB (C) 29*4096kB (C) = 128804kB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711663] 2545 total pagecache pages Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711669] 60 pages in swap cache Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711675] Swap cache stats: add 270671, delete 270604, find 8999/242120 Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711678] Free swap = 74584kB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711681] Total swap = 121980kB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711684] 65536 pages RAM Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711687] 0 pages HighMem/MovableOnly Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711690] 4544 pages reserved Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711693] 32768 pages cma reserved Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711699] Unreclaimable slab info: Oct 12 11:31:35 etj-55555555 kernel: [ 1361.711702] Name Used Total Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712107] zs_handle 179KB 204KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712187] RAWv6 47KB 47KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712193] UDPv6 35KB 35KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712216] TCPv6 63KB 63KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712227] sgpool-128 30KB 30KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712236] sgpool-64 31KB 31KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712245] sgpool-32 15KB 15KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712254] sgpool-16 7KB 7KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712259] mqueue_inode_cache 15KB 15KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712281] jfs_mp 3KB 3KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712299] jbd2_inode 15KB 15KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712316] kioctx 7KB 7KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712334] rpc_buffers 32KB 32KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712343] RAW 31KB 31KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712351] UDP 61KB 61KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712359] request_sock_TCP 3KB 3KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712369] TCP 126KB 126KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712383] eventpoll_pwq 15KB 15KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712394] inotify_inode_mark 15KB 15KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712406] request_queue 125KB 125KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712413] blkdev_ioc 16KB 16KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712422] biovec-max 453KB 453KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712432] biovec-128 126KB 126KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712439] biovec-64 63KB 63KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712450] dmaengine-unmap-256 31KB 31KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712457] dmaengine-unmap-128 47KB 47KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712465] audit_buffer 4KB 4KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712473] skbuff_fclone_cache 31KB 31KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712484] skbuff_head_cache 173KB 173KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712492] configfs_dir_cache 7KB 7KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712503] file_lock_cache 16KB 16KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712523] fsnotify_mark_connector 15KB 15KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712545] net_namespace 60KB 60KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712553] task_delay_info 19KB 19KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712564] taskstats 30KB 30KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712574] proc_dir_entry 88KB 88KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712580] pde_opener 15KB 15KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712591] seq_file 15KB 15KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712604] shmem_inode_cache 267KB 267KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712619] kernfs_iattrs_cache 15KB 15KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712635] kernfs_node_cache 2051KB 2051KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712654] filp 409KB 437KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712674] names_cache 180KB 192KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712700] key_jar 141KB 192KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712720] vm_area_struct 154KB 189KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712737] mm_struct 32KB 32KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712745] files_cache 20KB 20KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712754] signal_cache 157KB 157KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712762] sighand_cache 252KB 252KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712769] task_struct 334KB 334KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712777] cred_jar 40KB 40KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712785] anon_vma_chain 220KB 220KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712793] anon_vma 163KB 163KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712798] pid 20KB 20KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712803] trace_event_file 99KB 99KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712812] pool_workqueue 16KB 16KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712833] vmap_area 364KB 436KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712846] kmalloc-8k 984KB 1088KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712851] kmalloc-4k 356KB 356KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712856] kmalloc-2k 480KB 480KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712868] kmalloc-1k 850KB 864KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712881] kmalloc-512 598KB 656KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712886] kmalloc-256 132KB 132KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712891] kmalloc-192 173KB 173KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712896] kmalloc-128 292KB 292KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712903] kmalloc-64 1650KB 1652KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712908] kmem_cache_node 68KB 68KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712913] kmem_cache 251KB 252KB Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712916] Tasks state (memory values in pages): Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712920] [ pid ] uid tgid total_vm rss pgtables_bytes swapents oom_score_adj name Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712970] [ 295] 0 295 7021 358 59392 189 0 systemd-journal Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712981] [ 326] 0 326 4060 163 16384 154 -1000 systemd-udevd Oct 12 11:31:35 etj-55555555 kernel: [ 1361.712995] [ 456] 0 456 1812 2 14336 768 0 haveged Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713005] [ 579] 0 579 2657 336 20480 129 0 systemd-logind Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713014] [ 584] 0 584 1830 157 14336 52 0 cron Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713024] [ 592] 104 592 1371 284 16384 74 -900 dbus-daemon Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713046] [ 599] 0 599 6796 0 16384 34 0 rngd Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713063] [ 604] 0 604 2183 17 18432 101 0 wpa_supplicant Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713078] [ 606] 0 606 6197 211 22528 188 0 rsyslogd Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713097] [ 609] 0 609 5583 2 26624 1230 0 networkd-dispat Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713111] [ 615] 0 615 15327 194 45056 387 0 NetworkManager Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713125] [ 808] 0 808 8738 0 36864 1290 0 unattended-upgr Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713145] [ 832] 105 832 2753 133 12288 57 0 chronyd Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713160] [ 838] 105 838 806 0 12288 61 0 chronyd Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713176] [ 862] 0 862 2220 2 16384 143 -1000 sshd Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713194] [ 936] 0 936 8994 53 24576 144 0 polkitd Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713212] [ 943] 0 943 1561 2 14336 212 0 dhclient Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713226] [ 1178] 0 1178 1536 0 16384 29 0 agetty Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713243] [ 1182] 0 1182 959 0 10240 24 0 agetty Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713262] [ 1184] 0 1184 1536 0 14336 28 0 agetty Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713277] [ 1264] 0 1264 2557 184 16384 174 0 sshd Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713292] [ 1267] 0 1267 2987 0 20480 220 0 systemd Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713308] [ 1268] 0 1268 8105 0 30720 410 0 (sd-pam) Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713319] [ 1361] 0 1361 1957 210 14336 247 0 bash Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713332] [ 1369] 0 1369 1957 2 16384 233 0 bash Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713345] [ 1452] 0 1452 1688 319 14336 14 0 watch Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713361] [ 1671] 111 1671 1171 78 14336 80 0 avahi-daemon Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713376] [ 1672] 111 1672 1171 0 12288 60 0 avahi-daemon Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713405] [ 5006] 0 5006 47314 298 45056 558 0 php-fpm7.3 Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713416] [ 5010] 33 5010 47314 101 38912 571 0 php-fpm7.3 Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713425] [ 5011] 33 5011 47314 101 38912 571 0 php-fpm7.3 Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713436] [ 5083] 0 5083 14172 798 65536 2688 0 apt-get Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713453] [ 5137] 0 5137 2295 241 14336 373 0 dpkg Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713467] [ 5138] 0 5138 368 241 8192 13 0 mosquitto.posti Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713489] [ 5168] 0 5168 368 262 10240 0 0 invoke-rc.d Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713504] [ 5172] 0 5172 2247 621 18432 0 0 systemctl Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713515] [ 5173] 0 5173 8033 371 28672 340 0 (sd-executor) Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713529] [ 5174] 0 5174 2592 645 18432 0 0 systemd-bless-b Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713541] [ 5175] 0 5175 2595 1058 18432 0 0 systemd-cryptse Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713556] [ 5176] 0 5176 2593 1035 20480 0 0 systemd-debug-g Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713569] [ 5178] 0 5178 2596 1120 20480 0 0 systemd-fstab-g Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713583] [ 5180] 0 5180 2593 662 18432 0 0 systemd-getty-g Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713596] [ 5181] 0 5181 2596 1062 20480 0 0 systemd-gpt-aut Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713606] [ 5182] 0 5182 2593 1064 18432 0 0 systemd-hiberna Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713614] [ 5183] 0 5183 2593 1110 18432 0 0 systemd-rc-loca Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713623] [ 5184] 0 5184 2593 817 18432 0 0 systemd-run-gen Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713631] [ 5186] 0 5186 2593 1081 18432 0 0 systemd-system- Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713640] [ 5187] 0 5187 2596 669 18432 0 0 systemd-sysv-ge Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713662] [ 5188] 0 5188 2593 861 18432 0 0 systemd-veritys Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713675] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-0.slice/session-3.scope,task=apt-get,pid=5083,uid=0 Oct 12 11:31:35 etj-55555555 kernel: [ 1361.713779] Out of memory: Killed process 5083 (apt-get) total-vm:56688kB, anon-rss:2096kB, file-rss:1096kB, shmem-rss:0kB, UID:0 pgtables:65536kB oom_score_adj:0 Oct 12 11:31:35 etj-55555555 kernel: [ 1361.730340] oom_reaper: reaped process 5083 (apt-get), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB Oct 12 11:31:35 etj-55555555 systemd[1]: /lib/systemd/system/nginx.service:8: PIDFile= references path below legacy directory /var/run/, updating /var/run/nginx.pid → /run/nginx.pid; please update the unit file accordingly. Oct 12 11:31:36 etj-55555555 systemd[1]: Starting Mosquitto MQTT v3.1/v3.1.1 Broker... Oct 12 11:31:36 etj-55555555 systemd[1]: Started Mosquitto MQTT v3.1/v3.1.1 Broker. Oct 12 11:31:38 etj-55555555 systemd[1]: Reloading.
-
@5kft You could try to do some apt-get install commands.
For example: apt-get install php7.3-fpm, apt-get install mosquitto
Then purge again.
And look if your swap gets used...
Maybe this is only orange pi zero specific. But it is 99.99% NOT a hardware issue. It must be a software issue. Something in the kernel, or a driver is eating up memory or the swap usage isn't configured correctly.
-
Next run - this time with zram = 50%
After reboot:
total used free shared buff/cache available Mem: 238Mi 72Mi 127Mi 0.0Ki 37Mi 159Mi Swap: 119Mi 9.0Mi 109MiWhile "apt-get purge mosquitto" - it got stuck multiple times for a couple of minutes (=system unresponsive)
The whole process took waaaaay too long for just purging a package.
total used free shared buff/cache available Mem: 238Mi 94Mi 122Mi 0.0Ki 20Mi 137Mi Swap: 119Mi 79Mi 39Mi -
Setting CPU governor to performance (like described in this thread) does not seem to be a solution.
I had a freeze again while running apt and while CPU governor was set to performance running @ 1.01 GHz.
Memory before the test:
total used free shared buff/cache available Mem: 238Mi 67Mi 132Mi 0.0Ki 38Mi 165Mi Swap: 59Mi 20Mi 38MiMemory during the test (during freeze):
total used free shared buff/cache available Mem: 238Mi 94Mi 127Mi 0B 16Mi 139Mi Swap: 59Mi 58Mi 0.0Ki -
I think it's a memory issue.
I have tested again with kernel 5.4.7 (Armbian 19.11.6)
I had a second ssh connection open this time running a "free -h" command every second.
While running apt on the first ssh connection it showed me that free swap went down to 0 bytes, used: 59 Mi, total: 59 Mi
I had changed zram config of armbian to use 25% instead of 50% memory. But I don't think that's the issue because others have the same problems without this change. And on kernel 4.19.x this memory issue does not seem to arise.
Also the fact that users with 512M memory don't have stability issues is a hint that it's a memory issue.
-
just to be precise: in my tests I've been using an orange pi zero - board rev 1.5 (the revision number is printed on the circuit board)
-
@5kft
It is possible to hook a serial console to the board, but what kind of outcome do you expect?
I can even reproduce the freezing - all I have to do is to run a script that has some "apt install ..." calls with custom deb packages that I've built. Today it got stuck when configuring php7.3-cli (a dependency) for example.
Then it said "process killed". The very same script runs without error on kernel 4.9.
-
The causes for the system freezes are most probably NOT:
the expansion board (I have none in use)
the WiFi module (I have blacklisted xradio_wlan and use an ethernet connection)
The causes could have to do with:
*) the kernel*) system load / temperature / current draw / cpu frequency
-
My Orange Pi Zero (256MB RAM) is also instable with recent kernels.
I have tried:
Armbian 20.08.3 with kernel 5.4.63 - custom built image: unexpected SSH disconnects, freezes (only ping works, but no ssh login), random problems with "apt install" - system freezes. "echo 0 > /sys/devices/system/cpu/cpu2/online" leads to kernel dumps or SSH freezes.
Most recent custom armbian build with kernel 5.8.x: same as above
Armbian 19.11.6 with kernel 5.4.8 - official image: same problems as above but putting cpu2 offline is working.
Armbian 5.91 with kernel 4.19.59 - official image: everything working as expected.
What I can eliminate as a source for these troubles is the SD card. I tried multiple SD cards (same SanDisk Ultra 16GB A1 Model).
In my opinion there is something wrong with the kernel. The temperature readings (if correct) looked normal when installing packages ~50-60 degrees.
Something in the armbian image broke after kernel 4.19.59.
I am using a Xiaomi Mi5 Charger (rated for 2A) as power source, but I also have a programmable lab power supply available. I could try it with the lab power supply too but haven't done so.
-
Ok, apparently it is not possible to reproduce old builds after more than ~ 1 month.
-
I'm trying to add some extra packages and configuration changes to build v20.08.
I did the following:
git clone -b v20.08 https://github.com/armbian/build build-orange-pi-v20.08
cd build-orange-pi-v20.08 && git reset --hard 6e9b07e
touch .ignore_changes
./compile.sh docker BRANCH=current BOARD=orangepizero KERNEL_ONLY=no KERNEL_CONFIGURE=no RELEASE=buster BUILD_DESKTOP=no CLEAN_LEVEL="" NO_APT_CACHER=yes
The build ends with "ERROR in function compile_kernel [ compilation.sh:411 ]"When I clone the master without sticking to a revision, it's working fine.
But I want to stick to an "official" build. How can this be done?
-
Thank you.
I'm in the build process right now. It seems to work, the process is installing a bunch of packages.
-
I've attached the output.log
It says:
Displaying message: Checking for local cache buster-cli-armhf.e51...09a.tar.lz4 info
Displaying message: searching on servers...
and then:
Extracting ...
So .. no, the new cache image is not made.
How can I enforce this?
-
-
I'm running an armbian build under docker (Host = Linux Mint or Ubuntu Bionic).
I ran
git clone --depth 1 https://github.com/armbian/build
The problem is, in my customize-image.sh script I'm trying to build something that needs to have a package installed before.
My lib.config looks like this:
#DEBIAN_MIRROR='ftp.at.debian.org/debian/' #DEBOOTSTRAP_LIST="$DEBOOTSTRAP_LIST,apt-transport-https,ca-certificates" display_alert "Adding additional packages" "PHP 7, Redis, udisk2, dnsmasq, python3, ..." "info" PACKAGE_LIST_ADDITIONAL="$PACKAGE_LIST_ADDITIONAL php7.0 php7.0-cli php7.0-fpm php7.0-curl php7.0-intl php7.0-redis php7.0-mbstring" PACKAGE_LIST_ADDITIONAL="$PACKAGE_LIST_ADDITIONAL redis-server udisks2 task-print-server dnsmasq" PACKAGE_LIST_ADDITIONAL="$PACKAGE_LIST_ADDITIONAL libcups2-dev python-pip python3-dev python3-pip libsodium-dev libffi-dev" # lib bluetooth for bdaddr script [[ $BOARD == "orangepizeroplus2-h3" ]] && PACKAGE_LIST_ADDITIONAL="$PACKAGE_LIST_ADDITIONAL bluez bluez-tools libbluetooth-dev"
I get to see the alert output. But the packages are never installed, I don't see them on the screen. Another hint that they are not installed is that my customize script relies on libbluetooth-dev to be installed. And it fails (most probably because libbluetooth-dev is missing).
I also don't see other packages like hostapd, git, ethtool, network-manager being installed that are in the base additional package list.
The output at that point is:
htop is already the newest version (2.2.0-1+b1).
mmc-utils is already the newest version (0+git20180327.b4fe0c8c-1).
sunxi-tools is already the newest version (1.4.2+git20181114.6d598a-3).
hostapd is already the newest version (3:2.7-99~armbian5.86+1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Obiously it reads the PACKAGE_LIST_ADDITIONAL variable, but my additional packages are nowhere...
There is another problem with buster:
I get the output "qemu: Unsupported syscall: 382" in my customize-configuration.sh
-
I'm trying to use PA18/PA19 for custom purposes. I need to put these pins to Input state without any pullups/pulldowns.
What I can achieve is: to put these pins to input state via the command:
gpio mode 30 in
gpio mode 31 in
("tri" instead of "in" does not work, it accepts the command, but a multimeter shows the input is still high, as well as gpio readall)
These pins are probably pulled high because they are I2C pins. I want to disable the I2C functionality but have not found any means to do so.
I have tried this dts script:
#####
/dts-v1/;
/ {
compatible = "allwinner,sun8i-h3","allwinner,sun50i-h5","friendlyarm,nanopi-neo2";fragment@0 {
target-path = "/soc/pinctrl@1c20800";__overlay__ {
i2c1 {
function = "gpio_in";
bias-high-impedance;
};
};
};
};######
and had a look at the device tree after a reboot:
dtc -I fs -O dts -o ./extracted.dts /proc/device-tree
The values got inserted right, but pin behaviour did not change. What I also cannot do is to activate pulldown on those pins. It has no effect.
Also tried a python library - https://github.com/duxingkei33/orangepi_PC_gpio_pyH3 - to no avail.
Board is an Orange Pi Zero +2 with H3 processor.
To sum it up:
Input mode is working (with pullup still activated)
Pulldown is not working
Deactivating Pullup is not working
Setting Pin to output mode and switching high/low is working
Kernel: 4.19.38-sunxi
-
I have removed the stickers from the board
and placed the antenna differently so the metal piece would not touch any chip.
But still... 1.8W current draw.
I have tested a third board. All boards have the same configuration, same revision 1.0, and a usb extension board attached.
One board draws 1.3-1.4W, one draws 1.4-1.5W, and the strange one draws 1.8W.
The 2 "normal" boards reach ~45°C after 40 minutes (temp. seems stable).
The strange board reaches
~53°C after 11 minutes,
~57°C after 18 minutes
~60°C after 26 minutes
~61°C after 40 minutes
-
I have perfectly equal Orange Pi Zero Plus 2 H3 boards in their original case - booting from eMMC.
Test conditions are: WiFi Hotspot enabled, HDMI off, CPU idle, CPU governor: performance, CPU freq. 240MHz - 1.1 GHz, kernel 4.14.84
Xiaomi Mi5 Charger as psu, 2.4A usb cable
armbianmonitor gives me a temp of ~50°C on one board (idle@1.1GHz)
and a temp of 65°C on the other board (same conditions, CPU starts throttling here to ~960 MHz).
The temp gets so high, that after an apt-get update/upgrade and reboot the opizero plus2 would not boot with an error msg that the temp is too high.
The temp seems to be correct more or less, since also the power consumption is significantly higher. While the 50°C board draws ~1.5W, the 65°C board draws ~1.8W.
I have no explanation for this...
-
On 5/14/2017 at 4:15 AM, martinayotte said:
Ok ! I've finally found some discripancies in DT between H3 and H5 : the reset-gpios default level in wifi-pwrseq of DT.
Thoses fixes the OPiZeroPlus2-H5 as well as NanoPiM1Plus2-H5. Next nigthlies should reflect that.
(Be aware for those two boards : MicroUSB powering is choking when WiFi get powered. I need some new stronger cables)
A side note : OPiWin still not work with the same medecine, as well as the BanadaPi-M2-Ultra ... I will dig further ...
EDIT : For those who trying fresh builds, you sill need @tkaiser firmware hack, which is not part of the images yet :
download /lib/firmware/ap6212/fw_bcm43438a1.bin and copy it under /lib/firmware/brcm/brcmfmac43430-sdio.bin.
Currently - for Armbian Stretch / OPIZeroPlus2-H3 - the files in /lib/firmware/ap6212/fw_bcm43438a1.bin and /lib/firmware/brcm/brcmfmac43430-sdio.bin are not identical.
WiFi works with both of them, but when using /lib/firmware/ap6212/fw_bcm43438a1.bin ping times improve!
One more thing: When using the ap6212 driver, 14 wifi channels are supported.
When using the driver in the brcm folder, though, only 11 wifi channels are supported.
Conclusion: out of the box Armbian Stretch uses the wrong driver for OPIZeroPlus2-H3 - resulting in bad ping times, and reduced number of wifi channels.
-
Just for the sake of completeness:
I've changed the init script for AP6212, I've inserted this:Quote/usr/local/bin/dmem2 0x1f00060 b 1
echo 10 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio10/direction
echo 0 > /sys/class/gpio/gpio10/value
echo 1 > /sys/class/gpio/gpio10/value
sleep 0.1
-
I could make some tiny progress:
First I checked the orange pi zero plus 2 schematics to be sure it is using UART1 for Bluetooth. Yes it is.
Then I had a look at the current device tree - somebody wrote that there should be 2 addresses in the pinctrl-0 entry.
Mine had only 1 address.
I decompiled /boot/dtb-4.14.65-sunxi/sun8i-h3-orangepi-zeroplus2.dtb and had a look at the entry serial@01c28400This is what is loooks like
Quoteserial@01c28400 {
compatible = "snps,dw-apb-uart";
reg = <0x1c28400 0x400>;
interrupts = <0x0 0x1 0x4>;
reg-shift = <0x2>;
reg-io-width = <0x4>;
clocks = <0x6 0x3f>;
resets = <0x6 0x32>;
dmas = <0x1f 0x7 0x1f 0x7>;
dma-names = "rx", "tx";
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <0x24 0x25>;
linux,phandle = <0x66>;
phandle = <0x66>;
};Here you can see pinctrl-0 looks okay.
So it must be the overlay that messes this up. I also looked at the uart1 overlay file (decompiled it) but all these things are new to me, so I gave up on it.
But something different looked promising: The status field is "okay", so it is enabled, right in the /boot/dtb-4.14.65-sunxi/sun8i-h3-orangepi-zeroplus2.dtb
I guess I don't even need an overlay to enable it then?
So knowing that the overlay messes the pinctrl-0 entry up, and guessing that I don't even need it, I just removed the uart1 overlay from the /boot/armbianEnv.txt and rebooted.
Now the output of my script looks like this:
Quotebcm43xx_init
Set Controller UART speed to 115200 bit/s
Flash firmware /etc/firmware/ap6212/BCM43430A1.hcd
Initialization timed out.Before it only said "Initialization timed out" with no UART speed output or Flash firmware output.
It's still not working...
1) I copied BCM43430A1.hcd from some site on the internet, having the same MD5 hash as a user that claims it's been working on this orange pi. Maybe I should've used the original one shipped with armbian... (which had a different MD5 hash)... now I've restored the original file (simply by deleting it, the init script copies the original one over) - but same result
2) I've also removed param_uart1_rtscts=1 from armbianEnv.txt - I don't know if this affects anything...
-
I can only offer to test setup instructions on the boards I have, if anyone has recommendations.
I'd be glad to post the results here.
If Bluetooth is working on some boards with the same chip (AP6212A) then it should actually work on the Zero Plus2 H3 too.
-
Well, it would be a good hint to put a remark in the download section of Armbian - at least for the Orange Pi Zero Plus2.
When downloading Armbian it does not say anything about Bluetooth being completely dysfunctional.
Orange Pi zero - freezing randomly
in Orange Pi Zero
Posted
Next memory exception (page allocation failure) I found while doing rsync...
This time I even disabled ram-log (50MB). ZRAM still @ 50%.
During this failure the system did not freeze. So even if you have 512M, there might still be something broken with page allocation on kernels after 4.9.x!