kcn

Members
  • Content Count

    7
  • Joined

  • Last visited

  1. kcn

    systemd 100% CPU on OrangePi One

    Tido, this was just for example. Any other command with systemctl like status, restart, etc, outputs "Connection timed out". For system restart helps "reboot -f". But sometimes even serial console hangs, then only power cycle.
  2. kcn

    systemd 100% CPU on OrangePi One

    There are two log files attached: current_journal.log contains current logs since last spontaneous reboot this night. This time, there was no anomaly CPU utilization yet (system installed last evening). Second file - old_journal.log is from previous setup, when issue occured many times. Manual for systemd management is very good, but when issue happens, systemd becomes uncontrollable. Any command looks like this: # systemctl reboot Failed to set wall message, ignoring: Connection timed out Failed to reboot system via logind: Connection timed out Failed to start reboot.target: Connection timed out I think to try Armbian with legacy kernel. I have an OrangePi Lite working stable with such version. old_journal.log current_journal.log
  3. kcn

    systemd 100% CPU on OrangePi One

    Reinstalled with new image, modified cpufrequtils (MIN_SPEED=480000, GOVERNOR=conservative). This did not help. Filesystem is ok: pione:~$ sudo armbianmonitor -v Starting package integrity check. This might take some time. Be patient please... It appears you don't have any corrupt files or packages! Now trying minimal setup with only minidlna installed...
  4. kcn

    systemd 100% CPU on OrangePi One

    Indeed, armbianmonitor -v confirmed that the file system is damaged: pione:~$ sudo armbianmonitor -v Starting package integrity check. This might take some time. Be patient please... It appears you may have corrupt packages. This is usually a symptom of filesystem corruption caused by SD cards or eMMC dying or burning the OS image to the installation media went wrong. The following changes from packaged state files were detected: /var/lib/rpimonitor/updatestatus.txt Thanks
  5. kcn

    systemd 100% CPU on OrangePi One

    rufik, where to find this config? $ cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq 240000 Tido, there are no wireless adapters connected. Only external USB hard drive attached. $ lsmod Module Size Used by evdev 20480 0 snd_soc_hdmi_codec 16384 1 rc_cec 16384 0 dw_hdmi_i2s_audio 16384 0 dw_hdmi_cec 16384 0 ip6table_filter 16384 0 ip6_tables 20480 1 ip6table_filter lz4 16384 20 sun8i_dw_hdmi 16384 0 lz4_compress 53248 1 lz4 dw_hdmi 28672 2 dw_hdmi_i2s_audio,sun8i_dw_hdmi cec 40960 2 dw_hdmi_cec,dw_hdmi sun4i_i2s 16384 2 sun8i_codec_analog 24576 0 snd_soc_simple_card 16384 0 snd_soc_simple_card_utils 16384 1 snd_soc_simple_card sun4i_gpadc_iio 16384 0 snd_soc_core 118784 5 sun4i_i2s,sun8i_codec_analog,snd_soc_hdmi_codec,snd_soc_simple_card_utils,snd_soc_simple_card snd_pcm_dmaengine 16384 1 snd_soc_core snd_pcm 65536 4 sun4i_i2s,snd_pcm_dmaengine,snd_soc_hdmi_codec,snd_soc_core sun8i_mixer 16384 0 snd_timer 24576 1 snd_pcm sun4i_tcon 20480 1 sun8i_dw_hdmi snd 45056 4 snd_soc_hdmi_codec,snd_timer,snd_soc_core,snd_pcm xt_nat 16384 1 soundcore 16384 1 snd zram 24576 5 uio_pdrv_genirq 16384 0 xt_tcpudp 16384 1 sun4i_drm 16384 0 uio 16384 1 uio_pdrv_genirq iptable_nat 16384 1 nf_conntrack_ipv4 16384 2 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 nf_nat_ipv4 16384 1 iptable_nat nf_nat 24576 2 xt_nat,nf_nat_ipv4 nf_conntrack 81920 4 xt_nat,nf_conntrack_ipv4,nf_nat_ipv4,nf_nat iptable_filter 16384 0 ip_tables 20480 2 iptable_filter,iptable_nat x_tables 20480 6 xt_nat,ip_tables,iptable_filter,xt_tcpudp,ip6table_filter,ip6_tables uas 20480 0
  6. kcn

    systemd 100% CPU on OrangePi One

    armbianmonitor -u won't work: pione:~$ sudo armbianmonitor -u System diagnosis information will now be uploaded to /usr/bin/armbianmonitor: line 831: [: -gt: unary operator expected Please post the URL in the forum where you've been asked for. I manualy uploaded some armbianmonitor logs: https://pastebin.com/VGrMddE5
  7. Hi! Periodically, time in two-three days, sharply increases CPU utilization, the system becomes disfunctional. SD card and power supply maybe not the best, but they working fine in other systems and I'm tried others. SSH hangs on login while this problem is actual, but i have a serial connection, so can investigate in real time. Please, advise, what to look when this situation came again? top - 03:02:15 up 24855 days, 3:14, 1 user, load average: 1.75, 1.77, 1.93 Tasks: 125 total, 3 running, 70 sleeping, 0 stopped, 8 zombie %Cpu(s): 17.4 us, 26.6 sy, 0.0 ni, 56.1 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 505152 total, 9724 free, 144028 used, 351400 buff/cache KiB Swap: 1301132 total, 1299340 free, 1792 used. 343236 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 26012 3040 1304 R 100.0 0.6 46:55.28 systemd 851 root 20 0 6128 1368 948 R 75.2 0.3 34:13.74 systemd-lo+ 8668 root 20 0 7044 2608 2136 R 1.3 0.5 0:00.15 top 7 root 20 0 0 0 0 S 0.3 0.0 14:28.83 ksoftirqd/0 8 root 20 0 0 0 0 I 0.3 0.0 1:21.03 rcu_sched 2 root 20 0 0 0 0 S 0.0 0.0 0:00.05 kthreadd root@pione:/media/data/log# systemctl reboot Failed to set wall message, ignoring: Connection timed out Failed to reboot system via logind: Connection timed out Failed to start reboot.target: Connection timed out See system logs and 'systemctl status reboot.target' for details. root@pione:/media/data/log# root@pione:/media/data/log# systemctl status reboot.target Failed to get properties: Connection timed out root@pione:/media/data/log# root@pione:/media/data/log# reboot root@pione:/media/data/log# root@pione:/media/data/log# reboot -f Failed to read reboot parameter file: No such file or directory Rebooting. [141846.733884] reboot: Restarting system ▒▒▒▒▒▒ U-Boot SPL 2018.05-armbian (Aug 19 2018 - 17:07:52 +0200) DRAM: 512 MiB Trying to boot from MMC1 System log: