Bug#575660: With last kernels, terminal/console processing getting worse.
I noticed that the i8042 interrupt counter is 1, not 0. As if it got incremented once. I suspect the processing of key presses are some how messed up. Can you point some reasonable points (file name, perhaps a function and line number) in the source to insert a printk, just to see weather each key press produces a message at those points? Must I compile the entire kernel to get those printk into the binary? _ Hotmail: Trusted email with powerful SPAM protection. https://signup.live.com/signup.aspx?id=60969 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575660: With last kernels, terminal/console processing getting worse.
On Wed, 2010-03-31 at 20:04 +0200, Regid Ichira wrote: I noticed that the i8042 interrupt counter is 1, not 0. As if it got incremented once. I suspect the processing of key presses are some how messed up. Can you point some reasonable points (file name, perhaps a function and line number) in the source to insert a printk, just to see weather each key press produces a message at those points? The relevant source file is drivers/input/keyboard/atkbd.c. Must I compile the entire kernel to get those printk into the binary? I think so. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
