Le Mon, Dec 27, 2021 at 07:25:26PM +0200, [email protected] a écrit :
> >Synopsis:    Segfaults all over the place (most likely in libcrypto) ONLY in 
> >MP
> >Category:    library kernel amd64
> >Environment:
>       System      : OpenBSD 7.0
>       Details     : OpenBSD 7.0 (GENERIC.MP) #224: Thu Sep 30 14:13:34 MDT 
> 2021
>                        
> [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> 
>       Architecture: OpenBSD.amd64
>       Machine     : amd64
> >Description:
> Fresh installed 7.0 machine inside VMware 5.5 VM throws Segmentation faults 
> when using MP kernel.
> For example, on first install it could not even generate sshd keys during 
> first start.
> This report is actually generated with SP because MP is almost unusable. I 
> edited the Details above, adding '.MP'.
> 
> 6.9 runs apparently well with MP kernel on same host.
> Working 6.9 upgraded to 7.0 has the same problems (this is how I bumped into 
> the issue).
> 
> I narrowed the problem to one repeatable case (for me): 
> Downloading a https URL with ftp segfaults when running the MP kernel and 
> works when using SP kernel.
> Last lines from a 'ltrace ftp https://www.google.com/index.html' are:
> 70628 ftp      USER  .plt object: 26 bytes
>        "/usr/lib/libcrypto.so.47.0"
> 70628 ftp      USER  .plt symbol: 24 bytes
>        "ENGINE_get_digest_engine"
> 70628 ftp      USER  .plt object: 21 bytes
>        "/usr/lib/libc.so.96.1"
> 70628 ftp      USER  .plt symbol: 6 bytes
>        "calloc"
> 70628 ftp      USER  .plt object: 26 bytes
>        "/usr/lib/libcrypto.so.47.0"
> 70628 ftp      USER  .plt symbol: 9 bytes
>        "SHA1_Init"
> 70628 ftp      USER  .plt object: 26 bytes
>        "/usr/lib/libcrypto.so.47.0"
> 70628 ftp      USER  .plt symbol: 11 bytes
>        "SHA1_Update"
> 
> >How-To-Repeat:
> On VMware esxi 5.5 create one VM with 2 CPU, 1GB RAM, 16GB disk.
> Install 7.0 from full CD, with default settings.
> _IF_ segfaults allow you to get a prompt:
> Run 'ftp https://www.google.com/index.html'
> >Fix:
> Only workaround: Run only the SP kernel, even if multiple cores are 
> configured.
> 

Or upgrade, it works fine with ESXi 7.0U2.

Reply via email to