May be related to trackpad issues.

Additional report here:
https://listnr.corp.google.com/report/85499674068

"Trackpad stopped working after awaking the Pixelbook by opening the lid. No mouse cursor on the screen either. This is the second time it happens. Both time a reset restore the functionality."

If we can get a repro case for this we can go further. If this repros again the next time we should see if the cursor comes back using an external mouse, to narrow down if this is a problem in actually rendering the cursor or a problem with the touch pad itself. 

FWIW, statistically reports of this sort of problem have been trending down. 

Not sure if we have repo case for this yet, but seeing issues reported on M69 Dev & M68 Beta.

These reports specifically mention that the touch screen continues to work after the cursor has disappeared.

https://listnr.corp.google.com/report/85530104703
https://listnr.corp.google.com/report/85529658430
https://listnr.corp.google.com/report/85529987109

Has occurred to me multiple times in the last few weeks. Touch screen continues to work after the cursor disappears. I believe it happens after waking from sleep, and the cursor is still on the screen for a second, but it may be when I've touched the touch pad that it disappears? And it might have jumped on the screen first, but I may be misremembering that. Am on M69 Dev, June 26, 2018 build. Have been continuing to use it without rebooting for probably over 10 hours now with multiple sleeps, just using keyboard and touch screen, without any change or reappearance of the cursor. Let me know if there's any additional logs or diagnostic information that I could provide.

The touchpad kernel device is missing.

The cursor is just a symptom - it should still work if you plug in a USB mouse. The mouse/touchpad settings will also disappear from chrome://settings if there's no kernel device.

Some of the reports do have a kernel device - those have a different cause (and may have been fixed already, see bug 771264).

These messages seem relevant:

NOTICE chromeos-google-touch-firmware-update[1369]: Current active fw version is: ''
NOTICE chromeos-google-touch-firmware-update[1371]: Current updater fw version is: 'rose_v1.1.8546-ee1861e9e'
NOTICE chromeos-google-touch-firmware-update[1373]: error: Unable to detect the active FW version.
NOTICE chromeos-touch-update[777]: Eve touchpad firmware update failed.

Failed firmware update + No touchpad kernel device (Eve M67):

https://listnr.corp.google.com/report/85530104703
https://listnr.corp.google.com/report/85529987109

Other causes:
https://listnr.corp.google.com/report/85529658430 (cyan M69)
https://listnr.corp.google.com/report/85487638432 (meowth M69)
https://listnr.corp.google.com/report/85499819431 (eve M66)
https://listnr.corp.google.com/report/85483809097 (eve M66)
https://listnr.corp.google.com/report/85481225974 (edgar M66)
https://listnr.corp.google.com/report/85477449757 (candy M66)

bug 862738 sounds similar.

I just hit this today after my eve updated yesterday to 69.0.3497.87 (Official Build) beta (64-bit).

If I connect my bluetooth mouse the cursor comes back and I can use the bluetooth mouse, but using the touchpad does nothing.

From /var/log/messages

