Strange wakeup from suspend

After endeavouros works very well on desktop pc I installed it on my laptop too. Everything works wonderfully except for one little thing that is inexplicable to me.

I very often use the standby mode suspend-to-ram. When I close the lid it goes into standby and when I open the lid again it comes back on. So far so good.

Now I have the following phenomenon. The laptop is partially on another table and I grab it at the frontside with one hand to bring it over. As soon as I grab the laptop and lift it up, it wakes up from standby mode. Neither the mouse nor the keyboard can wake it up and neither is in use, neither is even touched. The switch for s lid is at the top, just below the display while I take it at the other end.

I know that there is a tool for Windows from Lenovo that shuts down the hard drive when certain acceleration forces occur. But there is no tool installed for that and for Linux there is no such thing as far as I know. Anyway, in my opinion this is the only way this could work. But the drive is sleeping when this happens. Maybe the sensor for the hdd is active in standby. It´s a very weird thing.

Do any of you have an idea how this strange wake up could happen?

inxi -Faz
System:
  Kernel: 5.15.12-arch1-1 x86_64 bits: 64 compiler: gcc v: 11.1.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-linux
    root=UUID=dc4d7aaa-1b95-4369-ad75-160042858db0 rw quiet loglevel=3
    nowatchdog nvme_load=YES
  Desktop: KDE Plasma 5.23.5 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: startx
    Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 78595BG v: ThinkPad L520
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: LENOVO model: 78595BG serial: <superuser required> BIOS: LENOVO
    v: 8GET46WW (1.23 ) date: 09/16/2013
Battery:
  ID-1: BAT1 charge: 64.2 Wh (96.3%) condition: 66.7/93.6 Wh (71.3%)
    volts: 12.7 min: 11.1 model: LGC 42T4912 type: Li-ion serial: <filter>
    status: N/A
  Device-1: hidpp_battery_0 model: Logitech M585/M590 Multi-Device Mouse
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: Discharging
CPU:
  Info: model: Intel Core i5-2520M bits: 64 type: MT MCP arch: Sandy Bridge
    family: 6 model-id: 0x2A (42) stepping: 7 microcode: 0x2F
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
    L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
    L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 871 high: 982 min/max: 800/3200 scaling:
    driver: intel_cpufreq governor: schedutil cores: 1: 982 2: 830 3: 877
    4: 798 bogomips: 19963
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf
    mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl and seccomp
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
    IBRS_FW, STIBP: conditional, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
    vendor: Lenovo driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:0126
    class-ID: 0300
  Display: server: X.Org 1.21.1.3 compositor: kwin_x11 driver:
    loaded: intel unloaded: modesetting alternate: fbdev,vesa display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.7x9.4")
    s-diag: 485mm (19.1")
  Monitor-1: LVDS1 res: 1600x900 hz: 60 dpi: 116
    size: 350x190mm (13.8x7.5") diag: 398mm (15.7")
  OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2)
    v: 3.3 Mesa 21.3.3 compat-v: 3.0 direct render: Yes
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio
    vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:1c20 class-ID: 0403
  Sound Server-1: ALSA v: k5.15.12-arch1-1 running: yes
  Sound Server-2: JACK v: 1.9.19 running: no
  Sound Server-3: PulseAudio v: 15.0 running: no
  Sound Server-4: PipeWire v: 0.3.43 running: yes
Network:
  Device-1: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi
    v: kernel modules: wl bus-ID: 03:00.0 chip-ID: 8086:0085 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel port: 3000 bus-ID: 09:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: enp9s0 state: down mac: <filter>
Bluetooth:
  Device-1: Broadcom BCM2045B (BDC-2.1) type: USB driver: btusb v: 0.8
    bus-ID: 1-1.6:4 chip-ID: 0a5c:217f class-ID: fe01 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 6 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: see --recommends
Drives:
  Local Storage: total: 525.39 GiB used: 256.19 GiB (48.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 830 Series
    size: 59.63 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 3B1Q scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Toshiba model: MK5061GSY
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 1.5 Gb/s
    type: HDD rpm: 7200 serial: <filter> rev: 2E scheme: MBR
Partition:
  ID-1: / raw-size: 20 GiB size: 19.52 GiB (97.59%) used: 12.36 GiB (63.3%)
    fs: ext4 dev: /dev/sda1 maj-min: 8:1
  ID-2: /home raw-size: 33 GiB size: 32.19 GiB (97.53%)
    used: 19.58 GiB (60.8%) fs: ext4 dev: /dev/sda2 maj-min: 8:2
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 58.0 C mobo: 0.0 C
  Fan Speeds (RPM): cpu: 743
Info:
  Processes: 174 Uptime: 7h 38m wakeups: 37 Memory: 7.61 GiB
  used: 1.95 GiB (25.6%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 11.1.0 clang: 13.0.0 Packages: pacman: 1077 lib: 264 Shell: Bash
  v: 5.1.12 running-in: konsole inxi: 3.3.11

There will be different methods of detecting the screen open, from physical switches sticking out the top of the base to magnetic switches like a reed switch to the more modern Hall effect sensors.

Given this is quite an old laptop now, it could be that the hinge mechanism has become looser over time, and so the movement is triggering whatever the switch is. Or, maybe you’re moving it through a magnetic field. :man_shrugging:

Hi @jonathon and thank you for your answer.
The device has always been treated with care and has hardly ever left the house. The lid switch works via a magnetic switch. The hinges hold like the first day and there is no magnetic field through which the device is moved. It also happens in different places in the house.

About 10 days ago I had the unit completely disassembled, cleaned, new thermal paste applied, etc.
So i thought there might be something slipped or out of place and opened it up again. But there was nothing, everything is where it should be.

It is not something that bothers me very much, but I would like to get to the bottom of it because it is - for me - relatively inexplicable. And of course such things are calling my tinker soul :wink:

2 Likes

The only other thing that comes to mind is that the slight pressure from being lifted at that specific point is causing a short or momentary disconnection.

For example, if I pick up my X230 using the front-left corner while it’s open and placed right-side down then Bluetooth will disconnect… (so I lift it from the rear left instead, getting a grip by hooking a finger around the rear left rubber base pad). :joy:

1 Like

Yeah exactly, something like that will be the evildoer. Anyway, I will stay tuned to find the reason. I will report…

1 Like

A short update… i could solve the problem now.
It is almost a little embarrassing because the associated flat ribbon cable was not properly inserted, but slightly tilted in the slot. When the probem occurred, I had checked this cable again, but probably overlooked that it does not sit correctly. Since the associated multimedia keys also functioned perfectly, I had ruled out the cable as the cause.

Have a relaxed sunday.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.