From owner-freebsd-current@FreeBSD.ORG Fri Aug 19 13:54:49 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 4C7C516A420 for ; Fri, 19 Aug 2005 13:54:49 +0000 (GMT) (envelope-from MH@kernel32.de) Received: from crivens.unixoid.de (crivens.unixoid.de [81.169.171.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id D471243D46 for ; Fri, 19 Aug 2005 13:54:48 +0000 (GMT) (envelope-from MH@kernel32.de) Received: from localhost (localhost [127.0.0.1]) by crivens.unixoid.de (Postfix) with ESMTP id 959C93FF3; Fri, 19 Aug 2005 15:54:47 +0200 (CEST) Received: from crivens.unixoid.de ([127.0.0.1]) by localhost (crivens.unixoid.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 38370-04; Fri, 19 Aug 2005 15:54:43 +0200 (CEST) Received: from [10.38.0.10] (unknown [212.12.51.89]) by crivens.unixoid.de (Postfix) with ESMTP id C548B3F6A; Fri, 19 Aug 2005 15:54:43 +0200 (CEST) Message-ID: <4305E4A3.6040902@kernel32.de> Date: Fri, 19 Aug 2005 15:54:43 +0200 From: Marian Hettwer User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Justin T. Gibbs" References: <4305967B.8010909@kernel32.de> <435838B88932CE9C36A18199@aslan.scsiguy.com> In-Reply-To: <435838B88932CE9C36A18199@aslan.scsiguy.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at unixoid.de Cc: freebsd-current@freebsd.org Subject: Re: Adaptec AIC-7901 (ahd) broken with 6.0-BETA2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2005 13:54:49 -0000 Justin T. Gibbs wrote: >>Hi All, >> >>I believe the support for Adaptec's AIC7901 is broken in 6-BETA2. > > > It looks like the system was able to talk to the controller and your > drive just fine, but hung later. Can you break into the debugger > and get a stack trace of where the system is hung? > Pardon me, but how do I break into the debugger ? :) I know, if I'm using -CURRENT I should know how to do it... could you point me at the right direction anyway ? :-) Even if I could break into debugger, I would need to get a serial console working, otherwise a stack trace could be quite hard to get. I don't think I want to type this by hand... best regards, Marian