On Fri, Oct 04, 2024 at 08:05:31PM +0200, Santiago Vila wrote: > Ok, after some tests this is what seems to happen: > > The test suite works with 3th generation AMD EPYC processorss, > but fails with 4th generation.
Ah! Does the VM set /proc/cpuinfo correctly ? Some years ago, I have seen problem when VM advertised support for CPU features. that where not actually supported. > > What you can do is to install the package in testing and do > > > > mlucas -fftlen 1024 -radset 4 -f 24 -iters 1000 > > mlucas -s m > > mlucas -fftlen 192 -iters 100 -radset 0 > > Thanks for the hint! > > I confirm that the second line (mlucas -s m) makes the SEGV to show. > > I think this (a test suite which segfaults) should never happen, > so I would just disable the offending line (not the whole test suite). /usr/bin/mlucas is actually a shellscript that try the various binaries in /usr/libexec/mlucas/ until it find one that works on the machine. by doing /usr/libexec/mlucas/mlucas-avx512 -fftlen 192 -iters 100 -radset 0 /usr/libexec/mlucas/mlucas-avx2 -fftlen 192 -iters 100 -radset 0 /usr/libexec/mlucas/mlucas-avx -fftlen 192 -iters 100 -radset 0 /usr/libexec/mlucas/mlucas-sse2 -fftlen 192 -iters 100 -radset 0 ... until this succeeds. Could you tell me what you get on epyc 3 and epyc 4 ? Maybe one of those is broken and I can just remove it. (I already disabled sse2 on i386 due to crashes) Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here.
