From owner-freebsd-current@FreeBSD.ORG Tue Sep 23 08:51:37 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E53116A4B3 for ; Tue, 23 Sep 2003 08:51:37 -0700 (PDT) Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 191F843F3F for ; Tue, 23 Sep 2003 08:51:36 -0700 (PDT) (envelope-from sos@spider.deepcore.dk) Received: from spider.deepcore.dk (localhost [127.0.0.1]) by spider.deepcore.dk (8.12.9/8.12.9) with ESMTP id h8NFpXKg021933; Tue, 23 Sep 2003 17:51:33 +0200 (CEST) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.9/8.12.9/Submit) id h8NFpXcj021932; Tue, 23 Sep 2003 17:51:33 +0200 (CEST) From: Soren Schmidt Message-Id: <200309231551.h8NFpXcj021932@spider.deepcore.dk> In-Reply-To: <004c01c381dc$f27aace0$1e64a8c0@spotripoli.local> To: Putinas Date: Tue, 23 Sep 2003 17:51:33 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 X-mail-scanned: by DeepCore Virus & Spam killer v1.3 cc: freebsd-current@FreeBSD.ORG Subject: Re: SATA drive lock-up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 15:51:37 -0000 It seems Putinas wrote: > Hi all, > Inspired with all the FreeBSD is free software , windows and buggy hardware > and blabla I realize what maybe I could do more to help solve this problem. > I made small research on my computer and I find out what till the cvsup date > 2003.08.24.00.00.00 till ATAng commitment to the source my SATA Sil3112A > working fine. > After this date I always get WRITE_DMA recovered from missing interrupt > error > after more or less intensive input output with harddisk subsystem , and > after I/O error and so on ... > My bet is what in this case buggy is not hardware .. at least this bug > didn't > show up until 25 August Well, it works here with pure SATA drives at least, do you use real SATA disks on PATA ones with SATA dongles ? So long that I cant reproduce the problem its hard to fix... -Søren