From owner-freebsd-current Thu Feb 27 6:39:21 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 79F8537B401 for ; Thu, 27 Feb 2003 06:39:20 -0800 (PST) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id D09BB43FBD for ; Thu, 27 Feb 2003 06:39:19 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0140.cvx40-bradley.dialup.earthlink.net ([216.244.42.140] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18oPBs-000054-00; Thu, 27 Feb 2003 06:39:16 -0800 Message-ID: <3E5E22BC.FA7BB8A5@mindspring.com> Date: Thu, 27 Feb 2003 06:37:48 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Vladimir Kushnir Cc: current@FreeBSD.ORG Subject: Re: Yet another ATA-related Kernel trap 12 :-( References: <20030227000832.H654@kushnir1.kiev.ua> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4e1a2cd6e261879645ae22101dc3e35d4350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c 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 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. 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-(. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message