From owner-freebsd-current@FreeBSD.ORG Wed Feb 25 19:00:39 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E899C106567B for ; Wed, 25 Feb 2009 19:00:39 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout0.freenet.de (mout0.freenet.de [IPv6:2001:748:100:40::2:2]) by mx1.freebsd.org (Postfix) with ESMTP id 7ED1C8FC29 for ; Wed, 25 Feb 2009 19:00:39 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from [195.4.92.23] (helo=13.mx.freenet.de) by mout0.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #76) id 1LcOzm-0005ia-1z for current@freebsd.org; Wed, 25 Feb 2009 20:00:38 +0100 Received: from te437.t.pppool.de ([89.55.228.55]:34864 helo=ernst.jennejohn.org) by 13.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #76) id 1LcOzl-0002MM-KX for current@freebsd.org; Wed, 25 Feb 2009 20:00:38 +0100 Date: Wed, 25 Feb 2009 20:00:35 +0100 From: Gary Jennejohn To: current@freebsd.org Message-ID: <20090225200035.623248c3@ernst.jennejohn.org> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: SATA disks suddenly stop working X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2009 19:00:41 -0000 I've been having lots of problems with SATA drives attached to higher port numbers, namely ata5 and ata6. I was installing Linux under qemu today and it had been running for several hours and had installed multi-gigabytes of data when qemu just stopped. I noticed that all I/O to the disk had ceased. Doing "atacontrol reinit" on the port (ata5) resulted in a message that the device was not configured, which was patently false since qemu had just been merrily writing to it. This with a kernel made from sources updated today at about 2 PM (GMT+1). I've also seen problems with a disk attached to ata6. It just sort of disappears after a while. Disks attached to ata2, ata3 and ata4 don't exhibit any problems. Is anyone else seeing this weird behavior? --- Gary Jennejohn