busy timeout[0], (60s): 'AppleAPFSMediaBSDClient'

rainer114,

Got it. After the steps you've already taken, the best step from here would be to have an authorized technician examine your Mac further. You can get help finding options with either of the two links below:

• Apple - Find Locations - Location Selector
• Contact Apple Support

Best regards.

I'm having exactly the same issue with my M1 MacBook Pro (2021). The key steps are

• it started happening after upgrading to 11.6.2
• it occurs when awakening after having disconnected an APFS volume (used for Time Machine)

Hey rainer114,

It appears that your MacBook Air is experiencing kernel panics. Check out the articles below and the steps inside to see if those possibly help:

• If your Mac restarted because of a problem - Apple Support
• If your Mac restarts and a message appears - Apple Support

Let us know if the steps in those articles help or if you've already tried that.

Best wishes to you.

Hi, I can confirm this is a specific bug with the macOS 11.6.2 update because the exact same kernel panic happens on my M1 MacBook Air. The steps I take to reproduce it are to plug in an external drive formatted with APFS, then disconnect it. When the computer wakes up from sleep afterward, it kernel panics 60 seconds later. This did not happen until updating to 11.6.2. Every version prior was perfectly fine, so it is an introduced bug.

rainer114, does this sound like your situation?

Had the same problem, namely a crash every time after shortly after:

1. External TM disk disconnect
2. Close lid
3. Open lid

This was on a MacBook Air M1 (late 2020). The crash was easy to reproduce and still happening in Big Sur 11.6.4.

Upgrading to Monterey 12.2.1 has fixed the problem.

Having the same problem: a crash shortly after:

1. External TimeMachine disk disconnect
2. Close lid
3. Open lid

This happens on a MacBook Pro M1 (2021). The crash was easy to reproduce and still happening in Big Sur 11.6.5.

I noticed that a kernel panic only happens when the unmounted external HDD continues to spin.

That is every time I use "Eject" from the drive's menu or when I unmount the volume in the Disk Utility, but NOT when I use "unmount" on the External Physical Disk.

So, to work around the bug, open the Disk Utility. First, choose "Show All Devices" in the menu next to the sidebar.

Then, use the highest level (physical device) unmount icon instead of one for a volume that it contains.

You'll know you're OK if the drive stops spinning.

If you forget about this method and use your regular "Eject" menu item, don't unplug the drive. Mount the volume again using the Disk Utility and unmount it using the above method.

Use it every time, for any drive that causes problems, until there is a better solution.

rainer114,

Thanks for letting us know. The numerous steps in the previous articles can help isolate if the issue is software or hardware. Can you tell us all the steps you've taken? That way we aren't providing any that have already been done.

Have you noticed that you are doing a certain task when the kernel panic happens? For example, using an app, opening an app, so on. Knowing his can also help isolate what might be going on.

Take care.

Rainer 114: Appreciate you writing "This take me a lot of time, with actually NO effect..." (saving us all time)

I'm having the same kernel shut down issue on my "new" MBP 13 M1.

One additional piece of info from my end...Maybe coincidence but did not have this kernel shut down problem until AFTER 11.6.2 update.

Not necessarily. It means that the developers can backtrack and undo the bug or find a new way to fix it. Something broke with the way APFS volumes are accessed in 11.6.2, and it needs to be fixed.

How long it takes to push the fix is up to Apple.

I'm having exactly the same issue with my M1 Air (2021). As 2to3sherpas said, I also believe this started happening after upgrading to 11.6.2. Hence, this should be easy to fix in a future update, though I have to point out that this bug is extremely annoying.

I did more testing, and it specifically happens to me when making a Time Machine backup. Other APFS-formatted drives don't trigger the crash. This makes it even worse because Time Machine is so important in case scenarios where something else goes wrong and there's a need to restore data. It does NOT happen in Monterey (I set up a separate APFS partition for a clean install), though I am not upgrading my machine to Monterey fully until later updates.

I sent a report through Apple's Product Feedback page. Hoping that helps push incentive for a fix.

I am successfully able to reproduce this error. For me, the crash happens after a TM backup, followed waking the Mac after putting it into sleep mode. I sent comments and links to this thread in the crash report. Perhaps that will add to your feedback and move this fix along.

Like you, I’m not ready to upgrade to Monterey.