Date: Tue, 11 Sep 2018 02:44:49 -0700 From: Mark Millard <marklmi@yahoo.com> To: freebsd-arm <freebsd-arm@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: FYI: devel/kyua 14 failures for head -r338518M based build in a Pine64+ 2GB (aarch64 / cortexA53 / A64) context Message-ID: <C7047A90-89C6-4CB9-A1F2-339A6E1256A4@yahoo.com>
next in thread | raw e-mail | index | archive | help
[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 <REPLACED>(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)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C7047A90-89C6-4CB9-A1F2-339A6E1256A4>