Works on my link with 51.0.2689.0.

It's possible that touchscreen pairing is broken; can you collect /var/log/chrome/chrome with

  vmodule=*touchscreen_util*=2

Seems to be working on 7978.43.0-16.04.05 / 50.0.2661.65. Closing.

Sorry, I apparently used wrong device to test. Still happening.

Google Chrome	51.0.2699.0 (Official Build) dev (64-bit)
Platform	8155.0.0 (Official Build) dev-channel samus

I don't have 51 dev machine at the moment. jdufault@, can you look into if this is pairing related?

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/c0708c1da9664bd232e7870db74c8b8c59f4d3c1

commit c0708c1da9664bd232e7870db74c8b8c59f4d3c1
Author: jdufault <jdufault@chromium.org>
Date: Tue Apr 12 20:34:10 2016

Emit warning when touchscreen association fails.

Useful to determine if a touchscreen not working is caused by touchscreen
association or by some other issue when the device is not in devmode.

BUG= 600436 

Review URL: https://codereview.chromium.org/1878393002

Cr-Commit-Position: refs/heads/master@{#386796}

[modify] https://crrev.com/c0708c1da9664bd232e7870db74c8b8c59f4d3c1/ash/touch/touchscreen_util.cc

Please collect the chrome log once you have a build with the patch in comment #6 on device.

From the machine in question (BEFORE the patch):
http://feedback/#/Report/7923039767
http://feedback/#/Report/7923072271

We can't reproduce this problem on the same build with our Samus.  Touchscreen is recognized as an input device by the hardware.  No touch-firmware problems.

There are a some kernel warnings such as:
2016-04-12T12:56:04.745498-07:00 WARNING kernel: [   42.216909] atmel_mxt_ts i2c-ATML0001:01: Move touch 0 to (0,0)
2016-04-12T12:56:04.745512-07:00 WARNING kernel: [   42.216928] atmel_mxt_ts i2c-ATML0001:01: Move touch 1 to (0,0)
2016-04-12T12:56:04.745520-07:00 WARNING kernel: [   42.216943] atmel_mxt_ts i2c-ATML0001:01: Release touch contact 0
2016-04-12T12:56:04.745521-07:00 WARNING kernel: [   42.216949] atmel_mxt_ts i2c-ATML0001:01: Release touch contact 1

It this specific to just one device? If so maybe it is bad hardware?

If the touch UI is working on another device (like cyan) or just another samus we can probably remove the release block label here.

I think this is hardware failure. I'll get new device. Closing