[Bug 412220] New: Keyboard blocked (X) after suspend to RAM on DELL inspiron 1525 and opensuse 11.0
https://bugzilla.novell.com/show_bug.cgi?id=412220 Summary: Keyboard blocked (X) after suspend to RAM on DELL inspiron 1525 and opensuse 11.0 Product: openSUSE 11.0 Version: Final Platform: i586 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: klaus.thoennissen@web.de QAContact: qa@suse.de Found By: Customer After installing opensuse 11.0 on a DELL Notebook inspiron 1525, suspend to disk works out of the context-menu of Kpowersave, suspend to RAM by using one of the following commands as superuser in konsole: s2ram -f -p -m s2ram -f -p -s s2ram -f -s s2ram -f -p Using the suspend to RAM-Menu of Kpowersave leads to an error (s2ram: Machine is unknown). But the problem is: After using s2ram out of the Konsole and restart the restored system (X), the keyboard is blocked in most cases of s2ram and maybe (not reproduced) sometimes of s2disk. The GUI is presented, the system can be operated by using the USB-mouse, but any key-in fails, for instance you are not able to key-in a username and password in the screensaver-window. System used: opensuse 11.0 version 2.6.25.9-0.2-pae KDE-Version 3.5.9 "release 49.1" DELL BIOS-Version A11 CPU Intel Pentium Dual T2390 1,86 GHz Display-controller Intel Mobile GM965/GL960 Integrated Graphics Controller AT translated Set 2 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 chrubis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c1 Cyril Hrubis <chrubis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |sndirsch@novell.com --- Comment #1 from Cyril Hrubis <chrubis@novell.com> 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 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c2 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|sndirsch@novell.com | --- Comment #2 from Stefan Dirsch <sndirsch@novell.com> 2008-07-25 12:54:16 MDT --- Don't know yet. Please reassign first to Mobile Devices. They know these issues best. -- 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 <chrubis@novell.com> 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 Cyril Hrubis <chrubis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |zoz@novell.com Status|ASSIGNED |NEW -- 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 <dkukawka@novell.com> 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 seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c3 Stefan Seyfried <seife@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #3 from Stefan Seyfried <seife@novell.com> 2008-08-18 03:27:02 MDT --- Probably a kernel issue. See bug 351119, especially this comment: https://bugzilla.novell.com/show_bug.cgi?id=351119#c31 for a possible workaround. Do you have a second machine available so that you can test stuff via network/ssh if the keyboard is blocked? -- 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 <klaus.thoennissen@web.de> 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 seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c5 --- Comment #5 from Stefan Seyfried <seife@novell.com> 2008-08-20 04:03:12 MDT --- Ok, it might actually really be different. Please try to suspend until the keyboard stops working, then log in via ssh and do a "chvt 1" to switch to the first text console. Check if the keyboard works there. If the keyboard still works in text mode but not in X, it looks like a X problem. In that case, restart X ("rcxdm restart"), I guess that the keyboard will then work again in X, but we will see. If the keyboard also stops working in text mode, then it might be similar to bug 351119 and issuing echo -n "i8042" > /sys/bus/platform/drivers/i8042/unbind echo -n "i8042" > /sys/bus/platform/drivers/i8042/bind might help. -- 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 <klaus.thoennissen@web.de> 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 seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c7 Stefan Seyfried <seife@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seife@novell.com AssignedTo|seife@novell.com |sndirsch@novell.com Status|ASSIGNED |NEW Component|Mobile Devices |X.Org QAContact|qa@suse.de |xorg-maintainer-bugs@forge.provo.novell.com --- Comment #7 from Stefan Seyfried <seife@novell.com> 2008-08-20 11:58:34 MDT --- "chvt 1" needs root privileges, so this is why the error messages showed up. Anyway, since restarting the X server makes the keyboard work again, I suspect that this is a X server bug => reassigning. -- 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 <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |klaus.thoennissen@web.de --- Comment #8 from Stefan Dirsch <sndirsch@novell.com> 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 sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c9 --- Comment #9 from Stefan Dirsch <sndirsch@novell.com> 2008-08-21 03:12:21 MDT --- And also try, if "chvt 1; chvt 7" gives you the keyboard back in X. -- 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 <klaus.thoennissen@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|klaus.thoennissen@web.de | --- Comment #10 from Klaus Thönnißen <klaus.thoennissen@web.de> 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#c11 --- Comment #11 from Stefan Seyfried <seife@novell.com> 2008-08-21 15:29:15 MDT --- (In reply to comment #10 from Klaus Thönnißen)
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
now please try the following (still on the ssh session, as root): echo -n "i8042" > /sys/bus/platform/drivers/i8042/unbind echo -n "i8042" > /sys/bus/platform/drivers/i8042/bind now check, if the keyboard works again. If this helps, the bug is at least similar to bug 351119. -- 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 <seife@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jkosina@novell.com --- Comment #12 from Stefan Seyfried <seife@novell.com> 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 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |klaus.thoennissen@web.de -- 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 <klaus.thoennissen@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|klaus.thoennissen@web.de | --- Comment #13 from Klaus Thönnißen <klaus.thoennissen@web.de> 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 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c14 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|sndirsch@novell.com |zoz@novell.com Component|X.Org |Mobile Devices QAContact|xorg-maintainer-bugs@forge.provo.novell.com |qa@suse.de --- Comment #14 from Stefan Dirsch <sndirsch@novell.com> 2008-08-22 06:38:05 MDT --- Ok. Looks like this is no longer a X issue. -- 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 <sndirsch@novell.com> 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 seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c15 Stefan Seyfried <seife@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|seife@novell.com |jkosina@novell.com Component|Mobile Devices |Kernel --- Comment #15 from Stefan Seyfried <seife@novell.com> 2008-08-22 07:47:39 MDT --- Correct, it is a kernel issue. Klaus, even if the debug-hooks helps you, this might be just luck. What you probably want to do is to remove the debug-hook and instead create a hook "99kbd-reinit" (actually, the name does not really matter) that just does ------- #!/bin/bash case "$1" in thaw|resume) echo -n "i8042" > /sys/bus/platform/drivers/i8042/unbind echo -n "i8042" > /sys/bus/platform/drivers/i8042/bind ;; *) ;; esac ------- On the other hand, the amount of messages should not pose a big problem since the syslog rotation should rotate the logfile once it gets too big. Please also make sure that you have the kernel mentioned in https://bugzilla.novell.com/show_bug.cgi?id=351119#c36 (or newer) already installed, you should have gotten it via the online update. Jiri, please take over, I can not decide if this is a duplicate of bug 351119. https://bugzilla.novell.com/show_bug.cgi?id=351119 -- 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 <klaus.thoennissen@web.de> 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 aspiers@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c17 Adam Spiers <aspiers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aspiers@novell.com --- Comment #17 from Adam Spiers <aspiers@novell.com> 2008-09-16 10:42:36 MDT --- I also see this keyboard blocking issue with 2.6.25.11-0.1-default x86_64 on a Dell Latitude D630. I have ssh access from another machine and managed to get the keyboard back somehow (I think it might have been the chvt 1 which did it because after Alt-F7 I had a working X display again). I am currently patching to the latest kernel 2.6.25.16-1.1_0.1 and will test some more. Very keen to help debug if necessary! P.S. I have not yet patched the BIOS so am still on an old factory BIOS version. -- 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 <jkosina@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |klaus.thoennissen@web.de --- Comment #18 from Jiri Kosina <jkosina@novell.com> 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#c19 Klaus Thönnißen <klaus.thoennissen@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|klaus.thoennissen@web.de | --- Comment #19 from Klaus Thönnißen <klaus.thoennissen@web.de> 2008-09-21 10:03:20 MDT --- Created an attachment (id=240746) --> (https://bugzilla.novell.com/attachment.cgi?id=240746) dmesg-output belongs to comment#19 -- 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 <klaus.thoennissen@web.de> 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 jkosina@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c21 Jiri Kosina <jkosina@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |klaus.thoennissen@web.de --- Comment #21 from Jiri Kosina <jkosina@novell.com> 2008-10-13 09:07:48 MDT --- Does booting with i8042.reset kernel parameter also mitigate the problem? Thanks. -- 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 <klaus.thoennissen@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|klaus.thoennissen@web.de | --- Comment #22 from Klaus Thönnißen <klaus.thoennissen@web.de> 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 Jiri Kosina <jkosina@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Priority|P5 - None |P3 - Medium -- 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 <nagyt@hu.inter.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nagyt@hu.inter.net --- Comment #23 from Tibor Nagy <nagyt@hu.inter.net> 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.
https://bugzilla.novell.com/show_bug.cgi?id=412220 User jkosina@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=412220#c24 Jiri Kosina <jkosina@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |klaus.thoennissen@web.de --- Comment #24 from Jiri Kosina <jkosina@novell.com> 2009-02-06 05:31:33 MST --- Please attach dmesg output of resume during which the keyboard is failing with 'i8042.debug' kernel parameter in place. Thanks. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com