Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MBP M1 - Wifi Dropouts?

JDGwf

JDGwf

macrumors member
Original poster
Oct 20, 2016
76
130
Is anyone else experiencing intermittent wifi dropouts under load with the M1 MBP or Air? Not seeing this behavior in any other device on the network
Code: 
Tue Nov 17 16:09:51.382 <airport[430]> ERROR: sharingd (1081) is not entitled for com.apple.wifi.join_history, will not allow request
Tue Nov 17 16:09:51.382 <airport[430]> ERROR: rapportd (727) is not entitled for com.apple.wifi.join_history, will not allow request
Tue Nov 17 16:20:13.241 <kernel> /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/AirPortFamily_kexts/AirPortFamily-1838/IO80211Family/BaseClass/IO80211ScanManager.cpp::scanControl[2182] Error: Scan control command failure
Tue Nov 17 16:20:13.242 <kernel> /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/AirPortFamily_kexts/AirPortFamily-1838/IO80211Family/BaseClass/IO80211ScanManager.cpp::scanControl[2182] Error: Scan control command failure
Tue Nov 17 16:20:13.242 <kernel> /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/AirPortFamily_kexts/AirPortFamily-1838/IO80211Family/BaseClass/IO80211ScanManager.cpp::scanControl[2182] Error: Scan control command failure
Tue Nov 17 16:20:13.242 <kernel> postMessage::1412 APPLE80211_M_BSSID_CHANGED received
Tue Nov 17 16:20:13.242  Tue Nov 17 16:20:13.684 <kernel> AppleBCMWLANCore::getSSIDData(): Get failure: APPLE80211_IOC_SSID: -528342013
Tue Nov 17 16:20:13.709 <airport[430]> _handleLinkEvent: Unable to process link event, op mode request returned 54 (Connection reset by peer)
Tue Nov 17 16:20:15.373 Usb Host Notification en0 driver available, seqNum 47, Total 0
Tue Nov 17 16:20:15.386 Usb Host Notification Error Apple80211Set: Operation not supported seqNum 47 en0
Tue Nov 17 16:20:15.763 Usb Host Notification en0 driver available, seqNum 48, Total 0
Tue Nov 17 16:20:15.764 Usb Host Notification Error Apple80211Set: Operation not supported seqNum 48 en0
Tue Nov 17 16:20:16.194 <kernel> postMessage::1412 APPLE80211_M_BSSID_CHANGED received
Tue Nov 17 16:20:16.194  <kernel> postMessage::1412 APPLE80211_M_BSSID_CHANGED received
Tue Nov 17 16:20:16.194  Tue Nov 17 16:20:16.252 <airport[430]> ERROR: sharingd (1081) is not entitled for com.apple.wifi.join_history, will not allow request
Tue Nov 17 16:20:16.252 <airport[430]> ERROR: rapportd (727) is not entitled for com.apple.wifi.join_history, will not allow request
Tue Nov 17 16:20:16.275 <airport[430]> ERROR: rapportd (727) is not entitled for com.apple.wifi.join_history, will not allow request
Tue Nov 17 16:20:16.275 <airport[430]> ERROR: sharingd (1081) is not entitled for com.apple.wifi.join_history, will not allow request
Tue Nov 17 16:20:16.283 <airport[430]> ERROR: sharingd (1081) is not entitled for com.apple.wifi.join_history, will not allow request
Tue Nov 17 16:20:16.283 <airport[430]> ERROR: rapportd (727) is not entitled for com.apple.wifi.join_history, will not allow request
Tue Nov 17 16:20:16.331 <airport[430]> ERROR: rapportd (727) is not entitled for com.apple.wifi.join_history, will not allow request
Tue Nov 17 16:20:16.331 <airport[430]> ERROR: sharingd (1081) is not entitled for com.apple.wifi.join_history, will not allow request
 
