From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 09:35:56 2003 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 0DD8E16A4B3 for ; Sun, 21 Sep 2003 09:35:56 -0700 (PDT) Received: from melusine.cuivre.fr.eu.org (melusine.cuivre.fr.eu.org [62.212.105.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2717D43F3F for ; Sun, 21 Sep 2003 09:35:55 -0700 (PDT) (envelope-from thomas@cuivre.fr.eu.org) Received: by melusine.cuivre.fr.eu.org (Postfix, from userid 1000) id 01A682A42B; Sun, 21 Sep 2003 18:35:53 +0200 (CEST) Date: Sun, 21 Sep 2003 18:35:53 +0200 From: Thomas Quinot To: Bryan Liesner Message-ID: <20030921163553.GA19729@melusine.cuivre.fr.eu.org> References: <200309200755.h8K7t4fA049614@spider.deepcore.dk> <20030920195311.GA97748@melusine.cuivre.fr.eu.org> <20030920192850.Y458@gravy.homeunix.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20030920192850.Y458@gravy.homeunix.net> User-Agent: Mutt/1.4i X-message-flag: WARNING! Using Outlook can damage your computer. cc: freebsd-current@freebsd.org Subject: Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt 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: Sun, 21 Sep 2003 16:35:56 -0000 Le 2003-09-21, Bryan Liesner écrivait : > The patch doesn't take care of the hang for me. Does it change anything, or do you still see the 'REQUEST_SENSE recovered from missing interrupt'? Is your source tree up-to-date? Several fixes have been committed to both the ATA and the CAM subsystems recently, that address problems uncovered by the transition to ATAng. > Did anyone read _any_ of my previous posts? Certainly so, since you already received answers to some of them. If you'd like to help speed up the resolution of the problems you see, maybe you could provide a backtrace at the point where your system hangs, and a log of boot -v output, with the CAMDEBUG and CAM_DEBUG_FLAGS=CAM_DEBUG_CCB options. Thomas. -- Thomas.Quinot@Cuivre.FR.EU.ORG