2018-09-12T08:31:00.705733+10:00 NOTICE chromeos-wacom-touch-firmware-update[1086]: Platform version detected as: 8
2018-09-12T08:31:00.707311+10:00 NOTICE chromeos-wacom-touch-firmware-update[1088]: Wacom device hardware ID dectected as: 
2018-09-12T08:31:00.709168+10:00 NOTICE chromeos-wacom-touch-firmware-update[1090]: Device product id detected as: 5143
2018-09-12T08:31:00.715274+10:00 NOTICE chromeos-wacom-touch-firmware-update[1097]: Attempting to find FW_V2: /lib/firmware/wacom2_firmware.hex
2018-09-12T08:31:00.720397+10:00 NOTICE chromeos-wacom-touch-firmware-update[1101]: Wacom fw v2 not found. Will use v1.
2018-09-12T08:31:00.727090+10:00 NOTICE chromeos-wacom-touch-firmware-update[1110]: Attempting to Load FW: '/lib/firmware/wacom_firmware_EVE.hex'
2018-09-12T08:31:00.741090+10:00 NOTICE chromeos-wacom-touch-firmware-update[1126]: Active firmware version: 5376
2018-09-12T08:31:00.743097+10:00 NOTICE chromeos-wacom-touch-firmware-update[1128]: New firmware version: 5376
2018-09-12T08:31:00.746448+10:00 NOTICE chromeos-wacom-touch-firmware-update[1132]: Firmware up to date.
2018-09-12T08:31:11.771484+10:00 NOTICE chromeos-google-touch-firmware-update[1415]: Current active fw version is: ''
2018-09-12T08:31:11.775626+10:00 NOTICE chromeos-google-touch-firmware-update[1417]: Current updater fw version is: 'rose_v1.1.8546-ee1861e9e'
2018-09-12T08:31:11.779785+10:00 NOTICE chromeos-google-touch-firmware-update[1419]: error: Unable to detect the active FW version.
2018-09-12T08:31:11.781168+10:00 NOTICE chromeos-touch-update[764]: Eve touchpad firmware update failed.

Here's my report: https://listnr.corp.google.com/report/85655051616

The touchpad on my Eve stopped working after the 70 beta update, adding release block.

Feedback report is at https://listnr.corp.google.com/product/208/report/85710665050?dateRange=All

We are nearing M70 Stable. Will this fix make M70? If not we should move it to M71.

Ping, need an update on this. Thanks.

Moving to M-71.

I updated my Eve, still on beta 70, touchpad still does not work.

If this is really not happening anywhere else but my system (which is an EVT and may not be representative) and a few flukes in the field, this may not need to block stable, but it makes me nervous that 70 stable might result in broader impact to users. 

<Bulk edit> Reminder M71 Stable is approaching. Please review this bug and assess if this is indeed a RBS. If not, please remove the RBS label. If so, please make sure any planned work will be tested in Beta and verified before the Stable date. Thanks

<BULK EDIT> Reminder we nearinf M71 Stable. Please review this issue and update with your plan on next actions. Thanks.

First off, given that this is not a regression from 70, I don't think it should be release block.

Shecky, do you know if this is still an issue?

I wasn't informed on the issue before but the previous reports seems to indicate that the EC driver wasn't ready when we were trying to get the FW version. We retry 10 times in the updater script so the EC driver must be completely dead.

I am running out of time digging into the issue today. Would come back tomorrow.

It seems like the EC probing failed for the touchpad and there are 2 ways it could fail:

==== TYPE 1 ====

2018-11-21T14:47:22.509615+08:00 DEBUG kernel: [    0.240374] acpi GOOG0008:00: GPIO: looking up 0 in _CRS
2018-11-21T14:47:22.509619+08:00 ERR kernel: [    0.242213] cros-ec-i2c i2c-GOOG0008:00: packet too long (8 bytes, expected 4)
2018-11-21T14:47:22.509638+08:00 ERR kernel: [    0.242215] cros-ec-i2c i2c-GOOG0008:00: Cannot identify the EC: error -28
2018-11-21T14:47:22.509648+08:00 ERR kernel: [    0.242216] cros-ec-i2c i2c-GOOG0008:00: cannot register EC
2018-11-21T14:47:22.509775+08:00 WARNING kernel: [    0.242224] cros-ec-i2c: probe of i2c-GOOG0008:00 failed with error -28


2018-11-21T14:24:45.513280+08:00 ERR kernel: [    0.247596] i2c_designware i2c_designware.2: i2c_dw_handle_tx_abort: lost arbitration
2018-11-21T14:24:45.513284+08:00 ERR kernel: [    0.249088] cros-ec-i2c i2c-GOOG0008:00: packet too long (8 bytes, expected 4)
2018-11-21T14:24:45.513289+08:00 ERR kernel: [    0.249090] cros-ec-i2c i2c-GOOG0008:00: Cannot identify the EC: error -28
2018-11-21T14:24:45.513995+08:00 ERR kernel: [    0.249092] cros-ec-i2c i2c-GOOG0008:00: cannot register EC

