From owner-freebsd-drivers@FreeBSD.ORG Fri Jul 13 16:17:37 2012 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C72410656AA for ; Fri, 13 Jul 2012 16:17:37 +0000 (UTC) (envelope-from dieterbsd@engineer.com) Received: from mailout-us.mail.com (mailout-us.gmx.com [74.208.5.67]) by mx1.freebsd.org (Postfix) with SMTP id A663C8FC0A for ; Fri, 13 Jul 2012 16:17:36 +0000 (UTC) Received: (qmail 7726 invoked by uid 0); 13 Jul 2012 16:12:19 -0000 Received: from 67.206.184.93 by rms-us018 with HTTP Content-Type: text/plain; charset="utf-8" Date: Fri, 13 Jul 2012 12:12:15 -0400 From: "Dieter BSD" Message-ID: <20120713161217.298420@gmx.com> MIME-Version: 1.0 To: freebsd-drivers@freebsd.org X-Authenticated: #74169980 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 Content-Transfer-Encoding: 8bit X-GMX-UID: ti1ycPYV3zOlNR3dAHAhqWd+IGRvb8DL Subject: siisch1 DISCONNECT requested - why? X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2012 16:17:37 -0000 FreeBSD 8.2 amd64 SiI3132 SATA controller Seagate Barracuda LP 2 TB sata disk Disk has been working fine for ~1.5 years, zero problems. Suddenly: siisch1: DISCONNECT requested siisch1: siis_sata_connect() calling DELAY(100) [ previous line repeated a gazillion times ] siisch1: SATA connect timeout time=10000us status=00000000 siisch1: SIIS reset done: phy reset found no device (ada5:siisch1:0:0:0): lost device (ada5:siisch1:0:0:0): Synchronize cache failed (ada5:siisch1:0:0:0): removing device entry siisch1: CONNECT requested siisch1: SIIS reset... and the disk comes back. After umount/fsck/mount it is working ok again. Smartctl doesn't report any problems. System has ECC memory, conditioned power, air conditioning, ... I looked at siis.c but didn't find any clues. What would cause a disconnect request out of the blue?