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 21:32:10 +0200 [thread overview]
Message-ID: <40f323d00708241232t1ea6a05fkebb1dbf67fbe69e9@mail.gmail.com> (raw)
In-Reply-To: <46CF1DDE.7070302@xs4all.nl>
On 8/24/07, Udo van den Heuvel <udovdh@xs4all.nl> wrote:
> Benoit Boissinot wrote:
> > 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]
> >
> > 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.
>
> The box runs stable for days on end.
> Only when running gpg --gen-key I get this issue.
> Other gpg operations, run by a user, are without issue.
> There is 512MB of RAM and the hardware is `refreshed` regularly when an
> interesting VIA board comes out. Case stays closed otherwise. I am ESD
> certified. (or how to put that in the english language)
> memtest86 shows no problems. Kernel compiles etc run without issue.
> F7 upgraded installation. Updated regularly. gnupg rpm is Red Hat-stock.
> My own compiles of gnupg show the same error.
>
> So what is next?
>
Sorry, I'll let the gurus speak then ;)
regards,
Benoit
next prev parent reply other threads:[~2007-08-24 19:32 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
2007-08-24 18:05 ` Udo van den Heuvel
2007-08-24 19:32 ` Benoit Boissinot [this message]
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=40f323d00708241232t1ea6a05fkebb1dbf67fbe69e9@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®