linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* invalid opcode: 0000 [#1] SMP [aesni_intel]
@ 2017-10-23 16:01 SviMik
  2017-11-02  4:33 ` Eric Biggers
  0 siblings, 1 reply; 2+ messages in thread
From: SviMik @ 2017-10-23 16:01 UTC (permalink / raw)
  To: linux-crypto

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).

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: invalid opcode: 0000 [#1] SMP [aesni_intel]
  2017-10-23 16:01 invalid opcode: 0000 [#1] SMP [aesni_intel] SviMik
@ 2017-11-02  4:33 ` Eric Biggers
  0 siblings, 0 replies; 2+ messages in thread
From: Eric Biggers @ 2017-11-02  4:33 UTC (permalink / raw)
  To: SviMik; +Cc: linux-crypto

On Mon, Oct 23, 2017 at 07:01:32PM +0300, SviMik wrote:
> 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).

Well, the program counter was at the 'vmovdqu' instruction, which is the first
AVX instruction in the function.  Is it possible you're running the kernel on a
broken hypervisor that claims AVX instructions are supported but really they
aren't?  Note that AVX is different from AES-NI; the code being executed has
both types of instructions.

(And as a side note, 4.8 is not being maintained as a long term support kernel,
so you really should switch to a different version.)

Eric

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-11-02  4:33 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-10-23 16:01 invalid opcode: 0000 [#1] SMP [aesni_intel] SviMik
2017-11-02  4:33 ` Eric Biggers

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).