Single instance of a feedback report:

https://feedback.corp.google.com/#/Report/61621902223 

--

From the report:

[   11.172792] atmel_mxt_ts 3-004b: Status: 10 Config Checksum: 06cb89
[   11.180067] atmel_mxt_ts 3-004b: Status: 00 Config Checksum: 06cb89
[   30.620691] atmel_mxt_ts 5-004a: i2c transfer failed (-6)
[   30.620733] atmel_mxt_ts 5-004a: Failed to read message count (-6).
[   30.620759] atmel_mxt_ts 5-004a: Handling message fails in IRQ, -6.
[   30.707334] udevd[3226]: Process '/sbin/crash_reporter --udev=SUBSYSTEM=i2c-atmel_mxt_ts:ACTION=change' failed with exit code 1.

--

From dtor email:

I wonder why device falls off the bus so that transfers report ENXIO... It does not look we were updating firmware:

2017-05-25 10:26:00.689 5 chromeos-atmel-touch-firmware-update[1144]:  Attempting to load FW: '/lib/firmware/maxtouch-ts.fw'
2017-05-25 10:26:00.707 5 chromeos-atmel-touch-firmware-update[1173]:  Product ID : 164.14
2017-05-25 10:26:00.712 5 chromeos-atmel-touch-firmware-update[1176]:  Current Firmware: 2.3.AA
2017-05-25 10:26:00.718 5 chromeos-atmel-touch-firmware-update[1183]:  Updater Firmware: 2.3.170
2017-05-25 10:26:00.728 5 chromeos-atmel-touch-firmware-update[1200]:  Attempting to load FW: '/lib/firmware/maxtouch-tp.fw'
2017-05-25 10:26:00.736 5 chromeos-atmel-touch-firmware-update[1207]:  Firmware up to date.
2017-05-25 10:26:00.746 5 chromeos-atmel-touch-firmware-update[1221]:  Product ID : 164.17
2017-05-25 10:26:00.751 5 chromeos-atmel-touch-firmware-update[1231]:  Current Firmware: 2.0.AA
2017-05-25 10:26:00.756 5 chromeos-atmel-touch-firmware-update[1239]:  Updater Firmware: 2.0.170
2017-05-25 10:26:00.769 5 chromeos-atmel-touch-firmware-update[1264]:  Firmware up to date.

--

Is there any chance that we simply had a bad connection (lose connector, cold solder joint, etc) and flexing the device at the wrong time caused this?