M1 macbook pro kernel panic

Hello, Ma7h!

Thanks for reaching out to the Apple Support Communities! It sounds like you're having an issue with your MacBook Pro experiencing kernel panics. Check out this article If your Mac restarted because of a problem. This article will give you steps to take for issues with your Mac restarting, as well as what to do if the issues continue.

Best regards.

Thanks for keep us posted on the results, Ma7h!

Since the issue is still going on, we would recommend reaching out to Apple directly by checking out this link to Get Support and they will be more than happy to proceed with additional steps.

Good luck!

I have been having the same exact issue since day one of my m1 MacBook Pro. Sometimes one crash a day sometimes 4-5. It happened before I even installed clamxav so its not caused by that I wouldn't think. Hopefully we will find the cause.

I have the same issue since yesterday. My M1 MBP freezes with a pink screen and after reboot I get the error log. Also in my log I have the same lines:

panic(cpu 4 caller 0xfffffe0027906620): "uipc_send connected but no connection?"

...

Panicked task 0xfffffe166e1d0638: 38041 pages, 3 threads: pid 318: clamd

So it is very likely that also for me the ClamXAV Daemon is the cause of the kernel panic. I have deinstalled ClamXAV and let's see if the kernel panic reoccurs.

Update:

I had 3 kernel panics so far and I have looked in all 3 logs. The logs are stored in: "/Library/Logs/DiagnosticReports/Retired" and they have the file extension ".panic"

In all logs the clamd (ClamXAV daemon) task causes the kernel panic. I have contacted the ClamXAV support and forwarded the issue.

I'm also seeing this.

M1 MacBook Pro with ClamXAV installed.

Several kernel panics per day where machine freezes for about 5-10 seconds (cursor won't move, no input or output) then a flash of pink screen before machine seems to partially restart and I have to log in again.

My panic logs include the same lines:

"uipc_send connected but no connection?"

and

|Panicked task ... clamd

I hardly ever have Safari running.

I've uninstalled ClamXAV and things seem to have been stable for about a day and a half.

I contacted ClamXAV support and they:

"Firstly, kernel panics are generally caused by hardware issues with your Mac, or, issues with third party kernel extension (kexts) - usually in the form of device drivers or similar. ClamXAV does not make use of any kernel extensions, therefore ClamXAV (including our process clamd) cannot be solely responsible for a kernel panic. Since we do not use kexts in ClamXAV, none of our code runs at the kernel level. The kernel is purposefully isolated from regular applications (such as ClamXAV) in order to prevent kernel panics occurring as a result of third party software. If the kernel is panicking due to third party software, this is something Apple needs to address, and you should report it to them.

In the panic log excerpt that you've attached, clamd is stated as the panicked task. This does not mean that clamd is responsible for the panic, it means that it was the last task that the kernel was handling when the panic occurred. This is known as a backtrace and is similar to how stack traces work (if you're familiar with them). The panic log should also include details of the last loaded kernel extension, I suggest you check for this and unload that extension to see if that helps. Above all, I suggest that you speak to Apple Support regarding this, as your Mac is new and it's not infeasible that a firmware issue relating to the M1 is the reason why this is happening."

Which may all be correct, but my panics always reference clamd as the panicked task, and it's been stable since I uninstalled it. So ClamXAV may not be the cause of the panic, but might it be the cause of something else that is then causing the panic?

I'll keep you updated. I might leave it for a few days, then re-install ClamXAV and see if things start up again.

I would like to say that granting ClamXAV full access, and downloading the beta from their website finally fixed by otherwise amazing M1 Mac Mini. I was at the point of asking for another unit, having been on the phone with support for several hours. As I suspected Support have a script, and ask you to unplug various peripherals then phone back, re-download Big Sur then phone back etc., etc. Having had at least one Macintosh since 1986, I've become pretty adept at troubleshooting... and while I first thought my multiple crashes (sometimes 3 or 4 per day) had to do with Bluetooth... I finally found this thread which has resulted in two solid weeks of continuous performance without a glitch!!! Hope anyone else who has the problem trips over this post.

Also getting kernel panic 1-5x a day on Safari. No ClamXAV installed at any point