From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Claudio Martins <ctpm@rnl.ist.utl.pt>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Processes stuck on D state on Dual Opteron
Date: Sun, 10 Apr 2005 12:53:00 +1000 [thread overview]
Message-ID: <4258950C.1040903@yahoo.com.au> (raw)
In-Reply-To: <200504100328.53762.ctpm@rnl.ist.utl.pt>
[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]
Claudio Martins wrote:
> On Tuesday 05 April 2005 03:12, Andrew Morton wrote:
>
>>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
>>>
[snip]
> ------------------------------------
>
>
> Unfortunately the system Oopsed in the middle of dumping the tasks, but from
> what I can see I'm tempted to think that this might be related to the MD
> code. md2_raid1 is blocked on D state and, although not shown on the dump, I
> know from ps command that md0_raid1 (the swap partition) was also on D state
> (along with the stress processes which are responsible for hogging memory,
> and top and df). There were about 200MB swapped out, but the swap partition
> size is 1GB.
>
Looks like you may possibly have a memory allocation deadlock
(although I can't explain the NMI oops).
I would be interested to see if the following patch is of any
help to you.
Thanks,
Nick
--
SUSE Labs, Novell Inc.
[-- Attachment #2: mempool-can-fail.patch --]
[-- Type: text/plain, Size: 605 bytes --]
Index: linux-2.6/mm/mempool.c
===================================================================
--- linux-2.6.orig/mm/mempool.c 2005-03-30 10:39:51.000000000 +1000
+++ linux-2.6/mm/mempool.c 2005-03-30 10:41:29.000000000 +1000
@@ -198,7 +198,10 @@ void * mempool_alloc(mempool_t *pool, in
void *element;
unsigned long flags;
DEFINE_WAIT(wait);
- int gfp_nowait = gfp_mask & ~(__GFP_WAIT | __GFP_IO);
+ int gfp_nowait;
+
+ gfp_mask |= __GFP_NORETRY; /* don't loop in __alloc_pages */
+ gfp_nowait = gfp_mask & ~(__GFP_WAIT | __GFP_IO);
might_sleep_if(gfp_mask & __GFP_WAIT);
repeat_alloc:
next prev parent reply other threads:[~2005-04-10 2:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 2:16 Processes stuck on D state on Dual Opteron Claudio Martins
2005-04-05 2:12 ` Andrew Morton
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 [this message]
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=4258950C.1040903@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=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