Jump to content

jogger

Members
  • Posts

    18
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I was experiencing slow writes to internal SD card and hard drives connected to an USB 2.0 hub on multiple Odroid HC1. IOWAIT was 99.99% most of the time during large file copies. I found that Armbian was simply waiting too long to write data to disk. Kernel parameters are optimized for writing small amounts of data to SD card when running from that in order to reduce wear. If you have the same problem, you might get factor 10-100 faster writes using the following sysctl settings: vm.dirty_writeback_centisecs=50 vm.dirty_expire_centisecs=50 No need to act, if iotop shows low IOWAIT values on your system.
  2. After upgrading to 5.14.2 I found that 1.5Ghz was missing for the LITTLE cores, what had previously been available with the optimized board settings. dmesg output: [ 0.982387] exynos-chipid 10000000.chipid: cpu0 opp0, freq: 1500 missing [ 0.982499] exynos-chipid 10000000.chipid: cpu4 opp0, freq: 2100 missing I decompiled the DTB file and found no 1.5Ghz section within in the opp-table1.
  3. 5.4 proved unusable as it also frequently dropped connections on an external SMC 75xx USB GB Ethernet adapter. Finally upgraded to edge kernel. Problem is gone.
  4. This is not related to SD-Card, but easiest to reproduce. Even a kernel upgrade might hang, when writing files to the card. Another example using USB HDD storage. During a local file copy, a client enumerated files using netatalk. First got slow, then hung the following processes: root 2214 0.0 0.0 0 0 ? D Aug16 0:01 [jbd2/sdb2-8] e 23991 1.6 0.3 71168 6900 ? D 10:09 0:47 /usr/sbin/afpd -d -F /e root 26980 0.6 0.0 0 0 ? D 10:28 0:10 [kworker/u16:0+flush-8:
  5. Upgraded to kernel 5.4 which made problems worse. Issue can always be reproduced by moving large amounts of data to SD-Card, which I use for archival only. Several processes get stuck: root 239 0.0 0.0 0 0 ? D< Aug09 0:07 [kworker/1:1H+kblockd] root 526 0.0 0.0 0 0 ? D Aug09 0:00 [jbd2/mmcblk1p1-] root 6628 0.0 0.0 0 0 ? D 15:09 0:05 [kworker/u16:2+flush-179:0] root 15287 0.0 0.1 32100 2612 ? Ds 16:09 0:00 (ionclean)
  6. Disabled all ZRAM / ZSWAP / logging. Rebootet and error reoccured after 2 weeks during heavy disk activity from JDownloader and ktorrent. Found I could get back to normal disk speeds by quitting Firefox (running the Webmin GUI). So maybe an issue with the overlay filesystem.
  7. http://ix.io/3plO generating this while copying files over Ethernet (Netatalk) to internal SATA with displayed write speed of only 500 kBps.
  8. Always running latest Armbian Buster: Since some months multiple machines with totally different application sets get slow writing to ANY mounted volume after one or more weeks of uptime (the busier the earlier). According to top IOWAIT exceeds user/kernel cpu usage. All applications and networking incl. disk reads run without any problem, until they write to the disk which makes them crawl. Even cp on a small file hangs. Any hint?
  9. Finally solved this issue. The first thermal zone tripping point is at 70C with a hysteresis of 10. One would expect to kick a throttle in at 70C and lift the throttle at 60C. However throttling occurs at 60C. So I adapted a script found elsewhere and raised the first two tripping points. echo 'setting cpu temperature limits ...' i=0 while [ $i -lt 4 ]; do sudo bash -c "echo \"85000\">/sys/devices/virtual/thermal/thermal_zone""$i""/trip_point_0_temp" sudo bash -c "echo \"95000\">/sys/devices/virtual/thermal/thermal_zone""$i""/trip_point_1_temp" i=$[$i+1] done
  10. With regard to CPU speed: problem is still there, others have discussed this as well and point to the device tree in the 4.19 kernel https://forum.openmediavault.org/index.php/Thread/25692-Problem-with-CPU-under-clocking-in-Odroid-HC1/
  11. Thanks for excellent support, the install made the systems nearly identical. Then I already had linux-u-boot-odroidxu4-next/buster,now 5.90 armhf installed, so everything looks fine. Autumn is coming, so it may take some time for the temp throttle to show up again, if it still exists.
  12. Getting nearer. Seems it is the current hc1.dtb that throttles down from about 60 degrees. Earlier releases or no dtb allowed 80, correct? Possible to configure?
  13. upgraded stretch to buster http://ix.io/1Tsv upgraded jessie to stretch to buster http://ix.io/1TrT There was an execution error at line 813
  14. Updated several HC1 to Buster. Reapplied the optimized board config, as done under stretch before. Main issue: No matter what CPU governor I set, max. frequency jumps around automagically between 1.8 GHz and 2.0 GHz. I can set performance governor to the range from 1.9 to 2.0 GHz, armbian-config confirms, and when I back out of the menu it says "soc runs between 1800 and 1800 MHz using performance governor". Even at > 90% CPU boards stay below 2.0 GHz. Minor glitches only for boards, I already upgraded from jessie to stretch: - boot.ini misses the hc1.dtb check - must manually edit - systemd misses armbian* entries, as well as the utilities referenced in /usr/lib/
  15. After upgrading to buster (great!!) and installing desktop on my HC1, the standard procedure of starting a VNC server and using Real VNC viewer from a Mac ran into errors. I tried the following alternative solutions to get to the desktop - xrdp and Microsoft Remote Desktop (Mac) - tigervnc-scraping-server and Real VNC Viewer (Mac) --> No support for clipboard transfer, keyboard support awful and incomplete (missing # and | and so on) x11vnc with Real VNC Viewer (Mac) solved both issues, except keyboard autorepeat. So I strongly suggest adding x11vnc prominently as an alternative to xrdp.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines