From owner-freebsd-current@freebsd.org Wed Mar 8 13:17:44 2017 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 D8F2ACFB55C for ; Wed, 8 Mar 2017 13:17:44 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A1C6D121F; Wed, 8 Mar 2017 13:17:44 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject; s=201508; t= 1488979062; bh=h47mD+TTzilunOqFS8g4nSLs579NWl0dO1q/p8t3XN8=; b=l J0sBA2FXq6IW+ZPFKhdqvv0eVMXZV78iooC4PeTBwje2YQxWT6R5Q048DvL9Nt+I P2t/rljdz5MSxqaUXXkvixQ/VQMSRyERL5d46js8BhXwJ9F0m5BSBXE166i9pwBy B5LqHYfL77wNrOM4U6YSu1T5iBWPNtqnZhydeV4Azk= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 5EEB0235C9; Wed, 8 Mar 2017 08:17:42 -0500 (EST) Subject: Re: start-up failure at SVN r314889 To: Andriy Gapon , freebsd-current References: <234d1d89-71e5-e6ca-ff2e-188a9ca2bdb2@FreeBSD.org> From: Michael Butler Openpgp: id=6F63E6399DCC8E3E94D60F0642FF6BAE0442D492 Message-ID: <5d58acbf-23d5-3bc7-c102-1c6d5859b3ef@protected-networks.net> Date: Wed, 8 Mar 2017 08:17:42 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: <234d1d89-71e5-e6ca-ff2e-188a9ca2bdb2@FreeBSD.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit 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, 08 Mar 2017 13:17:44 -0000 On 03/08/17 08:12, Andriy Gapon wrote: > On 08/03/2017 14:55, Michael Butler wrote: >> My laptop usually starts like this .. >> >> FreeBSD 12.0-CURRENT #21 r314812M: Mon Mar 6 19:34:51 EST 2017 >> imb@toshi.auburn.protected-networks.net:/usr/obj/usr/src/sys/TOSHI amd64 >> FreeBSD clang version 4.0.0 (branches/release_40 296509) (based on LLVM >> 4.0.0) >> VT(vga): resolution 640x480 >> info: [drm] Initialized drm 1.1.0 20060810 >> CPU: Intel(R) Core(TM)2 CPU T7600 @ 2.33GHz (2327.56-MHz >> K8-class CPU) >> [ .. ] >> >> This morning, I get this :-( >> >> FreeBSD 12.0-CURRENT #27 r314889M: Tue Mar 7 19:55:25 EST 2017 >> imb@toshi.auburn.protected-networks.net:/usr/obj/usr/src/sys/TOSHI >> FreeBSD clang version 4.0.0 (branches/release_40 296509) (based on LLVM >> 4.0.0) >> VT(vga): resolution 640x480 >> panic: kthread_add called too soon >> [ .. ] >> >> Any thoughts? > > Were messages replaced by the second '[..]' really so useless? Just the CPU number, then it halts :-( With no log, I typed what I could remember. With a verbose start-up, I can see that it gets through parsing the ACPI tables but fails shortly after. When I get home this evening, I'll take a screenshot, imb