From: David Miller <davem@davemloft.net>
To: matorola@gmail.com
Cc: sparclinux@vger.kernel.org, debian-sparc@lists.debian.org,
linux-crypto@vger.kernel.org
Subject: Re: [sparc] niagara2 cpu, opcodes not available message?
Date: Wed, 08 Jun 2016 11:33:48 -0700 (PDT) [thread overview]
Message-ID: <20160608.113348.1609018295943976971.davem@davemloft.net> (raw)
In-Reply-To: <CADxRZqwr9=9ZsrFR_8iC+f1Z=hSPi7Saj3uxB2=YmH42sVf6pQ@mail.gmail.com>
From: Anatoly Pugachev <matorola@gmail.com>
Date: Wed, 8 Jun 2016 20:30:40 +0300
> Can someone please tell, why do we get a bunch of the following
> messages on niagara2 cpu hardware (SPARC Enterprise T5120, T5220,
> T5140, and T5240 servers)
>
> Asking, because I see the following lines on kernel boot (removing
> first field boot time stamp in cut):
>
> mator@nvg5120:~/linux-sparc-boot-logs/t5120$ grep opcode
> dmesg-4.7.0-rc2+.log | cut -f2- -d' ' | sort | uniq -c
> 4 aes_sparc64: sparc64 aes opcodes not available.
> 7 camellia_sparc64: sparc64 camellia opcodes not available.
> 37 crc32c_sparc64: sparc64 crc32c opcode not available.
> 5 des_sparc64: sparc64 des opcodes not available.
> 4 md5_sparc64: sparc64 md5 opcode not available.
> 1 sha1_sparc64: sparc64 sha1 opcode not available.
> 2 sha256_sparc64: sparc64 sha256 opcode not available.
> 3 sha512_sparc64: sparc64 sha512 opcode not available.
Because the drivers unconditionally try to load, check the CPU capabilites
and emit the log message if the cpu caps aren't present.
I don't see what the problem is, everying is working as designed.
prev parent reply other threads:[~2016-06-08 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 17:30 [sparc] niagara2 cpu, opcodes not available message? Anatoly Pugachev
2016-06-08 17:57 ` Anatoly Pugachev
2016-06-08 18:27 ` Anatoly Pugachev
2016-06-08 18:33 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160608.113348.1609018295943976971.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=debian-sparc@lists.debian.org \
--cc=linux-crypto@vger.kernel.org \
--cc=matorola@gmail.com \
--cc=sparclinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox