From owner-freebsd-stable@freebsd.org Thu May 24 17:12:26 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7290EF8D70; Thu, 24 May 2018 17:12:25 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) (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 7AB667909C; Thu, 24 May 2018 17:12:25 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from amavis-ori.ijs.si (localhost [IPv6:::1]) by mail.ijs.si (Postfix) with ESMTP id 40sGCV73Rfz6y; Thu, 24 May 2018 19:12:22 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= user-agent:message-id:references:in-reply-to:organization :subject:subject:from:from:date:date:content-transfer-encoding :content-type:content-type:mime-version:received:received :received:received; s=jakla4; t=1527181938; x=1529773939; bh=JS4 FOnif74HRJuWy47rgz0M8DPUqzkLTf+qrFZ+6nFI=; b=J3P/KJGBLBceuTMZHr/ U8qbNQuH4QCSqKv7RElvsrbKlc4DoQn/Is5Jl735jKNG1ykww2PSFqJ73YggS+Oo VGVVzOBbwg0yGHEn/PLiQ2jMtVkT4nLXWNjlhLEbiDL44BFHG8C1EE2guJA5r5g7 IM8iHNX2YPEp35YmCj6HAMyc= X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10026) with LMTP id jc3Qk_X2qXsM; Thu, 24 May 2018 19:12:18 +0200 (CEST) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP id 40sGCM15BZz6H; Thu, 24 May 2018 19:12:15 +0200 (CEST) Received: from nabiralnik.ijs.si (nabiralnik.ijs.si [IPv6:2001:1470:ff80::80:16]) by mildred.ijs.si (Postfix) with ESMTP id 40sGCM07dHz1PN; Thu, 24 May 2018 19:12:15 +0200 (CEST) Received: from neli.ijs.si (2001:1470:ff80:88:21c:c0ff:feb1:8c91) by nabiralnik.ijs.si with HTTP (HTTP/1.1 POST); Thu, 24 May 2018 19:12:15 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 24 May 2018 19:12:15 +0200 From: Mark Martinec To: freebsd-stable@freebsd.org Cc: Mark Johnston , owner-freebsd-stable@freebsd.org Subject: Re: The 11.1-RC3 can only boot and attach disks in "Safe mode", otherwise gets stuck attaching Organization: Jozef Stefan Institute In-Reply-To: <81295bcacd7c44813de8d346c88cbb65@ijs.si> References: <20170717232434.GB21048@wkstn-mjohnston.west.isilon.com> <9b3563aae75aa954d7fe31ffe25e1d29@ijs.si> <20170720000325.GB9198@wkstn-mjohnston.west.isilon.com> <81295bcacd7c44813de8d346c88cbb65@ijs.si> Message-ID: <9648ad1b41cf184dbcce788a014cf4fa@ijs.si> X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.3.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 May 2018 17:12:26 -0000 Just a short report to a thread I started when 11.1 came out. This machine would stall in a busy loop while attaching disks during boot. Rebuilding a kernel with EARLY_AP_STARTUP disabled avoided the problem. This was a situation through the whole 11.1 life cycle (i.e. patch releases did not help). Today I have upgraded this host to 11.2-BETA2, and it is no longer necessary to disable EARLY_AP_STARTUP. Good, thanks! Mark > 2017-07-20 02:03, Mark Johnston wrote: >> One thing to try at this point would be to disable EARLY_AP_STARTUP in >> the kernel config. That is, take a configuration with which you're >> able >> to reproduce the hang during boot, and remove "options >> EARLY_AP_STARTUP". > > 2017-07-20 15:45, Mark Martinec wrote: > Done. And it avoids the problem altogether! Thanks. > Tried a reboot several times and it succeeds every time. > > Here is all that I had in a config file for building a kernel, > i.e. I took away the 'options DDB' which also seemingly avoided > the problem: > include GENERIC > ident NELI > nooptions EARLY_AP_STARTUP > >> This feature has a fairly large impact on the bootup process and has >> had a few problems that manifested as hangs during boot. There was at >> least one other case where an innocuous change to the kernel >> configuration "fixed" the problem by introducing some second-order >> effect (causing kernel threads to be scheduled in a different >> order, for instance). [...]