From owner-freebsd-scsi@FreeBSD.ORG Thu Jun 7 17:56:08 2007 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 74B6E16A400 for ; Thu, 7 Jun 2007 17:56:08 +0000 (UTC) (envelope-from ml@netfence.it) Received: from parrot.aev.net (parrot.aev.net [212.31.247.179]) by mx1.freebsd.org (Postfix) with ESMTP id 6982113C4C2 for ; Thu, 7 Jun 2007 17:56:07 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.ventu ([151.77.246.248]) (authenticated bits=128) by parrot.aev.net (8.14.1/8.13.8) with ESMTP id l57IBGrE002363 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 7 Jun 2007 20:11:24 +0200 (CEST) (envelope-from ml@netfence.it) Received: from alamar.ventu (alamar.ventu [10.1.2.18]) by soth.ventu (8.14.1/8.13.8) with ESMTP id l57HtupG022545; Thu, 7 Jun 2007 19:55:57 +0200 (CEST) (envelope-from ml@netfence.it) Message-ID: <466846A5.3010903@netfence.it> Date: Thu, 07 Jun 2007 19:55:49 +0200 From: Andrea Venturoli User-Agent: Thunderbird 2.0.0.0 (X11/20070605) MIME-Version: 1.0 To: Scott Long References: <20070606161221.GB31380@schottelius.org> <46672BAD.7010201@samsco.org> <466735B6.8050903@netfence.it> <20070607081316.GD30443@schottelius.org> <4667DE3A.1090802@samsco.org> In-Reply-To: <4667DE3A.1090802@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.61 on 212.31.247.179 Cc: freebsd-scsi@freebsd.org Subject: Re: Hangs with Adaptec 29320 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2007 17:56:08 -0000 Scott Long wrote: > Turning on every debugging option under the sun to slow the system to a > crawl is probably not a very good strategy. It's not a good direct strategy to solve a problem. It might be a good strategy to get insight about it, though. > As I said in a previous > mail, if you are having problems with the ahd driver, please contact the > ahd driver maintainer directly. As a developer myself, I find it very irritating to get a mail that says "It doesn't work" and nothing else. Turning on debug might help in getting a dump, a relevant error message or something alike; otherwise I wouldn't really know what one could write. BTW: I also complained in the past about the amrd driver on a SRCU42E: turned out from the serial number it was a faulty stock and I'm wating for Intel to replace it. I hope this solves it. bye av.