On Thu, Oct 15, 2009 at 11:13:37AM -0700, Dmitry Torokhov wrote: > On Thu, Oct 15, 2009 at 07:24:16PM +0200, Éric Piel wrote: > > Op 14-10-09 04:05, Dmitry Torokhov schreef: > > > On Tue, Oct 13, 2009 at 11:52:19AM +0200, Éric Piel wrote: > > >>> Could you please try and let me know if unloading at suspend and > > >>> reloading after resume atkbd and/or psmouse drivers and leaving i8042 > > >>> alone "fixes" the issue? > > >>> > > >> Unloading the modules before suspend and reloading them after works > > >> around the issue, indeed. > > >> > > > > > > Do both of them need to be reloaded? Or only one (my guess psmouse) is > > > enough. Hmm, this is HP laptop so it most likely has Synaptics touchpad. > > > I wonder what happens if you force it to bare PS/2 protocol (or maybe > > > Intellimouse)... Try adding "option psmouse proto=imps" and > > > "option psmouse proto=bare" and suspend/resume. > > Sorry for taking some time to answer back. The keyboard fails to come > > back only on the first suspend-resume (the next suspends, the keyboard > > comes back fine). So I need to reboot the computer for every single test. > > > > So far, what I can tell is that once the keyboard is not working > > anymore, just unloading and reloading atkbd fixes the problem. Attached > > is a dmesg log from just before supsending to after resume. The keyboard > > doesn't work anymore but the touchpad do. The lines at the very end of > > the log correspond to keypresses: although the keyboard doesn't work, > > there are still 3 interrupt per keypress generated: > > > > drivers/input/serio/i8042.c: 1c <- i8042 (interrupt, 0, 1) [320670] > > drivers/input/serio/i8042.c: f0 <- i8042 (interrupt, 0, 1) [320751] > > drivers/input/serio/i8042.c: 1c <- i8042 (interrupt, 0, 1) [320753] > > > > That's all the date for now. I'll test your questions about psmouse > > later on, and report back. > > > > It lokks like the keyboard controller switched from translated to > non-translated mode: '1c' is make code and 'f0 1c' is break (aka > release) code. > > Could you tell me how the keyboard indentified (in dmesg) after fresh > boot and after you do the bind/unbind trick on the older kernel? > BTW, do you have i8042.reset parameyer on your command line? What happens if you remove it? -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
