Here are similar landmarks for a different M1 model:Ģ2.740229 AudioDMAController_T8103 setDirectionAndRole: APA2TX::admac-aop-audio::589: TX:Initialized.Ģ2.740246 AudioDMAController_T8103 setDirectionAndRole: APA3TX::admac-aop-audio::589: TX:Initialized.ģ0.386373 Sandboxing init issue, couldn't find profile in default paths, attempting default compiled profileģ0.408469 Sandboxing init issue resolved: "Success"Ģ3.154775 = system wallclock time adjustedĢ3.182194 = system wallclock time adjustedĢ3.189528 Starting userland kernel management subsystem (KernelManagement_executables-102.60.20) This makes it easy to spot differences between systems. Adjustment of system time complicates observations: as shown, in this case there’s a step back in time by around 7 seconds, occurring over the two entries.īecause there are only three currently available Apple Silicon Macs with almost identical hardware, firmware and software, boot log entries between them are remarkably similar in sequence and timings. That should normally be less than about 8 seconds, and may not appear at all during some boots of M1 Macs. There’s a gap of 5.1 seconds there which occurs just before system time adjustment. For example:ġ0.309049 RTBuddy(GFX): start() - (Oct 31 wifiFirmwareLoader Sandboxing init issue, couldn't find profile in default paths, attempting default compiled profileġ5.391319 wifiFirmwareLoader Sandboxing init issue resolved: "Success"Ġ8.485687 = system wallclock time adjustedĠ8.514649 = system wallclock time adjusted This normally occurs just before a distinctive landmark, system time adjustment, and commonly close to a ‘sandboxing init issue’ with the Wi-Fi firmware loader. ![]() In this example, it’s around 6.6 seconds.įurther down the log, there’s a point at which boot transitions from the kernel to security phase, at which there’s another substantial time delay in entries. Typically, the time difference between them is 5-7 seconds on the M1 Macs which I have analysed. The first of those is the boot banner, and the second the start of the logged kernel phase. The first two entries in an M1 boot appear fixed, and are distinctive (all times being given in decimal seconds): (You’ll also want to note this important bug report affecting the log show command on M1 Macs running macOS 11.1.) I’ve been studying the logs of several M1 Macs and Intel models, and offer the following observations. ![]() Unfortunately, this varies according to Mac model, configuration, firmware and macOS version, and sometimes seemingly even the weather.Īlthough the unified log may not give details of what takes place during loading of extensions, it does provide valuable clues as to when things are going wrong as it provides precise timings. ![]() It’s worth timing each phase of what you see, up to the moment that the login screen appears, and comparing that with what your Mac usually does, assuming that you’ve previously made a record of a ‘healthy’ boot. Slow booting isn’t a specific symptom, but it suggests that something is awry. It could, for instance, be a misconfigured network connection or something else which doesn’t change with Safe mode. And if this doesn’t make booting any better, a third-party extension is unlikely to be the cause of the problem. So successful startup in Safe mode doesn’t actually prove that the problem was down to a third-party extension, but it should be a good clue. Safe mode also does other things, which sometimes magically solve problems, even though Apple is a little unclear as to exactly which caches and other data are cleared or rebuilt. If you’re working with an M1 Mac, remember that these new models enter Safe mode through Recovery Options, as explained here. ![]() As a quick test, there’s nothing to beat starting up in Safe mode. In Safe mode, all third-party extensions and some Apple-supplied ones aren’t loaded. So what can you do if you suspect that one of your third-party extensions could be running into trouble, or creating problems for others? In Big Sur’s unified log, mum’s the word: you’re unlikely to see any mention of loading of kernel or system extensions or their relatives. Long gone are the days when the log gave a running commentary on each kernel extension as they were loaded. Big Sur, particularly when it’s running on an M1 Mac, doesn’t make it easy to tackle extension problems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |