From owner-freebsd-stable@FreeBSD.ORG Thu Feb 28 14:47:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91EE71065673 for ; Thu, 28 Feb 2008 14:47:30 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by mx1.freebsd.org (Postfix) with ESMTP id 1A53D8FC18 for ; Thu, 28 Feb 2008 14:47:29 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so355313uge.37 for ; Thu, 28 Feb 2008 06:47:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=P4UPNDERik2MLCqvJoPA2zlYGpfvRoyRHnWbyaLsj3I=; b=h1u9ZNPaTgyfzrQXuzo3G7zN7IEs9zFDzwDXaLbIDjVb5mPwGrFkHirMfHJcKJ4CbgLw6bVAMLFKPh0u/DRpQ6kfAQS+B1ee24/vSvDQux80kL723MDaIEVDhe+i3QxRzwuYLstRZwMu9nZpvX0OT093rI1qWPVQyHka1FPpVS8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=oRlYi2vIaRlT0IvORFYndBiOybWVaC+oLKj/n+hZBIvalBdX8Fh5rH025leSlFkGx3/33bg9yKsX0qC2eijnUvSdHosMuz21U8woYGc/s72CcKaDxMed0HfLE6EBPhOZ2Kwo/qfdSTowdtOSCPCLcxh2I/hYpMsgnPcD9vn/K8c= Received: by 10.66.237.9 with SMTP id k9mr3498678ugh.13.1204210048867; Thu, 28 Feb 2008 06:47:28 -0800 (PST) Received: by 10.66.219.18 with HTTP; Thu, 28 Feb 2008 06:47:28 -0800 (PST) Message-ID: <3aaaa3a0802280647v25e288fgf786d9c8a0bfc667@mail.gmail.com> Date: Thu, 28 Feb 2008 14:47:28 +0000 From: Chris To: "Jeremy Chadwick" In-Reply-To: <20080227190509.GA9987@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47C52948.2070500@sasktel.net> <20080227121129.GA76419@eos.sc1.parodius.com> <47C5ACD0.8000009@sasktel.net> <20080227190509.GA9987@eos.sc1.parodius.com> Cc: freebsd-stable@freebsd.org, Stephen Hurd Subject: Re: ad0 READ_DMA TIMEOUT errors on install of 7.0-RELEASE 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: Thu, 28 Feb 2008 14:47:30 -0000 > > If you replace the disk and you still continue to see DMA errors, then > my vote would be that you're experiencing the same thing others (and > myself, on one occasion) are. I've done my best to bring this issue to > the attention of proper people in recent days, and that's all I can say > on the matter. > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > _______________________________________________ Ouch, I have a server which both hds show dma errors all new hardware. I cant rule out hardware failure, incompatible sata interface etc. but if it is a freebsd bug then surely its a showstopper as stability is compromised which freebsd has built its reputation on. Did they push ahead with release because waiting for the mia dev? Chris