MBIM close response shouldn't reset the number of consecutive timeouts
ModemManager has logic to detect timeouts in MBIM requests, and if 10 consecutive timeouts happen, the modem is flagged as Invalid.
But that logic should not consider a response to a "MBIM close" as a valid response to reset the number of timeouts, because that response is sent by the mbim-proxy
and not by the modem:
2022-09-20T18:10:02.874857Z ERR ModemManager[15294]: <error> [modem0] port cdc-wdm0 timed out 10 consecutive times, marking modem as invalid
2022-09-20T18:10:02.874955Z DEBUG ModemManager[15294]: <debug> [/dev/cdc-wdm0] number of consecutive timeouts: 10
...
2022-09-20T18:10:02.875827Z DEBUG ModemManager[15294]: <debug> [/dev/cdc-wdm0] closing device...
2022-09-20T18:10:02.875892Z DEBUG ModemManager[15294]: <debug> [/dev/cdc-wdm0] sent message...#012<<<<<< RAW:#012<<<<<< length = 12#012<<<<<< data = 02:00:00:00:0C:00:00:00:DB:01:00:00...#012
2022-09-20T18:10:02.875948Z DEBUG ModemManager[15294]: <debug> [/dev/cdc-wdm0] sent message (translated)...#012<<<<<< Header:#012<<<<<< length = 12#012<<<<<< type = close (0x00000002)#012<<<<<< transaction = 475#012
2022-09-20T18:10:02.877159Z DEBUG ModemManager[15294]: <debug> [/dev/cdc-wdm0] received message...#012>>>>>> RAW:#012>>>>>> length = 16#012>>>>>> data = 02:00:00:80:10:00:00:00:DB:01:00:00...#012
2022-09-20T18:10:02.877219Z DEBUG ModemManager[15294]: <debug> [/dev/cdc-wdm0] reseted number of consecutive timeouts