From owner-freebsd-scsi@freebsd.org Thu Sep 14 05:51:14 2017 Return-Path: Delivered-To: freebsd-scsi@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 8861AE01687 for ; Thu, 14 Sep 2017 05:51:14 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: from bizet.nethelp.no (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4D64465D7A; Thu, 14 Sep 2017 05:51:13 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: from localhost (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by bizet.nethelp.no (Postfix) with ESMTP id 4732DE6077; Thu, 14 Sep 2017 07:51:12 +0200 (CEST) Date: Thu, 14 Sep 2017 07:51:12 +0200 (CEST) Message-Id: <20170914.075112.74745398.sthaug@nethelp.no> To: scottl@samsco.org Cc: cgull@glup.org, freebsd-scsi@freebsd.org, jhb@freebsd.org Subject: Re: GEOM probes fail on aac with EARLY_AP_STARTUP From: sthaug@nethelp.no In-Reply-To: <0D188193-4562-483A-B123-6117CC65AF01@samsco.org> References: <20170908.151504.74703639.sthaug@nethelp.no> <0c73b27e-d4ac-4003-81df-b2d9a0a63a81@glup.org> <0D188193-4562-483A-B123-6117CC65AF01@samsco.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Sep 2017 05:51:14 -0000 > > Your issue isn't obviously directly related to mine. mps is a CAM driver > > and aac is not (at least not for normal block volumes), which makes disk > > probe/attach quite different. I also don't see an obvious driver flag > > like the one in aac. > > > > It's a different pattern in CAM, and CAM itself looks to be safe. MPS and MPR > have their own intrhooks, and on review just now I see a potential for a similar > problem to what you saw and that would match Steinar's symptoms. Please > try the following patch: I have applied the patch and verified that my 11.1 server boots nicely with this patch. However, my original problem turned out to have a different cause (config error on my part), and thus I cannot verify that this patch actually *fixes* a problem. Steinar Haug, Nethelp consulting, sthaug@nethelp.no