From owner-freebsd-current Thu Feb 27 6:43:15 2003 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 8E4B737B401 for ; Thu, 27 Feb 2003 06:43:14 -0800 (PST) Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9FD143FCB for ; Thu, 27 Feb 2003 06:43:08 -0800 (PST) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.5/8.12.6) id h1REgdkA033960; Thu, 27 Feb 2003 15:42:39 +0100 (CET) (envelope-from sos) From: Soeren Schmidt Message-Id: <200302271442.h1REgdkA033960@spider.deepcore.dk> Subject: Re: Yet another ATA-related Kernel trap 12 :-( In-Reply-To: <3E5E22BC.FA7BB8A5@mindspring.com> To: Terry Lambert Date: Thu, 27 Feb 2003 15:42:39 +0100 (CET) Cc: Vladimir Kushnir , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL98b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Terry Lambert wrote: > Vladimir Kushnir wrote: > > Setup: Fujitsu MPG3409AT E disk on external CMD649 controller (the only > > HD). Kernel trap while booting with timeout for ad0 device. Setting > > "hw.ata.ata_dma=0" solves the problem. Sources last cvsupped last night > > (after the last ATA-related commits). Dmesg output attached, but that's > > about all I can provide - no serial console here. > > This is probably related to the inverted sense-test that was > recently fixed. Nope. > FWIW: the CMD640 series of chips is well known to mung DMA, if > an interrupt occurs during a transfer. I can't say for certain > that the CMD649 has this problem, so you might want to look at > the vendor errata for the chips. Personally, I avoid the CMD64x > controllers entirely, so as to avoid getting a bad one, since I > have no idea if there is actually a good one in existance. 8-(. The old CMD640 should be avoided at all costs, the newer CMD646 has problems thats taken care of pr revision. The newer CMD648/649 are OK but are not the best performers... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message