Bug 1490516
| Summary: | Unintended suspend | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | jeremy9856 |
| Component: | systemd | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 26 | CC: | airlied, ajax, bskeggs, eparis, esandeen, harald, hdegoede, ichavero, itamar, jarodwilson, jforbes, jglisse, jonathan, josef, jsynacek, jwboyer, kay, kernel-maint, labbott, linville, lnykryn, lpoetter, mchehab, mjg59, mschmidt, msekleta, nhorman, quintela, ssahani, s, steved, systemd-maint, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-09-13 08:21:27 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
jeremy9856
2017-09-11 20:37:58 UTC
It seem the there is fake "Lid closed" event... sept. 12 19:59:30 hp systemd-logind[759]: Lid opened. sept. 12 19:59:30 hp systemd-logind[759]: Suspending... sept. 12 19:59:30 hp systemd-logind[759]: Lid closed. systemd-logind reacts to events from the lid switch input device. The custom firmware is likely to blame. You can observe the input events with the libinput tool: libinput list-devices In the output find which /dev/input/... device is identified as a "Lid Switch". Then: libinput debug-events --device /dev/input/... And you should see the same lid switch events that systemd-logind sees. As a workaround you can disable lid switch handling in /etc/systemd/logind.conf, by setting HandleLidSwitch=ignore. It does not look like a bug in systemd. It's just showing the GIGO principle (nonsense inputs lead to nonsense outputs). Ok thanks, I will check with them. What's surprise me is that I didn't had any problem with Fedora 25 with the same firmware that I run since July. About the KDE spin suspend problem, I'm looking to see if it's possible to install Fedora twice (Gnome + KDE) with UEFI. The Last time I tried Grub found only one Fedora. If you know how to do it let me know :) You could just add KDE to your Fedora Workstation installation: dnf group install kde-desktop-environment Then you can choose "Plasma" as the session type on the gdm login screen. You can also replace gdm with KDE's preferred display manager, sddm: systemctl enable --force sddm Well unfortunately that load gnome services on kde and vice versa and that make things behave strangely. Well I had an unintended suspend with John Lewis firmware. Either it's a Fedora 26 problem or my lid switch is broken. You could try running a kernel built with CONFIG_ACPI_DEBUG enabled (in Fedora it is enabled in 'kernel-debug' builds). Then in /sys/modules/acpi/parameters you'll find 'debug_layer' and 'debug_level' parameters that you can configure (see https://www.kernel.org/doc/Documentation/acpi/debug.txt) in order to get verbose messages in dmesg when the kernel processes events from the lid switch. Thank you Michal. |