Thank you - no worries. It was under a pretty high network load for app downloading and updates - might be a fluke
 
JDGwf said:
Thank you - no worries. It was under a pretty high network load for app downloading and updates - might be a fluke
Click to expand...
I did download the 3GiB OS11.0.1 today and even that seemed fast. I usually get a true 90+ Mib/s connection but it was fast and the install was quite fast as wwll.

Can't complain really.
 
I think I'm having the same issue on my new MacBook Air, 8-core GPU, 16GB RAM.
Don't know if it's a bug while the OS settles or if it's worth updating to the 11.1 beta.

Kind of sucks that there's an issue like that out of the box.
 
Since two days, I have the same issue with my MacBook Air 2020 (Catalina 10.15.3), using the eduroam WiFi at my university. I already …
  • did a PRAM/NVRAM reset
  • deleted and reconfigured the WiFi configuration
  • deleted and reinstalled the eduroam profile
  • updated macOS to 10.15.7 (it was about time anyways)
I have another MacBook (12 inch, macOS 10.4) which doesn't seem to be affected by this issue.
 
Currently having the problem - tried turning off and on the wifi... no networks (not even my hotspot) are being listed
Error: Scan control command failure seems to be the indicator, but I'm not seeing any other indicators.
 
JDGwf said:
tried turning off and on the wifi... no networks (not even my hotspot) are being listed
Click to expand...
It's the same here: After my Mac loses the WiFi connection, the list on the WiFi menu is empty. If I close the menu and open it again, all the networks are there, and I can log in again.
 
