[no subject]

apollo.backplane.com>
From: Francois Tigeot <ftigeot@wolfpond.org>
Subject: Re: Machine unresponsive with cache_lock: blocked on... message
Date: Tue, 23 Mar 2010 10:07:05 +0100
BestServHost: crater.dragonflybsd.org
List-Post: <mailto:bugs@crater.dragonflybsd.org>
List-Subscribe: <mailto:bugs-request@crater.dragonflybsd.org?body=subscribe>
List-Unsubscribe: <mailto:bugs-request@crater.dragonflybsd.org?body=unsubscribe>
List-Help: <mailto:bugs-request@crater.dragonflybsd.org?body=help>
List-Owner: <mailto:owner-bugs@crater.dragonflybsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
References: <1240.220.233.36.106.1269126548.squirrel@webmail.exetel.com.au> <201003202324.o2KNOrlX006114@apollo.backplane.com> <1366.220.233.36.106.1269129077.squirrel@webmail.exetel.com.au> <201003211824.o2LIOZUs015643@apollo.backplane.com> <20100321190708.GA63881@sekishi.zefyris.com> <201003211914.o2LJEBNo016061@apollo.backplane.com> <20100322083907.GA1801@sekishi.zefyris.com> <20100322110225.GA1925@sekishi.zefyris.com> <20100322181744.GA2162@sekishi.zefyris.com> <201003230542.o2N5gnh9031437@
apollo.backplane.com>
In-Reply-To: <201003230542.o2N5gnh9031437@apollo.backplane.com>
Sender: bugs-errors@crater.dragonflybsd.org
Errors-To: bugs-errors@crater.dragonflybsd.org
Lines: 24
NNTP-Posting-Host: 216.240.41.25
X-Trace: 1269335384 crater_reader.dragonflybsd.org 55378 216.240.41.25
Xref: crater_reader.dragonflybsd.org dragonfly.bugs:11563

On Mon, Mar 22, 2010 at 10:42:49PM -0700, Matthew Dillon wrote:
> :36 is slightly better but one of the running applications was still massively
> :paged out after a few hours.
> :
> :I vote for setting vfs.vm_cycle_point to 40.
> 
>     Ok, so 36 or 40.  I'm a bit worried about using 40, but I think its
>     worth setting it to 40 for the release and seeing how it fares.  People
>     can always drop it down if weird situations crop up.

I'm not completely happy either: even with 40 some applications get paged out,
which didn't occur with 2.4.

I also had a new deadlock this night (possibly during the daily periodic run).
Symptoms were the same as usual: no keyboard input, no network activity, many
pmap_interlock messages on the console...

The new crash dump is there: http://www.wolfpond.org/crash.dfly/

I have now set vfs.vm_cycle_point to 64 just in case. I may still be
positively surprised...

-- 
Francois Tigeot