From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 21 20:58:06 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71A0D106566C; Wed, 21 Oct 2009 20:58:06 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f210.google.com (mail-fx0-f210.google.com [209.85.220.210]) by mx1.freebsd.org (Postfix) with ESMTP id C97F08FC15; Wed, 21 Oct 2009 20:58:05 +0000 (UTC) Received: by fxm6 with SMTP id 6so7855689fxm.43 for ; Wed, 21 Oct 2009 13:58:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=kQEl5rmzKQF/leCwKSru5WiN1lRf0YouCWZ5z5b1EMA=; b=J945MyCTtDFJ/Z7UjhtDnsPSa0IZ2ITKxFnEk2SrLzc41cFDiZ01pOZzbAWsT4qxWM 3gDIOtYl9PvB0cBXIeX8EfHULWKRitz1nu5cvL/U8QtjSHJUNY+UzB05w0+/1pWrYiMF mF726cLkBBqEm6Aznx6eI/LnsOLg830UWVWKY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=o8bGqXtd6/h5oonR3phPM+ZwypkNP2K5yPAGhPjrJ7dw4v4ShcWJap+oJCNET0mJD+ LdqHIiJaB+/3zlY0qj3/1ew55LlTv0yTXX6lGRbD4TYqvJ3Ib+puT59SkS/gub4PDigP 86RvwLxM7xH51dvKpQpPmfXp+fFmsdhp5Gxng= Received: by 10.103.76.37 with SMTP id d37mr3460265mul.99.1256158684881; Wed, 21 Oct 2009 13:58:04 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id i5sm100573mue.38.2009.10.21.13.58.03 (version=SSLv3 cipher=RC4-MD5); Wed, 21 Oct 2009 13:58:03 -0700 (PDT) Sender: Alexander Motin Message-ID: <4ADF75DA.8040707@FreeBSD.org> Date: Wed, 21 Oct 2009 23:58:02 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20090901) MIME-Version: 1.0 To: Steve Polyack References: <4ADE060C.5050605@comcast.net> <4ADF44CE.3030605@comcast.net> In-Reply-To: <4ADF44CE.3030605@comcast.net> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable , freebsd-hardware@freebsd.org Subject: Re: FreeBSD and SATA Port Multipliers X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Oct 2009 20:58:06 -0000 Steve Polyack wrote: > Alexander Motin wrote: >> Have you tried new CAM-based ATA subsystem present in 8.x by siis(4) >> driver? Work is still in progress there, but it should work with port >> multipliers much better then previous implementation. > > Indeed, the siis(4) driver works MUCH better. However, it's still not > always detecting every drive if I fill a port multiplier with 5/5 > drives. Sometimes it boots up with 4, sometimes with 5. > > Snippet from the dmesg in my other reply: > siisch4: Timeout on slot 25 > siisch4: siis_timeout is 00000000 ss 02000000 rs 02000000 es 00000000 > sts 80192000 serr 00000000 > (aprobe0:siisch4:0:1:0): SIGNATURE: 0000 > (aprobe0:siisch4:0:2:0): SIGNATURE: 0000 > (aprobe0:siisch4:0:3:0): SIGNATURE: 0000 > (aprobe0:siisch4:0:4:0): SIGNATURE: 0000 > ada0 at siisch4 bus 0 target 1 lun 0 > ada0: ATA/ATAPI-8 SATA 2.x device > ada0: 300.000MB/s transfers > ada0: 1430799MB (2930277168 512 byte sectors: 16H 63S/T 16383C) > ada0: Native Command Queueing enabled > > siisch4 bus 0 target 0 lun 0 is missing here, due to some kind of > timeout. The drives are fine and the missing device does not follow a > specific physical drive. Lastly, using camcontrol to rescan port > multipliers and attached drives only leads to failure. Rescanning > everythign simply loses all but one drive attached to each port multiplier. As I have said, infrastructure is not finished yet, especially part of recovery from timeout state. That's why probably rescan does not solve situation. From other side, this timeout may be called by some driver issue, as it looks too repeatable. If your conditions permit, you can try to upgrade to recent HEAD to look how will it go with newer code. I am periodically merging my work there from Perforce. Also I am going to generate new test patch for HEAD, which includes reworked PMP support, tomorrow. I will put it to http://people.freebsd.org/~mav/ as usual, so you can test it. -- Alexander Motin