port-sparc/55573: sparc testbed logs many "coprocessor instruction" messages

[gson%gson.org@localhost (Andreas Gustafsson)]

>Number:         55573
>Category:       port-sparc
>Synopsis:       sparc testbed logs many "coprocessor instruction" messages
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    port-sparc-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Aug 14 08:15:00 +0000 2020
>Originator:     Andreas Gustafsson
>Release:        NetBSD-current
>Organization:
  
>Environment:
System: NetBSD
Architecture: sparc
Machine: sparc
>Description:

The qemu-based TNF sparc testbed has started logging large numbers of
kernel messages saying "coprocessor instruction", like the following:

  Starting syslogd.
  [  15.0167285] coprocessor instruction
  [  15.0167285] coprocessor instruction
  [  15.0167285] coprocessor instruction
  [  15.0167285] coprocessor instruction
  Mounting all file systems...

This is from:

  http://releng.netbsd.org/b5reports/sparc/2020/2020.06.22.03.16.29/test.log

There seem to be no ill effects other than cluttering the console
output and causing confusion.

The problem started during the period of build breakage between source
dates 2020.06.20.02.27.55 and 2020.06.22.03.16.29.  The only sparc
specific commits during the period in case were:

  2020.06.21.22.16.08 christos src/crypto/external/bsd/openssl/lib/libcrypto/arch/sparc/bn.inc 1.2
  2020.06.21.22.16.08 christos src/crypto/external/bsd/openssl/lib/libcrypto/arch/sparc/crypto.inc 1.13
  2020.06.21.22.16.08 christos src/crypto/external/bsd/openssl/lib/libcrypto/arch/sparc/modes.inc 1.4

Is openssl perhaps trying to use some kind of crypto coprocessor that
is not supported by qemu, and successfully falling back to another
method?  If that's the case, perhaps the message should simply be
disabled.

>How-To-Repeat:

>Fix: