Re: A reliable port cross-build failure (hangup) in my context (amd64->armv7 cross build, with native-tool speedup involved)
On 2018-Dec-28, at 12:12, Mark Millard wrote:
> On 2018-Dec-28, at 05:13, Michal Meloun wrote:
>
>> Mark,
>> this is known problem with qemu-user-static.
>> Emulation of every single interruptible syscall is broken by design (it
>> have signal related races). Theses races cannot be solved without major
>> rewrite of syscall emulation code.
>> Unfortunately, nobody actively works on this, I think.
>>
>
> Thanks for the note setting some expectations.
>
> On the evidence that I have I expect that more is going on than that:
>
> A) The hang-up always happens and always in the same place. So
> it would appear that no race is involved.
>
> B) (A) is true even for varying the number of builders in parallel
> (so other builds also happening) and the number of jobs allowed per
> builder. It also fails for only one builder allowed only one process.
> (I get traces from that last kind of context.)
>
> C) The problem started on the package-building servers for armv7
> and armv6 without qemu-user-static having an update (FreeBSD and
> cmake had updates, for example).
>
> D) The problem is only observed for targeting armv7 and armv6 as
> far as I can tell. I've never seen it for aarch64, neither my
> own builds nor when I looked at the package-building server
> history.
>
> At least that is what got me started. (I've since learned that
> qemu-user-static uses fork in place of a requested vfork.)
>
> My ktrace/kdump experiment yesterday showed something odd for the
> kevent that hangs in cmake:
>
> 93172 qemu-arm-static CALL
> kevent(0x3,0x7ffe7d40,0x2,0x7ffd7d40,0x400,0)
> 93172 qemu-arm-static STRU struct kevent[] = { { ident=6,
> filter=EVFILT_READ, flags=0x1, fflags=0, data=0, udata=0x0 }
> { ident=0x0, filter=, flags=0, fflags=0x8,
> data=0x1, udata=0x0 } }
>
> Note the 0x2 argument to kevent and the apparently-odd 2nd entry in the struct
> kevent[]. The kevent use is from cmake.
>
> So far I've not identified a signal being delivered at a time that would seem
> to me to be likely to contribute. (But this is not familiar code so my
> judgment
> is likely not the best.)
>
> Note: I normally run FreeBSD using a non-debug kernel, even when using
> head. (The kernel does have symbols.)
The detail of the signal usage involved leading up to the hang-up,
starting from just before the "press return" for the "make FLAVOR=qt5"
command that I had entered:
The only "Interrupted system call" prior to my killing the hung cmake
process was (kdump -H -r -S output):
93172 100717 qemu-arm-static CALL execve[59](0x10392,0x8605051a0,0x860cf5400)
93172 101706 qemu-arm-static RET nanosleep[240] -1 errno 4 Interrupted
system call
93172 100717 qemu-arm-static NAMI "/bin/sh"
93172 100717 sh RET execve[59] JUSTRETURN
93172 100717 sh CALL readlink[58](0x207a65,0x7fffccc0,0x400)
This is where ninja (via qemu-arm-static) execve's the amd64-native /bin/sh (to
in turn later run cmake via qemu-arm-static). (This was after the fork [for the
requested vfork].) So it is for the close-down of the thread that was in
nanosleep.
There were no PSIG's and no sigreturn's prior to the kill according to the
kdump output.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
[Bug 234070] problem with lld and wildcard characters in version scripts
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234070 --- Comment #1 from Tijl Coosemans --- Created attachment 200601 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=200601&action=edit qt5-version.patch Quoting https://bugs.llvm.org/show_bug.cgi?id=40176: "If more than one clause in a version script match the same symbol, the last one takes precedence. Thus, if you have the catch-all clause at end (i.e. "*"), it overwrites everything." This patch for Qt5 changes the version scripts to put the catch-all first. Note that if this is committed all ports that depend on Qt5 need to be rebuilt because many library symbols will get a different (corrected) version label. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
[Bug 234070] problem with lld and wildcard characters in version scripts
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234070 Mark Linimon changed: What|Removed |Added Keywords||patch -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
[Bug 234070] devel/qt5: problem with lld and wildcard characters in version scripts
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234070 Tijl Coosemans changed: What|Removed |Added CC||toolch...@freebsd.org Assignee|toolch...@freebsd.org |k...@freebsd.org Summary|problem with lld and|devel/qt5: problem with lld |wildcard characters in |and wildcard characters in |version scripts |version scripts --- Comment #2 from Tijl Coosemans --- Assign to kde@ for patch review. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
[Bug 234480] multimedia/aom: clang 7 crashes with aom >= 1.0.0.1109
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234480 Dimitry Andric changed: What|Removed |Added CC||d...@freebsd.org Status|New |Open Assignee|toolch...@freebsd.org |d...@freebsd.org --- Comment #3 from Dimitry Andric --- Reproduced, minimized and reported upstream: https://bugs.llvm.org/show_bug.cgi?id=40181 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
[Bug 234480] multimedia/aom: clang 7 crashes with aom >= 1.0.0.1109
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234480 Rodney W. Grimes changed: What|Removed |Added CC||toolch...@freebsd.org -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
[Bug 234480] multimedia/aom: clang 7 crashes with aom >= 1.0.0.1109
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234480 Dimitry Andric changed: What|Removed |Added CC||bro...@freebsd.org --- Comment #8 from Dimitry Andric --- (In reply to doctor from comment #7) > Crash on compile now > > Assertion failed: ((VT.getVectorNumElements() + N2C->getZExtValue() <= > N1.getValueType().getVectorNumElements()) && "Extract subvector overflow!"), > function getNode, file > /usr/ports/devel/llvm70/work/llvm-7.0.1.src/lib/CodeGen/SelectionDAG/ > SelectionDAG.cpp, line 4708. > Stack dump: > 0. Program arguments: /usr/local/llvm70/bin/clang-7 Ah, you're using the port version of clang 7.0, which doesn't yet have the patch. It's a little annoying that we have to apply those in two places. Brooks, are you OK with adding the patches of base r342592 and base r342593 to the llvm70 port? I can put up review if you like -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
[Bug 234480] multimedia/aom: clang 7 crashes with aom >= 1.0.0.1109
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234480 Jan Beich changed: What|Removed |Added Flags||maintainer-feedback?(brooks ||@FreeBSD.org) --- Comment #9 from Jan Beich --- (In reply to Dimitry Andric from comment #5) > Please re-check after base r342592, and close if it is now fixed. I confirm, builds fine on -CURRENT with base Clang 7: - 13.0 i386: https://ptpb.pw/-noq (CPUTYPE=native) - 13.0 amd64: https://ptpb.pw/qPa_ Leaving open per comment 8. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
