You are not logged in.

#1 2018-02-13 20:12:26

vkireyeu
Member
Registered: 2017-06-29
Posts: 17

System freezes after resuming from RAM

Dear all,

Yet another thread about how bad Linux performs on laptops with suspending to RAM.

So, when lid is closed or after pressing special button, my system suspend to RAM.
But then, when I open the lid (or I press same special button again) system tried to resume:
so there is some graphics - I can see workspace and opened applications, but the system does not respond to any mouse move or to keyboard signals,
even to Ctrl+Alt+Delete or  Ctrl+Alt+F{1..6}. It seems like it just freezes.

I tried a set of kernels: 4.14, 4.15 and now I am on 4.16 - same behaviour.
I also tried to enable "Early KMS start"

Without "Early KMS start"
journalctl boot log when suspending: https://pastebin.com/nBsewwXi
journalctl boot log after suspending: https://pastebin.com/YXRBJm86

With "Early KMS start"
journalctl boot log when suspending: https://pastebin.com/arWu0Dqz
journalctl boot log after suspending: https://pastebin.com/kEm4i6LR

acpi_listen.log: "button/lid LID close " (nothing else)

If it is important, my laptop is Apollo Lake based Chuwi Lapbook Air (n3450, 8Gb of RAM).

So, can someone suggest me how to fix this problem?

Thank you in advance and best regards!
Viktar

Offline

#2 2018-02-15 06:07:08

gnumdk
Member
Registered: 2009-10-15
Posts: 140

Re: System freezes after resuming from RAM

I have the same issue on an XPS 13 but it does not happen on Fedora. So using linux-lts should fix your issue.

Offline

#3 2018-02-15 16:48:00

vkireyeu
Member
Registered: 2017-06-29
Posts: 17

Re: System freezes after resuming from RAM

It seems like it's really works with linux-lts (4.14.19 now), thank you! No, still freezes.
But in that case touchpad refuses to work...

Last edited by vkireyeu (2018-02-15 17:14:41)

Offline

#4 2018-02-18 09:48:16

deadveal
Member
Registered: 2018-02-18
Posts: 7

Re: System freezes after resuming from RAM

I am having the same problem on a lenovo y700. Suspend was working before. I am going to try linux-lts and see how it goes.

UPDATE: Tried linux-lts and the problem persists. I think it is related to the latest mesa package. I had exactly the same problem on Windows and an update to the Intel graphics driver fixed it.
UPDATE 2: Found this https://bugzilla.redhat.com/show_bug.cgi?id=1519940
In particular:

kernel: PM: suspend entry (deep)

is the last entry in my previous boot log as well. However, the problem was supposed to be fixed with a patch to the 4.15 version of the kernel. This is either a regression in the latest kernel (4.15.3-2) or the i915 driver found in the mesa package.

UPDATE 3: It seems I have fixed the issue.

I booted using the linux-lts kernel (4.14.19-1-lts), enabled early KMS (added intel_agp and i915  to the MODULES line in /etc/mkinitcpio.conf) and enabled the GuC / HuC firmware loading (which has to be enabled for Skylake and newer processors, mine is a Skylake) by creating  the file

/etc/modprobe.d/i915.conf

  and setting the options:

options i915 enable_guc_loading=1 enable_guc_submission=1

Then, by following the instructions from https://01.org/linuxgraphics/documentat … ume-issues I executed

dmesg > dmesg_before; echo mem > /sys/power/state; dmesg > dmesg_after

as root and the system suspended and resumed normally. Trying to suspend from KDE also worked. It worked after rebooting as well.

Finally I tried the same process with the latest linux kernel (4.15.3-2) and it caused my system to freeze again. Also after rebooting, I found out that

dmesg_after

was not created and based on https://01.org/linuxgraphics/documentat … ume-issues, the problem is not related to the graphic drivers in the mesa package. Thus it is related to the kernel.

Last edited by deadveal (2018-02-18 13:25:39)

Offline

#5 2018-02-19 09:22:43

catalin.hritcu
Member
From: Paris, France
Registered: 2014-04-27
Posts: 26
Website

Re: System freezes after resuming from RAM

