The symptom is that system never comes back from suspend (indicated with
blinking LEDs per expectation), whatever I try (closing and reopening
the lid, etc., un-/plugging AC adapter, pressing the main switch and
whatever keys and functional key combos).
The difference I can observe in the journal around the event of
- bad case (4.15.0-0.rc1.git1.1)
> Dec 01 18:46:32 betenoire systemd-logind: Lid closed.
> Dec 01 18:46:32 betenoire systemd-logind: Suspending...
> Dec 01 18:46:32 betenoire systemd: Reached target Sleep.
> Dec 01 18:46:32 betenoire systemd: Starting Suspend...
> Dec 01 18:46:32 betenoire systemd-sleep: Suspending system...
> Dec 01 18:46:32 betenoire kernel: PM: suspend entry (deep)
[ nothing from here on, was unable to make the machine resume,
had to power off by force with a long power switch button press ]
- happy case (4.15.0-0.rc0.git7.2)
> Dec 01 18:49:00 betenoire systemd-logind: Lid closed.
> Dec 01 18:49:00 betenoire systemd-logind: Suspending...
> Dec 01 18:49:00 betenoire systemd: Reached target Sleep.
> Dec 01 18:49:00 betenoire systemd: Starting Suspend...
> Dec 01 18:49:00 betenoire systemd-sleep: Suspending system...
> Dec 01 18:49:00 betenoire kernel: PM: suspend entry (deep)
> Dec 01 18:49:00 betenoire kernel: PM: Syncing filesystems ... done.
[ gap until the system was successfully resumed again ]
For the record, I am using legacy BIOS to boot.
Looking briefly into the 0c86a6bd85ff...43570f0383d delta, there are
some vague hits, amongst others those related to drm/i915:
Hans, do you think these might be related?
This laptop indeed uses i915 driver/module to service
Intel Corporation HD Graphics 530 (rev 06).
Not going away with 4.15.0-0.rc1.git3.1.fc28.x86_64.
https://marc.info/?l=linux-kernel&m=151242635416764 Looks like there are systemwide suspsend issues
https://lkml.org/lkml/2017/11/30/546 this was reported to fix the issue and Linus picked it up. I'll double check this is in the next rawhide build.
Thanks, Laura, for the guidance, the patch indeed
works for me (from [comment 3], on top of 4.15.0-0.rc2.git0.1).
(83 minutes 9 second for an rpmbuild on that machine, also observing
things like bad parameter quoting of shell scripts amongst the produced
./arch/ia64/scripts/check-gas: line 11: [: !=: unary operator expected)
For the record, why having this issue fixed is important for me
is that there was a "genious" idea to hardwire Fn+4 combo to instant
suspend at least for some Lenovo machines. With my common shortcuts,
it sometimes happens to be pressed, though that's easy to recover
from unless a show stopper, as was this one, comes to play.
Confirming kernel-4.15.0-0.rc2.git2.1.fc28.x86_64 works for me
(not sure if accidentally or not).
Yes, I picked up the patch mentioned in the thread so it was expected. Going to mark this as resolved.
I was unsure because this bug wasn't marked in the changelog, although
I can see that might be a maintenance hell to have every bug tracked
with a fine granularity in the "component" of this size.
Cross-checking the records, mentioned version 4.15.0-0.rc2.git2.1 aka
v4.15-rc2-252-g968edbd93c0c should be, moreover, the very first release
fixing this bug.