From: Yan Li <elliot.li.tech@gmail.com>
To: Ritesh Raj Sarraf <rrs@researchut.com>
Cc: Yan Li <elliot.li.tech@gmail.com>, Milan Broz <mbroz@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Christophe Saout <christophe@saout.de>,
linux-kernel@vger.kernel.org, dm-devel@redhat.com,
Herbert Xu <herbert@gondor.apana.org.au>,
rjmaomao@gmail.com, Alasdair G Kergon <agk@redhat.com>,
dm-crypt@saout.de
Subject: Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
Date: Wed, 4 Jun 2008 07:13:39 +0800 [thread overview]
Message-ID: <20080603231339.GA5995@yantp.cn.ibm.com> (raw)
In-Reply-To: <2f83bcba0806031246m30f92892wc868d81a9c29d680@mail.gmail.com>
On Wed, Jun 04, 2008 at 01:16:30AM +0530, Ritesh Raj Sarraf wrote:
> Following is the bugzilla that was opened against this problem.
> http://bugzilla.kernel.org/show_bug.cgi?id=10378
>
> Since I wasn't able to reproduce it on a server machine again, it was later
> closed.
>
> If you think it is the same issue, please feel free to re-open it.
I think they are not the same. My problem lied in the slow crypto
computation under heavy I/O. I'm testing Milan Broz's patch, till now
it seems has solved my problem.
--
Li, Yan
prev parent reply other threads:[~2008-06-03 23:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 13:54 Ritesh Raj Sarraf
2008-02-29 7:20 ` Andrew Morton
2008-02-29 18:15 ` Herbert Xu
2008-02-29 18:46 ` [dm-devel] " Alasdair G Kergon
2008-02-29 18:59 ` Ritesh Raj Sarraf
2008-03-01 19:30 ` Milan Broz
2008-03-01 19:33 ` Milan Broz
2008-03-01 21:59 ` Gunter Ohrner
2008-03-02 7:58 ` Gunter Ohrner
2008-03-06 14:41 ` [dm-devel] " Ritesh Raj Sarraf
2008-06-02 3:07 ` Yan Li
2008-06-02 6:52 ` Milan Broz
2008-06-02 12:31 ` Yan Li
2008-06-02 12:51 ` Milan Broz
2008-06-05 22:44 ` Yan Li
2008-06-06 6:46 ` Milan Broz
[not found] ` <2f83bcba0806031246m30f92892wc868d81a9c29d680@mail.gmail.com>
2008-06-03 23:13 ` Yan Li [this message]
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=20080603231339.GA5995@yantp.cn.ibm.com \
--to=elliot.li.tech@gmail.com \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=christophe@saout.de \
--cc=dm-crypt@saout.de \
--cc=dm-devel@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mbroz@redhat.com \
--cc=rjmaomao@gmail.com \
--cc=rrs@researchut.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
all inboxes | Powered by JetHome®