Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Tadeusz Struk <tadeusz.struk@intel.com>
To: Anatoly Pugachev <matorola@gmail.com>,
	David Miller <davem@davemloft.net>
Cc: linux-crypto@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [crypto / sparc64] cryptomgr_test OOPS
Date: Wed, 4 May 2016 13:02:45 -0700	[thread overview]
Message-ID: <06c0b4f8-becf-25f3-109a-e1500f11626a@intel.com> (raw)
In-Reply-To: <CADxRZqzynaTAD+vcJwW2ueGnQyy=tQAJq2TvTT-_pZG26=_ZLQ@mail.gmail.com>

Hi Anatoly,
On 05/04/2016 12:10 PM, Anatoly Pugachev wrote:
> we're using 4.5.2 debian kernel here without this problem. I'm not
> sure I would be able to bisect, never did it before, but I could
> try...

On 4.5.2 could you try "modprobe rsa"

-- 
TS

  reply	other threads:[~2016-05-04 20:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-03 13:54 [crypto / sparc64] cryptomgr_test OOPS Anatoly Pugachev
2016-05-03 16:33 ` David Miller
2016-05-04  4:07   ` Herbert Xu
2016-05-04 14:49     ` Anatoly Pugachev
2016-05-05  8:42       ` Herbert Xu
2016-05-05  9:40         ` Anatoly Pugachev
2016-05-05  9:50           ` Herbert Xu
2016-05-05 16:17             ` Tadeusz Struk
2016-05-05 15:00           ` Tadeusz Struk
2016-05-05 15:31             ` Anatoly Pugachev
2016-05-05 15:52               ` John Paul Adrian Glaubitz
2016-05-05 16:09               ` Tadeusz Struk
2016-05-05 15:12         ` Anatoly Pugachev
2016-05-05 15:17           ` John Paul Adrian Glaubitz
2016-05-06 19:52         ` David Miller
2016-05-04 19:10   ` Anatoly Pugachev
2016-05-04 20:02     ` Tadeusz Struk [this message]
2016-05-04 20:51     ` David Miller

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=06c0b4f8-becf-25f3-109a-e1500f11626a@intel.com \
    --to=tadeusz.struk@intel.com \
    --cc=davem@davemloft.net \
    --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