Recurrent kernel panics on M1 MBP, Air [Merged]

[iphoneuserinyyz]

Wondering if anyone can provide any insight into the recurrent kernel panics I have been observing on brand new MBP M1. In every case, the screen flashes purple and green and then the computer instantly restarts. This seems to happen most often a few minutes after being disconnected from an external Thunderbolt 3 monitor (LG 5K, in case it is relevant here), but not every time that the computer is disconnected.
In every case, the error log that comes up ("your computer was restarted...") contains the following first line: panic(cpu 3 caller 0xfffffe0012d30a38): "busy timeout[0], (60s): 'IOHDIXHDDriveOutKernelUserClient', 'IOMediaBSDClient', 'IOMediaBSDClient', 'IOMediaBSDClient', 'AppleAPFSMedia'"

I worked through a number of troubleshooting steps with Apple support, including refreshing the OS, wiping and reinstalling the OS, etc. In the end, they had no answer and asked me to monitor the situation. I managed to find the same model in stock at a local Apple store, so was able to return the first one, in the hope that this was a hardware issue. But the second Mac (fresh OS install with Migration Assistant to restore the files) just crashed, and the error message log contained the same message quoted above.

Anyone have any insight into this? Is there any hope it might be fixed in an OS update?

 

[jdb8167]

What version of Big Sur? I don't have a Thunderbolt 3 monitor but it still sounds unusual. Do you sleep your MBP before unplugging?

 

[iphoneuserinyyz]

Big Sur 11.1. And yes, I always unmount/eject drives and sleep the computer before unplugging.

 

[jdb8167]

Big Sur 11.1. And yes, I always unmount/eject drives and sleep the computer before unplugging.

Even stranger. If you can get the crash report and send it to Apple that might help them track it down. Kernel panics are something that usually get fixed quickly if they occur in Apple's software and I think with Big Sur the vast majority of low level code is Apple's.

 

[iphoneuserinyyz]

I had already sent a complete diagnostic readout to Apple support, along with my text files of the error messages from 6 or 7 instances of this crash (which all contain the message posted above). This was apparently looked at by Apple engineering, but the only thing they came up with was to change the name of my hard drive from my customized name back to "Macintosh HD". I have not done so, because I can't see how that would cause these crashes?

 

[jdb8167]

I had already sent a complete diagnostic readout to Apple support, along with my text files of the error messages from 6 or 7 instances of this crash (which all contain the message posted above). This was apparently looked at by Apple engineering, but the only thing they came up with was to change the name of my hard drive from my customized name back to "Macintosh HD". I have not done so, because I can't see how that would cause these crashes?

I'm sure it got sent up the chain. Sounds like you got a low level tech support engineer since the proposed "solution" sounds nonsensical and even if it was the problem, they have a major issue. You can be pretty sure kernel panics are being collected by engineering and anything coming from an M1 is sure to be prioritized.

 

[iphoneuserinyyz]

Would you agree that the fact that I am seeing identical crashes on two different Macs pretty much rules out a hardware fault?

 

[jdb8167]

Would you agree that the fact that I am seeing identical crashes on two different Macs pretty much rules out a hardware fault?

Yes. Or in the awful case, there is a hardware design problem. One of the reasons that you can be pretty sure your reports are being sent to someone to diagnose is that if it is a hardware issue they want to mitigate it as quickly as possible. Still it is most likely a software problem and a relatively rare one. Something is different about your MBP usage since we aren't seeing a lot of similar reports here.

 

[jdb8167]

I just did a quick search on this forum. Most of the kernel panics reported here seem to be related to sleep and/or HDMI. I think I will go through those reports more carefully just out of curiosity.

 

[iphoneuserinyyz]

I wonder whether it could be an app I have installed (not that I use anything off the beaten track), or whether it could be related to the Thunderbolt connection with the LG monitor (but the crash happens minutes after it is disconnected, so I am not sure what the relationship would be)

 

[snakes-]

Check monitor and adapters too, turn off display shutdown and sleep, sleep is a bit corrupted and not fixed. I turn on off my monitor manually and have no problems. System always on, or shut down.

Why did you disconnect your monitor? on running system.

Have plugged my usb stick and one time I got some kernel panic. now since 2 days my systems have no errors or problems.

If I can speculate here then my opinion is that after sleep somewhere on the Mac (maybe ram or the controller itself) get not enough voltage/power when wake up, this causes the kernel panic.

 

[iphoneuserinyyz]

Check monitor and adapters too, turn off display shutdown and sleep, sleep is a bit corrupted and not fixed. I turn on off my monitor manually and have no problems. System always on, or shut down.

