Yes, I reported it months ago.
Which Autopilot hardware are you using? I strongly suspect that the problems are specific to the MCU1-HW3 combination, and might even be specific to the HW2.5 -> HW3 upgrade path, either because of the camera differences or the presence of a second RADAR input.
The failure is likely not energy-related, as I initially saw this manifest itself as:
- Randomly being unable to use the driver's side door controls for half a minute at a time
- Messages on the IC screen saying that it is unable to communicate with the MCU for half a minute
- MCU becoming unresponsive to touches for up to half a minute
with some of these symptoms sometimes occurring simultaneously. At this point, the other communication problems have subsided (I haven't seen them since a week or so after the "upgrade"), but the IC reboots and autopilot disengagement persists.
What's interesting is that when it fails, you get a "Take over immediately", but Autopilot remains engaged, and the IC remains lit. And then as soon as you disengage Autopilot, that's when the IC reboots. It makes me wonder if there is a memory leak that causes the IC computer to hit some low water mark memory-wise, and then reboot itself as soon as it thinks it is "safe" to do so.