Bug#894605: systemd: System fails to suspend.

[Michael Biebl]

On Wed, 13 Jun 2018 18:10:41 +0200 Michael Biebl  wrote:
> On Mon, 9 Apr 2018 23:17:28 +0200 (CEST) "hub...@golembiowski.pl"
>  wrote:
> 
> > echo "mem" > /sys/power/state suspends system correctly with possibility to 
> > wake
> > up as expected.
> >  
> > I run dist-upgrade regularly so I expect a number of packages upgrade 
> > recently.
> > Unfortunately can't correlate as I was not noting down packages being 
> > updated.
> > Found what seem to be related in #892321 mailto:892...@bugs.debian.org but 
> > can't
> > tell if both cases are the same.
> 
> systemd internally does basically nothing more then
> echo "mem" > /sys/power/state
> 
> What it does in addition though is send out a (D-Bus) signal that the
> system is going to suspend, so userspace software can react to that.
> 
> My guess is, that it is some other component reacting on that D-Bus
> signal which triggers that problem.
> 
> Which desktop environment are you using?
> If you use a minimal desktop environment / window manager and you run
> systemctl suspend
> does the problem happen as well?
> What if you run systemctl suspend when you are logged in on the console?


Ping?

Please also include the results of running
SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-sleep suspend


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#894605: systemd: System fails to suspend.

[Michael Biebl]

On Mon, 9 Apr 2018 23:17:28 +0200 (CEST) "hub...@golembiowski.pl"
 wrote:

> echo "mem" > /sys/power/state suspends system correctly with possibility to 
> wake
> up as expected.
>  
> I run dist-upgrade regularly so I expect a number of packages upgrade 
> recently.
> Unfortunately can't correlate as I was not noting down packages being updated.
> Found what seem to be related in #892321 mailto:892...@bugs.debian.org but 
> can't
> tell if both cases are the same.

systemd internally does basically nothing more then
echo "mem" > /sys/power/state

What it does in addition though is send out a (D-Bus) signal that the
system is going to suspend, so userspace software can react to that.

My guess is, that it is some other component reacting on that D-Bus
signal which triggers that problem.

Which desktop environment are you using?
If you use a minimal desktop environment / window manager and you run
systemctl suspend
does the problem happen as well?
What if you run systemctl suspend when you are logged in on the console?

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#894605: systemd: System fails to suspend.

[hub...@golembiowski.pl]

> On April 2, 2018 at 11:37 PM Michael Biebl  wrote:
>
>
> Am 02.04.2018 um 10:20 schrieb Hubert Golembiowski:
> > Package: systemd
> > Version: 238-3
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > Following issue observed:
> > - Select "Suspend" from UI or close laptop lid (closing lid is set to
> > trigger
> > suspend)
> > - System doesn't suspend but instead:
> > - screen goes blank
> > - keyboard stops to take input
> > - pc is still running (fans, leds are on, etc.)
> > - The only way to get out if that state is hard reset
> > - This used to work without any problem, issue appeared 4-5 days ago
>
> What happens if you run (as root)
> echo "mem" > /sys/power/state
>
> Did you upgrade other packages the last couple of days, like say the
> kernel? Does the failure to suspend correlate with a certain package update?

echo "mem" > /sys/power/state suspends system correctly with possibility to wake
up as expected.
 
I run dist-upgrade regularly so I expect a number of packages upgrade recently.
Unfortunately can't correlate as I was not noting down packages being updated.
Found what seem to be related in #892321 mailto:892...@bugs.debian.org but can't
tell if both cases are the same.
 
 
 
 
 
 
 

Bug#894605: systemd: System fails to suspend.

[Michael Biebl]

Control: tags -1 + moreinfo

Am 02.04.2018 um 23:37 schrieb Michael Biebl:
> Am 02.04.2018 um 10:20 schrieb Hubert Golembiowski:
>> Package: systemd
>> Version: 238-3
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> Following issue observed:
>> - Select "Suspend" from UI or close laptop lid (closing lid is set to trigger
>> suspend)
>> - System doesn't suspend but instead:
>> - screen goes blank
>> - keyboard stops to take input
>> - pc is still running (fans, leds are on, etc.)
>> - The only way to get out if that state is hard reset
>> - This used to work without any problem, issue appeared 4-5 days ago
> 
> What happens if you run (as root)
> echo "mem" > /sys/power/state
> 
> Did you upgrade other packages the last couple of days, like say the
> kernel? Does the failure to suspend correlate with a certain package update?

Ping




signature.asc
Description: OpenPGP digital signature

Bug#894605: systemd: System fails to suspend.

[Michael Biebl]

Am 02.04.2018 um 10:20 schrieb Hubert Golembiowski:
> Package: systemd
> Version: 238-3
> Severity: normal
> 
> Dear Maintainer,
> 
> Following issue observed:
> - Select "Suspend" from UI or close laptop lid (closing lid is set to trigger
> suspend)
> - System doesn't suspend but instead:
> - screen goes blank
> - keyboard stops to take input
> - pc is still running (fans, leds are on, etc.)
> - The only way to get out if that state is hard reset
> - This used to work without any problem, issue appeared 4-5 days ago

What happens if you run (as root)
echo "mem" > /sys/power/state

Did you upgrade other packages the last couple of days, like say the
kernel? Does the failure to suspend correlate with a certain package update?
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature