"shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs.

Bug #1832754 reported by Tim Ritberg
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
systemd
Fix Released
Unknown
systemd (Ubuntu)
Fix Released
Undecided
Unassigned
Bionic
Fix Released
Medium
Dan Streetman

Bug Description

[impact]

shutdown sometimes fails to unmount some fs, which causes shutdown hang

[test case]

it's unclear what the specific configuration is to be able to reproduce this, but there are some examples in the upstream bug

[regression potential]

as this adjusts shutdown umounting, any regression would likely involve either failure to unmount some filesystems on shutdown and/or failure to shutdown the system.

[scope]

this is needed for b.

this is fixed upstream by PR 8429 which is included starting in v239, so this is fixed already in Focal and later.

this was caused by upstream commit d5641e0d7e8 which was added in v236, so this bug is not present in x.

[original description]

I am using Xubuntu 18.04 64 bit and got "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs.

systemd: 237-3ubuntu10.22

It's this issue:
https://github.com/systemd/systemd/issues/8155

affects: nvidia-graphics-drivers-390 (Ubuntu) → systemd (Ubuntu)
Revision history for this message
Sebastien Bacher (seb128) wrote :

Upstream discussion points to https://github.com/systemd/systemd/pull/8429

summary: - ubuntu-bug systemd
+ "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or
+ reboot and hangs.
Changed in systemd:
status: Unknown → Fix Released
Revision history for this message
Dan Streetman (ddstreet) wrote :

Do you have a way to reproduce this? It likely only needs commit 8645ffd12b3cc7b0292acd9e1d691c4fab4cf409 and/or e783b4902f387640bba12496936d01e967545c3c but without a way to reproduce/test, it's hard to say if more of the upstream commits are needed.

tags: added: ddstreet
Changed in systemd (Ubuntu):
status: New → Fix Released
Dan Streetman (ddstreet)
description: updated
Changed in systemd (Ubuntu Bionic):
assignee: nobody → Dan Streetman (ddstreet)
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
Steve Langasek (vorlon) wrote :

> it's unclear what the specific configuration is to be able to reproduce this, but there are some examples in the upstream bug

So how do you intend to complete this SRU if there is no test case for verifying?

Changed in systemd (Ubuntu Bionic):
status: In Progress → Incomplete
Revision history for this message
Dan Streetman (ddstreet) wrote :

> So how do you intend to complete this SRU if there is no test case for verifying?

intermittent issues frequently are not easily reproducable, and sometimes require specific system configuration that can't be completely identified and duplicated, even by those experiencing the bug. Expecting all SRUs to have a reproducer is a noble goal, but unrealistic.

I suppose you could reject this upload and leave the bug in systemd in Bionic? Although it would probably be more useful to have a review of the code change instead of simply rejecting any fix for lack of a clear reproducer.

Changed in systemd (Ubuntu Bionic):
status: Incomplete → In Progress
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Please test proposed package

Hello Tim, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.42 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in systemd (Ubuntu Bionic):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-bionic
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

As per our discussion, since the changes here are relatively sane and with a low regression risk, I have accepted this without a clear reproducer. Please be sure to try and contact someone that has an affected device/configuration and trying to test it there - if not, your proposed test of rebooting various systems repeatedly to see if any hangs (or other issues) can be seen seems like a decent temporary test case.

Let's reopen the bug in case someone reports it not being fully fixed.

Revision history for this message
Tim Ritberg (xpert-reactos) wrote :

Too late, I am already at 20.04.

Revision history for this message
Dan Streetman (ddstreet) wrote :

with the proposed version of systemd, i've rebooted a system 100 times with no issues.

tags: added: verification-done verification-done-bionic
removed: verification-needed verification-needed-bionic
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (systemd/237-3ubuntu10.42)

All autopkgtests for the newly accepted systemd (237-3ubuntu10.42) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.0/5.0.0-58.62~18.04.1 (armhf)
linux-aws-edge/5.0.0-1019.21~18.04.1 (amd64)
linux-hwe-5.4/5.4.0-42.46~18.04.1 (arm64, armhf)
lxc/3.0.3-0ubuntu1~18.04.1 (arm64)
dovecot/1:2.2.33.2-1ubuntu4.5 (armhf)
casync/2+61.20180112-1 (amd64)
linux-raspi2-5.3/5.3.0-1030.32~18.04.2 (armhf)
umockdev/0.11.1-1 (armhf)
netplan.io/0.99-0ubuntu3~18.04.3 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Dan Streetman (ddstreet) wrote :

as this is the lowest-numbered bug for this systemd upload, here is the autopkgtest failure analysis:

linux-aws-edge is failing due to bug 1890178 which is not caused by this upload, and can be ignored

linux-hwe-5.4 tests appear flaky on all archs, but especially so on armhf; the repeated failures for this systemd upload are so far just test timeouts, because it's taking > 6 hours; it seems like this failure should be ignored also.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package systemd - 237-3ubuntu10.42

---------------
systemd (237-3ubuntu10.42) bionic; urgency=medium

  [ Dan Streetman ]
  * d/p/lp1860926/0001-networkd-Allow-to-retain-configs-even-if-carrier-is-.patch,
    d/p/lp1860926/0002-network-Change-IgnoreCarrierLoss-default-to-value-of.patch,
    d/p/lp1860926/0003-network-always-drop-configs-when-corresponding-netwo.patch:
    - Add IgnoreCarrierLoss and default to value of ConfigureWithoutCarrier
      (LP: #1860926)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9a12a31a62f1a50cd3a67a164ee34c546809815e
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3cc3870fde47982a4dda53f820e18065e5488e7e
  * d/e/rules-ubuntu/40-vm-hotadd.rules:
    - Hotadd only offline memory and CPUs
      (LP: #1876018)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ba305d7ad00e80bc1a03f93e6986eef7cbbb18fc
  * d/p/lp1881972-network-strdup-iif-and-oif-when-creating-RoutingPoli.patch:
    - Avoid double-free by strdup'ing iif/oif strings for new policy rules
      (LP: #1881972)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=874056f0d429aaa2cc872c3b35ec33cd3b740483
  * d/p/lp1886197-seccomp-more-comprehensive-protection-against-libsec.patch
    - Fix FTBFS on arm64 due to libseccomp changes (LP: #1886197)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c284a72ca2e3d87bfe1c20afb2fcfb379cda544f
  * d/p/lp1832754/0001-umount-Try-unmounting-even-if-remounting-read-only-f.patch,
    d/p/lp1832754/0002-umount-Don-t-bother-remounting-api-and-ro-filesystem.patch:
    - Try unmounting even if ro-remount fails, and don't bother remounting api/ro fs
      (LP: #1832754)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a518baa673aeaaf42000a3a01b7e03347652b216

  [ Alex Murray, Jamie Strandboge ]
  * d/p/lp1886115-pid1-fix-free-of-uninitialized-pointer-in-unit_fail_.patch:
    - Fix free of uninitialized pointer (LP: #1886115)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=491c76fd0f2fba0007a9b54d63a50f21add643c8

 -- Dan Streetman <email address hidden> Wed, 08 Jul 2020 14:59:14 -0400

Changed in systemd (Ubuntu Bionic):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.