New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 786221 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

ChromeOS issue: Candy touchpad unavailable in login screen

Project Member Reported by vkhabarov@chromium.org, Nov 17 2017

Issue description

ChromeOS version: 61-62
ChromeOS device model: Candy
Case#: 14091001

Description:
On some percentage of devices touchpad won't work on login screen. Rebooting or logging in resolves the issue temporarily. External mouse works at the same time.


Steps to reproduce: 
1. Start Chromebook
2. Try to use touchpad

Current Behavior / Reproduction: 
Touchpad won't work

Expected Behavior: 
Touchpad should work

Drive link to logs: 
https://drive.google.com/a/google.com/file/d/1uhek99tJ6gAJUqEhmpR-1y8k5MQDWZLC/view?usp=sharing

Relevant errors found in logs - 
2017-11-10T10:01:28.188603-05:00 INFO kernel: [ 0.596533] input: Elan Touchpad as /devices/platform/80860F41:00/i2c-0/i2c-ELAN0000:00/input/input6 
2017-11-10T10:01:28.188605-05:00 DEBUG kernel: [ 0.596890] atmel_mxt_ts i2c-ATML0000:00: GPIO lookup for consumer atmel,reset 
2017-11-10T10:01:28.188607-05:00 DEBUG kernel: [ 0.596895] atmel_mxt_ts i2c-ATML0000:00: using ACPI for GPIO lookup 
2017-11-10T10:01:28.188614-05:00 DEBUG kernel: [ 0.596899] acpi ATML0000:00: GPIO: looking up atmel,reset-gpios 
2017-11-10T10:01:28.188617-05:00 DEBUG kernel: [ 0.596904] acpi ATML0000:00: GPIO: looking up atmel,reset-gpio 
2017-11-10T10:01:28.188619-05:00 DEBUG kernel: [ 0.596907] acpi ATML0000:00: GPIO: looking up 0 in _CRS 
2017-11-10T10:01:28.188622-05:00 DEBUG kernel: [ 0.596929] atmel_mxt_ts i2c-ATML0000:00: using lookup tables for GPIO lookup 
2017-11-10T10:01:28.188624-05:00 DEBUG kernel: [ 0.596933] atmel_mxt_ts i2c-ATML0000:00: lookup for GPIO atmel,reset failed 
2017-11-10T10:01:28.188626-05:00 ERR kernel: [ 0.597608] i2c_designware 80860F41:00: i2c_dw_handle_tx_abort: slave address not acknowledged (7bit mode) 
2017-11-10T10:01:28.188630-05:00 DEBUG kernel: [ 0.597652] atmel_mxt_ts i2c-ATML0000:01: GPIO lookup for consumer atmel,reset 
2017-11-10T10:01:28.188636-05:00 DEBUG kernel: [ 0.597656] atmel_mxt_ts i2c-ATML0000:01: using ACPI for GPIO lookup 
2017-11-10T10:01:28.188639-05:00 DEBUG kernel: [ 0.597660] acpi ATML0000:01: GPIO: looking up atmel,reset-gpios 
2017-11-10T10:01:28.188641-05:00 DEBUG kernel: [ 0.597664] acpi ATML0000:01: GPIO: looking up atmel,reset-gpio 

 
Customer updated that issue happens in Public Session too.

3176: 2017-11-30T13:14:05.121926-05:00 INFO kernel: [ 0.469465] i2c /dev entries driver 
13177: 2017-11-30T13:14:05.121932-05:00 DEBUG kernel: [ 0.469925] elants_i2c i2c-ELAN0001:00: GPIO lookup for consumer reset 
13178: 2017-11-30T13:14:05.121938-05:00 DEBUG kernel: [ 0.469931] elants_i2c i2c-ELAN0001:00: using ACPI for GPIO lookup 
13179: 2017-11-30T13:14:05.121944-05:00 DEBUG kernel: [ 0.469936] acpi ELAN0001:00: GPIO: looking up reset-gpios 
13180: 2017-11-30T13:14:05.121949-05:00 DEBUG kernel: [ 0.469942] acpi ELAN0001:00: GPIO: looking up reset-gpio 
13181: 2017-11-30T13:14:05.121955-05:00 DEBUG kernel: [ 0.469946] acpi ELAN0001:00: GPIO: looking up 0 in _CRS 
13182: 2017-11-30T13:14:05.121960-05:00 DEBUG kernel: [ 0.469994] elants_i2c i2c-ELAN0001:00: using lookup tables for GPIO lookup 
13183: 2017-11-30T13:14:05.121970-05:00 DEBUG kernel: [ 0.469999] elants_i2c i2c-ELAN0001:00: lookup for GPIO reset failed 
13184: 2017-11-30T13:14:05.121977-05:00 INFO kernel: [ 0.470233] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input5 
Owner: jayhlee@chromium.org
Hi Jay, could you please help triage this? Thanks!

Comment 3 by kotah@chromium.org, Jan 24 2018

Cc: kotah@chromium.org royans@chromium.org
Owner: kathrelk...@chromium.org
kathrelkeld@, can you triage this issue and/or try if this is reproducible?


LINEPLAYHEREWEGO รหัสคูปองค่ะ
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".

Sign in to add a comment