2013-03-05, 00:54
Ok, this is a very strange problem I'm having lately, and I can find 0 help on the forums or Google. Hopefully someone has some insight as to what is going on. First, some quick system info:
AMD Phenom II x2
ATI Radeon HD 5770 using Catalyst drivers
Linux Mint 14 (Nadia)
XMBC Frodo
Now on to the crux of the matter... I tend to put my system to sleep every night using 'sudo pm-suspend'. When the system is resumed and XBMC is started, there is a constant fluctuation in CPU usage and corresponding fan speed cycles. The CPU and fan fluctuations only occur when XBMC is running, and the process using the CPU has been confirmed to be xbmc.bin. The issue doesn't seem to occur if the system is rebooted, only after it has been resumed from suspend. Has anyone else experienced anything like this, or am I just special? For the record, I have used at least 6 different Catalyst driver versions, and am currently running the bleeding edge version from the makson96 repository, but haven't noticed any difference. I bring this up, because the FOSS ATI drivers don't seem to have the same problem, but other apps needed the Catalyst drivers, so I stuck with those.
AMD Phenom II x2
ATI Radeon HD 5770 using Catalyst drivers
Linux Mint 14 (Nadia)
XMBC Frodo
Now on to the crux of the matter... I tend to put my system to sleep every night using 'sudo pm-suspend'. When the system is resumed and XBMC is started, there is a constant fluctuation in CPU usage and corresponding fan speed cycles. The CPU and fan fluctuations only occur when XBMC is running, and the process using the CPU has been confirmed to be xbmc.bin. The issue doesn't seem to occur if the system is rebooted, only after it has been resumed from suspend. Has anyone else experienced anything like this, or am I just special? For the record, I have used at least 6 different Catalyst driver versions, and am currently running the bleeding edge version from the makson96 repository, but haven't noticed any difference. I bring this up, because the FOSS ATI drivers don't seem to have the same problem, but other apps needed the Catalyst drivers, so I stuck with those.