main (14-CURRENT) may be unstable on powerpc64

Fri Feb 5 17:35:50 UTC 2021

On Fri, 5 Feb 2021 04:05:55 -0800
Mark Millard via freebsd-ppc <freebsd-ppc at freebsd.org> wrote:

> I am running on a 2-socket/1-core-each PowerMac G5
> (8 GiByte RAM) based on:
> 
> # ~/fbsd-based-on-what-freebsd-main.sh 
> merge-base: 847dfd2803f6c8b077e3ebc68e35adff2c79a65f
> merge-base: CommitDate: 2021-02-03 21:24:22 +0000
> 325d7069b027 (HEAD -> mm-src) mm-src snapshot for mm's patched build
> in git context. 847dfd2803f6 (freebsd/main, freebsd/HEAD, pure-src,
> main) readelf: do not trucate section name with -W FreeBSD FBSDG5L2
> 14.0-CURRENT FreeBSD 14.0-CURRENT mm-src-n244624-325d7069b027
> GENERIC64vtsc-NODBG-dcons  powerpc powerpc64 1400003 1400003
> 
> I attempted to rebuild the ports to get FreeBSD:14 based
> versions but got the below oddity in the process:
> 
> # poudriere bulk -jFBSDpowerpc64 -c -w -f
> ~/origins/powerpc64-origins.txt . . .
> =======================<phase: package
> >============================ ===>  Building package for
> >gettext-tools-0.21  
> Child process pid=44950 terminated abnormally: Segmentation fault
> Child process pid=44956 terminated abnormally: Segmentation fault
> actual-package-depends: dependency on /usr/local/lib/libtextstyle.so
> not registered (normal if it belongs to base) Child process pid=44958
> terminated abnormally: Segmentation fault Child process pid=44962
> terminated abnormally: Segmentation fault Child process pid=44971
> terminated abnormally: Segmentation fault actual-package-depends:
> dependency on /usr/local/lib/libintl.so not registered (normal if it
> belongs to base) Child process pid=44973 terminated abnormally:
> Segmentation fault Child process pid=44977 terminated abnormally:
> Segmentation fault Child process pid=44980 terminated abnormally:
> Segmentation fault actual-package-depends: dependency on
> /usr/local/bin/indexinfo not registered (normal if it belongs to
> base) Child process pid=44982 terminated abnormally: Segmentation
> fault . . .
> 
> Unfortunately, at the package phase, the above sort of thing
> does not lead to a saved copy of the work/ area for the port
> in poudriere and was classified as a Success. I do have the
> console report:
> 
> Feb  4 03:14:17 FBSDG5L2 kernel: pid 44950 (pkg-static), jid 4, uid
> 0: exited on signal 11 Feb  4 03:14:17 FBSDG5L2 kernel: pid 44956
> (pkg-static), jid 4, uid 0: exited on signal 11 Feb  4 03:14:17
> FBSDG5L2 kernel: pid 44958 (pkg-static), jid 4, uid 0: exited on
> signal 11 Feb  4 03:14:17 FBSDG5L2 kernel: pid 44962 (pkg-static),
> jid 4, uid 0: exited on signal 11 Feb  4 03:14:17 FBSDG5L2 kernel:
> pid 44971 (pkg-static), jid 4, uid 0: exited on signal 11 Feb  4
> 03:14:17 FBSDG5L2 kernel: pid 44973 (pkg-static), jid 4, uid 0:
> exited on signal 11 Feb  4 03:14:17 FBSDG5L2 kernel: pid 44977
> (pkg-static), jid 4, uid 0: exited on signal 11 Feb  4 03:14:17
> FBSDG5L2 kernel: pid 44980 (pkg-static), jid 4, uid 0: exited on
> signal 11 Feb  4 03:14:17 FBSDG5L2 kernel: pid 44982 (pkg-static),
> jid 4, uid 0: exited on signal 11
> 
> so which program got the failures is known but I
> did not end up with core files or other such. Also
> they all seem to have happened with the same
> reported time (second scale). (The messages above
> do not show "(core dumped)" either, so even with
> a copy of the work/ area there probably would not
> have been evidence.)
> 
> One point is that the time frame means that the once-a-day
> checking activity (defaults) was likely running in parallel
> with the poudriere activity.
> 
> The above left the "deps" information missing for
> gettex-tools-0.21 .
> 
> When the poudriere run finished, the status was 7 failures
> and 153 skipped because of lack of "deps" information for
> gettext-tools-0.21 :
> 
> [FBSDpowerpc64-default] [2021-02-04_02h19m21s] [committing:] Queued:
> 476 Built: 316 Failed: 7   Skipped: 153 Ignored: 0   Tobuild: 0
> Time: 24:28:45
> 
> For reference, from early in the build:
> 
> [00:24:17] [02] [00:00:00] Building devel/gettext-tools |
> gettext-tools-0.21 . . .
> [00:55:34] [02] [00:31:17] Finished devel/gettext-tools |
> gettext-tools-0.21: Success
> 
> 
> I then tried:
> 
> # poudriere bulk -jFBSDpowerpc64 -i -C -w devel/gettext-tools
> 
> and it built just fine this time:
> 
> [FBSDpowerpc64-default] [2021-02-05_02h50m31s] [committing:] Queued:
> 1  Built: 1  Failed: 0  Skipped: 0  Ignored: 0  Tobuild: 0   Time:
> 00:23:26
> 
> 
> In all cases, each poudriere job was allow to have an active
> process per cpu (so 2 active processes per job). The retry,
> of course, was just one poudriere job.
> 
> So far I've no evidence of problems with the other 315 of 316
> built ports from the first run, including no more pkg-static
> failures.
> 
> 
> I have started up an attempted build of the failed and skipped
> ports.
> 
> 
> I have no known way to repeat the problem on demand and no
> evidence for specifically where pkg-static was executing when
> it failed.
> 
> ===
> Mark Millard
> marklmi at yahoo.com
> ( dsl-only.net went
> away in early 2018-Mar)

This is probably fallout from 710e45c4b, which has since been reverted.
 710e45c4b broke other things like swig as well, which caused a lot of
 poudriere fallout for me (devel/llvm* failed because swig crashed).

Try updating past 33f0540b1 and testing again.

- Justin