Seems to happen under any CPU load - such as compiling. I'll give Apple support a call tomorrow. It's affecting Bluetooth connectivity too (as expected if it's a radio problem) while I'm listening with my AirPods.
 
  • Like
Reactions: Selfie
After an hour with Apple support - we think we fixed it with a PRAM reset:
Command-Option-P-R on reboot.

None of the typical recovery shortcuts seemed to work (Command-R, etc) - which is scary... and the PRAM reset didn't seem to beep at me either.
 
I've had an issue with using SideCar - will drop out after a period of time - and force me to turn wifi off and then back on. I haven't had any issues today though but I'm not using my iPad at all today as a second screen.
 
After two hours of tech support again... turned out they advised me to return it....
I was expecting better tech support, or at least them wanting to read the logs or something. :(

Now I wonder if I want to repurchase a Mac
 
JDGwf said:
After two hours of tech support again... turned out they advised me to return it....
I was expecting better tech support, or at least them wanting to read the logs or something. :(

Now I wonder if I want to repurchase a Mac
Click to expand...
Shame. I'd want a vanilla system installed to rule out errors during any system update or 3rd party that introduced errors.

Migration assistant in Bug Sur isn't always a nice person either, Intel or m1.

Your mac could be a goldmine for them, to find what went wrong and if it is hardware or software. An advance cross-ship would have been nice.
 
JDGwf said:
Is this happening on Intel Macs too?
Click to expand...
Yes. My situation here:

  • MacBook Air 2020 (Intel i5)
  • Since the day my university replaced the old eduroam access point in my building with a new one, the MacBook gets kicked out of WiFi every 30 minutes.
  • As my uni has installed this new type of new access points in other buildings now, I can confirm that this problem exists with all of them.
  • In buildings where they still have the old access points the connection is perfectly stable.
  • An older 12 inch MacBook is not affected by this problem, so clearly this is some kind of interaction between the new access points and the MacBook Air.
  • The problem occurred under Catalina 10.15.3, persisted under 10.15.7, and is still there in Big Sur 11.0.1.
  • In Catalina, I often (but not always) had to manually reconnect a dropped WiFi connection. In Big Sur, the MacBook automatically reconnects within a second or two. (Still, when in a video conference, the short D/C means that audio and video freeze for a while, which is annoying. Also, if I use a VPN, the VPN gets disconnected during the short D/C).
  • My uni's IT department has worked for days to find the issue, with no success. They now installed a LAN cable (!) in my room, so I have a stable connection for video conferences.
  • The IT guys have also informed me that Cisco's “Optimized Roaming” feature, which forces devices to disconnect under certain circumstances, is deactivated on all access points.
  • The problem occurs in 2.4 and 5 GHz networks and on different channels.
  • The country codes of all access points are correct.
My wifi.log is virtually identical to the OP's:

Code: 
Fri Dec 11 08:40:52.527 <kernel> postMessage::1412 APPLE80211_M_BSSID_CHANGED received
Fri Dec 11 08:40:52.529  Fri Dec 11 08:40:52.630 <kernel> AppleBCMWLANCore::getSSIDData(): Get failure: APPLE80211_IOC_SSID: -528342013
Fri Dec 11 08:40:53.377 <airport[185]> airportdProcessDLILEvent: <en0> event=1, flags=0xFFFF8863, lastPowerPref=on
Fri Dec 11 08:40:53.378 <airport[185]> airportdProcessDLILEvent: en0 marked UP, applying user power preferences (ON).
Fri Dec 11 08:40:53.378 <airport[185]> airportdProcessDLILEvent: <en0> Setting power ON
Fri Dec 11 08:40:53.384 <airport[185]> airportdProcessDLILEvent: <en0> event=1, flags=0xFFFF8863, lastPowerPref=on
Fri Dec 11 08:40:53.384 <airport[185]> airportdProcessDLILEvent: en0 marked UP, applying user power preferences (ON).
Fri Dec 11 08:40:53.384 <airport[185]> airportdProcessDLILEvent: <en0> Setting power ON
Fri Dec 11 08:40:53.814 <kernel> postMessage::1412 APPLE80211_M_BSSID_CHANGED received
Fri Dec 11 08:40:53.815  Fri Dec 11 08:40:53.815 <kernel> postMessage::1412 APPLE80211_M_BSSID_CHANGED received
Fri Dec 11 08:40:53.815  Fri Dec 11 08:40:53.892 <airport[185]> ERROR: sharingd (461) is not entitled for com.apple.wifi.join_history, will not allow request
Fri Dec 11 08:40:53.892 <airport[185]> ERROR: rapportd (384) is not entitled for com.apple.wifi.join_history, will not allow request
Fri Dec 11 08:40:53.928 <airport[185]> ERROR: rapportd (384) is not entitled for com.apple.wifi.join_history, will not allow request
Fri Dec 11 08:40:53.930 <airport[185]> ERROR: sharingd (461) is not entitled for com.apple.wifi.join_history, will not allow request
Fri Dec 11 08:40:53.986 <airport[185]> ERROR: rapportd (384) is not entitled for com.apple.wifi.join_history, will not allow request
Fri Dec 11 08:40:53.986 <airport[185]> ERROR: sharingd (461) is not entitled for com.apple.wifi.join_history, will not allow request
Fri Dec 11 08:40:54.239 <airport[185]> ERROR: rapportd (384) is not entitled for com.apple.wifi.join_history, will not allow request
Fri Dec 11 08:40:54.239 <airport[185]> ERROR: sharingd (461) is not entitled for com.apple.wifi.join_history, will not allow request
Fri Dec 11 08:41:17.181 Apple80211Set:9930 Processing APPLE80211_IOC_ROAM
Fri Dec 11 08:41:17.181 Apple80211Set:9944 Processing APPLE80211_IOC_ROAM dataRef:0x7f9fc2f9af40
Fri Dec 11 08:41:17.181 Apple80211Set:9965 CFType is CFData

Since the MacBook quickly reconnects under Big Sur, it's just a minor annoyance, still I'd prefer this to be fixed.
 
It was back in November and was within 15 days, the replacement has been quite the machine for a stopgap. Waiting on the 16” m1x or m2 then I’ll sell this one
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back