OpenELEC Testbuilds for RaspberryPi Part 3 (Kodi 14.0) - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: Raspberry Pi (https://forum.kodi.tv/forumdisplay.php?fid=166) +---- Thread: OpenELEC Testbuilds for RaspberryPi Part 3 (Kodi 14.0) (/showthread.php?tid=192380) Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
|
RE: OpenELEC Testbuilds for RaspberryPi Part 3 - RaVeNV1 - 2014-05-18 "Failed to stop xbmc-service.service: Unit xbmc-service.service not loaded." is the response i get, when i try to execute "systemctl stop xbmc-service". But without the "-service" prefix it works. So, i did the steps you mentioned, and the load is the same. Roundabout 70% right now, 5 minutes after bootup. Edit: this is the freshest log i have, maybe its useful: http://xbmclogs.com/show.php?id=204351 RE: OpenELEC Testbuilds for RaspberryPi Part 3 - Milhouse - 2014-05-18 (2014-05-18, 13:22)ken_s Wrote: Seeing the same as RaVeNV1, cpu 70-80% with no activity. You're measuring this with top (or maybe bcmstat.sh)? Because right now, with stock Confluence, I'm seeing under 20% (actually, with rbphdmi having switched off the HDMI, I'm currently seeing a total load of 14-15%). (2014-05-18, 13:23)RaVeNV1 Wrote: But without the "-service" prefix it works. Sorry duff instructions, wrote it from memory - yes, remove the -service - have updated the original post. RE: OpenELEC Testbuilds for RaspberryPi Part 3 - RaVeNV1 - 2014-05-18 top says: 390 1 root R 306m 82.0 0 73.5 /usr/lib/xbmc/xbmc.bin --standalone -fs --lircdev /run/lirc/lircd CPU load over 70%, but it switches between 60% and 80%, as i mentioned. RE: OpenELEC Testbuilds for RaspberryPi Part 3 - Milhouse - 2014-05-18 Can you paste the output from "pstree $(pidof xbmc.bin)" - it won't help much, but it's difficult to "see" what xbmc is doing unless it outputs something... pstree should show the threads belonging to the xbmc.bin process. RE: OpenELEC Testbuilds for RaspberryPi Part 3 - RaVeNV1 - 2014-05-18 OpenELEC:~ # pstree $(pidof xbmc.bin) xbmc.bin-+-2*[{AESink}] |-{ActiveAE} |-{AirPlayServer} |-4*[{CECAdapter}] |-{CRBPWorker} |-{EventServer} |-{HCEC Notify} |-{HDispmanx Notif} |-{HTV Notify} |-{ILCS_HOST} |-{JobWorker} |-4*[{LanguageInvoker}] |-{PeripBusCEC} |-{PeripBusUSBUdev} |-{TCPServer} |-{VCHIQ completio} |-2*[{libmicrohttpd}] `-2*[{xbmc.bin}] RE: OpenELEC Testbuilds for RaspberryPi Part 3 - Milhouse - 2014-05-18 The only obvious difference between your threads and my threads is you have "4*[{CECAdapter}]" threads - I've disabled CEC in XBMC as my monitor has no CEC support. What happens if you turn off/disable CEC - any change? Edit: I've enabled the CEC adapter on my Pi and after restarting XBMC I also have the "4*[{CECAdapter}]" threads but after a few minutes load is hovering around 20% so that's not likely to be the reason unless libcec is going bananas on your system for some reason. RE: OpenELEC Testbuilds for RaspberryPi Part 3 - RaVeNV1 - 2014-05-18 It remains the same. xbmc.bin-+-2*[{AESink}] |-{ActiveAE} |-{AirPlayServer} |-{CRBPWorker} |-{EventServer} |-{HCEC Notify} |-{HDispmanx Notif} |-{HTV Notify} |-{ILCS_HOST} |-{JobWorker} |-4*[{LanguageInvoker}] |-{PeripBusCEC} |-{PeripBusUSBUdev} |-{TCPServer} |-{VCHIQ completio} |-2*[{libmicrohttpd}] `-2*[{xbmc.bin}] Edit: Suddenly, there's no disk image of your build, i would try it with a clean and fresh install of your build. I installed OE 4.0.1 first via disk image, and then updated to your build via OpenELEC Dev Update. Maybe there was a failure, i dont know, i'm not familiar with this. RE: OpenELEC Testbuilds for RaspberryPi Part 3 - popcornmix - 2014-05-18 Code: top -H RE: OpenELEC Testbuilds for RaspberryPi Part 3 - Milhouse - 2014-05-18 (2014-05-18, 14:34)popcornmix Wrote: Sadly, not on OpenELEC... (maybe I can build "real" top somehow...) RE: OpenELEC Testbuilds for RaspberryPi Part 3 - RaVeNV1 - 2014-05-18 OpenELEC:~ # top -H top: invalid option -- 'H' BusyBox v1.22.1 (2014-05-16 19:17:29 BST) multi-call binary. Usage: top [-b] [-nCOUNT] [-dSECONDS] [-m] Provide a view of process activity in real time. Read the status of all processes from /proc each SECONDS and display a screenful of them. Keys: N/M/P/T: show CPU usage, sort by pid/mem/cpu/time S: show memory R: reverse sort H: toggle threads, 1: toggle SMP Q,^C: exit Options: -b Batch mode -n N Exit after N iterations -d N Delay between updates -m Same as 's' key Code: tc/eventlircd.d --socket=/run/lirc/lircd --release=_UP RE: OpenELEC Testbuilds for RaspberryPi Part 3 - Milhouse - 2014-05-18 OK, this is just a hack but should work... I've grabbed top from Raspbian: Code: cd /storage Now "/storage/fulltop/fulltop.sh -H" should work on OpenELEC. Fellas, please use [code] tags when posting formatted results... makes reading that bit easier! RE: OpenELEC Testbuilds for RaspberryPi Part 3 - RaVeNV1 - 2014-05-18 Code: OpenELEC:~/fulltop # /storage/fulltop/fulltop.sh -H Thats the output. I must mention, that I formatted the SD, installed OE 4.0.1 and then updated to your build. So no addons, scripts etc. installed anymore. Just your "naked" build. RE: OpenELEC Testbuilds for RaspberryPi Part 3 - Milhouse - 2014-05-18 [code] tags would make that output a lot more readable... just saying (again). RE: OpenELEC Testbuilds for RaspberryPi Part 3 - Martijn - 2014-05-18 and rather use pastebin.com to not dump this on our forum RE: OpenELEC Testbuilds for RaspberryPi Part 3 - Milhouse - 2014-05-18 Try: Code: /storage/fulltop/fulltop.sh -H -p $(pidof xbmc.bin) (2014-05-18, 15:10)Martijn Wrote: and rather use pastebin.com to not dump this on our forumFor a relatively small number of lines I don't see the harm. For longer logs, you're absolutely correct. |