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

Issue 621592 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 621269



Sign in to add a comment

Touchpad stops working after upgrade to R51 - Gnawty

Reported by charliemooney@chromium.org, Jun 20 2016

Issue description

The touchpad on Gnawty has a bug in its FW version 8.0 that means it may lose all functionality.  This new FW 8.0 was added to R51 to patch a pullup resistor issue where the physical click-button could stop working after extended use, however, it appears that it also introduced a new bug which can simply prevent the touchpad from functioning entirely.

We need to revert this broken touchpad FW immediately, then upload a new version once Elan (the touchpad vendor) has provided us with a fixed firmware.
 
Cc: gkihumba@chromium.org bhthompson@chromium.org
Labels: -Pri-3 Merge-Request-52 Merge-Request-51 M-51 M-52 Pri-1
This just merged into ToT here at the CL below (I'm not sure why it didn't post here)

https://chrome-internal-review.googlesource.com/#/c/265615/


This is an urgent fix to revert a bad touchpad firmware that is completely stopping some Gnawty users' touchpads from working.  We really need to merge this back to 51 and 52 to get these users' touchpads functional again as soon as possible.  The touchpad firmware that this CL reverts it to was the one used previously, so it's known to work.  (The newest FW, that caused the issue, was introduced to fix a rare bug with the click button under the touchpad.  It's far less common and severe than the bug it introduced though, so we need to revert it quickly and then we'll add a version with both fixes later)

Thanks,
Charlie
Labels: Merge-Approved-52
Project Member

Comment 3 by bugdroid1@chromium.org, Jun 21 2016

Project Member

Comment 4 by bugdroid1@chromium.org, Jun 21 2016

Labels: merge-merged-release-R52-8350.B
The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/overlay-gnawty-private/+/f3f1158e84991d9dd5574f159036b2d1e6294b28

commit f3f1158e84991d9dd5574f159036b2d1e6294b28
Author: Charlie Mooney <charliemooney@chromium.org>
Date: Mon Jun 20 17:41:05 2016

Labels: -M-51 -Merge-Request-51
It turns out the offending patch didn't make it into 51 for Gnawty, so there's no need to revert it there.

That means the faulty firmware has been reverted everywhere it exists for Gnawty.  Now we just have to wait for a new FW from Elan to replace it with
Blocking: 621269

Comment 7 by tin...@google.com, Jun 22 2016

Labels: -Merge-Request-52 Hotlist-Merge-Approved
Your change meets the bar and is auto-approved for M52 (branch: 2743)
Labels: -Hotlist-Merge-Approved -Merge-Approved-52
Merged, thanks
Status: Fixed (was: Started)
The firmware is reverted to 6.0; marking as Fixed.  This fix is now out to all channels.
Status: Verified (was: Fixed)

Sign in to add a comment