Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 13 Dec 2024 20:13:00 +0000
From:      bugzilla-noreply@freebsd.org
To:        virtualization@FreeBSD.org
Subject:   [Bug 279901] glibc-2.39-2 and above on the host segfault
Message-ID:  <bug-279901-27103-KRVAmFYMwl@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-279901-27103@https.bugs.freebsd.org/bugzilla/>
References:  <bug-279901-27103@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D279901

Mark Peek <mp@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mp@FreeBSD.org

--- Comment #29 from Mark Peek <mp@FreeBSD.org> ---
(In reply to Darren Henderson from comment #28)

The glibc changes indicated in this bug were specific to amd. I have tried
numerous times to reproduce this issue on intel systems but have not seen it
occur. Sadly I don't have an applicable AMD systems to test on.

Here's my arch install as a bhyve guest:
$ uname -a
Linux archlinux 6.12.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Mon, 09 Dec 2024 14:3=
1:57
+0000 x86_64 GNU/Linux
$ ld.so --list-diagnostics | grep -e version.version
version.version=3D"2.40"

Given some of the ld.so output in previous updates to this bug, I did a dif=
f to
try to find the x86 tunable changes between them.
43c40
< version.version=3D"2.36"
---
> version.version=3D"2.40"
189,191c196,199
< x86.cpu_features.rep_movsb_threshold=3D0x2000
< x86.cpu_features.rep_movsb_stop_threshold=3D0x80000
< x86.cpu_features.rep_stosb_threshold=3D0x800
---
> x86.cpu_features.memset_non_temporal_threshold=3D0xc000000000
> x86.cpu_features.rep_movsb_threshold=3D0x0
> x86.cpu_features.rep_movsb_stop_threshold=3D0xc000000000
> x86.cpu_features.rep_stosb_threshold=3D0xffffffffffffffff

Running binaries with this environment set, so the intel system would run t=
he
same code path in glibc as amd would, did not cause the issue on my intel
system.

GLIBC_TUNABLES=3D"glibc.cpu.x86_memset_non_temporal_threshold=3D0xc00000000=
0:glibc.cpu.x86_rep_movsb_threshold=3D0x0:glibc.cpu.x86_rep_movsb_stop_thre=
shold=3D0xc000000000:glibc.cpu.x86_rep_stosb_threshold=3D0xffffffffffffffff"

If anyone has seen it on intel, it would be great to have the repro steps a=
dded
to this bug.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-279901-27103-KRVAmFYMwl>