From owner-freebsd-questions@FreeBSD.ORG Thu Nov 4 13:43:16 2004 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 C2CC916A4CE for ; Thu, 4 Nov 2004 13:43:16 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FA3E43D4C for ; Thu, 4 Nov 2004 13:43:16 +0000 (GMT) (envelope-from nlamprecht@gmail.com) Received: by wproxy.gmail.com with SMTP id 64so202127wri for ; Thu, 04 Nov 2004 05:43:16 -0800 (PST) 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:references; b=h+rTu2Qc3x1+13Dk4TdijyBY3oj+DXRHNT8QINuVUmo4r1jM4qOkf1O2Dc4X46EDtB87AWsmr7fYf8fRzTEOfbR5Zqsojl5qQ0BcsgsMqD0dOqJN8Ton6NzEU0iEW0opL6ci1OYinczyhx3kX/xaPHj1TPaTMz1vCcAqsBnGJg4= Received: by 10.54.37.63 with SMTP id k63mr218117wrk; Thu, 04 Nov 2004 05:43:15 -0800 (PST) Received: by 10.54.38.55 with HTTP; Thu, 4 Nov 2004 05:43:15 -0800 (PST) Message-ID: <7cbadc8704110405434c734ae2@mail.gmail.com> Date: Thu, 4 Nov 2004 15:43:15 +0200 From: Nelis Lamprecht To: Are Bryne In-Reply-To: <20041104141000.F3017@david.i.communique.no> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041104141000.F3017@david.i.communique.no> cc: FreeBSD Questions Subject: Re: ad0: WRITE command timeout... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Nelis Lamprecht List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Nov 2004 13:43:16 -0000 On Thu, 4 Nov 2004 14:10:42 +0100 (CET), Are Bryne wrote: > > > Hello, > > After upgrading a computer from FreeBSD 4.8-something to 4.10-RELEASE-p3, > I'm getting lots of the following: > > ad0: WRITE command timeout tag=0 serv=0 - resetting > ata0: resetting devices .. done > Hi, Seen this once before and in my case it was a faulty hard drive cable. Check to see whether your cable is not loose or incorrectly inserted and perhaps try a new one. It may also be caused by an incorrect DMA setting if memory serves me correct. Nelis