airportd in activity moniter

Discussion in 'Mac Basics and Help' started by davidwarren, Jul 24, 2008.

  1. davidwarren macrumors 6502a

    Joined:
    Aug 28, 2007
    #1
    what does it do, and why is it 96-99% of cpu activity????
     
  2. Eidorian macrumors Penryn

    Eidorian

    Joined:
    Mar 23, 2005
    Location:
    Indianapolis
    #2
    airport + daemon = airportd

    Are you having any problems with your wireless connection?
     
  3. davidwarren thread starter macrumors 6502a

    Joined:
    Aug 28, 2007
    #3
    no, I restarted my MB, and everything is back to normal, still don't know what the deal was with it being so active. My fans would kick on about 30 sec after lifting the lid.

    I guess it was just one of those things.....


    edit-- yeah, I found that document, but I couldn't find any reports on what would make it use up so much cpu.
    Thanks though.
     
  4. Eidorian macrumors Penryn

    Eidorian

    Joined:
    Mar 23, 2005
    Location:
    Indianapolis
    #4
    I'm glad you did find that document. As much as I hate to say this, things do screw sometimes in OS X and a reboot is the only cure.
     
  5. SSB macrumors newbie

    Joined:
    Aug 22, 2008
    #5
    same thing just happened to me

    Very odd - I'd been outside and logged my MacBook Air onto a reputable wireless service earlier, came home, connected to my home network and left it running. Came back to the machine an hour or so later and it was very, very hot (CPU A is still over 50 deg after reboot), fan running over 6k and airportd was hogging the processor.

    Reboot sorted it out (temp & fan speed dropping now) - and airportd only showed up briefly in activity monitor when I turned airport back on - now it's not on the list.

    One to look out for.
     
  6. merl1n macrumors 65816

    merl1n

    Joined:
    Mar 30, 2008
    Location:
    New Jersey, USA
    #6
    If your curious, you can launch Console and look at the console and system logs at that time the airportd was consuming all of the cpu. It may have had a problem with the airport daemon or something else related to it. Just take a look at the messages in the logs.
     

Share This Page