[Touch-packages] [Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

2023-06-22 Thread Nick Rosbrook
I think this was reported upstream as
https://github.com/systemd/systemd/issues/19486, which was subsequently
fixed (a quick look at the patch makes me think that was the same
issue). So this should be fixed in newer releases.

Please re-open if I am mistaken.

** Bug watch added: github.com/systemd/systemd/issues #19486
   https://github.com/systemd/systemd/issues/19486

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1910252

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  I have plenty of swap space configured in my system:

  $ cat /sys/power/image_size
  6642229248   # ~ 6.2GiB

  $ swapon
  NAME  TYPE   SIZE USED PRIO
  /dev/dm-2 partition  980M   0B   -2
  /dev/sda2 partition 97.7G   0B   -3

  But when I attempt to hibernate:

  $ sudo systemctl hibernate
  Failed to hibernate system via logind: Not enough swap space for hibernation

  I have the swap partition configured as my resume device in my kernel
  commandline:

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro 
quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off 
vt.handoff=7
  $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756
  lrwxrwxrwx 1 root root 10 Jan  5 09:08 
/dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2

  (I'm not really sure how to further debug my issue, any assistance
  would be appreciated!)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.6-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jan  5 09:33:04 2021
  InstallationDate: Installed on 2019-05-07 (608 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (196 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910252/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

2021-08-01 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1910252

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I have plenty of swap space configured in my system:

  $ cat /sys/power/image_size
  6642229248   # ~ 6.2GiB

  $ swapon
  NAME  TYPE   SIZE USED PRIO
  /dev/dm-2 partition  980M   0B   -2
  /dev/sda2 partition 97.7G   0B   -3

  But when I attempt to hibernate:

  $ sudo systemctl hibernate
  Failed to hibernate system via logind: Not enough swap space for hibernation

  I have the swap partition configured as my resume device in my kernel
  commandline:

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro 
quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off 
vt.handoff=7
  $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756
  lrwxrwxrwx 1 root root 10 Jan  5 09:08 
/dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2

  (I'm not really sure how to further debug my issue, any assistance
  would be appreciated!)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.6-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jan  5 09:33:04 2021
  InstallationDate: Installed on 2019-05-07 (608 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (196 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910252/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

2021-01-14 Thread Dan Streetman
> /sys/power/image_size represents the required amount of space for the
image

no it doesn't:
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-power

"The kernel's suspend-to-disk code will do its best to ensure the image size
will not exceed this number.  However, if it turns out to be impossible, the
kernel will try to suspend anyway using the smallest image possible."

"Reading from this file will display the current image size limit, which is
set to around 2/5 of available RAM by default."

> /dev/dm-2: is a candidate device.
> /dev/sda2: ignoring device with lower priority
> /sys/power/resume is not configured; attempting to hibernate with path: 
> /dev/dm-2, device: 253:2, offset: 0, priority: -2
> Not enough swap for hibernation, Active(anon)=1134696 kB, size=1003516 kB, 
> used=0 kB, threshold=98%

yeah, this is the problem; the checks in sleep-config.c first look for
the highest-priority swap device that is valid as a target, but doesn't
actually check if it's large enough for all Active(anon) pages until
*after* selecting which swap device to use. Probably need to open an
upstream bug.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1910252

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

Status in systemd package in Ubuntu:
  New

Bug description:
  I have plenty of swap space configured in my system:

  $ cat /sys/power/image_size
  6642229248   # ~ 6.2GiB

  $ swapon
  NAME  TYPE   SIZE USED PRIO
  /dev/dm-2 partition  980M   0B   -2
  /dev/sda2 partition 97.7G   0B   -3

  But when I attempt to hibernate:

  $ sudo systemctl hibernate
  Failed to hibernate system via logind: Not enough swap space for hibernation

  I have the swap partition configured as my resume device in my kernel
  commandline:

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro 
quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off 
vt.handoff=7
  $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756
  lrwxrwxrwx 1 root root 10 Jan  5 09:08 
/dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2

  (I'm not really sure how to further debug my issue, any assistance
  would be appreciated!)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.6-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jan  5 09:33:04 2021
  InstallationDate: Installed on 2019-05-07 (608 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (196 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910252/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post 

[Touch-packages] [Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

2021-01-08 Thread Dan Watkins
So I've done a little more testing.  On boot, with /sys/power/resume
unset (i.e. 0:0), I see this in the logind debug logs:

Jan 08 09:47:11 surprise systemd-logind[1887]: Sleep mode "disk" is supported 
by the kernel.
Jan 08 09:47:11 surprise systemd-logind[1887]: /dev/dm-2: is a candidate device.
Jan 08 09:47:11 surprise systemd-logind[1887]: /dev/sda2: ignoring device with 
lower priority
Jan 08 09:47:11 surprise systemd-logind[1887]: /sys/power/resume is not 
configured; attempting to hibernate with path: /dev/dm-2, device: 253:2, 
offset: 0, priority: -2
Jan 08 09:47:11 surprise systemd-logind[1887]: Not enough swap for hibernation, 
Active(anon)=1134696 kB, size=1003516 kB, used=0 kB, threshold=98%

If I set /sys/power/resume correctly, then I see:

Jan 08 09:48:10 surprise systemd-logind[1887]: Sleep mode "disk" is supported 
by the kernel.
Jan 08 09:48:10 surprise systemd-logind[1887]: /dev/dm-2: is a candidate device.
Jan 08 09:48:10 surprise systemd-logind[1887]: /dev/sda2: ignoring device with 
lower priority
Jan 08 09:48:10 surprise systemd-logind[1887]: No swap partitions or files 
matching resume config were found in /proc/swaps.

(I haven't been able to test what happens if I restart logind because I
hit https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910769 if I
try; my plan is add an ExecStartPre which sets the resume device to
logind's unit file, to see if that does the trick.)

Does anyone know what in the system is _meant_ to be setting
/sys/power/resume?  Is it possible I'm missing some configuration
somewhere to have that setting happen?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1910252

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

Status in systemd package in Ubuntu:
  New

Bug description:
  I have plenty of swap space configured in my system:

  $ cat /sys/power/image_size
  6642229248   # ~ 6.2GiB

  $ swapon
  NAME  TYPE   SIZE USED PRIO
  /dev/dm-2 partition  980M   0B   -2
  /dev/sda2 partition 97.7G   0B   -3

  But when I attempt to hibernate:

  $ sudo systemctl hibernate
  Failed to hibernate system via logind: Not enough swap space for hibernation

  I have the swap partition configured as my resume device in my kernel
  commandline:

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro 
quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off 
vt.handoff=7
  $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756
  lrwxrwxrwx 1 root root 10 Jan  5 09:08 
/dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2

  (I'm not really sure how to further debug my issue, any assistance
  would be appreciated!)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.6-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jan  5 09:33:04 2021
  InstallationDate: Installed on 2019-05-07 (608 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (196 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

Re: [Touch-packages] [Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

2021-01-07 Thread Dan Watkins
And, for clarity, when systemd does hibernate, I haven't had issues
restoring: it's just getting systemd to find the correct swap space to
use that's been the issue.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1910252

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

Status in systemd package in Ubuntu:
  New

Bug description:
  I have plenty of swap space configured in my system:

  $ cat /sys/power/image_size
  6642229248   # ~ 6.2GiB

  $ swapon
  NAME  TYPE   SIZE USED PRIO
  /dev/dm-2 partition  980M   0B   -2
  /dev/sda2 partition 97.7G   0B   -3

  But when I attempt to hibernate:

  $ sudo systemctl hibernate
  Failed to hibernate system via logind: Not enough swap space for hibernation

  I have the swap partition configured as my resume device in my kernel
  commandline:

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro 
quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off 
vt.handoff=7
  $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756
  lrwxrwxrwx 1 root root 10 Jan  5 09:08 
/dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2

  (I'm not really sure how to further debug my issue, any assistance
  would be appreciated!)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.6-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jan  5 09:33:04 2021
  InstallationDate: Installed on 2019-05-07 (608 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (196 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910252/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


Re: [Touch-packages] [Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

2021-01-07 Thread Dan Watkins
On Thu, Jan 07, 2021 at 03:23:36PM -, Dimitri John Ledkov wrote:
> Also, you do disable secureboot as well right? Because with secureboot
> on, even though hybernation image is created, it will be ignored and
> not used upon resume.

Yep, Secure Boot is disabled on this system.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1910252

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

Status in systemd package in Ubuntu:
  New

Bug description:
  I have plenty of swap space configured in my system:

  $ cat /sys/power/image_size
  6642229248   # ~ 6.2GiB

  $ swapon
  NAME  TYPE   SIZE USED PRIO
  /dev/dm-2 partition  980M   0B   -2
  /dev/sda2 partition 97.7G   0B   -3

  But when I attempt to hibernate:

  $ sudo systemctl hibernate
  Failed to hibernate system via logind: Not enough swap space for hibernation

  I have the swap partition configured as my resume device in my kernel
  commandline:

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro 
quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off 
vt.handoff=7
  $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756
  lrwxrwxrwx 1 root root 10 Jan  5 09:08 
/dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2

  (I'm not really sure how to further debug my issue, any assistance
  would be appreciated!)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.6-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jan  5 09:33:04 2021
  InstallationDate: Installed on 2019-05-07 (608 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (196 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910252/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

2021-01-07 Thread Dimitri John Ledkov
these things are very weird indeed.


Also, you do disable secureboot as well right? Because with secureboot on, even 
though hybernation image is created, it will be ignored and not used upon 
resume.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1910252

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

Status in systemd package in Ubuntu:
  New

Bug description:
  I have plenty of swap space configured in my system:

  $ cat /sys/power/image_size
  6642229248   # ~ 6.2GiB

  $ swapon
  NAME  TYPE   SIZE USED PRIO
  /dev/dm-2 partition  980M   0B   -2
  /dev/sda2 partition 97.7G   0B   -3

  But when I attempt to hibernate:

  $ sudo systemctl hibernate
  Failed to hibernate system via logind: Not enough swap space for hibernation

  I have the swap partition configured as my resume device in my kernel
  commandline:

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro 
quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off 
vt.handoff=7
  $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756
  lrwxrwxrwx 1 root root 10 Jan  5 09:08 
/dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2

  (I'm not really sure how to further debug my issue, any assistance
  would be appreciated!)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.6-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jan  5 09:33:04 2021
  InstallationDate: Installed on 2019-05-07 (608 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (196 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910252/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

2021-01-07 Thread Dan Watkins
> So, looking at the systemd code at
https://github.com/systemd/systemd/blob/c5b6b4b6d08cf4c16a871401358faeb5a186c02a/src/shared
/sleep-config.c#L422-L426, perhaps setting /sys/power/resume to the
correct device actually was the workaround/fix?

The confusing part about this is that I don't believe I set
/sys/power/resume when I first booted, so I guess that was set correctly
for some reason this time around?  (Or maybe something else is going on
entirely, of course.)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1910252

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

Status in systemd package in Ubuntu:
  New

Bug description:
  I have plenty of swap space configured in my system:

  $ cat /sys/power/image_size
  6642229248   # ~ 6.2GiB

  $ swapon
  NAME  TYPE   SIZE USED PRIO
  /dev/dm-2 partition  980M   0B   -2
  /dev/sda2 partition 97.7G   0B   -3

  But when I attempt to hibernate:

  $ sudo systemctl hibernate
  Failed to hibernate system via logind: Not enough swap space for hibernation

  I have the swap partition configured as my resume device in my kernel
  commandline:

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro 
quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off 
vt.handoff=7
  $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756
  lrwxrwxrwx 1 root root 10 Jan  5 09:08 
/dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2

  (I'm not really sure how to further debug my issue, any assistance
  would be appreciated!)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.6-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jan  5 09:33:04 2021
  InstallationDate: Installed on 2019-05-07 (608 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (196 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910252/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

2021-01-07 Thread Dan Watkins
I enabled systemd-logind debug logging, and I saw:

Jan 06 17:45:18 surprise systemd-logind[73027]: Got message type=method_call 
sender=:1.264 destination=:1.220 path=/org/freedesktop/login1 
interface=org.freedesktop.login1.Manager member=CanHibernate cookie=6 
reply_cookie=0 signature=n/a error-name=n/a error-message=n/a
Jan 06 17:45:18 surprise systemd-logind[73027]: Sleep mode "disk" is supported 
by the kernel.
Jan 06 17:45:18 surprise systemd-logind[73027]: /dev/dm-2: is a candidate 
device.
Jan 06 17:45:18 surprise systemd-logind[73027]: /dev/sda2: ignoring device with 
lower priority
Jan 06 17:45:18 surprise systemd-logind[73027]: No swap partitions or files 
matching resume config were found in /proc/swaps.
Jan 06 17:45:18 surprise systemd-logind[73027]: Sent message type=method_return 
sender=n/a destination=:1.264 path=n/a interface=n/a member=n/a cookie=185 
reply_cookie=6 signature=s error-name=n/a error-message=n/a
Jan 06 17:45:18 surprise systemd-logind[73027]: Got message type=method_call 
sender=:1.264 destination=:1.220 path=/org/freedesktop/login1 
interface=org.freedesktop.login1.Manager member=CanHybridSleep cookie=7 
reply_cookie=0 signature=n/a error-name=n/a error-message=n/a
Jan 06 17:45:18 surprise systemd-logind[73027]: Sleep mode "disk" is supported 
by the kernel.
Jan 06 17:45:18 surprise systemd-logind[73027]: /dev/dm-2: is a candidate 
device.
Jan 06 17:45:18 surprise systemd-logind[73027]: /dev/sda2: ignoring device with 
lower priority
Jan 06 17:45:18 surprise systemd-logind[73027]: No swap partitions or files 
matching resume config were found in /proc/swaps.

However, after a reboot this morning, hibernation does seem to be
working, and I instead see:

Jan 07 09:29:37 surprise systemd-logind[1798]: Got message type=method_call 
sender=:1.125 destination=org.freedesktop.login1 path=/org/freedesktop/login1 
interface=org.freedesktop.login1.Manager member=Hibernate cookie=3 
reply_cookie=0 signature=b error-name=n/a error-message=n/a
Jan 07 09:29:37 surprise systemd-logind[1798]: Sleep mode "disk" is supported 
by the kernel.
Jan 07 09:29:37 surprise systemd-logind[1798]: /dev/sda2: device matches 
configured resume settings.
Jan 07 09:29:37 surprise systemd-logind[1798]: Hibernation will attempt to use 
swap entry with path: /dev/sda2, device: 8:2, offset: 0, priority: -3
Jan 07 09:29:37 surprise systemd-logind[1798]: Enough swap for hibernation, 
Active(anon)=3080788 kB, size=102401108 kB, used=0 kB, threshold=98%

So it looks like the issue is that my resume device was not being
detected correctly previously, meaning that priority was being used
(which resulted in the wrong device being selected).

So, looking at the systemd code at
https://github.com/systemd/systemd/blob/c5b6b4b6d08cf4c16a871401358faeb5a186c02a/src/shared
/sleep-config.c#L422-L426, perhaps setting /sys/power/resume to the
correct device actually was the workaround/fix?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1910252

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

Status in systemd package in Ubuntu:
  New

Bug description:
  I have plenty of swap space configured in my system:

  $ cat /sys/power/image_size
  6642229248   # ~ 6.2GiB

  $ swapon
  NAME  TYPE   SIZE USED PRIO
  /dev/dm-2 partition  980M   0B   -2
  /dev/sda2 partition 97.7G   0B   -3

  But when I attempt to hibernate:

  $ sudo systemctl hibernate
  Failed to hibernate system via logind: Not enough swap space for hibernation

  I have the swap partition configured as my resume device in my kernel
  commandline:

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro 
quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off 
vt.handoff=7
  $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756
  lrwxrwxrwx 1 root root 10 Jan  5 09:08 
/dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2

  (I'm not really sure how to further debug my issue, any assistance
  would be appreciated!)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.6-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jan  5 09:33:04 2021
  InstallationDate: Installed on 2019-05-07 (608 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
  SourcePackage: systemd
  

[Touch-packages] [Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

2021-01-05 Thread Dan Watkins
> $ cat /sys/power/resume
> 0:0

This was a red herring.  What I have found consistently fixes this is:

$ sudo swapoff /dev/sda2
$ sudo swapon -p 1 /dev/sda2

Hibernate then succeeds.  However, this is not how I want my system
configured: I have a small swap partition on my SSD, which I would like
to be used for swap under normal operation; changing the priority to
address my hibernation issues means that I'm using my slow HDD as
regular swap.

For reference, after the above changes:

$ swapon
NAME  TYPE   SIZE USED PRIO
/dev/dm-2 partition  980M   0B   -2
/dev/sda2 partition 97.7G   0B1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1910252

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

Status in systemd package in Ubuntu:
  New

Bug description:
  I have plenty of swap space configured in my system:

  $ cat /sys/power/image_size
  6642229248   # ~ 6.2GiB

  $ swapon
  NAME  TYPE   SIZE USED PRIO
  /dev/dm-2 partition  980M   0B   -2
  /dev/sda2 partition 97.7G   0B   -3

  But when I attempt to hibernate:

  $ sudo systemctl hibernate
  Failed to hibernate system via logind: Not enough swap space for hibernation

  I have the swap partition configured as my resume device in my kernel
  commandline:

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro 
quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off 
vt.handoff=7
  $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756
  lrwxrwxrwx 1 root root 10 Jan  5 09:08 
/dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2

  (I'm not really sure how to further debug my issue, any assistance
  would be appreciated!)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.6-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jan  5 09:33:04 2021
  InstallationDate: Installed on 2019-05-07 (608 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (196 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910252/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

2021-01-05 Thread Dan Watkins
Oh, and `free -h`:

  totalusedfree  shared  buff/cache   available
Mem:   15Gi   6.0Gi   667Mi   567Mi   9.0Gi   8.8Gi
Swap:  98Gi13Mi98Gi

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1910252

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

Status in systemd package in Ubuntu:
  New

Bug description:
  I have plenty of swap space configured in my system:

  $ cat /sys/power/image_size
  6642229248   # ~ 6.2GiB

  $ swapon
  NAME  TYPE   SIZE USED PRIO
  /dev/dm-2 partition  980M   0B   -2
  /dev/sda2 partition 97.7G   0B   -3

  But when I attempt to hibernate:

  $ sudo systemctl hibernate
  Failed to hibernate system via logind: Not enough swap space for hibernation

  I have the swap partition configured as my resume device in my kernel
  commandline:

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro 
quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off 
vt.handoff=7
  $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756
  lrwxrwxrwx 1 root root 10 Jan  5 09:08 
/dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2

  (I'm not really sure how to further debug my issue, any assistance
  would be appreciated!)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.6-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jan  5 09:33:04 2021
  InstallationDate: Installed on 2019-05-07 (608 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (196 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910252/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

2021-01-05 Thread Dan Watkins
/sys/power/image_size represents the required amount of space for the
image; that said, the machine has 16G RAM total, so even if that were
maxed out, it would fit into 97.7G comfortably.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1910252

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

Status in systemd package in Ubuntu:
  New

Bug description:
  I have plenty of swap space configured in my system:

  $ cat /sys/power/image_size
  6642229248   # ~ 6.2GiB

  $ swapon
  NAME  TYPE   SIZE USED PRIO
  /dev/dm-2 partition  980M   0B   -2
  /dev/sda2 partition 97.7G   0B   -3

  But when I attempt to hibernate:

  $ sudo systemctl hibernate
  Failed to hibernate system via logind: Not enough swap space for hibernation

  I have the swap partition configured as my resume device in my kernel
  commandline:

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro 
quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off 
vt.handoff=7
  $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756
  lrwxrwxrwx 1 root root 10 Jan  5 09:08 
/dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2

  (I'm not really sure how to further debug my issue, any assistance
  would be appreciated!)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.6-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jan  5 09:33:04 2021
  InstallationDate: Installed on 2019-05-07 (608 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (196 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910252/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

2021-01-05 Thread Dimitri John Ledkov
and how much RAM does the system have? and how much is used? and of
swap?

free -h

free swap should be more then used memory.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1910252

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

Status in systemd package in Ubuntu:
  New

Bug description:
  I have plenty of swap space configured in my system:

  $ cat /sys/power/image_size
  6642229248   # ~ 6.2GiB

  $ swapon
  NAME  TYPE   SIZE USED PRIO
  /dev/dm-2 partition  980M   0B   -2
  /dev/sda2 partition 97.7G   0B   -3

  But when I attempt to hibernate:

  $ sudo systemctl hibernate
  Failed to hibernate system via logind: Not enough swap space for hibernation

  I have the swap partition configured as my resume device in my kernel
  commandline:

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro 
quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off 
vt.handoff=7
  $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756
  lrwxrwxrwx 1 root root 10 Jan  5 09:08 
/dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2

  (I'm not really sure how to further debug my issue, any assistance
  would be appreciated!)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.6-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jan  5 09:33:04 2021
  InstallationDate: Installed on 2019-05-07 (608 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (196 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910252/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"

2021-01-05 Thread Dan Watkins
One thing I have noticed, is that on boot:

$ cat /sys/power/resume
0:0

I can't test right now, but I _think_ that before the holiday break
setting that to 8:2[0] and restarting systemd-logind meant that
hibernate did then work.

[0] $ ls -l /sys/dev/block/8:2
lrwxrwxrwx 1 root root 0 Jan  5 09:08 /sys/dev/block/8:2 -> 
../../devices/pci:00/:00:01.3/:02:00.1/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda2

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1910252

Title:
  `systemctl hibernate` incorrectly reports "Not enough swap space for
  hibernation"

Status in systemd package in Ubuntu:
  New

Bug description:
  I have plenty of swap space configured in my system:

  $ cat /sys/power/image_size
  6642229248   # ~ 6.2GiB

  $ swapon
  NAME  TYPE   SIZE USED PRIO
  /dev/dm-2 partition  980M   0B   -2
  /dev/sda2 partition 97.7G   0B   -3

  But when I attempt to hibernate:

  $ sudo systemctl hibernate
  Failed to hibernate system via logind: Not enough swap space for hibernation

  I have the swap partition configured as my resume device in my kernel
  commandline:

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro 
quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off 
vt.handoff=7
  $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756
  lrwxrwxrwx 1 root root 10 Jan  5 09:08 
/dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2

  (I'm not really sure how to further debug my issue, any assistance
  would be appreciated!)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.6-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jan  5 09:33:04 2021
  InstallationDate: Installed on 2019-05-07 (608 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (196 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910252/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp