From owner-freebsd-current@FreeBSD.ORG Fri Aug 19 14:58: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 5C00C16A41F for ; Fri, 19 Aug 2005 14:58: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 E0F3D43D46 for ; Fri, 19 Aug 2005 14:58:48 +0000 (GMT) (envelope-from MH@kernel32.de) Received: from localhost (localhost [127.0.0.1]) by crivens.unixoid.de (Postfix) with ESMTP id 80DAD3FF3; Fri, 19 Aug 2005 16:58: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-09; Fri, 19 Aug 2005 16:58:44 +0200 (CEST) Received: from [10.38.0.10] (unknown [212.12.51.89]) by crivens.unixoid.de (Postfix) with ESMTP id E2BAA3EDC; Fri, 19 Aug 2005 16:58:43 +0200 (CEST) Message-ID: <4305F3A3.3080504@kernel32.de> Date: Fri, 19 Aug 2005 16:58: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> <4305E4A3.6040902@kernel32.de> <3F5D63052EDC670D1C98312F@[10.0.0.90]> In-Reply-To: <3F5D63052EDC670D1C98312F@[10.0.0.90]> 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 14:58:49 -0000 Justin T. Gibbs wrote: >>> 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 ? :-) > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-online-ddb.html > Thanks, I'll give it a read-through. > >> 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... > > > The top few functions are likely all that are important. > followed by > PgUp is your friend. > I know this friend pretty good. Unluckily he's not available... Num-Lock still works, but scroll-lock doesn't. I'm unable to scroll up, which is a pity. With no serial console... I can't easily scroll up or even do some copy 'n paste. thanks so far and best regards, Marian