search

raphael / linux-samus

Linux 4.16 on Chromebook Pixel 2015
GNU General Public License v2.0
181 stars 36 forks source link

Trackpad and touchscreen problems after hibernation #219

Closed christianbundy closed 4 years ago

christianbundy commented 4 years ago

Strange, the backlight came back after a couple of reboots.

Since we seem to have a very similar setup on our Pixels, I was wondering if you have experimented with hibernation? I have a LUKS encrypted root partition with a swapfile on that partition and set up hibernation following this article. When executing systemctl hibernate, the system goes into hibernation successfully and boots back into its hibernated state after entering the decryption password. However, the trackpad and touchscreen stops working and only comes back to life after rebooting the system (see log below). Have you encountered this issue as well?

Nov 05 22:16:45 pixel systemd[1]: Starting Hibernate...
Nov 05 22:16:45 pixel kdeinit5[600]: ktp-kded-module: "screen-saver-away" presence change request: "away" ""
Nov 05 22:16:45 pixel kdeinit5[600]: ktp-kded-module: plugin queue activation: "away" ""
Nov 05 22:16:45 pixel systemd-sleep[894]: Suspending system...
Nov 05 22:16:45 pixel kernel: PM: hibernation entry
Nov 05 22:16:45 pixel kernel: PM: Syncing filesystems ... 
Nov 05 22:18:02 pixel kernel: PM: done.
Nov 05 22:18:02 pixel kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
Nov 05 22:18:02 pixel kernel: OOM killer disabled.
Nov 05 22:18:02 pixel kernel: PM: Marking nosave pages: [mem 0x00000000-0x00000fff]
Nov 05 22:18:02 pixel kernel: PM: Marking nosave pages: [mem 0x0009f000-0x000fffff]
Nov 05 22:18:02 pixel kernel: PM: Marking nosave pages: [mem 0x7ce28000-0xffffffff]
Nov 05 22:18:02 pixel kernel: PM: Basic memory bitmaps created
Nov 05 22:18:02 pixel kernel: PM: Preallocating image memory... done (allocated 546922 pages)
Nov 05 22:18:02 pixel kernel: PM: Allocated 2187688 kbytes in 0.32 seconds (6836.52 MB/s)
Nov 05 22:18:02 pixel kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Nov 05 22:18:02 pixel kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Nov 05 22:18:02 pixel kernel: wlp1s0: deauthenticating from 12:80:63:33:75:d9 by local choice (Reason: 3=DEAUTH_LEAVING)
Nov 05 22:18:02 pixel kernel: ACPI: EC: interrupt blocked
Nov 05 22:18:02 pixel kernel: ACPI: Preparing to enter system sleep state S4
Nov 05 22:18:02 pixel kernel: ACPI: EC: event blocked
Nov 05 22:18:02 pixel kernel: ACPI: EC: EC stopped
Nov 05 22:18:02 pixel kernel: PM: Saving platform NVS memory
Nov 05 22:18:02 pixel kernel: Disabling non-boot CPUs ...
Nov 05 22:18:02 pixel kernel: smpboot: CPU 1 is now offline
Nov 05 22:18:02 pixel kernel: smpboot: CPU 2 is now offline
Nov 05 22:18:02 pixel kernel: smpboot: CPU 3 is now offline
Nov 05 22:18:02 pixel kernel: PM: Creating hibernation image:
Nov 05 22:18:02 pixel kernel: PM: Need to copy 544475 pages
Nov 05 22:18:02 pixel kernel: PM: Normal pages needed: 544475 + 1024, available pages: 3632567
Nov 05 22:18:02 pixel kernel: PM: Restoring platform NVS memory
Nov 05 22:18:02 pixel kernel: ACPI: EC: EC started
Nov 05 22:18:02 pixel kernel: Enabling non-boot CPUs ...
Nov 05 22:18:02 pixel kernel: x86: Booting SMP configuration:
Nov 05 22:18:02 pixel kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Nov 05 22:18:02 pixel kernel:  cache: parent cpu1 should not be sleeping
Nov 05 22:18:02 pixel kernel: CPU1 is up
Nov 05 22:18:02 pixel kernel: smpboot: Booting Node 0 Processor 2 APIC 0x3
Nov 05 22:18:02 pixel kernel:  cache: parent cpu2 should not be sleeping
Nov 05 22:18:02 pixel kernel: CPU2 is up
Nov 05 22:18:02 pixel kernel: smpboot: Booting Node 0 Processor 3 APIC 0x2
Nov 05 22:18:02 pixel kernel:  cache: parent cpu3 should not be sleeping
Nov 05 22:18:02 pixel kernel: CPU3 is up
Nov 05 22:18:02 pixel kernel: ACPI: Waking up from system sleep state S4
Nov 05 22:18:02 pixel kernel: ACPI: EC: interrupt unblocked
Nov 05 22:18:02 pixel kernel: i2c_designware INT3433:00: timeout waiting for bus ready
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0001:01: __mxt_read_reg: i2c transfer failed (-110)
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0001:01: Failed to read T44 and T5 (-110)
Nov 05 22:18:02 pixel kernel: i2c_designware INT3433:00: timeout waiting for bus ready
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0001:01: __mxt_read_reg: i2c transfer failed (-110)
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0001:01: Failed to read T44 and T5 (-110)
Nov 05 22:18:02 pixel kernel: i2c_designware INT3432:00: timeout in disabling adapter
Nov 05 22:18:02 pixel kernel: i2c_designware INT3433:00: timeout waiting for bus ready
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0001:01: __mxt_read_reg: i2c transfer failed (-110)
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0001:01: Failed to read T44 and T5 (-110)
Nov 05 22:18:02 pixel kernel: i2c_designware INT3433:00: timeout waiting for bus ready
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0001:01: __mxt_read_reg: i2c transfer failed (-110)
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0001:01: Failed to read T44 and T5 (-110)
Nov 05 22:18:02 pixel kernel: i2c_designware INT3433:00: timeout in disabling adapter
Nov 05 22:18:02 pixel kernel: i2c_designware INT3433:00: timeout waiting for bus ready
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0001:01: __mxt_read_reg: i2c transfer failed (-110)
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0001:01: Failed to read T44 and T5 (-110)
Nov 05 22:18:02 pixel kernel: i2c_designware INT3433:00: timeout waiting for bus ready
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0001:01: __mxt_read_reg: i2c transfer failed (-110)
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0001:01: Failed to read T44 and T5 (-110)
Nov 05 22:18:02 pixel kernel: i2c_designware INT3433:00: timeout waiting for bus ready
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0001:01: __mxt_read_reg: i2c transfer failed (-110)
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0001:01: Failed to read T44 and T5 (-110)
Nov 05 22:18:02 pixel kernel: usb usb1: root hub lost power or was reset
Nov 05 22:18:02 pixel kernel: usb usb2: root hub lost power or was reset
Nov 05 22:18:02 pixel kernel: ACPI: EC: event unblocked
Nov 05 22:18:02 pixel kernel: ACPI: button: The lid device is not compliant to SW_LID.
Nov 05 22:18:02 pixel kernel: sd 0:0:0:0: [sda] Starting disk
Nov 05 22:18:02 pixel kernel: i2c_designware INT3433:00: timeout waiting for bus ready
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0001:01: __mxt_read_reg: i2c transfer failed (-110)
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0001:01: Failed to read T44 and T5 (-110)
Nov 05 22:18:02 pixel kernel: i2c_designware INT3432:00: timeout waiting for bus ready
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0000:01: __mxt_write_reg: i2c send failed (-110)
Nov 05 22:18:02 pixel kernel: i2c_designware INT3433:00: timeout waiting for bus ready
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0001:01: __mxt_read_reg: i2c transfer failed (-110)
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0001:01: Failed to read T44 and T5 (-110)
Nov 05 22:18:02 pixel kernel: i2c_designware INT3432:00: timeout waiting for bus ready
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0000:01: __mxt_write_reg: i2c send failed (-110)
Nov 05 22:18:02 pixel kernel: i2c_designware INT3433:00: timeout waiting for bus ready
Nov 05 22:18:02 pixel kernel: atmel_mxt_ts i2c-ATML0001:01: __mxt_write_reg: i2c send failed (-110)
Nov 05 22:18:02 pixel kernel: i2c_designware INT3433:00: timeout waiting for bus ready
[...]

Originally posted by @drivenbyentropy in https://github.com/raphael/linux-samus/issues/217#issuecomment-550417940

christianbundy commented 4 years ago

@drivenbyentropy I haven't, no. What's the benefit to hibernation? Not sure I understand suspend vs hibernate, but when I tried systemctl hibernate I got:

Failed to hibernate system via logind: Not enough swap space for hibernation

I'm guessing I should probably have read your article first. :~)

drivenbyentropy commented 4 years ago

Thanks for cleaning up the ticket. I was hesitant to open a new one because technically this is not related to the samus kernel any more.

The benefit I see is the ability to restore your exact work state with zero power consumption in between. I mainly use it when traveling.

I have my swap file set to 10gb which gets the job done with appropriate compression.

christianbundy commented 4 years ago

I have my swap file set to 10gb which gets the job done with appropriate compression.

I can barely survive on 64 GB alone, I can't imagine 10 GB dedicated to hibernation! I don't think I have the disk space to attempt this. :sweat_smile:

drivenbyentropy commented 4 years ago

No worries, as long as suspension is functional, I can work with it :+1:. Lets close this for now and reopen should new information arise.