Hi Michael,
Sorry I haven't been able to test out this fix yet. My laptop died shortly
after receiving your message, and I'm currently not sure when I'll be able to
get a suitable system together to test this out.
If someone else reading this wants to test out the fix instead, please be my
Hi Joel
On Tue, 26 Jun 2018 11:54:36 +0100 Joel Cross
wrote:
> Package: systemd
> Version: 239-1
> Severity: normal
>
> Dear Maintainer,
>
> Over the last few days (since my last system upgrade) I am unable to
> successfully hibernate/resume using the `systemctl hibernate` command. This is
>
On Mon, 2019-03-11 at 00:20 +0100, Michael Biebl wrote:
> Hi Ben
>
> Am 10.03.19 um 23:17 schrieb Ben Hutchings:
> > I think it would make sense for systemd to only set the hibernation
> > device if it's not already set (i.e. if /sys/power/resume contains
> > "0:0\n").
>
> I get $ cat
Hi Ben
Am 10.03.19 um 23:17 schrieb Ben Hutchings:
> I think it would make sense for systemd to only set the hibernation
> device if it's not already set (i.e. if /sys/power/resume contains
> "0:0\n").
I get $ cat /sys/power/resume
8:4
which part is responsible for setting that?
--
Why is it
On Sun, 2019-03-10 at 19:25 +0100, Michael Biebl wrote:
> Hi Mario,
>
>
> On Fri, 6 Jul 2018 12:41:37 + wrote:
[...]
> > Yes I could see two swap partitions causing the wrong one to be picked.
> > It's trying to select the bigger of the two.
> >
> > If they don't match the one you're
Hi Mario,
On Fri, 6 Jul 2018 12:41:37 + wrote:
> > -Original Message-
> > From: Michael Biebl [mailto:bi...@debian.org]
> > Sent: Friday, July 6, 2018 5:46 AM
> > To: Joel Cross; 902...@bugs.debian.org; Limonciello, Mario
> > Subject: Re: Bug#902416
> -Original Message-
> From: Joel Cross [mailto:j...@kazbak.co.uk]
> Sent: Saturday, July 7, 2018 10:00 AM
> To: Michael Biebl; Limonciello, Mario; 902...@bugs.debian.org
> Subject: Re: Bug#902416: systemd: systemctl hibernate: unable to resume after
> upgrade
>
>
On Fri, 6 Jul 2018, at 5:31 PM, Michael Biebl wrote:
> Am 06.07.2018 um 17:02 schrieb mario.limoncie...@dell.com:
> >> -Original Message-
> >> From: Michael Biebl [mailto:bi...@debian.org]
>
> >> If you have multiple swap partitions and you run
> >> echo "disk" > /sys/power/state
> >>
> -Original Message-
> From: Michael Biebl [mailto:bi...@debian.org]
> Sent: Friday, July 6, 2018 5:46 AM
> To: Joel Cross; 902...@bugs.debian.org; Limonciello, Mario
> Subject: Re: Bug#902416: systemd: systemctl hibernate: unable to resume after
> upgrade
>
>
Am 06.07.2018 um 12:32 schrieb Joel Cross:
> On Thu, 5 Jul 2018, at 1:17 PM, Michael Biebl wrote:
>> Am 05.07.2018 um 13:46 schrieb Joel Cross:
>>> Yes, I can confirm, after downgrading to 238-5 (I also downgraded the
>>> libsystemd0, udev and libudev0 packages) that I no longer experience the
On Thu, 5 Jul 2018, at 1:17 PM, Michael Biebl wrote:
> Am 05.07.2018 um 13:46 schrieb Joel Cross:
> > Yes, I can confirm, after downgrading to 238-5 (I also downgraded the
> > libsystemd0, udev and libudev0 packages) that I no longer experience the
> > issue.
>
> Do you know how to use git
On Wed, 4 Jul 2018, at 3:22 PM, Michael Biebl wrote:
> Am 26.06.2018 um 12:54 schrieb Joel Cross:
> > Package: systemd
> > Version: 239-1
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > Over the last few days (since my last system upgrade) I am unable to
> > successfully hibernate/resume
Am 26.06.2018 um 12:54 schrieb Joel Cross:
> Package: systemd
> Version: 239-1
> Severity: normal
>
> Dear Maintainer,
>
> Over the last few days (since my last system upgrade) I am unable to
> successfully hibernate/resume using the `systemctl hibernate` command. This is
> what happens:
Just
On Wed, 27 Jun 2018, at 3:47 PM, Michael Biebl wrote:
> Am 27.06.2018 um 16:03 schrieb Michael Biebl:
> > Joel, can you execute "/lib/systemd/systemd-sleep hibernate" directly
> > and see what happens then.
>
> Make that
>
> SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-sleep hibernate
>
> This
Am 27.06.2018 um 16:03 schrieb Michael Biebl:
> Joel, can you execute "/lib/systemd/systemd-sleep hibernate" directly
> and see what happens then.
Make that
SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-sleep hibernate
This way you should get a more verbose debug output
--
Why is it that all
Am 27.06.2018 um 14:17 schrieb Joel Cross:
> I have attached both logs.
Ok, thanks for the logs. So it looks like no proper hibernation image
was written to disk.
If you run "systemctl hibernate", systemd-logind logind will notify
clients via D-Bus that the system is going to hibernate.
Then
On Tue, 26 Jun 2018, at 12:27 PM, Michael Biebl wrote:
> >>> Please let me know what further information you need from me (if any) in
> >>> order
> >>> to be able to correctly diagnose this bug.
> >>
> >> What happens if you run
> >>
> >> echo "disk" > /sys/power/state
> >>
> >> Does the system
Am 26.06.2018 um 13:20 schrieb Joel Cross:
> On Tue, 26 Jun 2018, at 12:12 PM, Michael Biebl wrote:
>> Which backend have you configured in pm-hibernate? the in-kernel
>> hibernate mechanism, Tux0nIce, uswsusp?
>
> Sorry, I have no idea how to find that out. I do not recall ever configuring
> a
On Tue, 26 Jun 2018, at 12:12 PM, Michael Biebl wrote:
> Which backend have you configured in pm-hibernate? the in-kernel
> hibernate mechanism, Tux0nIce, uswsusp?
Sorry, I have no idea how to find that out. I do not recall ever configuring a
pm-hibernate backend, so I would guess whichever is
Am 26.06.2018 um 12:54 schrieb Joel Cross:
> Package: systemd
> Version: 239-1
> Severity: normal
>
> Dear Maintainer,
>
> Over the last few days (since my last system upgrade) I am unable to
> successfully hibernate/resume using the `systemctl hibernate` command. This is
> what happens:
>
> -
20 matches
Mail list logo
