Posts

Post marked as solved
4 Replies
0 Views
This is neither a user, nor a developer issue. This is a kernel issue. I am working on this one, and I would like to understand it. Back to the initial question, where is documented the error code -3905? I got it repeatedly in an environment of work after about 6 days of full load of the Wi-Fi network with 4 clients moving. Here is the typical track I get once the network is unusable for everyone end Wi-Fi Logging turned to on on one of the client Mac. Notably, iPhones and another Mac cannot reach anymore the network once this error appear. Sun May 22 10:45:37.994 Driver Event: <airportd[246]> _bsd_80211_event_callback: APPLE80211_M_ROAM_START (en0) Sun May 22 10:45:37.994 Info: <airportd[246]> Roaming started on interface en0 Sun May 22 10:45:37.994 Info: <airportd[246]> PRIORITY LOCK ADDED [client=airportd, type=4, interface=en0, priority=5] Sun May 22 10:45:37.995 Info: <airportd[246]> SUSPEND AWDL for interface en0, timeout=10.0s, reason=Roam, token=166 Sun May 22 10:45:37.995 Info: <airportd[246]> RESUME AWDL for interface en0, reason=Roam token=165 Sun May 22 10:45:37.995 Roam: <airportd[246]> Unschedule roam RSN handshake timeout, received ROAM_START Sun May 22 10:45:41.106 Info: <airportd[246]> PRIORITY LOCK REMOVED [client=airportd, type=4, interface=en0, priority=7] Sun May 22 10:45:41.106 Info: <airportd[246]> RESUME AWDL AFTER TIMEOUT for interface en0, timeout=10.0s, reason=Assoc token=163 Sun May 22 10:45:42.056 Info: <airportd[246]> RESUME AWDL AFTER TIMEOUT for interface en0, timeout=10.0s, reason=Assoc token=164 Sun May 22 10:45:42.513 Driver Event: <airportd[246]> _bsd_80211_event_callback: SCAN_CACHE_UPDATED (en0) Sun May 22 10:45:42.539 <kernel> en0: Terminating supplicant. Sun May 22 10:45:42.539 <kernel> RSNSupplicant: Releasing authenticator for 00:00:00:00:00:00 Sun May 22 10:45:42.540 Assoc: <airportd[246]> <en0> Auto-join association timed out on network ••••• ••• , returned error code -3905 ***** Sun May 22 10:45:42.540 Info: <airportd[246]> Failed to associate to Wi-Fi network ••••• ••• on interface en0, returned error code -3905 *****
Post not yet marked as solved
1 Replies
0 Views
[empty answer to replace the missing function: delete answer.]
Post not yet marked as solved
2 Replies
0 Views
I advise you to run Disk Utility in recovery mode. Thus there will be one uniq process running on your disk. It is safer and faster.
Post not yet marked as solved
2 Replies
0 Views
Why wouldn't you create such a folder: /Library/Application Support/application_name like this: _App_dir_name="/Library/Application Support/application_name" /usr/bin/sudo mkdir ${_App_dir_name} /usr/bin/sudo chmod 2766 ${_App_dir_name} This is the way many application are managing their globally used files. Look for example at: /Library/Application Support/Apple/Photos/Print Products
Post marked as solved
3 Replies
0 Views
Matt: thank you. I don't need an API, there is already a very large set of great tools (pfctl, pfd, InternetSharing…), I just need a documentation. I suggested an enhancement on "security documentation".
Post not yet marked as solved
7 Replies
0 Views
Do you still experience this bug?Could you please give us the output of:pmset -g
Post not yet marked as solved
2 Replies
0 Views
This is a developper-level question.I am talking here of kernel problems (I am a developper, I work on Unix internals and security bugs).Do you know of debugging functions inside the 10.13 debugging kernel which might help toreproduce and analyse this kind of problem?
Post not yet marked as solved
7 Replies
0 Views
This bug is fixed with an update to MacOS 10.13.5: https://support.apple.com/kb/DL1965.I tested it with the following power management settings:pmset standby 1 pmset autopoweroff 1then with:pmset hibernatemode 3 pmset hibernatemode 25All these tests were run with: FileVault on, battery level low battery level low to a level were the OS decides to sleep on its own.On all these tests I never saw the typical error:powerd Sleep Failure [code:0x11105000400001F]:and the exit from sleep, through any key or with the power on button were successfull.My conclusion is:MacOS 10.13.4 sleep bug fixed with 10.13.5,This version is good for work!
Post not yet marked as solved
7 Replies
0 Views
Do you still experience the same bug?Which version of MacOS X are you running?Could you include the output of command:pmset -g
Post not yet marked as solved
1 Replies
0 Views
Do you still experience the same problem?Which version of MacOS X do you actually run?Could you provide the output of command:pmset -g
Post not yet marked as solved
7 Replies
0 Views
I have the same problem on a newly installed MacBookPro:Version 10.13.4MacBook Pro (Retina, 15-inch, Mid 2015)FileVault is on/var/log/powermanagement/yyyy.mm.dd.aslcontains the typical error code:21:24:55.692880 +0200 powerd Sleep Failure [code:0x11105000400001F]:after the following entering into sleep mode on a low level battery:17:54:35.439839 +0200 powerd Entering Sleep state due to 'Low Power Sleep':TCPKeepAlive=inactive
Post not yet marked as solved
7 Replies
0 Views
Nothing really interesting in this discussion.Some silly pieces of advice: "upgrade to 10.13.4" when the problem seems typical of 10.13.4..
Post not yet marked as solved
7 Replies
0 Views
Go to:/var/log/powermanagemententer:ls -alt *.aslto get the appropriate log fileopen it with:open YYYY.MM.DD.asl