#5772 HIGH Never A: keyboard keys reported stuck in self-test
Zarro Boogs per Child
bugtracker at laptop.org
Fri Jan 4 08:26:19 EST 2008
#5772: keyboard keys reported stuck in self-test
------------------------+---------------------------------------------------
Reporter: kop | Owner: walter
Type: defect | Status: reopened
Priority: high | Milestone: Never Assigned
Component: keyboards | Version:
Resolution: | Keywords:
Verified: 0 | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Changes (by gnu):
* priority: normal => high
* status: closed => reopened
* resolution: duplicate =>
Comment:
According to later comments in #5658, this is *not* a duplicate of 5658.
This bug is in the OFW diagnostic for the keyboard (or in something that
it depends on, like the EC or the keyboard processor). It can be
demonstrated in otherwise-working keyboards, on arbitrary keys (not just
the Ctrl/Alt keys). It does not appear to happen while in Sugar and
!MiniTamTam.
Mitch: I wonder if adding a "view-lossage" type of display to the
diagnostic would help figure out what's up. Do we get a key-down and then
no key-up? Do we get two key-downs? Do we get a serial garble? Etc.
See: http://dev.laptop.org/ticket/5658#comment:61
http://dev.laptop.org/ticket/5658#comment:65
http://dev.laptop.org/ticket/5658#comment:50
http://dev.laptop.org/ticket/5658#comment:45
http://dev.laptop.org/ticket/5658#comment:46
We have with #5658 a high priority and pervasive flaky-keyboard problem
(which seems to be hardware at this point). Since this seemingly
unrelated bug that shows up in the OFW keyboard diagnostic tends to
confuse and/or mask diagnosis of the pervasive problem, I raised the
priority of this bug.
--
Ticket URL: <http://dev.laptop.org/ticket/5772#comment:4>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system
More information about the Bugs
mailing list