Bug #1943
closed
RPi CPU %100 latest Gotham test builds
Added by Fake Name over 11 years ago.
Updated about 11 years ago.
Found in version:
3.4.27~gfbda802
Description
The latest Gotham builds for the RPi (since http://forum.xbmc.org/showthread.php?tid...pid1584139) have had a problem whereby the RPi's CPU usage is stuck at %100 after booting. This happens on about 2/3 boots. I have determined that this is an issue with TVheadend because if I disable the service (via XBMC->Settings->addons->services) the CPU usage returns to normal (%19). This appears to only be a problem when TVheadend starts at boot because if I re-enable the service, the CPU remains at its normal low setting (%19).
I've looked over the 'Bug Reporting' page at this site but all the necessary steps for 'creating a ticket' (such as creating a mux dump and getting a debugging log) presume that the reader has an understanding of unix commands... I do not. If anyone can help by telling me exactly what I need to do to get the logs, I'm happy to pass them on.
- Status changed from New to Need feedback
Can you confirm that the CPU usage is 100% for the tvheadend process? Because reading the threads no-one seems to have actually specified this, I'd suspect (based on prior experience) that the problem is actually in XBMC. Especially since the only variable in the equation is XBMC! Though I won't jump to conclusions just yet.
Adam
Hi Addam. I just googled how to look at the processes running on the Pi and, having learned the 'top' command, I've discovered that even when XBMC is reporting 100 cpu it is actually only using ~%38. Tvheadend uses between %1 and %6 at idle. So you're probably right that this is an XBMC issue.
I do think it's strange that when I disable the TVheadend service (via XBMC settings) the cpu reported in XBMC drops to normal and XBMC seems to become more responsive.
- Status changed from Need feedback to Rejected
XBMC bug as suspected. Not at all surprised XBMC+PVR (specifically TVH) has never worked on the pi. It's not strange at all, you're disabling a bit of code in XBMC when you disable TVH. If that code is broken (highly probable) then the issue would go away when its not active.
Adam
What I meant was that disabling the service and then re-enabling it would fix the issue. I thought this strange. The Tvheadend code seems to run fine within the new builds of XBMC but only if it is restarted after boot.
Well that information looks like it might be useful to the person that maintains that piece of code in XBMC. But ultimately that's where the fault lies, until someone can demonstrate otherwise.
Adam
Also available in: Atom
PDF
Updated by 
Updated by