From owner-freebsd-current@FreeBSD.ORG Thu May 13 21:43:12 2004 Return-Path: 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 B61CE16A4CE for ; Thu, 13 May 2004 21:43:12 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id B63E743D41 for ; Thu, 13 May 2004 21:43:11 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (junior-wifi.samsco.home [192.168.0.11]) by pooker.samsco.org (8.12.10/8.12.10) with ESMTP id i4E4mDu6077426; Thu, 13 May 2004 22:48:14 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40A44E54.1080003@freebsd.org> Date: Thu, 13 May 2004 22:43:00 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <40A3F1D5.5010209@bellsouth.net> <200405140325.i4E3P9PE003085@siralan.org> <20040514035208.GA36652@xor.obsecurity.org> In-Reply-To: <20040514035208.GA36652@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: Nilson cc: FreeBSD current mailing list cc: "Michael L. Squires" Subject: Re: General -CURRENT status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 May 2004 04:43:12 -0000 Kris Kennaway wrote: > On Thu, May 13, 2004 at 10:25:09PM -0500, Michael L. Squires wrote: > > >>I'm running 5.2-CURRENT cvsup'd on May 10, and have just finished a complete >>make world, kernel, portupgrade -a (175 ports), compiled jdk13/jkd14 along with >>openoffice-1.1 and mozilla. Only problem I had was a few problems with >>KDE 3.2.2 dependencies (I compiled that too) but no real problems, other >>than a burst of retries from the ahc driver followed by a message that >>"tagged openings are now 64" which leads me to suspect the problem is >>ahc configuration. > > > Or dodgy disk hardware. > > Kris Neither. It is perfectly normal for a disk to have 64 tagged openings and for the ahc driver to detect this and adjust itself. What this message really means is that you generated enough i/o load to max out the drives, nothing more. Scott