From owner-freebsd-stable@freebsd.org Wed Sep 20 23:16:53 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A76BCE019B8 for ; Wed, 20 Sep 2017 23:16:53 +0000 (UTC) (envelope-from andrei@fazik.net.ua) Received: from mail.fazik.net.ua (mail.fazik.net.ua [176.9.63.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6F2718423B for ; Wed, 20 Sep 2017 23:16:53 +0000 (UTC) (envelope-from andrei@fazik.net.ua) Mime-Version: 1.0 DKIM-Filter: OpenDKIM Filter v2.10.3 mail.fazik.net.ua 80D7C8B7CD Date: Wed, 20 Sep 2017 23:06:11 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: andrei@fazik.net.ua Message-ID: Subject: CAM status: Command timeout To: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Sep 2017 23:16:53 -0000 Hello,=0AAfter updating to 11.1 my home server can't boot with errors lik= e=0A(ada0:ata2:0:0:0): WRITE_DMA48. ACB: 35 00 50 29 10 40 6c 00 0c 00=0A= (ada0:ata2:0:0:0): CAM status: Command timeout=0A(ada0:ata2:0:0:0): Retry= ing command=0Afor all 6 sata hdd(stripe from 2 raidz)=0AACB different fro= m boot to boot=0ASometimes it even can boot, but in few minutes will hang= with same errors.=0A=0AHardware: Supermicro X8DTN+-F / 6xWD1502FYPS-02W3= B0 /2xE5649=0AHDDs connected to sata ports on baseboard.=0AIf I add=0Ahin= t.ata.2.mode=3DPIO4=0Ahint.ata.3.mode=3DPIO4=0Ahint.ata.4.mode=3DPIO4=0Ah= int.ata.5.mode=3DPIO4=0Ato device.hints I'm able to boot but performance = of IO becomes really disappointing.=0AAlso, if I add something like "find= / -name something" to zfs rc script, than boots fine.=0A=0AIf I roll bac= k system to 11.0 all works fine again.=0AAny advise on debuging of this i= ssue?=0AAlso raised bug report some time ago for this issue=0Ahttps://bug= s.freebsd.org/bugzilla/show_bug.cgi?id=3D221704