From: SviMik <svimik@gmail.com>
To: linux-crypto@vger.kernel.org
Subject: invalid opcode: 0000 [#1] SMP [aesni_intel]
Date: Mon, 23 Oct 2017 19:01:32 +0300 [thread overview]
Message-ID: <CA++DawbkD6nioFR70ph1J26erZAwt74egm-pPDXJEHNt-QDAGw@mail.gmail.com> (raw)
Hi!
Got the following kernel panic:
invalid opcode: 0000 [#1] SMP
CPU: 0 PID: 1449 Comm: openvpn Not tainted 4.8.13-1.el6.elrepo.x86_64 #1
----cut----
Call Trace:
<IRQ>
[<ffffffff810be15e>] ? enqueue_entity+0x45e/0x6f0
[<ffffffffa0104f25>] ? aesni_gcm_enc_avx+0x95/0xd0 [aesni_intel]
[<ffffffffa0105417>] helper_rfc4106_encrypt+0x167/0x2f0 [aesni_intel]
[<ffffffffa0104bfb>] rfc4106_encrypt+0x5b/0x90 [aesni_intel]
----cut----
The detailed bug report with full oops dump can be found here:
https://bugzilla.kernel.org/show_bug.cgi?id=197363
Could not trigger this bug intentionally, but it happened three times
already (all three dumps are available).
next reply other threads:[~2017-10-23 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 16:01 SviMik [this message]
2017-11-02 4:33 ` invalid opcode: 0000 [#1] SMP [aesni_intel] Eric Biggers
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=CA++DawbkD6nioFR70ph1J26erZAwt74egm-pPDXJEHNt-QDAGw@mail.gmail.com \
--to=svimik@gmail.com \
--cc=linux-crypto@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;
as well as URLs for NNTP newsgroup(s).