Lately we are seeing reports from the market that on M5 Macbooks and A18 Neos the system will kernel panic using our solution, even though it never happens on M1-M4 and no significant code changes were made in the mean time. All crashes seem to be related to an internal double free in the kernel: Have you filed a bug on this and, if so, what's the bug number? Can you tell us please if this is a known problem and if there's a workaround or what can we do to narrow it down? I'm need full panic logs to be sure (that's why I asked about the bug) but, yes, I suspect this is a known issue (r.172793638). __ Kevin Elliott DTS Engineer, CoreOS/Hardware
Topic:
App & System Services
SubTopic:
Networking
Tags: