mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Benoit Boissinot" <bboissin@gmail.com>
To: "Udo van den Heuvel" <udovdh@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: possible BUG while doing gpg --gen-key
Date: Fri, 24 Aug 2007 19:57:20 +0200	[thread overview]
Message-ID: <40f323d00708241057k6549f22fl6abf802f14c03e44@mail.gmail.com> (raw)
In-Reply-To: <46CF079C.7010304@xs4all.nl>

On 8/24/07, Udo van den Heuvel <udovdh@xs4all.nl> wrote:
> While doing gpg --gen-key I can reproduce quite well some sort of
> crash/bug/etc:
> # gpg --gen-key

[snip]

> We need to generate a lot of random bytes. It is a good idea to perform
> some other action (type on the keyboard, move the mouse, utilize the
> disks) during the prime generation; this gives the random number
> generator a better chance to gain enough entropy.
>
[snip]
> Segmentation fault
> (...)
> Call Trace:
>  [<c0103b75>] show_trace_log_lvl+0x1a/0x2f
>  [<c0103c27>] show_stack_log_lvl+0x9d/0xa5
>  [<c0103dfc>] show_registers+0x1cd/0x2e3
>  [<c0104010>] die+0xfe/0x200
>  [<c010fb77>] do_page_fault+0x43c/0x511
>  [<c030220a>] error_code+0x6a/0x70

iirg gpg-keygen uses a lot of cpu time during that phase, you probably
should verify your ram and cpu. This kind of problem is often due to
faulty hardware.

regards,

Benoit

  reply	other threads:[~2007-08-24 17:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24 16:30 Udo van den Heuvel
2007-08-24 17:57 ` Benoit Boissinot [this message]
2007-08-24 18:05   ` Udo van den Heuvel
2007-08-24 19:32     ` Benoit Boissinot
2007-08-25  1:14 ` Adrian Bunk
2007-08-25  5:11   ` Udo van den Heuvel
2007-08-25  6:21   ` Udo van den Heuvel
2007-08-25 12:57     ` Udo van den Heuvel
2007-09-02 11:55       ` Andrew Morton
2007-09-05 16:40         ` Andrew Morton
2007-09-05 16:49           ` Udo van den Heuvel
2007-09-05 16:58             ` Andrew Morton

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=40f323d00708241057k6549f22fl6abf802f14c03e44@mail.gmail.com \
    --to=bboissin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=udovdh@xs4all.nl \
    /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

all inboxes | Powered by JetHome®