From owner-freebsd-current@freebsd.org Tue Nov 29 23:24: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 79C29C5C7AC for ; Tue, 29 Nov 2016 23:24:06 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5B2091410 for ; Tue, 29 Nov 2016 23:24:06 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by mail.baldwin.cx (Postfix) with ESMTPSA id D133E10AA27; Tue, 29 Nov 2016 18:24:03 -0500 (EST) From: John Baldwin To: "Julian H. Stacey" Cc: freebsd-current@freebsd.org Subject: Re: boot fails on Table SSDT at 0x... Date: Tue, 29 Nov 2016 15:24 -0800 Message-ID: <4385251.XWNjh4rSHY@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.0-PRERELEASE; KDE/4.14.10; amd64; ; ) In-Reply-To: <201611292249.uATMnWGj087462@fire.js.berklix.net> References: <201611292249.uATMnWGj087462@fire.js.berklix.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Tue, 29 Nov 2016 18:24:03 -0500 (EST) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean 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: Tue, 29 Nov 2016 23:24:06 -0000 On Tuesday, November 29, 2016 11:49:32 PM Julian H. Stacey wrote: > > Thanks for the Q. John, > > It hangs. > > I'm refining down which line of the custom config triggers the hang > > & will post when Ive found it. > > Sorry, after lots of kernel variants & reboots I failed to get it > to hang on boot. Eventually with same src/ I reverted to original > bad config. Even that wouldn't hang on boot, so I've given up ! :-/ Perhaps a stale .o wasn't being recompiled? None of your kernel option changes seemed to be related, so I suspect it was something oddball like that. -- John Baldwin