All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lingbo Tang (SINA)" <tanglb@sina.com>
To: Evgeniy Polyakov <zbr@ioremap.net>
Cc: linux-crypto <linux-crypto@vger.kernel.org>
Subject: Re: 回复:Re: vgdisplay problem with hifn795x
Date: Sat, 06 Dec 2008 22:09:55 +0800	[thread overview]
Message-ID: <493A87B3.3050209@sina.com> (raw)
In-Reply-To: <20081130101208.GA20720@ioremap.net>


Evgeniy Polyakov wrote:
> On Sun, Nov 30, 2008 at 04:26:00PM +0800, tanglb@sina.com (tanglb@sina.com) wrote:
>> I downloaded the source file from your link and compiled successfully.
>> But it still hang when I tried to run "mkfs.xfs".
> 
> Please enable debug mode with attached patch and send dmesg output.
> Thank you.

The weird thing is that there is no problem if I turned on the debug
option. I can see kcryptd taking 99% CPU time and there are many
debug output from the serial port, but the encrypted LVM worked eventually.

In some cases the non-debug version can work with "mkfs.xfs", but it
could not in most case.
I tried to disable most services in the system, but it seems have no
related to the system load.

> 
> diff --git a/drivers/crypto/hifn_795x.c b/drivers/crypto/hifn_795x.c
> index 6e9b39c..ca621f6 100644
> --- a/drivers/crypto/hifn_795x.c
> +++ b/drivers/crypto/hifn_795x.c
> @@ -38,7 +38,7 @@
>  
>  #include <asm/kmap_types.h>
>  
> -//#define HIFN_DEBUG
> +#define HIFN_DEBUG
>  
>  #ifdef HIFN_DEBUG
>  #define dprintk(f, a...) 	printk(f, ##a)
> 



  reply	other threads:[~2008-12-06 14:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-30  8:26 回复:Re: vgdisplay problem with hifn795x tanglb
2008-11-30 10:12 ` Evgeniy Polyakov
2008-12-06 14:09   ` Lingbo Tang (SINA) [this message]
2008-12-06 15:19     ` Evgeniy Polyakov
2008-12-07 10:13       ` Lingbo Tang (SINA)

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=493A87B3.3050209@sina.com \
    --to=tanglb@sina.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=zbr@ioremap.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.