From owner-freebsd-bugs@FreeBSD.ORG Fri Jan 27 23:28:00 2006 Return-Path: X-Original-To: freebsd-bugs@freebsd.org Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AF6816A420; Fri, 27 Jan 2006 23:28:00 +0000 (GMT) (envelope-from thede@loder.com) Received: from mini01.loder.com (mini01.loder.com [66.245.252.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0583B43D45; Fri, 27 Jan 2006 23:27:59 +0000 (GMT) (envelope-from thede@loder.com) Received: by mini01.loder.com (Postfix, from userid 501) id B7375304F18; Fri, 27 Jan 2006 15:27:59 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mini01.loder.com (Postfix) with ESMTP id A61AA304F13; Fri, 27 Jan 2006 15:27:59 -0800 (PST) Date: Fri, 27 Jan 2006 15:27:59 -0800 (PST) From: Thede Loder To: freebsd-bugs@freebsd.org In-Reply-To: <20060111115022.8AE1916A43A@hub.freebsd.org> Message-ID: References: <20060111115022.8AE1916A43A@hub.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: sos@FreeBSD.org Subject: kern/91408: ata(4) failure: SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jan 2006 23:28:00 -0000 >Number: 91410 >Category: kern >Synopsis: Promise SATA controller + striping : "SETFEATURES SET TRANSFER MODE semaphore timeout" >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jan 06 18:30:04 GMT 2006 >Closed-Date: >Last-Modified: >Originator: John McLaughlin >Release: 6.0-R >Organization: >Environment: FreeBSD jmcl.shadowbox.ie 6.0-STABLE FreeBSD 6.0-STABLE #0: Fri Jan 6 13:35:01 GMT 2006 Interestingly, this bug disappeared for me somewhere around 6.0-STABLE #4 (i386), but as of 6.0-STABLE #9 or 10, it is back. What I've noticed: * It only affects drives/filesystems attached via a SATA card * It occurs with SI 3113 or Promise 20575 SATA controllers, maybe others * The error starts under heavy file system load (What I usually do to trigger it is to start a file system copy of several gigs worth of files from a drive attached to the SATA controller to another drive on the motherboard bus (Via 8235). Sometimes this copy alone will trigger it. But its much more likely if I start some other read operation on the drive, like 'ls -lR' or a $ 'wc `find . -type file`) * it is reproducable based upon my own experience with it, I'd say that the following three bugs may be the same thing: kern/91410 kern/91408 i386/86364 Soren, I think this is your domain. Since it's fairly reproducible, let me know what I can do to help you find it. E: thede@loder.com