Firmware stops on Raspi when receiving valid framing

[stko]

Firmware stops on raspi when another module is connected. But as just observed, this might happen when the first valid answer frame comes from the module. On the screenshot in the left it can be seen that the third frame is a diagnostic answer frame

pi@raspberrypi:~ $ candump can0
  can0  7DF   [8]  03 22 F1 13 00 00 00 00
  can0  028   [8]  00 00 02 00 01 00 00 00
  can0  505   [8]  05 01 00 00 00 00 00 00
  can0  749   [8]  10 1B 62 F1 13 43 56 31

in the log its visible, that the firmware stopped working after receiving 3 frames Receive ISR on socket 4. in

[file mc_can.c, line 203]: CAN- Send Buffer with len 8
Signalhandler signal nr: 29
callback for unknown socket fd 0
seach for socket fd 3
seach for socket fd 4
OOBD Receive Callback on socket 4
Signalhandler signal nr: 29
callback for unknown socket fd 0
seach for socket fd 3
seach for socket fd 4
OOBD Receive Callback on socket 4
Receive ISR on socket 4.
Signalhandler signal nr: 29
callback for unknown socket fd 0
seach for socket fd 3
seach for socket fd 4
OOBD Receive Callback on socket 4
Receive ISR on socket 4.

so hopefully it has to do with the valid frame as such, but not with the socketcan in general