From owner-freebsd-current Mon Feb 24 8:33:34 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B70F37B405 for ; Mon, 24 Feb 2003 08:33:33 -0800 (PST) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60CAD43FA3 for ; Mon, 24 Feb 2003 08:33:32 -0800 (PST) (envelope-from wa1ter@myrealbox.com) Received: from myrealbox.com wa1ter@smtp-send.myrealbox.com [66.126.108.94] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 3.31 $ on Novell NetWare via secured & encrypted transport (TLS); Mon, 24 Feb 2003 09:33:35 -0700 Message-ID: <3E5A495B.2080504@myrealbox.com> Date: Mon, 24 Feb 2003 08:33:31 -0800 From: walt Organization: none User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030213 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Giving up on three buffers... References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David Wolfskill wrote: >>Date: Mon, 24 Feb 2003 07:39:08 -0800 >>From: walt > > >>After this morning's cvsup I now get a 'syncing disks...giving up >>on three buffers' error message when shutting down the system and >>the filesystem doesn't get properly dismounted. > > >>For the last four days I could never shut the system down cleanly >>because of the nVidia driver problem causing a kernel panic >>when X got shut down, so I'm not sure if this problem really >>just started this morning or somethime in the past four days. > > >>Anyone else seeing this just today? > > > My build machine runs headless, so there may well be a salient > difference there, but today's -CURRENT build & reboot went just fine... I discovered that I was still running SCHED_ULE from yesterday and switching back to SCHED_4BSD eliminated the problem. I've actually been wondering why the system was so sluggish and now I know why ;-) Compiling a kernel was enough to drag the machine practically to uselessness, but now it's back to it's old self. The new scheduler still needs a bit of tweaking, methinks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message