AppleFWAudio CPU usage causes heat increa…
Imported from the Apple Support Forums via the Wayback Machine 🔗
I have found that by plugging in my Apogee Duet firewire audio interface and ONLY WHEN AppleFWAudio was loaded there was a 10c CPU raise that was making my MBP (late 2008) hot! I was considered that it maybe because it is bus powered:
*I wanted to monitor the power that was required for Duet to run and to see if the temperature rise was due to that, so*:
- With Apogee drivers uninstalled (just to be sure its not their drivers related, which is not)
- MBP on battery power with System Profiler opened (to monitor the mA required by the computer from System Profiler -> Power)
- CoolBook opened to monitor the temps
- Terminal opened to load/unload the AppleFWAudio
- GeekBench on desktop to monitor the CPU performance
I did the following tests:
*1st Test*:
Idling machine. Duet is unplugged, AppleFWAudio.kext is not loaded
Results:
Idle CPU temps: ~40c :: Power Consumption: ~ -900mA :: GeekBench Score: ~3550
2nd Test:
Im plugging in Duet. AppleFWAudio gets loaded. Duet outputs audio
Results:
Idle CPU temps: ~
50c :: Power Consumption: ~ -1850mA :: GeekBench Score: ~
3450
3rd Test:
With Duet plugged in. I kextunload AppleFWAudio. Duet cannot longer output. The device is disappeared from System Preferences > Audio
Results:
Idle CPU temps: ~
41c :: Power Consumption: ~ -1300mA :: GeekBench Score: ~*_3550 (like 1st Test)_*
4th Test:
I unplug the Duet. Wait for a minute
Results:
Idle CPU temps: ~41c :: Power Consumption: ~ -900mA :: GeekBench Score: ~3550
5th Test:
I plug the Duet again. The AppleFWAudio is not auto loaded since i unloaded previously. Duet cannot output
Results:
Idle CPU temps: ~42c :: Power Consumption: ~ -1300mA :: GeekBench Score: ~3550
6th Test:
With Duet plugged in, i kextload the ApppleFWAudio again. Duet can output again
Results:
Idle CPU temps: ~
51c :: Power Consumption: ~ -1800mA :: GeekBench Score: ~*_3450 (100 points drop again)_*
So you could say, you can link, power consumption raise equals CPU temp raise. Thats why i have a CPU raise with my FireWire audio interface.
WRONG
*7th Test* (and most interesting):
With Duet plugged in, I unload the ApppleFWAudio again. Duet can not output
Results:
Idle CPU temps: ~41c :: Power Consumption: ~ -1300mA :: GeekBench Score: ~3550
*So i say what if i raise the power consumption, but without the higher consumption caused by the Duet. So i plugin my iPod Touch and it starts charging*
Power Consumption reaches ~ -1850mA
*_BUT, CPU temp remains ~41c_*
_This clear states that the CPU temp raise caused by the AppleFWAudio is not because of bus powered required by the Duet but from the fact that AppleFWAudio clearly uses some CPU when the interface is connected. This is clearly happening because it causes a rapid, constant speedstep switching - a 100 points drop on GeekBench and a CPU Temperature raise of 10c._
_I dont know if i'm paranoid but i think i bought a Firewire audio interface because it is considered for professional use. To my eyes there is nothing professional in rapid speedstep switching (bad BAD for AD/DA clocking) neither in the use of CPU power (even if this is just as little a.k.a. 100 points on geekbench). But most of all, CPU heat bothers me the most. I was working with a USB bus powered interface and my MBP was never getting that hot!_
_*If this is not an AppleFWAudio bug but its just the way it works, id like to have an official word for it*. The fact that there was no such issues under Tiger (google it), tickles me_
You can also watch a video i made that shows the rapid speedstep switch here:
http://www.youtube.com/watch?v=JYHnX3CGUoo
If anyone else with similar problems has the time to do the same tests, it would be nice to have the results.
The commands for the terminal:
sudo kextstat -> Lists the currently loaded kexts
sudo kextunload -b com.apple.driver.AppleFWAudio -> Unloads the AppleFWAudio (dont be bothered about the classes report after unloaded) will disable output
sudo kextload "/System/Library/Extensions/AppleFWAudio.kext" -> Loads the AppleFWAudio and will enable output
4 replies
Sign in or join Beachball Help to reply.
- 0
- 0
- 0
- 0