From: Andrew Morton <akpm@osdl.org>
To: Michael Sabala <lkml@saahbs.net>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.18 mmap hangs unrelated apps
Date: Fri, 15 Dec 2006 13:41:16 -0800 [thread overview]
Message-ID: <20061215134116.f93f471b.akpm@osdl.org> (raw)
In-Reply-To: <20061215213500.GA16106@prosiaczek>
On Fri, 15 Dec 2006 15:35:00 -0600
Michal Sabala <lkml@saahbs.net> wrote:
> On 2006/12/15 at 14:42:08 Andrew Morton <akpm@osdl.org> wrote
> > On Fri, 15 Dec 2006 11:50:30 -0600
> > Michal Sabala <lkml@saahbs.net> wrote:
> >
> > > On 2006/12/15 at 10:24:15 Trond Myklebust <trond.myklebust@fys.uio.no> wrote
> > > > On Thu, 2006-12-14 at 20:30 -0600, Michal Sabala wrote:
> > > > >
> > > > > `cat /proc/*PID*/wchan` for all hanging processes contains page_sync.
> > > >
> > > > Have you tried an 'echo t >/proc/sysrq-trigger' on a client with one of
> > > > these hanging processes? If so, what does the output look like?
> > >
> > > Hello Trond,
> > >
> > > Below is the sysrq trace output for XFree86 which entered the
> > > uninterruptible sleep state on the P4 machine with nfs /home. Please
> > > note that XFree86 does not have any files open in /home - as reported by
> > > `lsof`. Below, I also listed the output of vmstat.
> >
> > We'd need to see the trace of all D-state processes, please. Xfree86 might
> > just be a victim of a deadlock elsewhere. However there is a problem here..
>
> Hi Andrew,
>
> In most cases only a single process enters the D-state, this time it was
> XFree, but I've seen gimp, firefox, gconfd and bash. Once or twice I did
> see two or three processes ending up in uninterruptible sleep, but I
> suspect they entered this state at different test-mmap.c runs (I left
> test-mmap.c running in a bash loop and checked the system after a few
> hours).
OK, useful info, thanks.
> Would it be beneficial to keep running test-mmap.c on this machine until
> two or more processes end up in D-state? I can leave this machine
> running test-mmap.c over the weekend.
No, that's OK. The next step should be for a kernel wrangler to get in
there with your testcase. It could well be that lock_page-inside-lock_page
thing.
next prev parent reply other threads:[~2006-12-15 21:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 2:30 2.6.18 mmap hangs unrelated apps Michal Sabala
2006-12-15 16:24 ` Trond Myklebust
2006-12-15 17:50 ` Michal Sabala
2006-12-15 19:44 ` Trond Myklebust
2006-12-15 21:06 ` Michal Sabala
2006-12-15 21:12 ` Arjan van de Ven
2006-12-15 21:43 ` Michal Sabala
2006-12-15 21:44 ` Trond Myklebust
2006-12-15 22:05 ` Michal Sabala
2006-12-19 22:26 ` Andrew Morton
2006-12-19 23:19 ` Trond Myklebust
2006-12-20 0:03 ` Andrew Morton
2006-12-20 0:17 ` Trond Myklebust
2006-12-20 0:22 ` Andrew Morton
2006-12-20 1:21 ` Trond Myklebust
2007-01-08 14:48 ` [PATCH] NFS: Fix race in nfs_release_page() Peter Zijlstra
2006-12-20 14:51 ` 2.6.18 mmap hangs unrelated apps Michal Sabala
2006-12-15 20:42 ` Andrew Morton
2006-12-15 21:35 ` Michal Sabala
2006-12-15 21:41 ` Andrew Morton [this message]
2006-12-16 12:59 ` Christian Kuhn
2006-12-16 18:45 ` Christian Kuhn
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=20061215134116.f93f471b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@saahbs.net \
--cc=trond.myklebust@fys.uio.no \
/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