From owner-freebsd-current@freebsd.org Wed Dec 14 20:08:06 2016 Return-Path: Delivered-To: freebsd-current@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 1BEA1C80C77 for ; Wed, 14 Dec 2016 20:08:06 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qk0-x243.google.com (mail-qk0-x243.google.com [IPv6:2607:f8b0:400d:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CA653A0; Wed, 14 Dec 2016 20:08:05 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qk0-x243.google.com with SMTP id x190so4584457qkb.0; Wed, 14 Dec 2016 12:08:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=4Jrdl1wRxDUiNYGRbpeTEyxzXlyYvCCSUEbHYfFpACw=; b=FP4oGVmCmYC8D7HMNyYda4Gz06FT/59/ypBg2cua2YKWcpdBLiyTU77EYD63doB/0e eEIq6wxIG9K4JRIlpHIo6BYW5iAHjRAPRyn1WYmDshC8p88xFnB8bsSS864ZnmQcV1KC trYi8xm8pQcyXp/JvQ78ghWeBP6BjYPZ+Q1YXHexTa3d4t/89FDsT57ysQj2kCRFw6rn 2CxuOovhkKTQZ9VSFn0G6+BFcS+6fKzxVRaMYO4LSLTVGMc28CI9Vscgoix9Ys1gv8Hp ZD+Q350MQACDe14WS/UqJ9UZaE0zP+y1QVrmUWASFuWp1ai8zGJ+vatmASREzZA8rBfy jSpw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=4Jrdl1wRxDUiNYGRbpeTEyxzXlyYvCCSUEbHYfFpACw=; b=Wn/b8NLcVLUculshrdUODosKP9otboTiVSlHRQkVt7Coi7rcRNbvxOJnxa7cA5BeHn 4hAt8tzvBmh1tUvfr5Cx2NRb3Rail+qXXJKOlDeijS1dlY6r5EnGZNNn25LkOfZ55kx1 8QKtLPYzQjU8DtBWvGhXGPBzgaQX/+CTT5SzxMv/J4gA5+gvfVd2RX4CZdQCYIDAgBV6 dHTOtUJshrA7HnzTKKCcuIua6HltS3/Z5HLdk4a36PjbbCziEoAV/LRcPS0wNgGaA8/g ilBEVvyOlDlSceDvawXMfz1BHxwJFCwuEeq/xIUsvS7DHSNeWko54zSzkbMSCmfByby3 i8rA== X-Gm-Message-State: AKaTC02kHu9tynBHiZfLM4TBRB4gwYLLvDYSm6FtJ2pzQo5b1cVdZZdyaZR+JGIlcm0c5w== X-Received: by 10.55.69.67 with SMTP id s64mr30117033qka.102.1481746085002; Wed, 14 Dec 2016 12:08:05 -0800 (PST) Received: from wkstn-mjohnston.west.isilon.com (c-76-104-201-218.hsd1.wa.comcast.net. [76.104.201.218]) by smtp.gmail.com with ESMTPSA id r8sm32454601qtc.32.2016.12.14.12.08.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Dec 2016 12:08:04 -0800 (PST) Sender: Mark Johnston Date: Wed, 14 Dec 2016 12:14:16 -0800 From: Mark Johnston To: kargl@uw.edu Cc: freebsd-current@freebsd.org, kib@freebsd.org Subject: Re: Revision 309657 to stack_machdep.c renders unbootable system Message-ID: <20161214201416.GA64767@wkstn-mjohnston.west.isilon.com> References: <20161214194848.GA881@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161214194848.GA881@troutmask.apl.washington.edu> User-Agent: Mutt/1.7.1 (2016-10-04) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2016 20:08:06 -0000 On Wed, Dec 14, 2016 at 11:49:26AM -0800, Steven G. Kargl wrote: > Well, after 3 days of bisection, I finally found the commit > that renders my system unbootable. The system does not panic. > It simply gets stuck in some state. Nonfunctional keyboard, > so can't break into debugger. No serial console available. > The verbose dmesg.boot for a working kernel from revision > 309656 is at > > http://troutmask.apl.washington.edu/~kargl/freebsd/dmesg.309656.txt > > The kernel config file is at > > http://troutmask.apl.washington.edu/~kargl/freebsd/SPEW.txt > > In looking at /usr/src/UPDATING, there is no warning that one > can create a boat anchor by upgrading to 309657. If compiling > a kernel with 'options DDB' is no longer supported, this should > be stated in UPDATING. Or, UPDATING should state that 'options > DDB' requires 'options STACK'. Or, 'options DDB' should simply > to the right thing and pull in whatever 'option STACK' does. It is supported though - the point of that change was to fix a problem that occurred when DDB is configured but STACK isn't. While testing I tried every combination of the two options, and I just tried and successfully booted a kernel with DDB and !STACK. Does the kernel boot successfully if STACK is added to your configuration?