Hi again, it looks that there was missing bit in some earlier patch included in 4.9 stable kernel : https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.9.y&id=3146a32b39cd78722869bca6e839b3c59155e012 I tested with this single patch on top of 4.9.82-1+deb9u2 and I could do some heavy linux compilation without issue. The latest upstream 4.9.84 has that fix. F. On Mon, 26 Feb 2018 12:33:56 +0100, Frédéric Bonnard <frediz@debian.org> wrote: > Hi, > I got this as well, not immediatly though but adding some > parallelization to the build helped. I'll look into this as well. > > F. > > On Fri, 23 Feb 2018 19:52:35 +0100, Aurelien Jarno <aurel32@debian.org> wrote: > > Source: linux > > Version: 4.9.82-1+deb9u2 > > Severity: critical > > Justification: causes serious data corruption > > > > DSA has installed the latest security kernel (4.9.82-1+deb9u2) on the > > Debian POWER8 machines running ppc64el. While they boot correctly, then > > programs segfault randomly (apt, sbuild, systemd, etc...). Passing > > no_rfi_flush to the command line does not change anything. Looking more > > in details, things looks scarying as some code actually get wrongly > > executed. Here are some build logs examples: > > - https://buildd.debian.org/status/fetch.php?pkg=python-msgpack&arch=ppc64el&ver=0.5.1-1&stamp=1519399908&raw=0 > > - https://buildd.debian.org/status/fetch.php?pkg=python-msgpack&arch=ppc64el&ver=0.5.1-1&stamp=1519396907&raw=0 > > - https://buildd.debian.org/status/fetch.php?pkg=tk8.5&arch=ppc64el&ver=8.5.19-3&stamp=1519362938&raw=0 > > > > While in the above case the packages fail to build from source, I guess > > there are also some cases of undetected corruptions. > > > > I'll try to run the 4.9.80-2 kernel at some point to narrow down the > > issue. > > > >
Attachment:
pgpayGSmUO_on.pgp
Description: PGP signature