After recent upgrade from 4.19.43 to 5.4.24 I noticed that my laptop (Macbook 17" late 2011) does not detect the event of closig the lid anymore and fails to suspend. Observed facts: 1) sudo cat /proc/acpi/button/lid/LID0/state ALWAYS yields "open" even when the lid is closed. 2) running the command "systemctl suspend" and subsequent waking up cures the problem. /proc/acpi/button/lid/LID0/state begins to report "closed" when appropriate. UNTIL a full reboot. The hardware sensor is OK. 3) Any manipulations with HandleLidSwitch* in /etc/systemd/logind.conf have no effect.
This bug is still present in kernel 5.4.31. Kernels 4.x woked well. The hardware lid sensor is OK and works stable after running "systemctl suspend" manually on each reboot.
NB! An affected notebook can easily be closed, put into a soft plush (and thus thermal insulating) case and left there by a user assuming that the computer sleeps. The result is an EXTREMELY hot running computer posing a risk of fire and eventual human casualties.
re: 1) sudo cat /proc/acpi/button/lid/LID0/state ALWAYS yields "open" even when the lid is closed. can you run git bisect to find out which commit introduces this problem?
hmm, I've seem quite some updates from Hans, maybe he has more ideas on this, without bisecting.
Vyacheslav, can you attach an acpidump of your macbook please?
Created attachment 290041 [details] ACPI table dump (made by running acpidump -o DSDT.dat) I am running kernel 5.5.17-un-def-alt1 (ALTLinux Sisyphus standard built) now. The dump was made using this kernel.
It appears that the bug no longer manifests itself with kernel 5.5.17.
(In reply to Vyacheslav Dikonov from comment #7) > It appears that the bug no longer manifests itself with kernel 5.5.17. Thank you for letting us know about this, I guess that means that this bug can be closed now ?
I am not sure. Has the reason been found? It can still happen that my hw is OK now, but some other hw is still affected. Maybe, if several versions of the kernel turn out to be bug-free, we can deem the problem to be self-resolved.
(In reply to Vyacheslav Dikonov from comment #9) > I am not sure. Has the reason been found? It can still happen that my hw is > OK now, but some other hw is still affected. You are/were the only reporter of this problem. No one else has seen/reported this. So lets close this, we can always re-open it later if necessary.