Bug 215794

Summary: Suspension in Vaio FE14 is not properly working
Product: ACPI Reporter: Davi Vasconcelos (davijbvasconcelos)
Component: Power-Sleep-WakeAssignee: Zhang Rui (rui.zhang)
Status: CLOSED ANSWERED    
Severity: high CC: rui.zhang
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 5.16.18-200.fc35.x86_64 Subsystem:
Regression: No Bisected commit-id:

Description Davi Vasconcelos 2022-04-02 17:07:52 UTC 
When I try to suspend my notebook a Vaio FE14, it goes for reboot. I'm using Fedora 35, kernel 5.16.18-200.fc35.x86_64.

Anyway, at first, the system just doesn't suspend at all and reboots after I close the lid of the laptop. My primary tought was a problem with the lid and systemd and, hence, I changed some configs at /etc/systemd/logind.conf based on a debian article for suspension in systemd (https://wiki.debian.org/SystemdSuspendSedation). I had some good results but not a solution, and again I changed other configs at /etc/systemd/sleep.conf.

After that, the system is able to do two or three suspensions in a row, but only that. The major behavior is, after two succesfully suspensions, the third one goes directly for a reboot. Sometimes, it bugs and I get a reboot at the first attempt to suspend. Futhermore, it doesn't matter if it is by closing the lid or selecting suspension on power off / quit session in gnome. It's the same result.

Any help will be great, thanks in advance.

At /etc/systemd/logind.conf, I uncomment this lines:
HandleSuspendKey=suspend
HandleLidSwitch=suspend
HandleLidSwitchDocked=suspend

At /etc/systemd/sleep.conf, I uncomment this lines:
AllowSuspend=yes
SuspendState=mem standby freeze


# journalctl -b | grep -i lid
abr 02 09:07:59 vaio-de-davi kernel: DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
abr 02 09:07:59 vaio-de-davi kernel: iommu: DMA domain TLB invalidation policy: lazy mode 
abr 02 09:07:59 vaio-de-davi kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:19/PNP0C09:00/PNP0C0D:00/input/input0
abr 02 09:07:59 vaio-de-davi kernel: ACPI: button: Lid Switch [LID0]
abr 02 09:07:59 vaio-de-davi kernel: ACPI: thermal: [Firmware Bug]: No valid trip found
abr 02 09:07:59 vaio-de-davi kernel: ACPI: thermal: [Firmware Bug]: No valid trip found
abr 02 12:08:22 vaio-de-davi systemd-logind[778]: Watching system buttons on /dev/input/event0 (Lid Switch)
abr 02 12:15:41 vaio-de-davi kernel: ACPI: button: The lid device is not compliant to SW_LID.
abr 02 12:15:37 vaio-de-davi systemd-logind[778]: Lid opened.

# dmesg | grep lid
[   62.441651] ACPI: button: The lid device is not compliant to SW_LID.

# inxi -Fxz
System:
  Kernel: 5.16.18-200.fc35.x86_64 x86_64 bits: 64 compiler: gcc
    v: 2.37-10.fc35 Console: pty pts/0 Distro: Fedora release 35 (Thirty Five)
Machine:
  Type: Laptop System: Positivo Bahia - VAIO product: VJFE41F11X-XXXXXX
    v: N/A serial: <filter>
  Mobo: Positivo Tecnologia SA model: VJFE-KL v: 11158959 serial: <filter>
    UEFI: Positivo Tecnologia SA v: 1.025.X date: 09/16/2020
Battery:
  ID-1: BAT0 charge: 36.5 Wh (97.1%) condition: 37.6/37.6 Wh (100.0%)
    volts: 12.3 min: 11.4 model: KBL-R MRD SR Real Battery status: Discharging
CPU:
  Info: quad core model: Intel Core i5-8250U bits: 64 type: MT MCP
    arch: Coffee Lake rev: A cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 799 high: 800 min/max: 400/3400 cores: 1: 794 2: 800
    3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 bogomips: 28800
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel UHD Graphics 620 vendor: nCipher Security driver: i915
    v: kernel bus-ID: 00:02.0
  Device-2: Microdia USB 2.0 Camera type: USB driver: uvcvideo
    bus-ID: 1-5:4
  Display: server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting
    unloaded: fbdev,vesa gpu: i915 resolution: 1920x1080~60Hz
  OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2)
    v: 4.6 Mesa 21.3.8 direct render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Realtek
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
  Sound Server-1: ALSA v: k5.16.18-200.fc35.x86_64 running: yes
  Sound Server-2: PipeWire v: 0.3.49 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: r8169 v: kernel port: e000 bus-ID: 01:00.0
  IF: enp1s0 state: down mac: <filter>
  Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak]
    driver: iwlwifi v: kernel bus-ID: 02:00.0
  IF: wlp2s0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel Wireless-AC 3168 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 1-3:3
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Drives:
  Local Storage: total: 931.51 GiB used: 73.02 GiB (7.8%)
  ID-1: /dev/sda vendor: Toshiba model: MQ04ABF100 size: 931.51 GiB
    temp: 37 C
Partition:
  ID-1: / size: 103.85 GiB used: 17.8 GiB (17.1%) fs: ext4 dev: /dev/sda6
  ID-2: /boot/efi size: 499 MiB used: 14 MiB (2.8%) fs: vfat dev: /dev/sda5
  ID-3: /home size: 552.44 GiB used: 55.21 GiB (10.0%) fs: ext4
    dev: /dev/sda7
Swap:
  ID-1: swap-1 type: partition size: 11.18 GiB used: 0 KiB (0.0%)
    dev: /dev/sda8
  ID-2: swap-2 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 41.0 C pch: 39.5 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 277 Uptime: 1h 37m Memory: 11.44 GiB used: 2.3 GiB (20.1%)
  Init: systemd runlevel: 5 Compilers: gcc: 11.2.1 Packages: N/A
  note: see --pkg Shell: Bash v: 5.1.8 inxi: 3.3.13
Comment 1 Davi Vasconcelos 2022-04-11 21:08:59 UTC 
The behaviour still the same in kernel 5.17.0.
Comment 2 Zhang Rui 2022-06-27 03:53:47 UTC 
please run "rtcwake -m freeze -s 20" and "rtcwake -m mem -s 20" for suspend first and check if the problem still exists.
And please attach the full dmesg output before the failure suspend.
Comment 3 Davi Vasconcelos 2022-06-27 15:23:58 UTC 
(In reply to Zhang Rui from comment #2)
> please run "rtcwake -m freeze -s 20" and "rtcwake -m mem -s 20" for suspend
> first and check if the problem still exists.
> And please attach the full dmesg output before the failure suspend.

I'm not using this kernel and the current distro anymore. The kernel that i'm using is 5.18.5-200.fc36 and the problem is solved.
Comment 4 Davi Vasconcelos 2022-06-27 15:25:23 UTC 
(In reply to Davi Vasconcelos from comment #3)
> (In reply to Zhang Rui from comment #2)
> > please run "rtcwake -m freeze -s 20" and "rtcwake -m mem -s 20" for suspend
> > first and check if the problem still exists.
> > And please attach the full dmesg output before the failure suspend.
> 
> I'm not using this kernel and the current distro anymore. The kernel that
> i'm using is 5.18.5-200.fc36 and the problem is solved.