From owner-freebsd-current@FreeBSD.ORG Thu Sep 25 00:33:01 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 EFD5916A4B3 for ; Thu, 25 Sep 2003 00:33:01 -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 953BE43FE9 for ; Thu, 25 Sep 2003 00:33:00 -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 h8P7WuKg050816; Thu, 25 Sep 2003 09:32:56 +0200 (CEST) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.9/8.12.9/Submit) id h8P7Wt4M050815; Thu, 25 Sep 2003 09:32:55 +0200 (CEST) From: Soren Schmidt Message-Id: <200309250732.h8P7Wt4M050815@spider.deepcore.dk> In-Reply-To: <5.2.1.1.2.20030923185208.012f2240@www.computinginnovations.com> To: Derek Ragona Date: Thu, 25 Sep 2003 09:32:55 +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: Putinas 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: Thu, 25 Sep 2003 07:33:02 -0000 It seems Derek Ragona wrote: > Søren, > > My setup is as follows: > Maxtor 6Y120MO 120GB SATA drive > Adaptec Serial ATA RAID 1210SA > Intel® Desktop Board D845GEBV2 > 1GB RAM > 1.7 GHz Celeron CPU Ok, I'll try to get something semialr setup here and try to reproduce. > If there is some way to get more debugging information, please let me > know. If you want the ATA subsystem rebuilt differently for more > debugging, I'm happy to do that as well. If you want access to the box, I > will give you that too. Hmm debugging this kind of problems most often requires "hands on" access to the HW, in some cases the ability to hook up measuring/test equipment greatly enhances the problem hunting (or is the only way to catch it). -Søren