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.
