Using the debug node to control the driver, two Identical responses were seen to the same request. The dissected exchange.log from kernel exchange and dmesg is shown below.
It can be seen that the TDME-GETSFR Confirm is received twice, which means that the SETSFR command response is lost. It can also be seen that there were a lot of retries and failed IRQs around the time of error.
The driver does not require restarting, and remains functional following the issue.
Using the debug node to control the driver, two Identical responses were seen to the same request. The dissected exchange.log from kernel exchange and dmesg is shown below.
It can be seen that the TDME-GETSFR Confirm is received twice, which means that the SETSFR command response is lost. It can also be seen that there were a lot of retries and failed IRQs around the time of error.
The driver does not require restarting, and remains functional following the issue.
Dmesg: