From owner-freebsd-current@FreeBSD.ORG Mon Aug 2 17:36:22 2004 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 7A3D716A4CE for ; Mon, 2 Aug 2004 17:36:22 +0000 (GMT) Received: from will.iki.fi (will.iki.fi [217.169.64.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2890643D39 for ; Mon, 2 Aug 2004 17:36:22 +0000 (GMT) (envelope-from will+freebsd-current@will.iki.fi) Received: from [10.129.39.131] (b212-54-23-216.elisa-laajakaista.fi [212.54.23.216]) by will.iki.fi (Postfix) with ESMTP id E5F351F3; Mon, 2 Aug 2004 20:36:18 +0300 (EEST) Message-ID: <410E7B8B.3080407@will.iki.fi> Date: Mon, 02 Aug 2004 20:36:11 +0300 From: Ville-Pertti Keinonen User-Agent: Mozilla Thunderbird 0.7.1 (X11/20040708) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kenneth Culver References: <410E688D.7020709@will.iki.fi> <410E74F7.1070000@will.iki.fi> <20040802132802.3d7kgoow0c80ss0s@www.sweetdreamsracing.biz> In-Reply-To: <20040802132802.3d7kgoow0c80ss0s@www.sweetdreamsracing.biz> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: ATA driver races with interrupts 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: Mon, 02 Aug 2004 17:36:22 -0000 Kenneth Culver wrote: > I have this exact same motherboard, but I'm using the onboard promise > controller > set up with 2 disks as a raid0, and I'm not having any problems with this > setup. I used the promise controller because from what I've been told, > the > promise controllers are very fast in FreeBSD compared to other > controllers. If the two disks appear as one to FreeBSD, the problem probably isn't going to show up. It may also depend on the controller, since the channel registers might not satisfy the conditions in ata_generic_interrupt (I didn't bother digging up my ATA specs while debugging this), but even if it is a controller oddity, I don't think the ATA driver should be sensitive such conditions.