From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 25 21:24:48 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9D0716A4CE; Tue, 25 Jan 2005 21:24:48 +0000 (GMT) Received: from manor.msen.com (manor.msen.com [148.59.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63F5943D39; Tue, 25 Jan 2005 21:24:48 +0000 (GMT) (envelope-from wayne@manor.msen.com) Received: from manor.msen.com (localhost [127.0.0.1]) by manor.msen.com (8.12.9p2/8.12.9) with ESMTP id j0PLOjTA054629; Tue, 25 Jan 2005 16:24:47 -0500 (EST) (envelope-from wayne@manor.msen.com) Received: (from wayne@localhost) by manor.msen.com (8.12.9p2/8.12.9/Submit) id j0PLOjAI054628; Tue, 25 Jan 2005 16:24:45 -0500 (EST) (envelope-from wayne) Date: Tue, 25 Jan 2005 16:24:45 -0500 From: "Michael R. Wayne" To: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Message-ID: <20050125212445.GY1168@manor.msen.com> Mail-Followup-To: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org References: <20050119214229.GE1168@manor.msen.com> <20050119191813.H78340@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050119191813.H78340@carver.gumbysoft.com> User-Agent: Mutt/1.4.2.1i Subject: Re: Failure on today's CVS (stable, AMD) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 21:24:49 -0000 On Wed, Jan 19, 2005 at 07:19:49PM -0800, Doug White wrote: > On Wed, 19 Jan 2005, Michael R. Wayne wrote: > > > CVS today. Dual Opteron running > > 5.3-STABLE #3: Tue Nov 30 01:44:05 EST 2004 > > > > Following the instructions in UPDATING, I get the following, > > indicating a bad kernel. 2 questions: > > > > 1) Is this a known, corrected issue as of today? I ran another > > CVSUP and did not see any changed to src. > > Looks like your SCSi controller stopped probing. You'll need to look at > the dmesg more closely to identify why. Followup for the archives. The twa driver has known issues right now, a fix is being worked on. I received a patch and applied it, which did indeed solve the problem. My understanding is that this patch should be committed later this week so if you are reading this thread much after Feb 1, 2005 it likely does not apply. /\/\ \/\/