From: Mingming Cao <cmm@us.ibm.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, pbadari@us.ibm.com
Subject: Re: 2.5.70-mm6
Date: 11 Jun 2003 15:15:06 -0700 [thread overview]
Message-ID: <1055369707.7509.8.camel@w-ming2.beaverton.ibm.com> (raw)
In-Reply-To: <20030610201242.7fde819b.akpm@digeo.com>
On Tue, 2003-06-10 at 20:12, Andrew Morton wrote:
> Mingming Cao <cmm@us.ibm.com> wrote:
> >
> > I run 50 fsx tests on ext3 filesystem on 2.5.70-mm6 kernel. Serveral fsx
> > tests hang with the status D, after the tests run for a while. No oops,
> > no error messages. I found same problem on mm5, but 2.5.70 is fine.
> >
> > Here is the stack info:
>
> Thanks for this.
>
> Everything is waiting on I/O. It looks like either the device driver
> failed or the IO scheduler got its state all screwed up.
>
> Which device driver are you using there?
I am usering Qlogic qla2xxx V8 driver
>
> If you could, please retest with "elevator=deadline"?
>
Sure.
And I saw sysrq on 2.5.70-mm6 failed on my test machine, 2.5.70-mm5
works. I could trigger sysrq by send"t", but the stack info for all
threads are the same ---the stack info of the sysrq itself.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-06-11 22:15 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-07 22:14 2.5.70-mm6 Andrew Morton
2003-06-08 0:37 ` 2.5.70-mm6 Alexander Hoogerhuis
2003-06-08 0:56 ` 2.5.70-mm6 Andrew Morton
2003-06-08 1:13 ` 2.5.70-mm6 Alexander Hoogerhuis
2003-06-08 12:25 ` 2.5.70-mm6 Christoph Hellwig
2003-06-08 12:09 ` 2.5.70-mm6 Felipe Alfaro Solana
2003-06-08 22:52 ` 2.5.70-mm6 Pasi Savolainen
2003-06-09 17:45 ` 2.5.70-mm6 Maciej Soltysiak
2003-06-09 17:39 ` 2.5.70-mm6 Martin J. Bligh
2003-06-09 18:19 ` 2.5.70-mm6 Maciej Soltysiak
2003-06-09 18:51 ` 2.5.70-mm6 Martin J. Bligh
2003-06-09 19:42 ` 2.5.70-mm6 Maciej Soltysiak
2003-06-09 20:04 ` 2.5.70-mm6 William Lee Irwin III
2003-06-10 8:54 ` 2.5.70-mm6 Maciej Soltysiak
2003-06-10 9:20 ` 2.5.70-mm6 William Lee Irwin III
2003-06-10 11:31 ` 2.5.70-mm6 Mike Galbraith
2003-06-10 11:41 ` 2.5.70-mm6 William Lee Irwin III
2003-06-10 11:51 ` Sharing Boottime allocated memory with user-space processes ZCane, Ed (Test Purposes)
2003-06-10 18:53 ` 2.5.70-mm6 Mike Galbraith
2003-06-10 19:11 ` 2.5.70-mm6 William Lee Irwin III
2003-06-10 11:52 ` 2.5.70-mm6 Maciej Soltysiak
2003-06-09 20:08 ` 2.5.70-mm6 Felipe Alfaro Solana
2003-06-09 20:14 ` 2.5.70-mm6 Martin J. Bligh
2003-06-09 21:09 ` 2.5.70-mm6 Felipe Alfaro Solana
2003-06-10 9:56 ` 2.5.70-mm6 Felipe Alfaro Solana
2003-06-09 18:39 ` 2.5.70-mm6 Felipe Alfaro Solana
2003-06-09 18:06 ` 2.5.70-mm6 Alistair J Strachan
2003-06-09 18:36 ` 2.5.70-mm6 Felipe Alfaro Solana
2003-06-09 19:07 ` 2.5.70-mm6 Pasi Savolainen
2003-06-11 2:15 ` 2.5.70-mm6 Mingming Cao
2003-06-11 3:12 ` 2.5.70-mm6 Andrew Morton
2003-06-11 22:15 ` Mingming Cao [this message]
2003-06-12 16:37 ` 2.5.70-mm6 Mingming Cao
2003-06-12 17:50 ` 2.5.70-mm6 Andrew Morton
2003-06-12 18:43 ` 2.5.70-mm6 Mingming Cao
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=1055369707.7509.8.camel@w-ming2.beaverton.ibm.com \
--to=cmm@us.ibm.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pbadari@us.ibm.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