4

I have a Macbook Pro (model 10,1) running OS X 10.9.3 (13D65) with a wireless problem; it keeps dropping connection. That is, it says it's connected, but if you ping a host...even localhost...the packets aren't returned for a period of time, then it comes up, only to lose connection after a few seconds, then it stays down for awhile before cycling back up again. If you turn off the wireless, it can ping localhost just fine. And a wired Ethernet connection works fine.

While troubleshooting I found this line in the logs:

_handleLinkEvent: Got an error trying to queyer WiFi for power. Resetting state variables.

That makes me suspect a hardware issue with the Airport card, but I can't seem to find documentation about that error anywhere. Does anyone know what would cause this or if there's another cause beyond hardware failure?

  • Are you looking for a count of input/output errors? – Bart Silverstrim Jun 18 '14 at 21:42
  • the _handleLinkEvent: Got an error trying to queyer WiFi for power. Resetting state variables. -- is normal message following drop in connection, if you look in the console you can see it. – Ruskes Jun 18 '14 at 21:46
  • en0 1500 <Link#6> c8:e0:eb:16:30:e7 993039 0 427001 0 0 en0 1500 myhost fe80:6::cae0:ebff 993039 - 427001 - - en0 1500 10.110.4/24 10.110.4.115 993039 - 427001 - - – Bart Silverstrim Jun 18 '14 at 21:48
  • Well, that formatting was yucked. Summary: 0 Ierrs, 0 Oerrs. – Bart Silverstrim Jun 18 '14 at 21:49
  • @Buscar웃 so basically that error is just some status detritus, nothing that helps diagnose if it's software, software settings, or hardware problem. – Bart Silverstrim Jun 18 '14 at 21:50
1

Example on my MBA 10.9.3

6/18/14 01:48:14.000 kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep 
6/18/14 01:48:16.000 kernel[0]: AirPort: Link Down on en0. Reason 8 (Disassociated because station leaving).
6/18/14 01:48:16.579 airportd[80]: _handleLinkEvent: WiFi is not powered. Resetting state variables.

So that is a normal message following a drooped connection or closing the lid.

Open your console and report the lines before that message to see who is shutting your airport down.

Run netstat -i to get a overview of all ongoing activity

sample

Name  Mtu   Network       Address            Ipkts Ierrs    Opkts Oerrs  Coll
lo0   16384 <Link#1>                          7925     0     7925     0     0
lo0   16384 localhost   ::1                   7925     -     7925     -     -
lo0   16384 127           localhost           7925     -     7925     -     -
lo0   16384 localhost   fe80:1::1             7925     -     7925     -     -
gif0* 1280  <Link#2>                             0     0        0     0     0
stf0* 1280  <Link#3>                             0     0        0     0     0
en0   1500  <Link#4>    14:10:9f:f0:29:8c   830672     0   665716     0     0
en0   1500  mba-host.lo fe80:4::1610:9fff   830672     -   665716     -     -
en0   1500  10.5.50/24    10.5.50.95        830672     -   665716     -     -
en3   1500  <Link#5>    32:00:1a:e9:a9:a0        0     0        0     0     0
bridg 1500  <Link#6>    16:10:9f:0f:1e:00        0     0        0     0     0
p2p0  2304  <Link#7>    06:10:9f:f0:29:8c        0     0        0     0     0

Run Airport -I to get more information on the current connection.

sample

agrCtlRSSI: -33
     agrExtRSSI: 0
    agrCtlNoise: -86
    agrExtNoise: 0
          state: running
        op mode: station 
     lastTxRate: 130
        maxRate: 144
lastAssocStatus: 0
    802.11 auth: open
      link auth: none
          BSSID: 9c:d3:6d:b3:75:f0
           SSID: Mijas900850808-80_EXT
            MCS: 15
        channel: 8

For debugging and monitoring you can use the build in tool.

Hold the alt key and click on the WiFi icon

at the bottom of the pop up you will find the Open Wireless Diagnostics

In the new window that opens select Utilities in the Window tab.

Run test like Performances to see the signal stability

signal

  • You suggested running Airport -I, but there is no Airport command in the path. Is it part of a specific package that needs to be run with full path? – haridsv Oct 26 '15 at 5:32
0

Resetting the SMC (System Management Controller) eventually solved it for me: https://support.apple.com/en-us/HT201295

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .