From: Ingo Molnar <mingo@elte.hu>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Simon Arlott <simon@fire.lp0.eu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: BUG: unable to handle kernel NULL pointer dereference at 000000000000000e (reset_prng_context)
Date: Tue, 15 Jul 2008 13:51:17 +0200 [thread overview]
Message-ID: <20080715115117.GA3300@elte.hu> (raw)
In-Reply-To: <20080715113304.GA30565@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> i have just triggered this crash too. Please, when you know about
> bootup crashes in your code send a patch to the lkml thread so that
> people can apply it and have a working system.
here's the band-aid patch i'm using.
Ingo
-------------->
commit 3fdcd29e5c272c66424ac7616fcd4a9a725bc206
Author: Ingo Molnar <mingo@elte.hu>
Date: Tue Jul 15 13:34:15 2008 +0200
crypto: exclude broken CRYPTO_PRNG code
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
crypto/Kconfig | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/crypto/Kconfig b/crypto/Kconfig
index ea50357..2cf66ca 100644
--- a/crypto/Kconfig
+++ b/crypto/Kconfig
@@ -670,6 +670,8 @@ comment "Random Number Generation"
config CRYPTO_PRNG
tristate "Pseudo Random Number Generation for Cryptographic modules"
+ # causes bootup crashes with config-Tue_Jul_15_10_35_22_CEST_2008.bad
+ depends on 0
help
This option enables the generic pseudo random number generator
for cryptographic modules. Uses the Algorithm specified in
next prev parent reply other threads:[~2008-07-15 11:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 23:25 BUG: unable to handle kernel NULL pointer dereference at 000000000000000e (reset_prng_context) Simon Arlott
2008-07-15 2:04 ` Neil Horman
2008-07-15 11:33 ` Ingo Molnar
2008-07-15 11:49 ` Ingo Molnar
2008-07-15 11:51 ` Ingo Molnar [this message]
2008-07-15 14:21 ` Neil Horman
2008-07-15 20:44 ` David Miller
2008-07-15 21:49 ` Alexey Dobriyan
2008-07-15 22:11 ` Andrew Morton
2008-07-15 22:36 ` Alexey Dobriyan
2008-07-16 0:04 ` Neil Horman
2008-07-16 2:08 ` Herbert Xu
2008-07-16 4:07 ` Herbert Xu
2008-07-16 4:25 ` Andrew Morton
2008-07-16 4:33 ` Herbert Xu
2008-07-16 4:51 ` Andrew Morton
2008-07-16 5:34 ` Herbert Xu
2008-07-16 6:17 ` Andrew Morton
2008-07-16 6:35 ` Herbert Xu
2008-07-16 16:57 ` Joe Perches
2008-07-18 22:16 ` Ingo Molnar
2008-07-15 2:16 ` Neil Horman
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=20080715115117.GA3300@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=simon@fire.lp0.eu \
/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