From owner-freebsd-arm@freebsd.org Tue Sep 11 09:44:59 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD760108AC31 for ; Tue, 11 Sep 2018 09:44:59 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic309-13.consmr.mail.bf2.yahoo.com (sonic309-13.consmr.mail.bf2.yahoo.com [74.6.129.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 51DB78E9DD for ; Tue, 11 Sep 2018 09:44:59 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: EvKtiP8VM1n6JCZpfesxwzvsuB2cJf8zopR5p3XQ8ioj6CkJYnutdIZuY4BWhkM c0M.cmgwjHN5uWPxIT96pWwqnCUgg1Ygbm9iJphU7PfhCSqaWazJg_rRf7g2_js2VofOcPvQG1_c a20UgAHFSnasEBOOU.kEI34ViUpKXJ6PXChiz7TyGMpHE3vHu4uO0e4OlejOeYT8w0PF0b5SnSkf Qy8UKavTEQihIF1mMY1yl89df2F1Jzl.Ao5zWZd0uf8CDYEDP.yUibDNyZlhpKi3GcB8tGQYkvDY fgZ088iGDmhK1cH1_tTCAz_.KsbcTOzdnZnO1TTr5EMey7IJ0LSDqjuHq08X7T05QNEplAjAb96u pPg69uPFeS1T26sNiZSVqSZWHYIh2yrX5xuRezpktpOsvcOe62Ig.lGUuqlA5DkCnAGaQOt2pxrz NfDyLxAGg77.YjAqmoKrDWtxjNiUo7GEpnxg46BtN5ElvpIQSwH5hBlTHtmmAqIplD2GXmB2xMq0 M.nRHiZqf1hBwQ50Ch75o34sJbi97FcnnK48BYOoAV.VzAE.ONaRUbiEXOUvet2NRrbz7xubKZbB bF_j4u5r.HTSD2gi8uMArI_KGvXoT1WHL7PMxdf4P4161QMlAo.rlLEW4SF0tczKWAtL1n3m0MJo ONFJzpDe42HMl4vt6U9EhN41ULYX.GRQYiQd41UyEzpQW4NV93vo7l0_c2TktNlUGb96tjiP3tBD x.z52i94YHs.QMmfhhGrhVcsWOVFGeuiuG735OILacviOIus10exC.aaD3ikHN8I3F6m2W_o_Cxn UBjxCTkHvs8tyFj1UYdtgrWA1UfOArtD_ZXWeMcFD1QnZnRVPFYKmEUvCcUhF0PB_FFBF9anseqo a9xNNaHdRy.4A2eQOf9nInaL9w584dU0W5kkm9O8VyHjF9NgtlbmtSim72DCahvuh1eoK6nxhk.n edshj9k7dpZYOfRpTOesEqOCSXHRHZiN22BuhYUeZGbmF70vWs.S5FmdjZ6t0qP6shVuAEuiGtIc G6HScBV595A-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.bf2.yahoo.com with HTTP; Tue, 11 Sep 2018 09:44:53 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp419.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 32c42484b2aa6d29488d41a9bc0fb0e4; Tue, 11 Sep 2018 09:44:51 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: FYI: devel/kyua 14 failures for head -r338518M based build in a Pine64+ 2GB (aarch64 / cortexA53 / A64) context Message-Id: Date: Tue, 11 Sep 2018 02:44:49 -0700 To: freebsd-arm , FreeBSD Current X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2018 09:45:00 -0000 [No zfs use, just a UFS e.MMC filesystem on a microsd adapter.] I got 14 failures. I've not enabled any configuration properties. I do not know if official devel/kyua tests are part of the head -> stable transition for any tier or not. I'm not claiming to know if anything here could be a significant issue. Someone may want to test an official aarch64 build rather than presume that my personal build is good enough. But I expect that its results should be strongly suggestive, even if an official tests uses a more normal-for-FreeBSD configuration of an aarch64 system. The e.MMC is V5.1 is operating in DDR52 mode and is faster than normal configurations for the Pine 64+ 2GB. TRIM is in use for the UFS file system. This might let some things pass that otherwise would time out. =3D=3D=3D> Failed tests lib/libc/resolv/resolv_test:getaddrinfo_test -> failed: = /usr/src/lib/libc/tests/resolv/resolv_test.c:299: = run_tests(_hostlist_file, METHOD_GETADDRINFO) =3D=3D 0 not met = [98.834s] lib/libc/ssp/ssp_test:vsnprintf -> failed: atf-check failed; see the = output of the test for details [0.107s] lib/libc/ssp/ssp_test:vsprintf -> failed: atf-check failed; see the = output of the test for details [0.105s] lib/libproc/proc_test:symbol_lookup -> failed: = /usr/src/lib/libproc/tests/proc_test.c:143: memcmp(sym, &tsym, = sizeof(*sym)) !=3D 0 [0.057s] lib/msun/trig_test:accuracy -> failed: 3 checks failed; see output for = more details [0.013s] lib/msun/trig_test:special -> failed: 8 checks failed; see output for = more details [0.013s] local/kyua/utils/stacktrace_test:dump_stacktrace__integration -> = failed: Line 391: atf::utils::grep_file("#0", = exit_handle.stderr_file().str()) not met [4.015s] local/kyua/utils/stacktrace_test:dump_stacktrace__ok -> failed: Line = 420: atf::utils::grep_file("^frame 1$", exit_handle.stderr_file().str()) = not met [4.470s] local/kyua/utils/stacktrace_test:dump_stacktrace_if_available__append = -> failed: Line 560: atf::utils::grep_file("frame 1", = exit_handle.stderr_file().str()) not met [4.522s] local/kyua/utils/stacktrace_test:find_core__found__long -> failed: = Core dumped, but no candidates found [3.988s] local/kyua/utils/stacktrace_test:find_core__found__short -> failed: = Core dumped, but no candidates found [4.014s] sys/kern/ptrace_test:ptrace__PT_STEP_with_signal -> failed: = /usr/src/tests/sys/kern/ptrace_test.c:3465: WSTOPSIG(status) =3D=3D = SIGABRT not met [0.017s] usr.bin/indent/functional_test:nsac -> failed: atf-check failed; see = the output of the test for details [0.151s] usr.bin/indent/functional_test:sac -> failed: atf-check failed; see = the output of the test for details [0.150s] =3D=3D=3D> Summary Results read from = /root/.kyua/store/results.usr_tests.20180911-070147-413583.db Test cases: 7301 total, 212 skipped, 37 expected failures, 116 broken, = 14 failed Total time: 6688.125s I'll note that the console reported over 73720 messages like (with = figures where I've listed ????'s): md????.eli: Failed to authenticate ???? bytes of data at offset ????. There are also device created and destroyed/removed notices with related material. Overall there were over 84852 lines reported with "GEOM_ELI:" on the line. This did not prevent tests from passing. (The huge console output is unfortunate in my view: it makes finding interesting console messages a problem while watching messages go by.) I did get the console message block: kern.ipc.maxpipekva exceeded; see tuning(7) Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of = memory. Sep 11 01:36:25 pine64 kernel: nd6_dad_timer: called with non-tentative = address (epair2Freed UMA keg (rtentry) was not empty (18 = items). Lost 1 pages of memory. a) Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of = memory. Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of = memory. Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of = memory. Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of = memory. Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of = memory. Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of = memory. Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of = memory. Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of = memory. Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of = memory. Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of = memory. Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of = memory. Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of = memory. Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of = memory. Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of = memory. Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of = memory. But no failure reports seemed to be associated. Still, I wonder if the block of messages is significant. Some other console messages seen (extracted from various places): GEOM_MIRROR: Request failed (error=3D5). md29[READ(offset=3D524288, = length=3D2048)] GEOM_MIRROR: Request failed (error=3D6). md28[READ(offset=3D1048576, = length=3D2048)] GEOM_MIRROR: Request failed (error=3D5). md28[WRITE(offset=3D0, = length=3D2048)] GEOM_MIRROR: Cannot write metadata on md29 (device=3Dmirror.KRYGpE, = error=3D5). GEOM_MIRROR: Cannot update metadata on disk md29 (error=3D5). GEOM_MIRROR: Request failed (error=3D5). md28[READ(offset=3D0, = length=3D131072)] GEOM_MIRROR: Synchronization request failed (error=3D5). = mirror/mirror.YQGUHJ[READ(offset=3D0, length=3D131072)] GEOM_MIRROR: Request failed (error=3D5). md29[READ(offset=3D0, = length=3D131072)] Again no failure reports seemed to be associated. Some or all of the following may be normal/expected: Sep 11 00:05:44 pine64 kernel: pid 21057 (process_test), uid 0: exited = on signal 3 (core dumped) Sep 11 00:05:49 pine64 kernel: pid 21071 (sanity_test), uid 0: exited on = signal 6 (core dumped) Sep 11 00:05:54 pine64 kernel: pid 21074 (sanity_test), uid 0: exited on = signal 6 (core dumped) Sep 11 00:05:58 pine64 kernel: pid 21077 (sanity_test), uid 0: exited on = signal 6 (core dumped) Sep 11 00:06:03 pine64 kernel: pid 21080 (sanity_test), uid 0: exited on = signal 6 (core dumped) Sep 11 00:06:44 pine64 kernel: pid 23170 (cpp_helpers), uid 0: exited on = signal 6 (core dumped) Sep 11 00:06:49 pine64 kernel: pid 23306 (c_helpers), uid 977: exited on = signal 6 (core dumped) Sep 11 00:06:54 pine64 kernel: pid 23308 (cpp_helpers), uid 977: exited = on signal 6 (core dumped) Sep 11 00:18:44 pine64 kernel: pid 38227 (assert_test), uid 0: exited on = signal 6 Sep 11 00:51:38 pine64 kernel: pid 39883 (getenv_test), uid 0: exited on = signal 11 (core dumped) Sep 11 00:51:51 pine64 kernel: pid 40063 (memcmp_test), uid 0: exited on = signal 6 (core dumped) Sep 11 00:53:26 pine64 kernel: pid 40627 (wait_test), uid 0: exited on = signal 11 (core dumped) Sep 11 00:53:27 pine64 kernel: pid 40632 (wait_test), uid 0: exited on = signal 3 Sep 11 00:53:27 pine64 kernel: pid 40634 (wait_test), uid 0: exited on = signal 3 Sep 11 07:53:32 pine64 h_fgets[41013]: stack overflow detected; = terminated Sep 11 00:53:32 pine64 kernel: pid 41013 (h_fgets), uid 0: exited on = signal 6 Sep 11 07:53:33 pine64 h_gets[41049]: stack overflow detected; = terminated Sep 11 00:53:33 pine64 kernel: pid 41049 (h_gets), uid 0: exited on = signal 6 Sep 11 07:53:33 pine64 h_memcpy[41066]: stack overflow detected; = terminated Sep 11 00:53:33 pine64 kernel: pid 41066 (h_memcpy), uid 0: exited on = signal 6 Sep 11 07:53:33 pine64 h_memmove[41083]: stack overflow detected; = terminated Sep 11 00:53:33 pine64 kernel: pid 41083 (h_memmove), uid 0: exited on = signal 6 Sep 11 07:53:33 pine64 h_memset[41100]: stack overflow detected; = terminated Sep 11 00:53:33 pine64 kernel: pid 41100 (h_memset), uid 0: exited on = signal 6 Sep 11 07:53:33 pine64 h_read[41135]: stack overflow detected; = terminated Sep 11 00:53:33 pine64 kernel: pid 41135 (h_read), uid 0: exited on = signal 6 Sep 11 07:53:33 pine64 h_readlink[41152]: stack overflow detected; = terminated Sep 11 00:53:33 pine64 kernel: pid 41152 (h_readlink), uid 0: exited on = signal 6 Sep 11 07:53:33 pine64 h_snprintf[41169]: stack overflow detected; = terminated Sep 11 00:53:33 pine64 kernel: pid 41169 (h_snprintf), uid 0: exited on = signal 6 Sep 11 07:53:34 pine64 h_sprintf[41186]: stack overflow detected; = terminated Sep 11 00:53:34 pine64 kernel: pid 41186 (h_sprintf), uid 0: exited on = signal 6 Sep 11 07:53:34 pine64 h_stpcpy[41203]: stack overflow detected; = terminated Sep 11 00:53:34 pine64 kernel: pid 41203 (h_stpcpy), uid 0: exited on = signal 6 Sep 11 07:53:34 pine64 h_stpncpy[41220]: stack overflow detected; = terminated Sep 11 00:53:34 pine64 kernel: pid 41220 (h_stpncpy), uid 0: exited on = signal 6 Sep 11 07:53:34 pine64 h_strcat[41237]: stack overflow detected; = terminated Sep 11 00:53:34 pine64 kernel: pid 41237 (h_strcat), uid 0: exited on = signal 6 Sep 11 07:53:34 pine64 h_strcpy[41254]: stack overflow detected; = terminated Sep 11 00:53:34 pine64 kernel: pid 41254 (h_strcpy), uid 0: exited on = signal 6 Sep 11 07:53:34 pine64 h_strncat[41271]: stack overflow detected; = terminated Sep 11 00:53:34 pine64 kernel: pid 41271 (h_strncat), uid 0: exited on = signal 6 Sep 11 07:53:34 pine64 h_strncpy[41288]: stack overflow detected; = terminated Sep 11 00:53:34 pine64 kernel: pid 41288 (h_strncpy), uid 0: exited on = signal 6 Sep 11 00:53:41 pine64 kernel: pid 41478 (target_prog), uid 0: exited on = signal 5 (core dumped) Sep 11 00:56:53 pine64 kernel: pid 43967 (exponential_test), uid 0: = exited on signal 6 (core dumped) Sep 11 00:56:58 pine64 kernel: pid 43972 (fenv_test), uid 0: exited on = signal 6 (core dumped) Sep 11 00:57:02 pine64 kernel: pid 43974 (fma_test), uid 0: exited on = signal 6 (core dumped) Sep 11 00:57:07 pine64 kernel: pid 43990 (invtrig_test), uid 0: exited = on signal 6 (core dumped) Sep 11 00:57:13 pine64 kernel: pid 44067 (logarithm_test), uid 0: exited = on signal 6 (core dumped) Sep 11 00:57:17 pine64 kernel: pid 44069 (lrint_test), uid 0: exited on = signal 6 (core dumped) Sep 11 00:57:21 pine64 kernel: pid 44073 (nearbyint_test), uid 0: exited = on signal 6 (core dumped) Sep 11 00:57:26 pine64 kernel: pid 44075 (next_test), uid 0: exited on = signal 6 (core dumped) Sep 11 00:57:31 pine64 kernel: pid 44100 (rem_test), uid 0: exited on = signal 6 (core dumped) Sep 11 00:57:43 pine64 kernel: pid 44248 (exhaust_test), uid 0: exited = on signal 11 (core dumped) I'm not sure that they all would be expected. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)