From owner-freebsd-stable@FreeBSD.ORG Sun May 14 07:08:38 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E779416A402 for ; Sun, 14 May 2006 07:08:38 +0000 (UTC) (envelope-from nakal@nurfuerspam.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 1E8A543D49 for ; Sun, 14 May 2006 07:08:37 +0000 (GMT) (envelope-from nakal@nurfuerspam.de) Received: (qmail invoked by alias); 14 May 2006 07:08:35 -0000 Received: from p5090DD90.dip.t-dialin.net (EHLO klotz.local) [80.144.221.144] by mail.gmx.net (mp042) with SMTP; 14 May 2006 09:08:35 +0200 X-Authenticated: #989277 Received: from [192.168.0.1] (klotz.local [192.168.0.1]) by klotz.local (8.13.6/8.13.6) with ESMTP id k4E78Q4q026586; Sun, 14 May 2006 09:08:29 +0200 (CEST) (envelope-from nakal@nurfuerspam.de) Message-ID: <4466D76A.3030903@nurfuerspam.de> Date: Sun, 14 May 2006 09:08:26 +0200 From: Martin User-Agent: Thunderbird 1.5 (X11/20060205) MIME-Version: 1.0 To: Phil Kernick References: <44668F8D.3090208@Kernick.org> In-Reply-To: <44668F8D.3090208@Kernick.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-stable Subject: Re: ATA DMA corruption on 5.5-beta4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 May 2006 07:08:39 -0000 Phil Kernick wrote: > Looking through the stable archives this was reported last year but there > does not seem to be any resolution of the problem. Yea. I had this problem, too. My controller was an old Highpoint ATA 66. Since noone could help, I moved directly to 6.x branch. That solved my issues. Something is fishy since 5.4R there. When you see any ATA DMA write errors, switch your PC immediatly off, or suffer severe file system damage. Martin