You are not logged in.

Pages: 1

#1 2017-07-24 10:10:23

bbb1991
Member
Registered: 2017-05-03
Posts: 7
Website

[SOLVED] Keyboard not working after suspending

Hello everyone!
After suspending my keyboard not working. To work again need to reboot laptop after suspending.
Laptop:

Sony Vaio SVF1521K1RW

Journalctl log for suspending/wake up:

Jul 24 12:12:47 localhost polkitd[384]: Registered Authentication Agent for unix-process:1023:10537 (system bus name :1.102 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jul 24 12:12:47 localhost gnome-shell[417]: Screen lock is locked down, not locking
Jul 24 12:12:47 localhost polkitd[384]: Unregistered Authentication Agent for unix-process:1023:10537 (system bus name :1.102, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Jul 24 12:12:47 localhost org.gnome.Shell.desktop[417]: Window manager warning: Failed to set power save mode for output LVDS-1: Permission denied
Jul 24 12:12:47 localhost systemd[1]: Reached target Sleep.
Jul 24 12:12:47 localhost systemd[1]: Starting Suspend...
Jul 24 12:12:47 localhost systemd-sleep[1031]: Suspending system...
Jul 24 12:13:09 localhost kernel: PM: Syncing filesystems ... done.
Jul 24 12:13:09 localhost kernel: PM: Preparing system for sleep (mem)
Jul 24 12:13:09 localhost kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Jul 24 12:13:09 localhost kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Jul 24 12:13:09 localhost kernel: PM: Suspending system (mem)
Jul 24 12:13:09 localhost kernel: Suspending console(s) (use no_console_suspend to debug)
Jul 24 12:13:09 localhost kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jul 24 12:13:09 localhost kernel: sd 0:0:0:0: [sda] Stopping disk
Jul 24 12:13:09 localhost kernel: ACPI : EC: event blocked
Jul 24 12:13:09 localhost kernel: PM: suspend of devices complete after 374.375 msecs
Jul 24 12:13:09 localhost kernel: PM: late suspend of devices complete after 15.098 msecs
Jul 24 12:13:09 localhost kernel: ACPI : EC: interrupt blocked
Jul 24 12:13:09 localhost kernel: r8169 0000:0e:00.0: System wakeup enabled by ACPI
Jul 24 12:13:09 localhost kernel: ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
Jul 24 12:13:09 localhost kernel: ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
Jul 24 12:13:09 localhost kernel: xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
Jul 24 12:13:09 localhost kernel: PM: noirq suspend of devices complete after 16.751 msecs
Jul 24 12:13:09 localhost kernel: ACPI: Preparing to enter system sleep state S3
Jul 24 12:13:09 localhost kernel: ACPI : EC: EC stopped
Jul 24 12:13:09 localhost kernel: PM: Saving platform NVS memory
Jul 24 12:13:09 localhost kernel: Disabling non-boot CPUs ...
Jul 24 12:13:09 localhost kernel: smpboot: CPU 1 is now offline
Jul 24 12:13:09 localhost kernel: smpboot: CPU 2 is now offline
Jul 24 12:13:09 localhost kernel: smpboot: CPU 3 is now offline
Jul 24 12:13:09 localhost kernel: ACPI: Low-level resume complete
Jul 24 12:13:09 localhost kernel: ACPI : EC: EC started
Jul 24 12:13:09 localhost kernel: PM: Restoring platform NVS memory
Jul 24 12:13:09 localhost kernel: Suspended for 21.434 seconds
Jul 24 12:13:09 localhost kernel: Enabling non-boot CPUs ...
Jul 24 12:13:09 localhost kernel: x86: Booting SMP configuration:
Jul 24 12:13:09 localhost kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Jul 24 12:13:09 localhost kernel:  cache: parent cpu1 should not be sleeping
Jul 24 12:13:09 localhost kernel: CPU1 is up
Jul 24 12:13:09 localhost kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Jul 24 12:13:09 localhost kernel:  cache: parent cpu2 should not be sleeping
Jul 24 12:13:09 localhost kernel: CPU2 is up
Jul 24 12:13:09 localhost kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Jul 24 12:13:09 localhost kernel:  cache: parent cpu3 should not be sleeping
Jul 24 12:13:09 localhost kernel: CPU3 is up
Jul 24 12:13:09 localhost kernel: ACPI: Waking up from system sleep state S3
Jul 24 12:13:09 localhost kernel: ACPI : EC: interrupt unblocked
Jul 24 12:13:09 localhost kernel: ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 24 12:13:09 localhost kernel: xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
Jul 24 12:13:09 localhost kernel: ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 24 12:13:09 localhost kernel: PM: noirq resume of devices complete after 17.253 msecs
Jul 24 12:13:09 localhost kernel: PM: early resume of devices complete after 0.709 msecs
Jul 24 12:13:09 localhost kernel: ACPI : EC: event unblocked
Jul 24 12:13:09 localhost kernel: r8169 0000:0e:00.0: System wakeup disabled by ACPI
Jul 24 12:13:09 localhost kernel: ath: phy0: ASPM enabled: 0x42
Jul 24 12:13:09 localhost kernel: sd 0:0:0:0: [sda] Starting disk
Jul 24 12:13:09 localhost kernel: ACPI : button: The lid device is not compliant to SW_LID.
Jul 24 12:13:09 localhost kernel: mei_me 0000:00:16.0: Could not read IF version
Jul 24 12:13:09 localhost kernel: rtc_cmos 00:01: System wakeup disabled by ACPI
Jul 24 12:13:09 localhost kernel: r8169 0000:0e:00.0 enp14s0: link down
Jul 24 12:13:09 localhost kernel: PM: resume of devices complete after 118.781 msecs
Jul 24 12:13:09 localhost kernel: PM: Finishing wakeup.
Jul 24 12:13:09 localhost kernel: Restarting tasks ... done.
Jul 24 12:13:09 localhost kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul 24 12:13:09 localhost kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Jul 24 12:13:09 localhost kernel: ata5.00: configured for UDMA/133
Jul 24 12:13:09 localhost kernel: ata1.00: configured for UDMA/133
Jul 24 12:13:13 localhost systemd-sleep[1031]: System resumed.
Jul 24 12:13:13 localhost systemd[1]: Started Suspend.
Jul 24 12:13:13 localhost systemd[1]: sleep.target: Unit not needed anymore. Stopping.
Jul 24 12:13:13 localhost systemd[1]: Stopped target Sleep.
Jul 24 12:13:13 localhost systemd[1]: suspend.target: Bound to unit systemd-suspend.service, but unit isn't active.
Jul 24 12:13:13 localhost systemd[1]: Dependency failed for Suspend.
Jul 24 12:13:13 localhost systemd-logind[339]: Operation 'sleep' finished.
Jul 24 12:13:13 localhost systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
Jul 24 12:13:13 localhost org.gnome.Shell.desktop[417]: Window manager warning: Failed to set power save mode for output LVDS-1: Permission denied
Jul 24 12:13:24 localhost kernel: i8042: Can't write CTR while closing AUX port
Jul 24 12:13:24 localhost kernel: i8042: Can't reactivate AUX port
Jul 24 12:13:24 localhost /usr/lib/gdm/gdm-x-session[765]: (EE) SynPS/2 Synaptics TouchPad: Read error 19
Jul 24 12:13:24 localhost /usr/lib/gdm/gdm-x-session[765]: (EE) SynPS/2 Synaptics TouchPad: Read error 19
Jul 24 12:13:24 localhost kernel: atkbd serio0: Spurious ACK on isa0060/serio0. Some program might be trying to access hardware directly.
Jul 24 12:13:24 localhost /usr/lib/gdm/gdm-x-session[765]: (EE) SynPS/2 Synaptics TouchPad: Read error 19
Jul 24 12:13:24 localhost /usr/lib/gdm/gdm-x-session[765]: (EE) SynPS/2 Synaptics TouchPad: Read error 19
Jul 24 12:13:24 localhost /usr/lib/gdm/gdm-x-session[765]: (II) config/udev: removing device SynPS/2 Synaptics TouchPad
Jul 24 12:13:24 localhost /usr/lib/gdm/gdm-x-session[765]: (II) UnloadModule: "synaptics"
Jul 24 12:13:24 localhost /usr/lib/gdm/gdm-x-session[765]: (II) systemd-logind: releasing fd for 13:73
Jul 24 12:13:24 localhost kernel: psmouse serio1: synaptics: queried max coordinates: x [..5666], y [..4710]
Jul 24 12:13:24 localhost kernel: psmouse serio1: synaptics: queried min coordinates: x [1276..], y [1144..]
Jul 24 12:13:25 localhost kernel: psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xd00123/0x840300/0x126800/0x0, board id: 2739, fw id: 1366777
Jul 24 12:13:25 localhost kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input15
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event9)
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) SynPS/2 Synaptics TouchPad: Applying InputClass "libinput touchpad catchall"
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (EE) systemd-logind: failed to take device /dev/input/event9: No such device
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) SynPS/2 Synaptics TouchPad: always reports core events
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) Option "Device" "/dev/input/event9"
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (EE) synaptics: SynPS/2 Synaptics TouchPad: Synaptics driver unable to detect protocol
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (EE) PreInit returned 11 for "SynPS/2 Synaptics TouchPad"
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (II) UnloadModule: "synaptics"
Jul 24 12:13:25 localhost kernel: psmouse serio1: synaptics: queried max coordinates: x [..5666], y [..4710]
Jul 24 12:13:25 localhost kernel: psmouse serio1: synaptics: queried min coordinates: x [1276..], y [1144..]
Jul 24 12:13:25 localhost kernel: psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xd00123/0x840300/0x126800/0x0, board id: 2739, fw id: 1366777
Jul 24 12:13:25 localhost kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input17
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event9)
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) SynPS/2 Synaptics TouchPad: Applying InputClass "libinput touchpad catchall"
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (II) systemd-logind: got fd for /dev/input/event9 13:73 fd 34 paused 0
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) SynPS/2 Synaptics TouchPad: always reports core events
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) Option "Device" "/dev/input/event9"
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (II) synaptics: SynPS/2 Synaptics TouchPad: found clickpad property
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1276 - 5666 (res 43)
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1144 - 4710 (res 58)
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left double triple
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) SynPS/2 Synaptics TouchPad: always reports core events
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input17/event9"
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 13)
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.035
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
Jul 24 12:13:25 localhost /usr/lib/gdm/gdm-x-session[765]: (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found

System info:

 admin@localhost
 OS: Arch Linux 
 Kernel: x86_64 Linux 4.11.9-1-ARCH
 Uptime: 20m
 Packages: 987
 Shell: zsh 5.3.1
 Resolution: 1366x768
 WM: Awesome
 WM Theme: default
 CPU: Intel Core i3-3217U @ 4x 1.8GHz [46.0°C]
 GPU: intel
 RAM: 2194MiB / 7869MiB

Will happy for any suggestion. Thanks!

Last edited by bbb1991 (2017-09-06 13:58:59)

Offline

#2 2017-07-24 12:04:07

seth
Member
Registered: 2012-09-03
Posts: 50,929

Re: [SOLVED] Keyboard not working after suspending

* Why is there gnome-shell and org.gnome.Shell.desktop processes if you're using awesome?
* Elaborate on "not working" - can you still use it to switch the VT or ctrl+alt+backspace (assuming this is activated in your xorg config)
* There seems to be trouble with the touchpad as well, does it remain to work after the wake up?
* Get gdm out of the equation, try the behavior with startx/xinit.
* Please provide your xorg log (incl. the S3 wakeup, ie. in doubt from the former session), see https://wiki.archlinux.org/index.php/Xorg#General
* Fix your hostname! https://wiki.archlinux.org/index.php/Ne … e_hostname - notably along networkmanager, "localhost" is a safe way to break your X11 session.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2017-09-06 14:05:17

bbb1991
Member
Registered: 2017-05-03
Posts: 7
Website

Re: [SOLVED] Keyboard not working after suspending

The problem on driver i8042. This bug on Linux Kernel <= 4.10 and issue still open (current kernel version 4.13).
Issue on Kernel bugtracker: https://bugzilla.kernel.org/show_bug.cgi?id=195471
I've installed kernel 4.9 LTS and now everything is works fine.

Last edited by bbb1991 (2017-09-06 14:17:47)

Offline

#4 2017-11-25 21:42:57

zyp001a
Member
Registered: 2017-11-25
Posts: 1

Re: [SOLVED] Keyboard not working after suspending

Thank you, bb1991. I'm using Sony Vaio SVE1512S7C, linux-lts package (kernel 4.9 LTS ) works perfect for me to solve the problem. For newbie, remember to add entries to boot loader, for me: grub-mkconfig -o /boot/grub/grub.conf

Last edited by zyp001a (2017-11-25 21:43:38)

Offline

#5 2020-11-23 16:57:24

dreieck
Member
Registered: 2012-10-08
Posts: 56

Re: [SOLVED] Keyboard not working after suspending

I had same problem on Sony Vaio SVE 1512 with linux 5.9.3: After suspend to ram, keyboard stopped working; doing a suspend to disk afterwards made it work again.

Solution was to load the module `atkbd` with the option `reset=1`, or if it is statically compiled in the kernel adding `atkbd.reset=1` to the boot command line.

(Idea for this from [here](https://askubuntu.com/questions/38797/k … -ram-sleep).)

Offline

Pages: 1

Board footer

Powered by FluxBB