Is this happening on milestones >56? The current stable stable channel is M59.

Sorry but I don't think is a bug I can help with.  It sounds like Chrome is freaking out, not the low-level touch workings.  If the touchscreen was the issue it wouldn't be rebooting the whole machine.  (The touchscreen's firmware runs on its own separate microcontroller.  Obviously it's theoretically possible for a touch FW bug to to fully crash/reboot the main system, but it's quite tough) It seems much more likely to me that there is some root cause in Chrome that is causing it to stop listening to touch events coming from the touchscreen and also causes reboot.

Re: comment 6
Comment from Additional details, "Chrome devices for meetings in their entire domain."
So, Chrome devices for meetings still run on v56 as latest OS version.

Please let us know if you require any other info from the customer site.

gkihumba@
Could you please assist this case.

Yung is this another buddy issue ?

How many units are having this problem?  Is it just 1 or all units exhibiting this issue?

Hi Yung,

Zep here, this bug is about my chromebases deployment so I am joining in to offer any info you need to expedite a resolution to this.

The problem has been very intermittent, most, if not all of my units have been affected at some point in their life.  We have about 35 chromebases deployed.

youngleem@
Is there any update for this case?
Please let us know if you require any extra info for your investigation.

We should separate the two issues, #1) Chromebase stops responding to touch input and #2) Chromebase reboots every 10 minutes. Root cause of these issues could be same, but as mentioned in #c7, unresponsive touch screen is unlikely to cause OS crash, and mixing up investigation can easily result in confusion and longer resolution times.

Let's focus on #1 (Chromebase stops responding to touch input) in this bug, and continue discussion for #2 in  crbug.com/752192 .

Additional points to clarify:

- Any trend in the timing of issue? (ex. As soon as the device boot up, when joining Video calls, after the device is left untouched for a while, etc.)
- From #c1, "Date and Time issue was reproduced: 06/16/2017 Around 2pm" Is this when the touch screen issue occurred, or when the device rebooted, or both? (This is why we should separate bugs)

The touch issue seems to happen when the device is left untouched for a
while, but it is intermittent so its a little hard to tell.  I have never
seen it lose functionality in a call, only on the main menu.  As far as
date and time re-produced, the issue is ongoing, yet intermittent (it
usually takes a long time for a device to do this a 2nd time, however there
is always a device with this problem in my deployment, end users have
figured out that rebooting fixes the problem so I am sure there are alot of
undocumented instances of this problem.

*--*
*Zep Brattesani - CTS*
IT/AV Engineer
5 <+15715276968>30.400.3694
[image: Lyft] <http://www.lyft.com/>

Royans, how do we get logs from the device when hitting this issue?  Seems like it's running in Hotrod mode but am not sure how customer can trigger feedback?

#c17: From Cfm home screen, user can simply submit feedback and tell us date/time and device serial number. This feedback includes a short period of logs.

For full logs, 1) reboot Cfm, 2) enter ChromeOS mode by pressing Ctrl+Alt+S during boot 3) Start guest mode and save file from chrome://net-internals/#chromeos

To move forward with investigation it would be great if we have specific recent date/time of issue along with logs captured from the same device. That way we can minimize risk of investigating logs unrelated to issue.

When the next instance of this issue is reported, I will have a tech perform these diagnostics and provide logs/submit feedback.

ChromeOs version in the debug logs: 9460.73.0	59.0.3071.134

Here are the logs that were collected after the problem was reproduced on
9/5/2017 1:30-2pm

debug logs: https://drive.google.com/open?id=0B01ZVp8vDQocWDNLRWJfY01UTlU

Hello team, is there any update on this issue?

We haven't heard any recent complaints; please reopen if this is still an issue.