I was having a very similar "kernel: PM: suspend entry (deep)" resumption problem and for me simply switching to kernel 4.14.19-1-lts solved it. I'm on an old Lenovo Thinkpad T440p with a Haswell chip (i7-4700MQ).

Last edited by catalin.hritcu (2018-02-19 09:23:05)

Offline

#6 2018-02-19 13:33:41

deadveal
Member
Registered: 2018-02-18
Posts: 7

Re: System freezes after resuming from RAM

Just a small update. I had the linux-hardened kernel version 4.15.2 installed and tried suspending the system and it worked. I'll check if 4.15.4 displays the same problem or not.

Offline

#7 2018-02-19 18:24:20

vkireyeu
Member
Registered: 2017-06-29
Posts: 17

Re: System freezes after resuming from RAM

> I booted using the linux-lts kernel (4.14.19-1-lts), enabled early KMS (added intel_agp and i915  to the MODULES line in /etc/mkinitcpio.conf) and enabled the GuC / HuC firmware loading (which has to be enabled for Skylake and newer processors, mine is a Skylake) by creating  the file

Does not work for me sad

Offline

#8 2018-02-21 18:09:05

deadveal
Member
Registered: 2018-02-18
Posts: 7

Re: System freezes after resuming from RAM

UPDATE: Probably ignore what I've written below. Try adding modprobe.blacklist=nvidiafb to your boot entry. It works for me for kernel versions from 4.15.3-2 and up. Look at https://bbs.archlinux.org/viewtopic.php?id=234659. If that does not work try  setting the kernel option intel_iommu=igfx_off.

I checked both linux-hardened (4.15.4.a-1), as the standard version is not in core yet, and linux-lts (4.14.20-1-lts). The first one does not work while the second one, as expected, works. The problem started with version 4.15.3 and is not fixed in 4.15.4 either.

vkireyeu wrote:

Does not work for me

Can you see your boot entries to check if there are any options there about the graphic modules? I saw your kernel logs and it seems like we have the same problem, so with linux-lts it should have been fixed.
I also saw this:

i915: unknown parameter 'enable_rc6' ignored
Setting dangerous option enable_fbc - tainting kernel
i915: unknown parameter 'semaphores' ignored

Normally those options should not be a problem and they are ignored as the log shows, but remove those and test again with the linux-lts kernel.
Also check that you do not have any other drivers than the ones from the mesa package installed, just to rule out the case the drivers are the source of the problem.

Last edited by deadveal (2018-02-21 23:50:39)

Offline

#9 2018-02-22 08:18:06

vkireyeu
Member
Registered: 2017-06-29
Posts: 17

Re: System freezes after resuming from RAM

Still have the same problem.

So, I removed vulkan-intel package, disabled some options concerning i915, kernel is 4.14.20-1-lts now.
Boot entry is like that:

linux   /vmlinuz-linux-lts
initrd  /intel-ucode.img
initrd  /initramfs-linux-lts.img
options root=UUID=fa621d48-6190-452f-b115-bdf62cac25f4  rw quiet systemd.gpt_auto=0 modprobe.blacklist=nvidiafb resume=UUID=2b48fada-c192-45ac-81f1-72369561c688

I also tried intel_iommu=igfx_off, but in that case system became very unstable and started to freeze even without suspending.


Logs with modprobe.blacklist=nvidiafb + intel_iommu=igfx_off: https://pastebin.com/apUbTb4q
Logs with modprobe.blacklist=nvidiafb only: https://pastebin.com/ndnTX5Yq

In that case I was able to try suspending twice, but the second time it did not work and I found this:

