Bug#662895: i8042: keys get stuck and keyboard stops responding

To: Jonathan Nieder <jrnieder@gmail.com>
Cc: 662895@bugs.debian.org
Subject: Bug#662895: i8042: keys get stuck and keyboard stops responding
From: GSR <gsr.bugs@infernal-iceberg.com>
Date: Tue, 20 Mar 2012 02:03:46 +0100
Message-id: <[🔎] 20120320010346.GA27298@fortress.battleship>
Reply-to: GSR <gsr.bugs@infernal-iceberg.com>, 662895@bugs.debian.org
In-reply-to: <[🔎] 20120318011823.GD2042@burratino>
References: <[🔎] 20120307040835.GA13876@fortress.battleship> <[🔎] 20120316223433.GA31834@burratino> <[🔎] 20120317233144.GA5462@fortress.battleship> <[🔎] 20120318011823.GD2042@burratino>

Hi,
jrnieder@gmail.com (2012-03-17 at 2018.23 -0500):
[...]

So far no issues after 3 sessions with the asus_atk0110 module
blacklisted. Probably I will try 2.6.32 now and see if the hangs
happen then.

GSR

Reply to:

References:
- Bug#662895: linux-image-3.2.0-1-amd64: keys get stuck and keyboard stops responding
  - From: GSR <gsr.bugs@infernal-iceberg.com>
- Bug#662895: i8042: keys get stuck and keyboard stops responding
  - From: Jonathan Nieder <jrnieder@gmail.com>
- Bug#662895: i8042: keys get stuck and keyboard stops responding
  - From: GSR <gsr.bugs@infernal-iceberg.com>
- Bug#662895: i8042: keys get stuck and keyboard stops responding
  - From: Jonathan Nieder <jrnieder@gmail.com>

Prev by Date: ath5k driver bug in Squeeze kernel
Next by Date: Processed: Re: Bug#664287: Fails to forcibly merge an old fixed bug with a current unfixed one (The 'fixed' parameter ("HASH(0x299a550)") to Debbugs::Control::set_fixed was a 'hashref', which is not one of the allowed types: scalar arrayref)
Previous by thread: Processed (with 1 errors): Re: i8042: keys get stuck and keyboard stops responding
Next by thread: Bug#662895: i8042: keys get stuck and keyboard stops responding
Index(es):
- Date
- Thread