Unfortunately, the error here seems to be related to something strange occurring in the Linux Kernel. During the failure, two consecutive status messages from the main mcu got reordered and thus could not be parsed by the host. The host correctly aborted the homing operation as a result.
The first occurrence is:
(030.470769) can0 RX - - 109 [6] A2 F3 10 0D 48 7E
(030.470643) can0 RX - - 109 [8] 0E 14 58 0B 01 00 8E 8F
And the second:
(030.480394) can0 RX - - 109 [6] 90 E1 46 F2 B3 7E
(030.480264) can0 RX - - 109 [8] 0E 15 58 0B 01 00 8E 90
Oddly, it seems Linux knows that it has reordered the packets as the timestamps are not in incrementing order.
What is the host hardware you are using? What operating system are you using (uname -a ; cat /etc/os-release)?
-Kevin