From owner-freebsd-questions@FreeBSD.ORG Thu Nov 4 15:55:39 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 9BB0E16A4CE for ; Thu, 4 Nov 2004 15:55:39 +0000 (GMT) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71B9E43D31 for ; Thu, 4 Nov 2004 15:55:38 +0000 (GMT) (envelope-from are.bryne@communique.no) Received: from david.i.communique.no ([83.227.105.114] [83.227.105.114]) by mxfep02.bredband.com with ESMTP <20041104155537.XEUJ44.mxfep02.bredband.com@david.i.communique.no> for ; Thu, 4 Nov 2004 16:55:37 +0100 Date: Thu, 4 Nov 2004 16:55:30 +0100 (CET) From: Are Bryne To: FreeBSD Questions In-Reply-To: <7cbadc8704110405434c734ae2@mail.gmail.com> Message-ID: <20041104164030.V3017@david.i.communique.no> References: <20041104141000.F3017@david.i.communique.no> <7cbadc8704110405434c734ae2@mail.gmail.com> Organization: Communique DA MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; boundary="0-1355040245-1099583602=:3017" Content-ID: <20041104165338.P3017@david.i.communique.no> Subject: Re: ad0: WRITE command timeout... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Nov 2004 15:55:39 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1355040245-1099583602=:3017 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8BIT Content-ID: <20041104165338.Q3017@david.i.communique.no> On Thu, 4 Nov 2004, Nelis Lamprecht wrote: > On Thu, 4 Nov 2004 14:10:42 +0100 (CET), Are Bryne > wrote: [...] >> 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 The disk in question is a FUJITSU MPC3043AT/6018 using ATA/ATAPI rev 3 according to atacontrol. It is master on its controller and uses UDMA33 transfers, and has an idle PIO4 cd-rom player as a slave. The controller is identified in dmesg as: atapci0: port 0xe000-0xe00f at device 7.1 on pci0 [...] > 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. Thank you - I will check that. > It may also be caused by an incorrect DMA setting if memory serves me > correct. I might try turning DMA off to see if that helps... > Nelis Again, please CC me to make sure I see the whole thread. Regards, Are Bryne -- Communiqué DA Office: +47 22 44 33 99 Postboks 9050 Grønland Mobile: +47 900 22 009 NO-0133 Oslo URL: http://www.communique.no --0-1355040245-1099583602=:3017--