фев 22 10:48:41 vkbook kernel: Oops: 0003 [#1] SMP PTI
фев 22 10:48:41 vkbook kernel: Modules linked in: cmac rfcomm bnep joydev mousedev spi_pxa2xx_platform arc4 8250_dw hid_multitouch intel_rapl intel_telemetry_pltdrv snd_soc_skl intel_punit_ipc intel_telemetry_core intel_pmc_ipc snd_soc_skl_ipc x86_pkg_temp_thermal snd_soc_sst_ipc intel_powerclamp coretemp snd_soc_sst_dsp kvm_intel snd_hda_ext_core snd_soc_sst_match iwlmvm nls_iso8859_1 snd_soc_core nls_cp437 kvm vfat fat hid_generic mac80211 irqbypass crct10dif_pclmul snd_compress crc32_pclmul snd_hda_codec_realtek ghash_clmulni_intel snd_hda_codec_generic uvcvideo snd_pcm_dmaengine pcbc ac97_bus iwlwifi videobuf2_vmalloc btusb aesni_intel snd_hda_intel btrtl videobuf2_memops videobuf2_v4l2 aes_x86_64 btbcm crypto_simd snd_hda_codec glue_helper btintel cryptd intel_cstate videobuf2_core intel_rapl_perf input_leds snd_usb_audio
фев 22 10:48:41 vkbook kernel:  wdat_wdt lpc_ich bluetooth cfg80211 pcspkr i2c_i801 videodev snd_usbmidi_lib snd_hda_core ecdh_generic snd_rawmidi rfkill snd_seq_device snd_hwdep media mei_me snd_pcm snd_timer idma64 snd intel_lpss_pci processor_thermal_device intel_lpss int340x_thermal_zone shpchp mei soundcore intel_soc_dts_iosf fan thermal i2c_hid ac battery evdev usbhid mac_hid hid pinctrl_broxton pinctrl_intel int3400_thermal intel_hid dptf_power acpi_thermal_rel sparse_keymap sch_fq_codel sg crypto_user ip_tables x_tables ext4 crc16 mbcache jbd2 fscrypto mmc_block serio_raw atkbd libps2 ahci sdhci_pci crc32c_intel xhci_pci sdhci libahci led_class xhci_hcd libata mmc_core usbcore usb_common scsi_mod i8042 serio i915 video button i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm intel_agp
фев 22 10:48:41 vkbook kernel:  intel_gtt agpgart
фев 22 10:48:41 vkbook kernel: CPU: 2 PID: 287 Comm: irq/125-ALPS000 Not tainted 4.14.20-1-lts #1
фев 22 10:48:41 vkbook kernel: Hardware name: CHUWI Co.Ltd LapBook Air/X14, BIOS N1410AL.TE7.A0L3HWC3.Chuwi.Z002 08/30/2017
фев 22 10:48:41 vkbook kernel: task: ffff89db75c1b800 task.stack: ffffa21481260000
фев 22 10:48:41 vkbook kernel: RIP: 0010:memset_erms+0x9/0x10
фев 22 10:48:41 vkbook kernel: RSP: 0000:ffffa21481263db0 EFLAGS: 00010246
фев 22 10:48:41 vkbook kernel: RAX: 0000000000001000 RBX: ffff89db734f4602 RCX: 0000000000006aff
фев 22 10:48:41 vkbook kernel: RDX: 0000000000006aff RSI: 0000000000000000 RDI: ffff89db734edb08
фев 22 10:48:41 vkbook kernel: RBP: 00000000ffff9506 R08: 0000000000000001 R09: ffff89db734edb08
фев 22 10:48:41 vkbook kernel: R10: 0000000000000001 R11: 000000000000038c R12: 0000000000006aff
фев 22 10:48:41 vkbook kernel: R13: 00000000ffff9505 R14: 0000000000000001 R15: ffff89db735dd8b8
фев 22 10:48:41 vkbook kernel: FS:  0000000000000000(0000) GS:ffff89db7fd00000(0000) knlGS:0000000000000000
фев 22 10:48:41 vkbook kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
фев 22 10:48:41 vkbook kernel: CR2: ffff89db734edb08 CR3: 000000023500a000 CR4: 00000000003406e0
фев 22 10:48:41 vkbook kernel: Call Trace:
фев 22 10:48:41 vkbook kernel:  hid_report_raw_event+0xb3/0x450 [hid]
фев 22 10:48:41 vkbook kernel:  ? __i2c_transfer+0x120/0x3f0
фев 22 10:48:41 vkbook kernel:  hid_input_report+0x119/0x180 [hid]
фев 22 10:48:41 vkbook kernel:  ? irq_thread_check_affinity+0xa0/0xa0
фев 22 10:48:41 vkbook kernel:  i2c_hid_irq+0xd7/0x120 [i2c_hid]
фев 22 10:48:41 vkbook kernel:  ? irq_finalize_oneshot.part.42+0xf0/0xf0
фев 22 10:48:41 vkbook kernel:  irq_thread_fn+0x21/0x50
фев 22 10:48:41 vkbook kernel:  irq_thread+0x145/0x1a0
фев 22 10:48:41 vkbook kernel:  ? irq_forced_thread_fn+0x70/0x70
фев 22 10:48:41 vkbook kernel:  kthread+0x11a/0x130
фев 22 10:48:41 vkbook kernel:  ? kthread_create_on_node+0x70/0x70
фев 22 10:48:41 vkbook kernel:  ret_from_fork+0x35/0x40
фев 22 10:48:41 vkbook kernel: Code: 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 f3 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 <f3> aa 4c 89 c8 c3 90 49 89 fa 40 0f b6 ce 48 b8 01 01 01 01 01 
фев 22 10:48:41 vkbook kernel: RIP: memset_erms+0x9/0x10 RSP: ffffa21481263db0
фев 22 10:48:41 vkbook kernel: CR2: ffff89db734edb08
фев 22 10:48:41 vkbook kernel: ---[ end trace 53ed3463cfbbcc1e ]---
фев 22 10:48:41 vkbook kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000001
фев 22 10:48:41 vkbook kernel: IP: 0x1
фев 22 10:48:41 vkbook kernel: PGD 0 P4D 0 
фев 22 10:48:41 vkbook kernel: Oops: 0010 [#2] SMP PTI
фев 22 10:48:41 vkbook kernel: Modules linked in: cmac rfcomm bnep joydev mousedev spi_pxa2xx_platform arc4 8250_dw hid_multitouch intel_rapl intel_telemetry_pltdrv snd_soc_skl intel_punit_ipc intel_telemetry_core intel_pmc_ipc snd_soc_skl_ipc x86_pkg_temp_thermal snd_soc_sst_ipc intel_powerclamp coretemp snd_soc_sst_dsp kvm_intel snd_hda_ext_core snd_soc_sst_match iwlmvm nls_iso8859_1 snd_soc_core nls_cp437 kvm vfat fat hid_generic mac80211 irqbypass crct10dif_pclmul snd_compress crc32_pclmul snd_hda_codec_realtek ghash_clmulni_intel snd_hda_codec_generic uvcvideo snd_pcm_dmaengine pcbc ac97_bus iwlwifi videobuf2_vmalloc btusb aesni_intel snd_hda_intel btrtl videobuf2_memops videobuf2_v4l2 aes_x86_64 btbcm crypto_simd snd_hda_codec glue_helper btintel cryptd intel_cstate videobuf2_core intel_rapl_perf input_leds snd_usb_audio
фев 22 10:48:41 vkbook kernel:  wdat_wdt lpc_ich bluetooth cfg80211 pcspkr i2c_i801 videodev snd_usbmidi_lib snd_hda_core ecdh_generic snd_rawmidi rfkill snd_seq_device snd_hwdep media mei_me snd_pcm snd_timer idma64 snd intel_lpss_pci processor_thermal_device intel_lpss int340x_thermal_zone shpchp mei soundcore intel_soc_dts_iosf fan thermal i2c_hid ac battery evdev usbhid mac_hid hid pinctrl_broxton pinctrl_intel int3400_thermal intel_hid dptf_power acpi_thermal_rel sparse_keymap sch_fq_codel sg crypto_user ip_tables x_tables ext4 crc16 mbcache jbd2 fscrypto mmc_block serio_raw atkbd libps2 ahci sdhci_pci crc32c_intel xhci_pci sdhci libahci led_class xhci_hcd libata mmc_core usbcore usb_common scsi_mod i8042 serio i915 video button i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm intel_agp
фев 22 10:48:41 vkbook kernel:  intel_gtt agpgart
фев 22 10:48:41 vkbook kernel: CPU: 2 PID: 287 Comm: irq/125-ALPS000 Tainted: G      D         4.14.20-1-lts #1
фев 22 10:48:41 vkbook kernel: Hardware name: CHUWI Co.Ltd LapBook Air/X14, BIOS N1410AL.TE7.A0L3HWC3.Chuwi.Z002 08/30/2017
фев 22 10:48:41 vkbook kernel: task: ffff89db75c1b800 task.stack: ffffa21481260000
фев 22 10:48:41 vkbook kernel: RIP: 0010:0x1
фев 22 10:48:41 vkbook kernel: RSP: 0000:ffffa21481263ea8 EFLAGS: 00010282
фев 22 10:48:41 vkbook kernel: RAX: 0000000000000001 RBX: ffff89db75c1b800 RCX: ffffa21481263ed0
фев 22 10:48:41 vkbook kernel: RDX: ffffa21481263ed0 RSI: 0000000000000000 RDI: ffffa21481263ed0
фев 22 10:48:41 vkbook kernel: RBP: ffff89db75c1bf64 R08: 0000000000000000 R09: 0000000000000000
фев 22 10:48:41 vkbook kernel: R10: 0000000000000010 R11: 0000000000000000 R12: ffffffffb555ae10
фев 22 10:48:41 vkbook kernel: R13: 0000000000000000 R14: 0000000000000001 R15: ffff89db75c1bf38
фев 22 10:48:41 vkbook kernel: FS:  0000000000000000(0000) GS:ffff89db7fd00000(0000) knlGS:0000000000000000
фев 22 10:48:41 vkbook kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
фев 22 10:48:41 vkbook kernel: CR2: 0000000000000001 CR3: 000000023500a000 CR4: 00000000003406e0
фев 22 10:48:41 vkbook kernel: Call Trace:
фев 22 10:48:41 vkbook kernel:  ? task_work_run+0x8a/0xb0
фев 22 10:48:41 vkbook kernel:  ? do_exit+0x309/0xb30
фев 22 10:48:41 vkbook kernel:  ? kthread+0x11a/0x130
фев 22 10:48:41 vkbook kernel:  ? rewind_stack_do_exit+0x17/0x20
фев 22 10:48:41 vkbook kernel: Code:  Bad RIP value.
фев 22 10:48:41 vkbook kernel: RIP: 0x1 RSP: ffffa21481263ea8
фев 22 10:48:41 vkbook kernel: CR2: 0000000000000001
фев 22 10:48:41 vkbook kernel: ---[ end trace 53ed3463cfbbcc1f ]---
фев 22 10:48:41 vkbook kernel: Fixing recursive fault but reboot is needed!

Last edited by vkireyeu (2018-02-22 08:19:04)

Offline

#10 2018-02-22 09:37:17

deadveal
Member
Registered: 2018-02-18
Posts: 7

Re: System freezes after resuming from RAM

vkireyeu wrote:

In that case I was able to try suspending twice, but the second time it did not work and I found this:

You mean when you have modprobe.blacklist=nvidiafb set or with intel_iommu=igfx_off?
Also did resume from S3 (suspend to ram) work before? Or did the problem appear when you updated the system? I ask because it might have to do with your Apollo Lake cpu. Look at the last comment of https://bugs.launchpad.net/ubuntu/+sour … ug/1728244 which is quite similar.

Btw, I forgot to mention that nvidiafb is not an issue with linux-lts but with linux. So try booting 4.15.3-2 again with modprobe.blacklist=nvidiafb and remove it from the linux-lts entry.

At the same time, in order to reproduce my setup with i915, be sure to have early kms enabled and the file /etc/modprobe.d/i915.conf
with content: options i915 enable_guc_loading=1 enable_guc_submission=1, assuming that Apollo Lake based systems behave like Skylake ones on that matter.

Last edited by deadveal (2018-02-22 10:16:22)

Offline

#11 2018-02-23 19:09:17

vkireyeu
Member
Registered: 2017-06-29
Posts: 17

Re: System freezes after resuming from RAM

No, it something... I do not know.
Behaviour still the same.

As I understand, early KMS is enabled by this:

$ cat /etc/mkinitcpio.conf | grep MODULES
MODULES="intel_agp i915"

And I did mkinitcpio for all my kernels.

i915 options:

$ cat /etc/modprobe.d/i915.conf 
options i915 enable_guc_loading=1 enable_guc_submission=1

Boot options for 4.15.4:
options    root=UUID=fa621d48-6190-452f-b115-bdf62cac25f4 rw quiet modprobe.blacklist=nvidiafb UUID=2b48fada-c192-45ac-81f1-72369561c688

Boot options for 4.14.20 (LTS):
options    root=UUID=fa621d48-6190-452f-b115-bdf62cac25f4  rw quiet resume=UUID=2b48fada-c192-45ac-81f1-72369561c688

vulkan-intel driver was already remover.
4.15: https://ptpb.pw/9E9_
4.14: https://ptpb.pw/4Ymy and https://ptpb.pw/DqLg (here I was able to suspend and resume once, but got a kernel Oops).

> Also did resume from S3 (suspend to ram) work before? Or did the problem appear when you updated the system?
No, never. But I got this laptop in the end of January.

Offline

#12 2018-02-24 10:05:26

deadveal
Member
Registered: 2018-02-18
Posts: 7

Re: System freezes after resuming from RAM

I scanned through your logs and one of them does point to i2c_hid crashing or something similar (https://ptpb.pw/DqLg):

фев 23 20:53:16 vkbook kernel: CPU: 1 PID: 319 Comm: irq/126-ALPS000 Not tainted 4.14.20-1-lts #1
фев 23 20:53:16 vkbook kernel: Hardware name: CHUWI Co.Ltd LapBook Air/X14, BIOS N1410AL.TE7.A0L3HWC3.Chuwi.Z002 08/30/2017
фев 23 20:53:16 vkbook kernel: task: ffff8d8b729a5400 task.stack: ffffba3c012b4000
фев 23 20:53:16 vkbook kernel: RIP: 0010:memset_erms+0x9/0x10
фев 23 20:53:16 vkbook kernel: RSP: 0000:ffffba3c012b7db0 EFLAGS: 00010246
фев 23 20:53:16 vkbook kernel: RAX: 0000000000001000 RBX: ffff8d8b728dea02 RCX: 0000000000006aff
фев 23 20:53:16 vkbook kernel: RDX: 0000000000006aff RSI: 0000000000000000 RDI: ffff8d8b728d7f08
фев 23 20:53:16 vkbook kernel: RBP: 00000000ffff9506 R08: 0000000000000001 R09: ffff8d8b728d7f08
фев 23 20:53:16 vkbook kernel: R10: 0000000000000001 R11: 00000000000000c4 R12: 0000000000006aff
фев 23 20:53:16 vkbook kernel: R13: 00000000ffff9505 R14: 0000000000000001 R15: ffff8d8b73ac58b8
фев 23 20:53:16 vkbook kernel: FS:  0000000000000000(0000) GS:ffff8d8b7fc80000(0000) knlGS:0000000000000000
фев 23 20:53:16 vkbook kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
фев 23 20:53:16 vkbook kernel: CR2: ffff8d8b728d7f08 CR3: 000000011200a000 CR4: 00000000003406e0
фев 23 20:53:16 vkbook kernel: Call Trace:
фев 23 20:53:16 vkbook kernel:  hid_report_raw_event+0xb3/0x450 [hid]
фев 23 20:53:16 vkbook kernel:  ? __i2c_transfer+0x120/0x3f0
фев 23 20:53:16 vkbook kernel:  hid_input_report+0x119/0x180 [hid]
фев 23 20:53:16 vkbook kernel:  ? irq_thread_check_affinity+0xa0/0xa0
фев 23 20:53:16 vkbook kernel:  i2c_hid_irq+0xd7/0x120 [i2c_hid]
фев 23 20:53:16 vkbook kernel:  ? irq_finalize_oneshot.part.42+0xf0/0xf0
фев 23 20:53:16 vkbook kernel:  irq_thread_fn+0x21/0x50
фев 23 20:53:16 vkbook kernel:  irq_thread+0x145/0x1a0
фев 23 20:53:16 vkbook kernel:  ? irq_forced_thread_fn+0x70/0x70
фев 23 20:53:16 vkbook kernel:  kthread+0x11a/0x130
фев 23 20:53:16 vkbook kernel:  ? kthread_create_on_node+0x70/0x70
фев 23 20:53:16 vkbook kernel:  ret_from_fork+0x35/0x40
фев 23 20:53:16 vkbook kernel: Code: 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 f3 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 <f3> aa 4c 89 c8 c3 90 49 89 fa 40 0f b6 ce 48 b8 01 01 01 01 01
фев 23 20:53:16 vkbook kernel: RIP: memset_erms+0x9/0x10 RSP: ffffba3c012b7db0
фев 23 20:53:16 vkbook kernel: CR2: ffff8d8b728d7f08
фев 23 20:53:16 vkbook kernel: ---[ end trace b12f70eb33c868f1 ]---

In the same log I see

фев 23 20:53:16 vkbook kernel: ACPI: Waking up from system sleep state S3

thus it does resume but then i2c_hid displays the aforementioned crash and also this:

фев 23 20:53:16 vkbook kernel: i2c_hid i2c-ALPS0001:00: failed to reset device.
фев 23 20:53:16 vkbook kernel: dpm_run_callback(): i2c_hid_resume+0x0/0xf0 [i2c_hid] returns -61
фев 23 20:53:16 vkbook kernel: PM: Device i2c-ALPS0001:00 failed to resume async: error -61

This is probably related to this: https://bugs.launchpad.net/ubuntu/+sour … ug/1738491

i2c_hid has to do with your touchpad and in that thread they are talking about the Chuwi Lapbook Air's touch pad not working.

What you can try, apart from looking for a fix at those threads related to the touch pad is to blacklist i2c_hid with

modprobe.blacklist=i2c_hid

in the boot entry for which resume worked once. From the log it should be this one:

фев 23 12:13:01 vkbook kernel: Linux version 4.14.20-1-lts (builduser@andyrtr) (gcc version 7.3.0 (GCC)) #1 SMP Sat Feb 17 21:35:28 CET 2018
фев 23 12:13:01 vkbook kernel: Command line: initrd=\intel-ucode.img initrd=\initramfs-linux-lts.img root=UUID=fa621d48-6190-452f-b115-bdf62cac25f4  rw quiet resume=UUID=2b48fada-c192-45ac-81f1-72369561c688

If the touchpad does not work after blacklisting i2c_hid, just connect a usb mouse.
Post the logs here after you try this and tell me how it goes.

One more question: In your first post you mention the following:

But then, when I open the lid (or I press same special button again) system tried to resume:
so there is some graphics - I can see workspace and opened applications, but the system does not respond to any mouse move or to keyboard signals,
even to Ctrl+Alt+Delete or  Ctrl+Alt+F{1..6}. It seems like it just freezes.

Does this also happen when you try to resume for a second time? I mean does your screen display your workspace and opened applications or do you get a black screen?

I ask because if you get a black screen and blacklisting i2c_hid does not work, to rule out problems from the graphic drivers, execute:

dmesg > dmesg_before; echo mem > /sys/power/state; dmesg > dmesg_after

This will suspend the system to ram. If dmesg_after exists, then resume from S3 works and it could be a problem with the i_915 graphics driver. In any case, it is good to have a log after resuming. Post dmesg_after if it exists here.

Last edited by deadveal (2018-02-24 10:26:26)

Offline

#13 2018-02-27 12:53:17

vkireyeu
Member
Registered: 2017-06-29
Posts: 17

Re: System freezes after resuming from RAM

So, I reinstalled everything and now I use gnome3 instead of openbox.
Kernel: 4.15.5-1-ARCH
Added boot parameter as you suggested "modprobe.blacklist=i2c_hid"

And now suspend worked twice in a row! journalctl does not show any kernel "Oops" like in previous boots. So it seems like problem is partially solved.
Partially - because my touchpad does not work big_smile

Last edited by vkireyeu (2018-02-27 12:54:09)

Offline

#14 2018-02-27 13:52:03

R00KIE
Forum Moderator
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,732

Re: System freezes after resuming from RAM

Report the problem in the proper upstream channel (kernel bugzilla/mailing list/other). If no one reports problems they will never get fixed.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

Board footer

Powered by FluxBB