From owner-freebsd-fs@FreeBSD.ORG Wed Apr 13 17:04:18 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C991106566C for ; Wed, 13 Apr 2011 17:04:18 +0000 (UTC) (envelope-from kungfujesus06@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 10F8F8FC12 for ; Wed, 13 Apr 2011 17:04:17 +0000 (UTC) Received: by fxm11 with SMTP id 11so797424fxm.13 for ; Wed, 13 Apr 2011 10:04:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=dFXnbPTu2MnuZ4UiBMjxg611BcqBsEPEP8hNeZitWJQ=; b=W7dmykmLijWJIajgztHw2Tb71SM/Y3wf7nC/+11I+DrmQ6Vv5UgAD2RvIssUYbGnDJ ab6wqjnoabCFRfsQ2KIvSKz/s0yISOBWqJbUvRBpoeUmfakvJkWoK37Bgi6p7AtDK6Do +0VqW0oHR1UWcxmtmS9J/oaQAVq8JkLkIcQUM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=tqgRl/3eYTew5RjOYw5ieq5jwffIzZiMdb32ruVdSvSnspEBCNVAsucEBrUOsFEIly 1qaL1fqDk6H95L8UBqRFvmEPNLDs7HzZmJ/kZ1edLmgYKjQVhl0vziIfrIAkPIWARNFq NRnHER/ffedDQrgywAs+058DTaOh//TgjUvOo= MIME-Version: 1.0 Received: by 10.223.160.8 with SMTP id l8mr1342253fax.114.1302714256956; Wed, 13 Apr 2011 10:04:16 -0700 (PDT) Received: by 10.223.118.204 with HTTP; Wed, 13 Apr 2011 10:04:16 -0700 (PDT) Date: Wed, 13 Apr 2011 13:04:16 -0400 Message-ID: From: Adam Stylinski To: koie@suri.co.jp Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: siisch0: Timeout on slot 30 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Apr 2011 17:04:18 -0000 I've encountered similar situations with my Silicon Image SATA controller which uses internally a SATA port multiplier for the E-SATA ports. When used in conjunction with enough disks I'd constantly get these issues. In short I'd avoid port multipliers until a proper bug fix has been found for this driver.