From owner-freebsd-questions@FreeBSD.ORG Fri Jan 28 12:57:44 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4729A16A4CE for ; Fri, 28 Jan 2005 12:57:44 +0000 (GMT) Received: from allrounder.lame.at (mail.softlink.at [195.58.166.252]) by mx1.FreeBSD.org (Postfix) with ESMTP id B064643D31 for ; Fri, 28 Jan 2005 12:57:43 +0000 (GMT) (envelope-from haimat@lame.at) Received: from itchy.lame.at (unknown [213.235.192.15]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by allrounder.lame.at (Postfix) with ESMTP id A708D300E6 for ; Fri, 28 Jan 2005 13:57:40 +0100 (CET) From: "Matthias F. Brandstetter" To: freebsd-questions@freebsd.org Date: Fri, 28 Jan 2005 13:57:39 +0100 User-Agent: KMail/1.7 References: <41F5460F.3050408@mindling.com> In-Reply-To: <41F5460F.3050408@mindling.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501281357.39992.haimat@lame.at> Subject: Re: READ_DMA timed out on Promise FastTrak100 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jan 2005 12:57:44 -0000 ---------- quoting list@mindling.com ---------- > However, when I boot FreeBSD, the system reports READ_DMA errors on the > second drive, and the array reports a degraded state. I can still mount > it, and both drive lights flash when accessing the volume. I had similar problems with my SATA RAID controller, lots of DMA errors. Looks like a bug in 5.3 -- or is it fixed now? I solved this issue in disabling DMA via sysctl... HTH! Greetings, Matthias -- Marge, tell Bart I just want to drink a nice glass of syrup like I do every morning. -- Homer Simpson Lisa the Vegetarian