public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Udo van den Heuvel <udovdh@xs4all.nl>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
	bunk@kernel.org, mpm@selenic.com, mb@bu3sch.de
Subject: Re: possible BUG while doing gpg --gen-key
Date: Wed, 05 Sep 2007 18:49:39 +0200	[thread overview]
Message-ID: <46DEDE23.1090607@xs4all.nl> (raw)
In-Reply-To: <20070905094023.3542dacc.akpm@linux-foundation.org>

Andrew Morton wrote:
>> On Sun, 2 Sep 2007 04:55:20 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>>> On Sat, 25 Aug 2007 14:57:17 +0200 Udo van den Heuvel <udovdh@xs4all.nl> wrote:
>>> Udo van den Heuvel wrote:
>>>> Now it works:
>>> Stranger even:
>>>
>>> With audio-entropyd, rngd active and the netdev-random patch working I
>>> cannot reproduce the crash. Even after a fresh boot.
>> It would really help if your oops stack trace wasn't truncated.  Can you
>> see if you can generate a complete one using a recent kernel?  Enabling
>> CONFIG_FRAME_POINTER and disabling CONFIG_4K_STACKS might help in this.
>>
> 
> So... what's happening here?  Did the trail go cold?

Well, I just rebooted the box for an other problem (see
http://bugzilla.kernel.org/show_bug.cgi?id=8377 for details) and did a
fresh try:

 strace gpg --gen-key 2> ~/gpg.txt

Oddly enough the action completes successfully. This is with both
audio-entropyd and rngd running and netdev-random patch in the kernel.
The very same thing triggered the bug without problem before trying with
the mentioned deamons stopped.
Now even doing rm -rf .gnupg/ does not help in reproducing.

So yes, all is OK, and no, I don't know why.


  reply	other threads:[~2007-09-05 16:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24 16:30 possible BUG while doing gpg --gen-key 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
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 [this message]
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=46DEDE23.1090607@xs4all.nl \
    --to=udovdh@xs4all.nl \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=mpm@selenic.com \
    /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