==== TYPE 2 ====

2018-10-08T10:09:08.738792-07:00 DEBUG kernel: [    0.310780] acpi GOOG0008:00: GPIO: looking up 0 in _CRS
2018-10-08T10:09:08.738793-07:00 ERR kernel: [    0.311274] cros-ec-i2c i2c-GOOG0008:00: i2c transfer failed: -121
2018-10-08T10:09:08.738793-07:00 ERR kernel: [    0.311280] cros-ec-i2c i2c-GOOG0008:00: Cannot identify the EC: error -121
2018-10-08T10:09:08.738794-07:00 ERR kernel: [    0.311283] cros-ec-i2c i2c-GOOG0008:00: cannot register EC
2018-10-08T10:09:08.738795-07:00 WARNING kernel: [    0.311301] cros-ec-i2c: probe of i2c-GOOG0008:00 failed with error -121

In both ways it looks like the I2C transaction fails for some reason and therefor the cros-ec-i2c driver couldn't probe the device. This is similar to the i2c timeout issue that we track at b/78885145 .

On a side note, I have found a reliable way to reproduce the issue on campfire. If I stay in the selection screen for a long time before booting CrOS, I can reproduce both types of failures at 100% success rate. So this might have something to do with timing too.

This isn't a M71 regression. Why tag as an RBS? Let's remove that label.

Removing the RBS per #30.  If you thing it needs the RBS please retag and escalate.  Thanks 

https://listnr.corp.google.com/product/208/report/85823663179

My mouse cursor was working fine until the latest beta on eve (71.0.3578.85 (Official Build) beta (64-bit)).  With this beta, my mouse has disappeared twice, both times upon coming back from standby (not every time, but maybe after a day or two).  A reboot fixes it.  If it helps, I was running 20+ Chrome windows, One Crostini terminal window, and the Kindle Android app.

This happened to me again today.  I did shift-alt-i and reported it as a mouse cursor disappearing.  The touch screen still worked, but the touch pad did not.

FWIW my dad reported this issue to me today, first time he's encountered it after about 6 weeks of usage, he's using a Pixelbook running standard consumer versions of everything. A quick Google search uncovered a few forums where it is being discussed by users:

https://productforums.google.com/forum/#!msg/pixelbook/98z2wMxvrvQ/CfxIzG0UAgAJ and 

https://amp.reddit.com/r/Crostini/comments/9bd1ep/mouse_cursor_disappears/

Any updates to share here: I also see cros-ec-i2c erros

localhost /var/log # dmesg | grep cros-ec-i2c
[    0.346435] cros-ec-i2c i2c-GOOG0008:00: i2c transfer failed: -121
[    0.346442] cros-ec-i2c i2c-GOOG0008:00: Cannot identify the EC: error -121
[    0.346445] cros-ec-i2c i2c-GOOG0008:00: cannot register EC
[    0.346465] cros-ec-i2c: probe of i2c-GOOG0008:00 failed with error -121

I guess once that fails all bets are off for the touchpad?

localhost /var/log # cat /proc/bus/input/devices | grep Name
N: Name="Power Button"
N: Name="Lid Switch"
N: Name="Power Button"
N: Name="AT Translated Set 2 keyboard"
N: Name="WCOM50C1:00 2D1F:5143"
N: Name="WCOM50C1:00 2D1F:5143 Pen"
N: Name="Tablet Mode Switch"
N: Name="kbl_r5514_5663_max Headset Jack"
N: Name="kbl_r5514_5663_max HDMI/DP, pcm=6 Jack"
N: Name="kbl_r5514_5663_max HDMI/DP, pcm=7 Jack"