From owner-freebsd-current Mon Feb 11 19:29:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from newman2.bestweb.net (newman2.bestweb.net [209.94.102.67]) by hub.freebsd.org (Postfix) with ESMTP id 5DD2737B61A for ; Mon, 11 Feb 2002 18:18:26 -0800 (PST) Received: from okeeffe.bestweb.net (okeefe.bestweb.net [209.94.100.110]) by newman2.bestweb.net (Postfix) with ESMTP id 1B98523054; Mon, 11 Feb 2002 21:17:43 -0500 (EST) Received: by okeeffe.bestweb.net (Postfix, from userid 0) id E834A9F00F; Mon, 11 Feb 2002 21:12:21 -0500 (EST) Date: Fri, 8 Feb 2002 20:06:24 -0800 (PST) From: David Wolfskill To: julian@elischer.org, Tor.Egge@cvsup.no.freebsd.org Subject: Re: Hang on flushing buffers w/today's -CURRENT, SMP system Cc: current@FreeBSD.ORG, gene@nttmcl.com Message-Id: <20020212021221.E834A9F00F@okeeffe.bestweb.net> 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 >Date: Fri, 8 Feb 2002 17:34:45 -0800 (PST) >From: Julian Elischer >Thats it for sure! >committing now.. >On Sat, 9 Feb 2002 Tor.Egge@cvsup.no.freebsd.org wrote: >> It looks like a call to setrunqueue() was incorrectly dropped in >> the latest version of kern_shutdown.c. Applying that one-line patch to the kernel sources from this morning, then rebuilding the kernel, yielded a kernel that no longer exhibited the earlier-reported symptoms did not occur. Thanks to all! Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill david@catwhisker.org I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message