From owner-freebsd-stable@FreeBSD.ORG Fri Jun 24 06:39:43 2005 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 CE46C16A41C for ; Fri, 24 Jun 2005 06:39:43 +0000 (GMT) (envelope-from nakal@nurfuerspam.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 21F1B43D49 for ; Fri, 24 Jun 2005 06:39:42 +0000 (GMT) (envelope-from nakal@nurfuerspam.de) Received: (qmail invoked by alias); 24 Jun 2005 06:39:40 -0000 Received: from p5090C3B7.dip.t-dialin.net (EHLO klotz.local) [80.144.195.183] by mail.gmx.net (mp023) with SMTP; 24 Jun 2005 08:39:40 +0200 X-Authenticated: #989277 Received: from [127.0.0.1] (localhost [127.0.0.1]) by klotz.local (8.13.3/8.13.3) with ESMTP id j5O6daEK001436 for ; Fri, 24 Jun 2005 08:39:37 +0200 (CEST) (envelope-from nakal@nurfuerspam.de) Message-ID: <42BBAAA8.3050503@nurfuerspam.de> Date: Fri, 24 Jun 2005 08:39:36 +0200 From: Martin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050403) X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD Stable References: <1117573047.3095.24.camel@klotz.local> In-Reply-To: <1117573047.3095.24.camel@klotz.local> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Re: ATA DMA timeouts [FIXED] 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: Fri, 24 Jun 2005 06:39:43 -0000 Hi, thank you, whoever fixed it and whatever it was, but -STABLE is stable again for me. The ATA DMA timeouts have disappeared with yesterdays kernel. Looking at the CVS tree, I notice that there weren't many changes to the ATA code before the problems appeared and also when it has been fixed. More info: I didn't update world to build this latest kernel and there were no changes in my kernel configuration. There is still one and only difference. I updated the nvidia-driver this time. I wonder if an "old" nvidia-driver can lead to ATA DMA errors. I don't think so, but I just want to tell you to make my report complete here. (Btw, nvidia-driver triggers a "panic: spinlock rm.mutex_mtx not in order list, when using "option WITNESS" without "option WITNESS_SKIPSPIN".) Thanks, Martin