https://bugzilla.novell.com/show_bug.cgi?id=412220 User chrubis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c1 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |sndirsch@novell.com --- Comment #1 from Cyril Hrubis 2008-07-25 11:53:59 MDT --- Stephan is this problem likely in X or in kernel? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=412220 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Mobile Devices -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=412220 Danny Kukawka changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dkukawka@novell.com AssignedTo|zoz@novell.com |seife@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=412220 User klaus.thoennissen@web.de added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c4 --- Comment #4 from Klaus Thönnißen 2008-08-20 00:04:53 MDT --- Yes I have, and I have tested the SSH-connection from my tower-PC to th Dell 1525-Notebook in case of the keyboard-failure - it was OK and i could halt the system remote. Please give me some information which commands I should use in your sense of "test stuff". Reading the comments of bug 351119 it seems for me that my situation is a little bit different, particularly because the string"i8042" doesn't appear in /var/log/messages. For this reason I made the following tests to get some more informations: suspend to disk via kpowersave: 3 times OK, in one case after resume the system was frozen when displaying the screensaver suspend to ram via console-command s2ram -f -p: Test 1: OK Test 2: OK Test 3: resumed, but keyboard blocked; USB-mouse and touchpad OK, KDE-restart by mouse (closing actual session), log-in again, keyboard now is OK Test 4: same as Test 3 Test 5: resumed, but keyboard blocked; USB-mouse and touchpad OK, reboot by mouse Test 6: OK Test 7: resumed, but keyboard blocked; USB-mouse and touchpad OK; waited too long, so screensaver was active and prevented using the menu-items for KDE-restart etc. (keying-in of password is not possible), then access from my tower-pc via ssh and halt the system Thanks for your hint concerning temporary debug-mode, but I didn't test it until now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=412220 User klaus.thoennissen@web.de added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c6 --- Comment #6 from Klaus Thönnißen 2008-08-20 09:33:23 MDT --- Now I have performed the following Tests: Test 1: boot the notebook, konsole, su - and s2ram -f -p after resume the window is restored, but keyboard blocked ssh from tower-pc and chvt 1, error-message: Konnte keinen Dateibezeichner finden, der auf die Konsole verweist in Konsole-Window of the notebook the following messages are presented: Switching from vt7 to vt1 fbcon fb0 state 1 Calling do_post fbcon fb0 state 0 switching back to vt7 keyboard of notebook doesn't work then via ssh-connection: su - and rcxdm restart messages: Shutting down service kdm Starting service kdm Notebook-display presents the KDE-login-window and keyboard works fine Test2: Reboot Notebook konsole, su - and s2ram -f -p after resume the window is restored, but keyboard blocked and in konsole-window the messages of Test1 are presented! (Switching ... back to vt7) ssh from tower-pc and chvt 1, error-message: Konnte keinen Dateibezeichner finden, der auf die Konsole verweist then via ssh-connection: su - and rcxdm restart Notebook-display presents the KDE-login-window and keyboard works fine Login on Notebook and again konsole, su - and s2ram -f -p after resume: the window is restored, but keyboard blocked then ssh from tower-pc and chvt 1: this time OK without the above mentioned error-messages and the notebook-display presents vt1 with login-prompt via ssh rcxdm restart Notebook-display presents the KDE-login-window and keyboard works fine Test3: Reboot Notebook konsole, su - and s2ram -f -p after resume the window is restored and in konsole-window the messages of Test1 are presented!! and keyboard is OK again konsole, su - and s2ram -f -p after resume the window is restored and in konsole-window the messages of Test1 are presented!! and keyboard is blocked ssh from tower-pc and chvt 1, error-message: Konnte keinen Dateibezeichner finden, der auf die Konsole verweist then via ssh-connection: su - and rcxdm restart Notebook-display presents the KDE-login-window and keyboard works fine Login on Notebook and konsole, su - and s2ram -f -p after resume the window is restored and in konsole-window the messages of Test1 are presented!! and keyboard is OK -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=412220 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c8 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |klaus.thoennissen@web.de --- Comment #8 from Stefan Dirsch 2008-08-20 20:14:54 MDT --- Please run "chvt 1" as root (in ssh) to verify that keyboard really works on the linux console right after resume from suspend to ram. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=412220 User klaus.thoennissen@web.de added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c10 Klaus Thönnißen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|klaus.thoennissen@web.de | --- Comment #10 from Klaus Thönnißen 2008-08-21 14:24:18 MDT --- Next Test: Boot Notebook, konsole, su - and s2ram -f -p after resume the window is restored and keyboard is blocked On Tower-PC konsole, ssh username@ip-adress, connection OK su - chvt 1 then on notebook-display the login-prompt is presented, but keyboard is also blocked in vt1 then on tower-PC konsole, chvt 7 now on notebook-PC the graphic is presented but keyboard doesn't work then on tower-PC konsole, rcxdm restart, messages: Shutting down service kdm Starting service kdm then on notebook-PC the KDE-login-window is presented and keyboard works -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=412220 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c12 Stefan Seyfried changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jkosina@novell.com --- Comment #12 from Stefan Seyfried 2008-08-21 15:31:41 MDT --- Jiri, do you maybe have an idea what might be going wrong here and what we could do to find out? I'm quickly running out of ideas... :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=412220 User klaus.thoennissen@web.de added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c13 Klaus Thönnißen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|klaus.thoennissen@web.de | --- Comment #13 from Klaus Thönnißen 2008-08-22 06:13:18 MDT --- Next test Boot notebook, konsole, su - and s2ram -f -p after resume the window is restored and keyboard is blocked On tower-PC konsole, ssh username@ip-adress, connection OK su - and echo -n "i8042" > /sys/bus/platform/drivers/i8042/unbind echo -n "i8042" > /sys/bus/platform/drivers/i8042/bind after that the keyboard on notebook-PC works again in all applications (X) I repeated the suspend-command on notebook-PC and the two echo-commands over SSH, and again: the locked keyboard was reactivated. ----------------------------------------------- In next step I tried the hint mentioned in bug 351119 Comment 31: I stored the script 99ZZi8042debug to /etc/pm/sleep.d/ After reboot suspend to RAM worked multiple times without keyboard-blocking. Maybe that this is a good way for me to solve my problem. Thank you very much for your help. Please could you give me some tips which directories or files I should observe for avoiding file-system-problems (great amount of messages produced by debug-mode and afterwards file-system-full). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=412220 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@novell.com AssignedTo|zoz@novell.com |seife@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=412220 User klaus.thoennissen@web.de added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c16 --- Comment #16 from Klaus Thönnißen 2008-08-22 11:28:35 MDT --- Hello Stefan, I deleted the file 99ZZi8042debug and stored the script 99kbd-reinit in the directory /etc/pm/sleep.d/ But after reboot of the notebook-PC, suspend to ram and resume the keyboard was blocked again; by using the commands (via SSH from tower-PC) echo -n "i8042" > /sys/bus/platform/drivers/i8042/unbind echo -n "i8042" > /sys/bus/platform/drivers/i8042/bind I could reactivate the keyboard. Now I deleted the file 99kbd-reinit and restored the file 99ZZi8042debug in the directory /etc/pm/sleep.d/ In this case after reboot of notebook, suspend to ram and resume the keyboard works fine. P.S.: My actual kernel-version is: uname -r: 2.6.25.9-0.2-pae -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=412220 User jkosina@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c18 Jiri Kosina changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |klaus.thoennissen@web.de --- Comment #18 from Jiri Kosina 2008-09-19 11:30:26 MDT --- Could you please provide the dmesg output of the failing case when i8042.debug is used? (please be aware that this way it is able to see what you have been typing on your keyboard). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=412220 User klaus.thoennissen@web.de added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c20 --- Comment #20 from Klaus Thönnißen 2008-09-21 10:13:10 MDT --- Hello Jiri, this is the report which I wanted to commit together with the attachment in comment#19, but I didn't find the correct way to use - anyway - here are the steps I did before adding the dmesg-output in comment#19: To get the information you need I tried again to suspend to RAM while the script 99ZZi8042debug was stored in the directory /etc/pm/sleep.d - but in contrast to comment#16 - after suspension by s2ram -f -p and resume the keyboard was blocked now. Then I used the commands (via SSH from my tower-PC) echo -n "i8042" > /sys/bus/platform/drivers/i8042/unbind and echo -n "i8042" > /sys/bus/platform/drivers/i8042/bind I could reactivate the keyboard; then I provided the attached dmesg-output in the file c18_kosina.txt -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=412220 User klaus.thoennissen@web.de added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c22 Klaus Thönnißen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|klaus.thoennissen@web.de | --- Comment #22 from Klaus Thönnißen 2008-10-14 10:18:33 MDT --- Before using the mentioned boot-parameter I tested the behavior of s2ram. While 99Z99ZZi8042debug was active the first s2ram -f -p leads to a resume with working keyboard!!!, but the second time I suspended with s2ram -f -p the keyboard was blocked again. After shutdown by keypad and gui, I temporarily used the boot-parameter i8042.reset and rebooted. After this the situation was exactly the same as without boot-parameter i8042.reset: The first resume after s2ram -f -p was OK (keyboard not blocked), the second resume leads to the blocked-keyboard-situation. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=412220 User nagyt@hu.inter.net added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c23 Tibor Nagy changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nagyt@hu.inter.net --- Comment #23 from Tibor Nagy 2009-01-30 10:40:37 MST --- I have similar problem on OpenSuSe 11.1 X86_64 on my laptop: HP Pavilion dv5 1120 eh. (2.1 GHz AMD Athlon X2) As default "suspend to ram" does not work, s2ram doesn't know the machine. I tried different s2ram options and determined that "-f -a 3" works more or less, but after resume the keyboard, the touchpad and even the network does not work. If I connect an USB mouse and keyboard to the laptop I can work. Entering the two commands above manually echo -n "i8042" > /sys/bus/platform/drivers/i8042/unbind echo -n "i8042" > /sys/bus/platform/drivers/i8042/bind i could reactivate the keyboard. But the touch pad and the network doesn't work even after an "rcnetwork restart" command. Note, that I tried to write the commands above into /etc/pm/sleep.d, but it did not help. This behavior is the same with the default SuSe kernel (2.6.27.7-9) and also with last stable the kernel 2.6.28.2. Should I open an other bug (operating system is different from this one)? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.