From owner-freebsd-questions@FreeBSD.ORG Mon Sep 18 07:18:18 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D34E16A40F for ; Mon, 18 Sep 2006 07:18:18 +0000 (UTC) (envelope-from nick@nickwithers.com) Received: from mail.nickwithers.com (mail.manrags.com [203.219.206.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98AC243D5C for ; Mon, 18 Sep 2006 07:18:12 +0000 (GMT) (envelope-from nick@nickwithers.com) Received: from localhost (shmick.shmon.net [10.0.0.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.nickwithers.com (Postfix) with ESMTP id AC8BB3AB1C for ; Mon, 18 Sep 2006 17:18:00 +1000 (EST) Date: Mon, 18 Sep 2006 17:17:59 +1000 From: Nick Withers To: freebsd-questions@freebsd.org Message-Id: <20060918171759.94cb86d9.nick@nickwithers.com> Organization: nickwithers.com X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.10.3; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-nickwithers-MailScanner: Found to be clean X-nickwithers-MailScanner-From: nick@nickwithers.com Subject: swap_pager: indefinite wait buffer: bufobj (...) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2006 07:18:18 -0000 G'day all, Just wondering whether anyone knows any details regarding the "swap_pager warnings" bug noted on the 6.1-RELEASE Release Engineering "to do" page (http://www.freebsd.org/releases/6.1R/todo.html). Specifically, a PR number would be excellent (I'm assuming one exists). I believe that this issue has been biting me for a while now (or at least it only began appearing after I enabled a swap file on a lowly machine which had to have bad RAM removed that I'm too cheap / poor to replace) and often results in machine lockups. I'd love to see it addressed (assuming that this is indeed what's biting me, which I'm fairly sure of*) before 6.2-RELEASE (probably a little unlikely, I guess) and would be happy to test patches / etc.. Thanks all! * I _could_ disable the swap file and leave the thing belting away for a while to see if the problem doesn't reoccur, but it'll mean a few processes getting killed here and there due to lack of available memory... -- Nick Withers email: nick@nickwithers.com Web: http://www.nickwithers.com Mobile: +61 414 397 446