From: Andrew Morton <akpm@osdl.org>
To: Claudio Martins <ctpm@rnl.ist.utl.pt>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Processes stuck on D state on Dual Opteron
Date: Mon, 4 Apr 2005 19:12:46 -0700 [thread overview]
Message-ID: <20050404191246.24b11158.akpm@osdl.org> (raw)
In-Reply-To: <200504050316.20644.ctpm@rnl.ist.utl.pt>
Claudio Martins <ctpm@rnl.ist.utl.pt> wrote:
>
> While stress testing 2.6.12-rc2 on an HP DL145 I get processes stuck in D
> state after some time.
> This machine is a dual Opteron 248 with 2GB (ECC) on one node (the other
> node has no RAM modules plugged in, since this board works only with pairs).
>
> I was using stress (http://weather.ou.edu/~apw/projects/stress/) with the
> following command line:
>
> stress -v -c 20 -i 12 -m 10 -d 20
>
> This causes a constant load avg. of around 70, makes the machine go into
> swap a little, and writes up to about 20GB of random data to disk while
> eating up all CPU. After about half and hour random processes like top, df,
> etc get stuck in D state. Half of the 60 or so stress processes are also in D
> state. The machine keeps being responsive for maybe some 15 minutes but then
> the shells just hang and sshd stops responding to connections, though the
> machine replies to pings (I don't have console acess till tomorrow).
>
> The system is using ext3 with md software Raid1.
>
> I'm interested in knowing if anyone out there with dual Opterons can
> reproduce this or not. I also have access to an HP DL360 Dual Xeon, so I will
> try to find out if this is AMD64 specific as soon as possible. Please let me
> know if you want me to run some other tests or give some more info to help
> solve this one.
Can you capture the output from alt-sysrq-T?
next prev parent reply other threads:[~2005-04-05 3:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 2:16 Claudio Martins
2005-04-05 2:12 ` Andrew Morton [this message]
2005-04-10 2:28 ` Claudio Martins
2005-04-10 2:47 ` Andrew Morton
2005-04-10 3:19 ` Claudio Martins
2005-04-11 0:38 ` Claudio Martins
2005-04-11 6:36 ` Nick Piggin
2005-04-11 9:55 ` Nick Piggin
2005-04-11 12:45 ` Nick Piggin
2005-04-11 14:05 ` Claudio Martins
2005-04-11 22:59 ` Nick Piggin
2005-04-12 0:22 ` Claudio Martins
2005-04-12 0:46 ` Andrew Morton
2005-04-13 0:31 ` Claudio Martins
2005-04-13 2:24 ` Nick Piggin
2005-04-12 1:19 ` Nick Piggin
2005-04-12 7:07 ` Jens Axboe
2005-04-12 8:03 ` Chen, Kenneth W
2005-04-12 11:09 ` Nick Piggin
2005-04-12 11:26 ` Nick Piggin
2005-04-12 12:04 ` Nick Piggin
2005-04-12 17:07 ` Thomas Davis
2005-04-12 18:33 ` Chen, Kenneth W
2005-04-13 1:45 ` Nick Piggin
2005-04-11 23:46 ` Neil Brown
2005-04-12 0:30 ` Claudio Martins
2005-04-10 2:53 ` Nick Piggin
2005-04-10 3:22 ` Claudio Martins
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=20050404191246.24b11158.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ctpm@rnl.ist.utl.pt \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome