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

Issue 594747 link

Starred by 1 user
Status: WontFix
Owner:
bleung@chromium.org
Closed: Mar 2016
Cc:
bleung@chromium.org
ka...@chromium.org
pucchakayala@chromium.org
█ charliemooney@chromium.org
jonr...@chromium.org
█ bhthompson@chromium.org
omrilio@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression


Participants' hotlists:
Fixing-touch


Sign in to add a comment

Touch doesn't work on Cyan

Project Member Reported by songsuk@chromium.org, Mar 14 2016 
Chrome Version   :  51.0.2672.0 (Official Build) dev (64-bit)
Platform         :  8062.0.0 (Official Build) dev-channel cyan


What steps will reproduce the problem?
1. install CrOS 8062.0.0 Cyan build 
2. try to touch on Time/Network icons on Shelf
3. after login, launch Chrome, try to touch on NTP


What is the expected result?
Should be able to open options by touch

What happens instead?
On step#2&3, nothing happens. 


Please provide any additional information below. Attach a screenshot if
possible.

Comment 1 by girard@chromium.org, Mar 21 2016

Cc: jonr...@chromium.org
Labels: OS-Chrome

Comment 2 by jonr...@chromium.org, Mar 21 2016 

Does touch work anywhere else in the UI?

Comment 3 by songsuk@chromium.org, Mar 21 2016 

Touch doesn't work anywhere in any UIs
>>> Comment#2.  Does touch work anywhere else in the UI?

Comment 4 by bhthompson@chromium.org, Mar 21 2016

Cc: charliemooney@chromium.org bhthompson@chromium.org
Can we get a log from this? The kernel log may have a lead if the driver is dying somehow.

Comment 5 by songsuk@chromium.org, Mar 21 2016 

Please see attached log file.
log-032116-151249.tar.gz
438 KB Download

Comment 6 by bhthompson@chromium.org, Mar 21 2016

Cc: bleung@chromium.org
Thanks, it does look like the kernel is sad.

...
2016-03-21T18:17:06.150824+00:00 ERR kernel: [    0.868503] Warning: unable to open an initial console.
2016-03-21T18:17:06.150831+00:00 INFO kernel: [    0.891795] input: Elan Touchpad as /devices/platform/808622C1:05/i2c-2/i2c-ELAN0000:00/input/input5
2016-03-21T18:17:06.150837+00:00 INFO kernel: [    0.893972] input: Elan Touchscreen as /devices/platform/808622C1:00/i2c-0/i2c-ELAN0001:00/input/input6
2016-03-21T18:17:06.150842+00:00 ERR kernel: [    0.894598] GPIO chip INT33FF:01: gpiochip_lock_as_irq: tried to flag a GPIO set as output for IRQ
2016-03-21T18:17:06.150847+00:00 ERR kernel: [    0.894615] GPIO chip INT33FF:01: unable to lock HW IRQ 13 for IRQ
2016-03-21T18:17:06.150852+00:00 ERR kernel: [    0.894626] genirq: Failed to request resources for ELAN0001:00 (irq 184) on irqchip chv-gpio
2016-03-21T18:17:06.150857+00:00 ERR kernel: [    0.894854] elants_i2c i2c-ELAN0001:00: Failed to register interrupt
2016-03-21T18:17:06.150868+00:00 WARNING kernel: [    0.908135] elants_i2c: probe of i2c-ELAN0001:00 failed with error -22
...

It looks like we are failing to get an IRQ now, not sure what changed here. 

Whom is the right person to dig into this one, Benson or Charlie perhaps?

Comment 7 by charliemooney@google.com, Mar 21 2016 

Hmm, I'm not sure what that's all about.  I think this needs a kernelier kinda person than me

Comment 8 by bhthompson@chromium.org, Mar 22 2016

Owner: bleung@chromium.org
Benson, could you take a look? I believe this is in your area of expertise, but if not please feel free to reassign.

Comment 10 by kathrelk...@chromium.org, Mar 23 2016

Status: WontFix (was: Untriaged)
Can't mark this bug as Duplicate since the other bug is on partner tracker and Monorail won't let me leave the ID blank...

I filed a bug against Monorail about that problem and am marking this as WontFix instead.
►

Sign in to add a comment