No subject

Unknown Unknown
Tue Mar 23 02:08:23 PDT 2010>
From: Francois Tigeot <ftigeot at>
Subject: Re: Machine unresponsive with cache_lock: blocked on... message
Date: Tue, 23 Mar 2010 10:07:05 +0100
List-Post: <mailto:bugs at>
List-Subscribe: <mailto:bugs-request at>
List-Unsubscribe: <mailto:bugs-request at>
List-Help: <mailto:bugs-request at>
List-Owner: <mailto:owner-bugs at>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
References: <1240. at> <201003202324.o2KNOrlX006114 at> <1366. at> <201003211824.o2LIOZUs015643 at> <20100321190708.GA63881 at> <201003211914.o2LJEBNo016061 at> <20100322083907.GA1801 at> <20100322110225.GA1925 at> <20100322181744.GA2162 at> <201003230542.o2N5gnh9031437@>
In-Reply-To: <201003230542.o2N5gnh9031437 at>
Sender: bugs-errors at
Errors-To: bugs-errors at
Lines: 24
X-Trace: 1269335384 55378
Xref: 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:

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

Francois Tigeot

More information about the Bugs mailing list