From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel Panic in FIPS mode
Date: Tue, 23 Feb 2016 12:02:02 -0800 [thread overview]
Message-ID: <20160223200202.GA26480@kroah.com> (raw)
In-Reply-To: <CAOXsZUf7t2vSq1DOzxd4YhNq=-YMOT6BUqmOtUJOq_cu_hM4bQ@mail.gmail.com>
On Tue, Feb 23, 2016 at 01:41:50PM -0600, Tapas Sarangi wrote:
> I am recompiling 3.18.27 on a platform derived from el6. FIPS mode is
> enabled by checking the following configs:
>
> CONFIG_CRYPTO_FIPS=y
> CONFIG_CRYPTO_TEST=y
<snip>
If you are using a RHEL system, you need to contact Red Hat for support
as that is what you are paying for. Their kernel is a very "odd" one.
Also note that 3.18 is very old and obsolete as well, please use a
"modern" kernel release, the community can't support old kernels like
that.
best of luck,
greg k-h
next prev parent reply other threads:[~2016-02-23 20:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 19:41 Kernel Panic in FIPS mode Tapas Sarangi
2016-02-23 20:02 ` Greg KH [this message]
2016-02-23 20:41 ` Tapas Sarangi
2016-02-23 21:14 ` Greg KH
2016-02-23 23:01 ` Tapas Sarangi
2016-02-23 20:02 ` Leo Silva (a.k.a kirotawa)
2016-02-23 23:02 ` Tapas Sarangi
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=20160223200202.GA26480@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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).