Bug#853755: installation-reports: ppc64el fails to boot after installation

[Cyril Brulebois]

Hi Erwan,

Erwan Prioul <erwan at linux.vnet.ibm.com> (2017-02-02):
> AFAIK 4.9.6-x is not yet provided in the daily image for ppc64el.
> It's still the 4.9.2-2. Anyway, I ran a couple of tests with
> 4.9.6-3 and 4.8.15-2, and I got the same error.

The switch from 4.9.2 to 4.9.6 was first seen with d-i daily builds
with this one:
  https://d-i.debian.org/daily-images/ppc64el/20170130-00:02/

> I did another install but this time I took the previous version of
> systemd, 232-8 instead of 232-14 (current version), and it worked.

Ah, right, that's one of the big differences between a boot to d-i and
a boot to the installed system… Good catch!

> I'll reassign this to systemd.

An easy suspect would be:
| commit 7b17f7c824429e95826528d4c6e9d40662ae45ca
| Author: Michael Biebl <biebl at debian.org>
| Date:   Wed Jan 18 19:43:28 2017 +0100
| 
|     Enable seccomp support on ppc64

first published in 232-12.

Feel free to keep me in cc so that I follow the progress here.


KiBi.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20170202/2952f69c/attachment.sig>