Have made those changes, will see if it helps.

 

[jdb8167]

It is odd. I don't see any kernel panic reports that match yours on the Apple Silicon forums here. Yet you've had it happen with two different MBPs. Decidedly odd.

 

[iphoneuserinyyz]

Yes it is!

 

[harrisonjr98]

Migration Assistant is almost always a headache. Try clean install and manually move your files, I can almost guarantee that'll fix it.

 

[jdb8167]

Migration Assistant is almost always a headache. Try clean install and manually move your files, I can almost guarantee that'll fix it.

That's not a bad suggestion. For me, since I keep most of my files synced on iCloud, doing a manual move to the new machine doesn't take much more effort than the migration assistant. I could see how it is a bit daunting though if you haven't done it before. But I'd imagine the chances of something bad slipping in when migrating between two machines with different architectures is higher than normal.

Edit: I did manually move my files when I moved from the 2018 13" MacBook Pro to the M1 MacBook Air.

 

[lethal753]

Wondering if anyone can provide any insight into the recurrent kernel panics I have been observing on brand new MBP M1. In every case, the screen flashes purple and green and then the computer instantly restarts. This seems to happen most often a few minutes after being disconnected from an external Thunderbolt 3 monitor (LG 5K, in case it is relevant here), but not every time that the computer is disconnected.
In every case, the error log that comes up ("your computer was restarted...") contains the following first line: panic(cpu 3 caller 0xfffffe0012d30a38): "busy timeout[0], (60s): 'IOHDIXHDDriveOutKernelUserClient', 'IOMediaBSDClient', 'IOMediaBSDClient', 'IOMediaBSDClient', 'AppleAPFSMedia'"

I worked through a number of troubleshooting steps with Apple support, including refreshing the OS, wiping and reinstalling the OS, etc. In the end, they had no answer and asked me to monitor the situation. I managed to find the same model in stock at a local Apple store, so was able to return the first one, in the hope that this was a hardware issue. But the second Mac (fresh OS install with Migration Assistant to restore the files) just crashed, and the error message log contained the same message quoted above.

Anyone have any insight into this? Is there any hope it might be fixed in an OS update?

When connected to the external display, do you also have the MBP display/lid open too? I had a M1 MBP I returned for other reasons and this new M1 MBA they both kernel panicked after a few hours connected to external display with lid open.

 

[iphoneuserinyyz]

When connected to the external display, do you also have the MBP display/lid open too? I had a M1 MBP I returned for other reasons and this new M1 MBA they both kernel panicked after a few hours connected to external display with lid open.

No, I only use it in clamshell mode.

 

[iphoneuserinyyz]

Migration Assistant is almost always a headache. Try clean install and manually move your files, I can almost guarantee that'll fix it.

I will have to consider doing this, but the thought of having to manually reinstall and configure all my apps/settings is more than I can stomach right now.

 

[KShopper]

Can you try a clean restore of MacOS *without* restoring your files at all just to see if the problem persists on a clean load? That at least would tell you if you it's related to something you have installed or not.

 

[iphoneuserinyyz]

Good advice, but hard for me to implement, because this is my work computer and I am on it constantly, and depend on the suite of apps and files that are installed.

So far with the new machine, only one crash has occurred, where with the older one the crashes were occurring 1-2 times every day. I think I will wait and see what happens over the next week or so, and if the KPs keep happening, I will have to bite the bullet and do an erase/fresh install without migration.

 

[iphoneuserinyyz]

Thinking through this some more. One of the apps I dragged along from my old Mac was "Mountain", which has not been updated in years. I use it to eject/dismount external disks/network shares prior to disconnecting from my dock. Is it possible that old software could be causing this issue, which I am seeing a short time after I dismount external drives? I have already uninstalled it to see if it might fix the problem.

 

[jdb8167]

Thinking through this some more. One of the apps I dragged along from my old Mac was "Mountain", which has not been updated in years. I use it to eject/dismount external disks/network shares prior to disconnecting from my dock. Is it possible that old software could be causing this issue, which I am seeing a short time after I dismount external drives? I have already uninstalled it to see if it might fix the problem.

Yup, that is probably it. It is known to cause trouble. It apparently hasn't been updated in 8 years.

 

[iphoneuserinyyz]

Yup, that is probably it. It is known to cause trouble. It apparently hasn't been updated in 8 years.

Can you point me to any posts here or other info about that app in particular? Interested in reading more.

 

[jdb8167]

Can you point me to any posts here or other info about that app in particular? Interested in reading more.

Unfortunately it is not from a public forum but it has a lot of experts in running beta software and new versions of MacOS. I'd bet a whole dollar that it is your problem.