Related but no direct cause.
The "connect" now loops through all possible addresses and tries to connect them, instead of only trying the first one. The "hog" happened when all connect attempts failed, it left the socket in a "twilight" state (wasn't connecting, but also not closing).
Recent changes causing enigma2 process cpu hog
Started by greatred, 20 May 2015 14:18
enigma2 cpu vuuno
28 replies to this topic
Re: Recent changes causing enigma2 process cpu hog #21
-
- PLi® Core member
- 14,045 posts
+298
Excellent
Posted 23 May 2015 - 08:28
Real musicians never die - they just decompose
Re: Recent changes causing enigma2 process cpu hog #22
-
- PLi® Core member
- 56,262 posts
+691
Excellent
Posted 23 May 2015 - 09:34
Mike, can I re-re commit pieterg's ipv6 stuff ?
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: Recent changes causing enigma2 process cpu hog #23
-
- PLi® Core member
- 14,045 posts
+298
Excellent
Posted 23 May 2015 - 17:19
I already reverted the revert and added the fix.
Real musicians never die - they just decompose
Re: Recent changes causing enigma2 process cpu hog #24
-
- PLi® Core member
- 56,262 posts
+691
Excellent
Posted 23 May 2015 - 17:34
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: Recent changes causing enigma2 process cpu hog #25
-
- Senior Member
- 268 posts
+2
Neutral
Posted 25 May 2015 - 20:32
Many thanks for resolving that issue !
Re: Recent changes causing enigma2 process cpu hog #26
-
- Senior Member
- 65 posts
+2
Neutral
Posted 30 May 2015 - 21:20
Well, on vu+ zero enigma's process has a low CPU usage, but the system still big load 
OpenPLI 4.0 build date (e2 version) & load average:
2015-03-16 0.09, 0.08, 0.06, 0.20, 0.16, 0.14 2015-03-20 0.07, 0.05, 0.05 2015-04-04 0.09, 0.07, 0.17 2015-05-11 0.05, 0.11, 0.13 2015-05-20 1.11, 1.05, 1.01 <-- heavy load 2015-05-28 1.07, 1.05, 1.04 <-- still heavy load What is still broken?
Edited by pepinoogorino, 30 May 2015 - 21:20.
Re: Recent changes causing enigma2 process cpu hog #27
-
- Senior Member
- 65 posts
+2
Neutral
Posted 31 May 2015 - 10:00
Update:
Probably oscam have some issue, because on mgcamd load return to low values...
Re: Recent changes causing enigma2 process cpu hog #28
-
- Senior Member
- 284 posts
+11
Neutral
Posted 31 May 2015 - 23:51
U can find what take alot of power with command top
on my box:
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2015.06.01 00:37:47 =~=~=~=~=~=~=~=~=~=~=~=
Using username "root".
Authenticating with public key "rsa-key-20140206"
root@vuduo2:~# top[J
[H[JMem: 146604K used, 1262124K free, 0K shrd, 7992K buff, 30320K cached
CPU: 35% usr 5% sys 5% nic 55% idle 0% io 0% irq 0% sirq
Load average: 0.15 0.14 0.12 3/114 3478
[7m PID PPID USER STAT VSZ %VSZ %CPU COMMAND[0m
512 500 root S 263m 19% 41% /usr/bin/enigma2
3478 3477 root R 2868 0% 5% top
536 1 root S 77008 5% 0% /usr/local/hbb-browser/lib/hbbtv.app restart
495 1 root S 23036 2% 0% /usr/bin/CCcam
3457 414 root S 7468 1% 0% smbd -D
414 1 root S 6920 0% 0% smbd -D
431 414 root S 6920 0% 0% smbd -D
533 1 root S 4860 0% 0% /usr/bin/streamproxy
412 1 root S 3964 0% 0% nmbd -D
490 1 avahi S 3608 0% 0% avahi-daemon: running [vuduo2.local]
491 490 avahi S 3608 0% 0% avahi-daemon: chroot helper
3477 3476 root S 3188 0% 0% -sh
473 1 root S 2984 0% 0% /usr/sbin/inetd
453 1 messageb S 2980 0% 0% /usr/bin/dbus-daemon --system
3476 460 root S 2956 0% 0% /usr/sbin/dropbear -r /etc/dropbear/dropbear_rsa_host_key -p 22
483 1 root S 2868 0% 0% /sbin/klogd -n
480 1 root S 2868 0% 0% /sbin/syslogd -n -O /var/log/messages
437 1 root S 2868 0% 0% udhcpc -b -H vuduo2 -p /var/run/udhcpc.eth0.pid -i eth0
500 1 root S 2868 0% 0% {enigma2.sh} /bin/sh /usr/bin/enigma2.sh
460 1 root S 2700 0% 0% /usr/sbin/dropbear -r /etc/dropbear/dropbear_rsa_host_key -p 22
464 1 rpc S 2688 0% 0% /usr/sbin/rpcbind
469 1 rpcuser S 2280 0% 0% /usr/sbin/rpc.statd
1 0 root S 1940 0% 0% init [3]
203 2 root SW 0 0% 0% [lcd2]
148 2 root SW 0 0% 0% [nx_sched_high_s]
9 2 root SW 0 0% 0% [migration/0]
3 2 root SW 0 0% 0% [ksoftirqd/0]
10 2 root SW 0 0% 0% [migration/1]
150 2 root SW 0 0% 0% [dpcr_integrator]
11 2 root SW 0 0% 0% [ksoftirqd/1]
7 2 root SW 0 0% 0% [rcu_sched]
45 2 root SW 0 0% 0% [kworker/u4:1]
1242 2 root SW 0 0% 0% [kdvb-ad-0-fe-0]
1154 2 root SW 0 0% 0% [kworker/1:1]
152 2 root SW 0 0% 0% [nx_sched_low]
22 2 root SW 0 0% 0% [kworker/0:1]
216 2 root SW 0 0% 0% [ca08]
147 2 root SW 0 0% 0% [nx_sched]
25 2 root SW 0 0% 0% [kswapd0]
217 2 root SW 0 0% 0% [ci_kthread]
83 2 root SW< 0 0% 0% [kworker/1:1H]
93 2 root SW< 0 0% 0% [kworker/0:1H]
100 2 root SW 0 0% 0% [jbd2/sda1-8]
6 2 root SW 0 0% 0% [kworker/u4:0]
44 2 root SW 0 0% 0% [scsi_eh_1]
root@vuduo2:~# [6nexit
Re: Recent changes causing enigma2 process cpu hog #29
-
- Senior Member
- 65 posts
+2
Neutral
Posted 1 June 2015 - 13:28
It's not oscam
root@vuzero:~# uptime
01:06:35 up 6 min, load average: 1.00, 0.80, 0.39
First runing of image OpenPLi-4.0-beta-vuzero-20150601, nothing else installed.
This is output from top:
Mem: 88428K used, 227148K free, 0K shrd, 0K buff, 38244K cached
CPU: 0% usr 0% sys 0% nic 99% idle 0% io 0% irq 0% sirq
Load average: 1.00 0.85 0.44 2/64 609
PID PPID USER STAT VSZ %VSZ %CPU COMMAND
609 600 root R 3188 1% 0% top
585 581 root S 70516 22% 0% /usr/bin/enigma2
599 549 root S 3192 1% 0% telnetd
24 2 root SW 0 0% 0% [kworker/1:1]
488 1 root S 6920 2% 0% smbd -D
498 488 root S 6920 2% 0% smbd -D
486 1 root S 3964 1% 0% nmbd -D
564 1 avahi S 3608 1% 0% avahi-daemon: running [vuzero.local]
565 564 avahi S 3608 1% 0% avahi-daemon: chroot helper
549 1 root S 3240 1% 0% /usr/sbin/inetd
600 599 root S 3188 1% 0% -sh
528 1 messageb S 2980 1% 0% /usr/bin/dbus-daemon --system
554 1 root S 2868 1% 0% /sbin/syslogd -n -O /var/log/messages
556 1 root S 2864 1% 0% /sbin/klogd -n
581 1 root S 2864 1% 0% {enigma2.sh} /bin/sh /usr/bin/enigma2.sh
512 1 root S 2864 1% 0% udhcpc -b -H vuzero -p /var/run/udhcpc.eth0.pid -i eth0
536 1 root S 2700 1% 0% /usr/sbin/dropbear -r /etc/dropbear/dropbear_rsa_host_key -p 22
540 1 rpc S 2688 1% 0% /usr/sbin/rpcbind
545 1 rpcuser S 2280 1% 0% /usr/sbin/rpc.statd
1 0 root S 1940 1% 0% init [3]
3 2 root SW 0 0% 0% [ksoftirqd/0]
10 2 root SW 0 0% 0% [migration/1]
132 2 root DW 0 0% 0% [cip]
11 2 root SW 0 0% 0% [ksoftirqd/1]
9 2 root SW 0 0% 0% [migration/0]
52 2 root SW 0 0% 0% [ubi_bgt0d]
7 2 root SW 0 0% 0% [rcu_sched]
22 2 root SW 0 0% 0% [kworker/0:1]
90 2 root SW 0 0% 0% [nx_sched]
2 0 root SW 0 0% 0% [kthreadd]
15 2 root SW 0 0% 0% [kdevtmpfs]
45 2 root SW 0 0% 0% [kworker/u4:1]
55 2 root SW 0 0% 0% [ubifs_bgt0_0]
137 2 root SW 0 0% 0% [ci_kthread]
5 2 root SW< 0 0% 0% [kworker/0:0H]
6 2 root SW 0 0% 0% [kworker/u4:0]
8 2 root SW 0 0% 0% [rcu_bh]
12 2 root SW 0 0% 0% [kworker/1:0]
13 2 root SW< 0 0% 0% [kworker/1:0H]
14 2 root SW< 0 0% 0% [khelper]
16 2 root SW< 0 0% 0% [writeback]
17 2 root SW< 0 0% 0% [bioset]
18 2 root SW< 0 0% 0% [kblockd]
19 2 root SW< 0 0% 0% [ata_sff]
20 2 root SW 0 0% 0% [khubd]
21 2 root SW< 0 0% 0% [cfg80211]
23 2 root SW< 0 0% 0% [rpciod]
25 2 root SW 0 0% 0% [kswapd0]
26 2 root SW 0 0% 0% [fsnotify_mark]
27 2 root SW< 0 0% 0% [nfsiod]
28 2 root SW< 0 0% 0% [cifsiod]
29 2 root SW< 0 0% 0% [crypto]
43 2 root SW 0 0% 0% [scsi_eh_0]
44 2 root SW 0 0% 0% [scsi_eh_1]
51 2 root SW< 0 0% 0% [deferwq]
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
