Arch Linux

W54J04S07T

Member

Registered: 2016-06-27

Posts: 107

Re: [SOLVED] shutdown[1]: Failed to wait for process: Protocol error

Oh, and also, the S/W is on github not the Arch git.

The PKGBUILD for the arch package systemd is not in the arch git?
Edit:
The instructions I provided pulled the PKGBUILD from the arch git then makepkg pulls the upstream sources from github then use git log to find the newest commit ID
update the PKGBUILD with that commit ID then use makepkg to build the package.
Edit2:

But, there is a report upstream in the bug report
of system hanging requiring reset/shutdown button.

Can you link that post please searching for reboot, hang or reset I could not find it in the the upstream report.

Interesting, didn't know makepkg would pull from further upstream.

Also see here;
https://github.com/systemd/systemd/issues/8155   post by patrick-ausderau some 23 days ago.

W54J04S07T

Member

Registered: 2016-06-27

Posts: 107

Re: [SOLVED] shutdown[1]: Failed to wait for process: Protocol error

You could build such a package yourself

git clone git://git.archlinux.org/svntogit/packages.git --single-branch --branch "packages/systemd"
cd packages/trunk/
makepkg -Codd
cd src/systemd/
git log
commit d24e70fe8b6bebd9abe4c1578d22cb5536044cc2 (HEAD -> master, origin/master, origin/HEAD)
Author: futpib <futpib@gmail.com>
Date:   Fri Mar 16 17:25:14 2018 +0300

    hwdb: fix comment suggested `udevadm trigger` command (#8465)
cd ../.. #then edit PKGBUILD change _commit to _commit='d24e70fe8b6bebd9abe4c1578d22cb5536044cc2'
makepkg -rsi

Well, after much messing around, I managed to get;

asp checkout systemd
makepkg -C nocheck

to compile a systemd package with latest upstream pulls
( as of March 21 ) and install same in a virtual machine.

Sorry to say... problem was not eliminated.

Tried to do a makepkg today... got compile errors
So no.  Problem not resolved yet.

loqs

Member

Registered: 2014-03-06

Posts: 18,055

Re: [SOLVED] shutdown[1]: Failed to wait for process: Protocol error

What errors?  What commit did you test?  Why the use of --nocheck? https://bbs.archlinux.org/viewtopic.php?id=57855
Edit:
Apologies missed git checkout origin/HEAD to sync the local checkout to origin/HEAD before using git log commit 1147eef0b6a5937526247ff81ca1e5e45205ed16 builds on this system and passes check.

git clone git://git.archlinux.org/svntogit/packages.git --single-branch --branch "packages/systemd"
cd packages/trunk/
makepkg -Codd
cd src/systemd/
git checkout origin/HEAD
git log
commit 1147eef0b6a5937526247ff81ca1e5e45205ed16 (HEAD, origin/master, origin/HEAD, master)
Author: Jan Synacek <jan.synacek@gmail.com>
Date:   Thu Mar 22 19:24:37 2018 +0100

    man/udevadm: remove superfluous --version from subcommands (#8549)
cd ../.. #then edit PKGBUILD change _commit to _commit='1147eef0b6a5937526247ff81ca1e5e45205ed16'
makepkg -rsi

Last edited by loqs (2018-03-22 20:01:33)

W54J04S07T

Member

Registered: 2016-06-27

Posts: 107

Re: [SOLVED] shutdown[1]: Failed to wait for process: Protocol error

...builds on this system and passes check....

Sorry, didn't think anyone would be too concerned about
the meanderings of a "noob".  OTOH, your comment
leaves an important question... did your build
clear up the problem on your system?

loqs

Member

Registered: 2014-03-06

Posts: 18,055

Re: [SOLVED] shutdown[1]: Failed to wait for process: Protocol error

No the latest commit can not be installed on my system because systemd then conflicts with openresolve.
Backporting the fixes for this issue produces a kernel panic at the end of shutdown need to find which of the commits in particular is causing it.
Edit:

_backports=(
  '659b15313b9ca8c7f3f6e523e0d3fd696243ff8b'
  '0494cae03d762eaf2fb7217ee7d70f615dcb5183'
  '1d62d22d9432d5c4a637002c9a29b20d52f25d9a'
  '3bc341bee9fc7dfb41a131246b6fb0afd6ff4407'
  '8645ffd12b3cc7b0292acd9e1d691c4fab4cf409'
  'e783b4902f387640bba12496936d01e967545c3c'
  '456b2199f6ef0378da007e71347657bcf83ae465'
  'b93618644bf24bc0cd87adb1346955d783f6f9b8'
)

This set of cherry-picks fixes the issues and does not cause a kernel panic on this system from the upstream report there may be some more that should be added.
Edit2:
This is on top of 238.51-1 which is the arch version currently in testing based on commit c58ab03f64890e7db88745a843bd4520e307099b
Edit3:
https://github.com/systemd/systemd/pull/8452 contains other commits that may need cherry-picking beyond b93618644bf24bc0cd87adb1346955d783f6f9b8

Last edited by loqs (2018-03-23 02:35:27)

W54J04S07T

Member

Registered: 2016-06-27

Posts: 107

Re: [SOLVED] shutdown[1]: Failed to wait for process: Protocol error

...
Edit2:
This is on top of 238.51-1 which is the arch version currently in testing based on commit c58ab03f64890e7db88745a843bd4520e307099b
Edit3:
https://github.com/systemd/systemd/pull/8452 contains other commits that may need cherry-picking beyond b93618644bf24bc0cd87adb1346955d783f6f9b8

Outstanding.  Light at the end of the tunnel!
What I don't understand, is where 238.51 comes from "upstream".
Is this just a Arch build?  Would it be possible to get the Arch maintainers
to plug in those patches you IDed or is there more to the
process I don't get?

loqs

Member

Registered: 2014-03-06

Posts: 18,055

Re: [SOLVED] shutdown[1]: Failed to wait for process: Protocol error

pkgver() {
  local version count

  cd "$pkgbase-stable"

  version="$(git describe --abbrev=0 --tags)"
  count="$(git rev-list --count ${version}..)"
  printf '%s.%s' "${version#v}" "${count}"
}

238 refers to systemd version 238 from upstream.  51 is the number of commits from systemd-stable included in this version on top of those already in 238.
Yes you could open a bug report asking for those commits to be cherry-picked until version 239.  Right now it is more complicated because of https://bugs.archlinux.org/task/57925.

W54J04S07T

Member

Registered: 2016-06-27

Posts: 107

Re: [SOLVED] shutdown[1]: Failed to wait for process: Protocol error

  Right now it is more complicated because of https://bugs.archlinux.org/task/57925.

FWIW, 238.51-1 is out and of course it still has the same issues.

I did ( in a clean directory );

#asp checkout systemd
>edit PKGBUILD to include your backports from above post
#makepkg -C -f
#pacman -U <<<< the 3 archives -- systemd, systemd-sysvcompat, libsystemd

At this point it "seems" to produce a systemd on the build VM
that works without any problems using your backports.

Last edited by W54J04S07T (2018-03-30 20:54:19)

rgzfxf6bhu

Member

Registered: 2015-10-30

Posts: 100

Re: [SOLVED] shutdown[1]: Failed to wait for process: Protocol error

FWIW, 238.51-1 is out and of course it still has the same issues.

238.76-1 is out and still same problem. For you too?
So I was wondering how to check which commits are already included. Do I just need to check commit 1 to 76 after the release of 238?

loqs

Member

Registered: 2014-03-06

Posts: 18,055

Re: [SOLVED] shutdown[1]: Failed to wait for process: Protocol error

The update was from 51-76,  76-51=25 so you need to check the last 25 commits in https://github.com/systemd/systemd-stab … 238-stable
but you also need the commit arch is using for the starting point to check backwards https://git.archlinux.org/svntogit/pack … d2ed70a#n9
and see if any of the commits has been cherry picked from those needed for this issue.
Alternatively you can build a local version with the listed backports and if they have been applied the build will fail trying to apply them again.

Bronze

Member

Registered: 2016-12-23

Posts: 61

Re: [SOLVED] shutdown[1]: Failed to wait for process: Protocol error

Did anybody succeed at identifying the commits that fix this issue?

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,249

Re: [SOLVED] shutdown[1]: Failed to wait for process: Protocol error

loqs has look at post #30

W54J04S07T

Member

Registered: 2016-06-27

Posts: 107

Re: [SOLVED] shutdown[1]: Failed to wait for process: Protocol error

Alternatively you can build a local version with the listed backports and if they have been applied the build will fail trying to apply them again.

Which is exactly what I just did following my method in post #33

And no, it did NOT fail, and it does seem to work in the VM I used
to build it in.  So I guess they weren't included(?).

BTW, upstream seems to treat this as a "cosmetic" issue,
although some are a bit concerned that systemd can't
seem to control the dismount/mount of these disks.  Anybody
who ever had to deal with DBAs knows just how serious
some people take data security.  So keep in mind,
this solution really only suppresses ( for the most part )
the output of these messages.  In the mean time, we'll have
to wait for a more "definitive" resolution... I guess...

loqs

Member

Registered: 2014-03-06

Posts: 18,055

Re: [SOLVED] shutdown[1]: Failed to wait for process: Protocol error

In the mean time, we'll have to wait for a more "definitive" resolution... I guess...

Who is working on this more "definitive" resolution?  The output is silenced on the first unmount pass if systemd detects there will be a second later pass.

Last edited by loqs (2018-04-26 20:06:42)

unnilquadium

Member

Registered: 2017-08-27

Posts: 86

Re: [SOLVED] shutdown[1]: Failed to wait for process: Protocol error

With systemd 238.133-4 this is now fixed.

Last edited by unnilquadium (2018-06-17 09:07:59)