Unexpected crash: i/o error

Subject of the issue

AutoPi crashed during long drive. Write failed: Input/output error.

Your environment


Steps to reproduce


Expected behaviour

Not crash

Actual behaviour

During a long drive my AutoPi crashed. I did nothing with the device at the moment. I heard the voice feedback from the AutoPi but could not hear what it said due to noise.

I only discovered it had crashed when I had to manually restart it the day after by pulling the OBDII connector and reattaching it. After this, the device uploaded the following Events to the cloud which explains why my Trip was cut short:

December 8th 2021, 20:31:14 system/power/3v3 restarted reason: qmi_device_missing
December 8th 2021, 20:28:47 system/network/wwan0 offline reason: QMI device not found ‘/dev/cdc-wdm0’
December 8th 2021, 20:27:55 system/minion offline
December 8th 2021, 20:27:05 system/kernel error timestamp: '2021-12-08T19:26:35,840604+0000’
message: 'usb usb1-port1: Cannot enable. Maybe the USB cable is bad?'
level: err
facility: kern
December 8th 2021, 20:27:05 error timestamp: '2021-12-08T19:26:34,290710+0000’
message: 'usb usb1-port1: disabled by hub (EMI?), re-enabling…'
level: err
facility: kern
December 8th 2021, 20:26:43 unknown reason: >- [Errno 2] could not open port /dev/ttyQCT02: [Errno 2] No such file or directory: ‘/dev/ttyQCT02’
December 8th 2021, 20:26:36 vehicle/position unknown reason: ‘write failed: [Errno 5] Input/output error’
December 8th 2021, 20:22:28 vehicle/position moving
December 8th 2021, 20:22:23 vehicle/position unknown reason: no_fix

1: What does the above mean? I understand it lost contact with a device, but which device? The modem?
2: Why did that happen?
3: What can I do to prevent it from happening again?

Output of power.status command

$ power.status
users: 1
seconds: 584
since_t: 1639071819
days: 0
since_iso: ‘2021-12-09T17:43:39.908621’
time: ‘0:9’
state: discharging
voltage: 12.6
level: 100
sleep: NONE
wake: NONE
vl_wake: ’ >13.00V FOR 5 s’
vchg_wake: ’ +0.40V IN 1000 ms’
uart_sleep: ’ 900 s’
vl_sleep: ’ <12.10V FOR 240 s’
ext_sleep: ’ LOW FOR 3000 ms’
ext_wake: ’ HIGH FOR 500 ms’
down: none
up: ‘on’
sleep_interval: 0
version: ‘2.2’
current_state: ‘on’
down: none
up: spm


The issue that is present here is that the modem somehow got disconnected.
To troubleshoot this, please run the command: lsusb ,saving a screenshot of it.
Besides, run the commands qmi-manager down, qmi-manager up and save screenshots of these too.
Next, run the command i2cdetect 1 and save a screenshot of it too.

Then, create a support ticket linking to this forum link, upload the screenshots and then we’ll take it from there.


This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.