bananapinas

Members
  • Content Count

    9
  • Joined

  • Last visited

  1. With linux-image-next-sunxi, linux-dtb-next-sunxi and linux-u-boot-bananapipro-next = 5.31: up time 39 days
  2. After over 20 days uptime without a freeze I got 2 freezes within 24hours. I never rolled back though, running > 20 days with linux-image-next-sunxi: 5.41 linux-dtb-next-sunxi: 5.41 linux-u-boot-bananapipro-next: 5.41 Rolled these 3 now back to 5.31 - let's see... should I downgrade the linux-headers also?
  3. Great, thanks. apt-cache policy shows version 5.35 and 5.31 for uboot and image. image 5.32 has no matching uboot. So I'll try 5.35 first and if it occurs again I'll try 5.31. But so far your help is really appreciated. I really like the armbian project and will use it on my raspberries and banana pi (without pro) soon also. Donation on the way
  4. Hi Igor, thanks for the reply. Does "was found in the latest update" means "it's a known issue, problem found" or "it could be the latest kernel update"? Sorry as obviously i'm not a native speaker.. And - never did this - how do i roll back a kernel? After that I'll freeze for some weeks.. TIA!
  5. I additionaly observed now with armbianmonitor -m that the cpu frequency seems to be fixed at 960mhz with just one lower value 528mhz, even if there is no heavy load (load = 0.15-0.3, %cpu avg. <10%, cpu temp ~33-34°C). So it looks like cpufrequtils are working, but why is the frequency that high..?
  6. Maybe I'll have a look at it, but I'm not sure if this would help at all. If it's an hardware issue (board, sd card, hdd, powering) this wouldn't change anything - also I don't believe it is, as it worked before, and I'll after the next freeze change hdd and sd card back to the "bananian system originals". And if it's an os issue it would stay there with armbian, sooner or later also OMV will use the 5.38 kernel I think (?). But before trying something completely else like OMV I'd like to try to get this freezing issue fixed... just need to know how to find out.. would a serial console UART log help here?
  7. yes I tried it once before setting up my own solution about a year ago. I did not really like it then It seemed slow and overloaded, and I prefer(ed) nextcloud over owncload. But both the old bananian and new armbian systems were/are working really fine, everything is ok - apart from the freezes...
  8. I think I got the same or similar issue with a banana pi pro. I used the board about a year with the latest bananian os without an issue, rock solid, uptimes up to 1 month (then planed shutdown for backup image of the sd card). 2.5" hdd attached through the SATA port. Now I migrated to the latest 5.38 debian with mainline kernel . Output of armbian-monitor -u here: http://ix.io/Fpe Sporadic "freezes" - after just one hour runtime or (max for now) 14h. Symptoms: - no hdmi output after turning on monitor. - the green onboard led was used for "cpu" as trigger - led is just on so I assume 100% CPU usage. - the blue onboard led was used for "mmc0" - zero activity then - green led of eth0 blinks periodic - yellow led of eth0 blinks sporadic - ssh no connect possible After repowering and startup CPU shows high temperature after login (nearly 50°C). System is used as nextcloud and samba server. Installed packages mainly are nginx, mariadb, php7/fpm, samba, default-jdk-headless, proftpd-basic, nfs-kernel-server Every time while freezing there was no special user activity, at night or early in the morning. At max one nextcloud windows client syncing, all other clients (user / hardware :)) sleeping or not at home. So far I tried: 1) Monitoring CPU load / processes with top every minute and write to a file on the sdcard. Last full output @08:13:16 (yesterday) top - 08:13:16 up 1:09, 2 users, load average: 0,09, 0,14, 0,13 Tasks: 128 total, 1 running, 88 sleeping, 0 stopped, 0 zombie %Cpu(s): 2,2 us, 6,1 sy, 0,1 ni, 91,3 id, 0,3 wa, 0,0 hi, 0,0 si, 0,0 st KiB Mem : 1022524 total, 587192 free, 162788 used, 272544 buff/cache KiB Swap: 131068 total, 131068 free, 0 used. 800756 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4499 root 20 0 8664 3092 2680 R 16,7 0,3 0:00.08 top 1 root 20 0 25928 5484 3808 S 0,0 0,5 0:08.51 systemd 2 root 20 0 0 0 0 S 0,0 0,0 0:00.01 kthreadd 4 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/0:+ 6 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 mm_percpu_+ 7 root 20 0 0 0 0 S 0,0 0,0 0:00.16 ksoftirqd/0 ..... Next output 1 min later was interrupted while writing (?) top - 08:14:17 up 1:10, 2 users, load average: 0,08, 0,12, 0,13 Tasks: 128 total, 1 running, 88 sleeping, 0 stopped, 0 zombie %Cpu(s): 2,2 us, 6,1 sy, 0,1 ni, 91,4 id, 0,3 wa, 0,0 hi, 0,0 si, 0,0 st KiB Mem : 1022524 total, 587148 free, 162820 used, 272556 buff/cache KiB Swap: 131068 total, 131068 free, 0 used. 800732 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4528 root 20 0 8664 3116 2704 R 20,0 0,3 0:00.07 top 4481 root 20 0 0 0 0 I 5,0 0,0 0:02.14 kworker/1:0 1 root 20 0 25928 5484 3808 S 0,0 0,5 0:08.52 systemd 2 root 20 0 0 0 0 S 0,0 0,0 0:00.01 kthreadd 4 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/0:+ 6 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 mm_percpu_+ 7 root 20 0 0 0 0 S 0,0 0,0 0:00.16 ksoftirqd/0 8 root 20 0 0 0 0 I 0,0 0,0 0:00.69 rcu_sched 9 root 20 0 0 0 0 I 0,0 0,0 0:00.00 rcu_bh 10 root rt 0 0 0 0 S 0,0 0,0 0:00.03 migration/0 11 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/0 12 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/1 13 root rt 0 0 0 0 S 0,0 0,0 0:00.03 migration/1 14 root 20 0 0 0 0 S 0,0 0,0 0:00.46 ksoftirqd/1 16 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/1:+ 17 root 20 0 0 0 0 S 0,0 0,0 0:00.02 kdevtmpfs 18 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 netns 21 root 20 0 0 0 0 S 0,0 0,0 0:00.00 oom_reaper 22 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 writeback 23 root 20 0 0 0 0 S 0,0 0,0 0:00.00 kcompactd0 24 root 25 5 0 0 0 S 0,0 0, <-- here it ends 2) Using as accesspoint: I used the new armbian system as an access point (wlan0->eth0 bridge) with br0 in /etc/network/interfaces and hostapd. I disabled this again - it was the only difference in usage between bananian and armbian. Did not help 3) Power: powering while using with bananian was done through the micro usb port, and the hdd was attached to the onboard power jack - worked without an issue. I thought about improving this while migrating to armbian and changed to another power supply and powering the hdd directly from this and powering the board through the now unsed jack (which previously powered the hdd). I changed this back to the old power supply and wiring scheme - result unknown, waiting to see if it happens again. Note: other changes from bananian to armbian were: - using another SD card - but same model (transcend ultimate 600x 8GB, as recommended here https://docs.armbian.com/User-Guide_Getting-Started/). The card used for armbian was brand new. Maybe dd the armbian system to the previously used bananian sd card? - 2.5" hdd upgraded from seagate 250GB to western digital 1TB - could this worth the change back? Any ideas what to check / look for? Any help very appreciated. I'm not an expert in linux but got some basic skills and aim to learn