From owner-freebsd-stable@FreeBSD.ORG Fri Jun 24 19:00:09 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 057D016A41C for ; Fri, 24 Jun 2005 19:00:09 +0000 (GMT) (envelope-from twesky@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFDCF43D49 for ; Fri, 24 Jun 2005 19:00:08 +0000 (GMT) (envelope-from twesky@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so517945wri for ; Fri, 24 Jun 2005 12:00:08 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LDrsW6wfvtX36dwdy8ESs3MKjc72QN2drDhXg7oCFAhlyJMTo2C9nqyi2fNVh7BI/+nfXLrHAduN+/Dc2g5tmqdozflB/U3aXsG3j+qwA5xFnTRHDfrR0cSsZkAPxjJ6gjrxZcaYwV7AGf+levzt7DWF7uF6awnPTc3/e2R5F5M= Received: by 10.54.42.17 with SMTP id p17mr1966853wrp; Fri, 24 Jun 2005 12:00:08 -0700 (PDT) Received: by 10.54.45.71 with HTTP; Fri, 24 Jun 2005 12:00:08 -0700 (PDT) Message-ID: <8d02aed005062412001c7903b3@mail.gmail.com> Date: Fri, 24 Jun 2005 14:00:08 -0500 From: twesky To: Johny Mattsson In-Reply-To: <42BC5353.1090807@earthmagic.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <8d02aed00506181404642100b9@mail.gmail.com> <42BC5353.1090807@earthmagic.org> Cc: freebsd-stable@freebsd.org Subject: Re: ATA_DMA errors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: twesky 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 19:00:09 -0000 I don't think it is a hardware problem. Unless you replace it with the exact same hardware, it'll be difficult to determine if it was the hardware. I haven't had any issues with 5.3R or any stable version before April 15. I am going to do some checking this weekend and see if it is hardware or software what is causing my timeouts.