From owner-freebsd-current@freebsd.org Wed Aug 15 04:02:20 2018 Return-Path: Delivered-To: freebsd-current@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 856651071530 for ; Wed, 15 Aug 2018 04:02:20 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 336D076C39 for ; Wed, 15 Aug 2018 04:02:20 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lf1-f54.google.com (mail-lf1-f54.google.com [209.85.167.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id C82D71101C for ; Wed, 15 Aug 2018 04:02:19 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lf1-f54.google.com with SMTP id n96-v6so8069lfi.1 for ; Tue, 14 Aug 2018 21:02:19 -0700 (PDT) X-Gm-Message-State: AOUpUlH2hmvNF8n/gkvE5hXtR3GwKYUqWCm0gX8YXw8Gy2QtzAKd4fiZ N9GX4CXmadFGdo4syDnco9jXdU4e6X+l9R/Ksfw= X-Google-Smtp-Source: AA+uWPzrF2G2DnNP5EmZAK4xb8bfY+4OxYLZZmSCwseCJEXhzJ4uuXAO3WRDrm8w2rbdzXF9y8tmQCOZXNWh3Bqlgrw= X-Received: by 2002:a19:2194:: with SMTP id h142-v6mr14858340lfh.75.1534305738460; Tue, 14 Aug 2018 21:02:18 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:5742:0:0:0:0:0 with HTTP; Tue, 14 Aug 2018 21:01:57 -0700 (PDT) In-Reply-To: <68a10054-44a6-c363-8e05-01aa7f8201c3@nomadlogic.org> References: <68a10054-44a6-c363-8e05-01aa7f8201c3@nomadlogic.org> From: Kyle Evans Date: Tue, 14 Aug 2018 23:01:57 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection To: Pete Wright Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 15 Aug 2018 04:02:20 -0000 On Tue, Aug 14, 2018 at 10:56 PM, Pete Wright wrote: > > On 8/14/18 8:45 PM, Kyle Evans wrote: >> >> On Tue, Aug 14, 2018 at 10:41 PM, Pete Wright wrote: >>> >>> On 8/14/18 6:13 PM, Kyle Evans wrote: >>>> >>>> On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright >>>> wrote: >>>>> >>>>> i also attempted to boot using UEFI but the system hangs very early in >>>>> the >>>>> boot process. i have reverted to legacy mode for now so that i can >>>>> work, >>>>> but am keen to test out any patches or do any other debugging that is >>>>> needed. >>>> >>>> Hi Pete, >>>> >>>> Where in the process does it hang with UEFI? I can't help much with >>>> any of your other problems, but I am curious about this one. =) >>> >>> sure thing - the last several lines are: >>> >>> random: fast provider: "Intel Secure Key RNG" >>> kbd1 at kbdmux0 >>> netmap: loaded module >>> nexus0 >>> >>> at this point it hangs. let me know if you want me to try booting with >>> verbose output to dmesg or something. >>> >> Are you running GENERIC, or custom config? Any modules loaded? > > > > this is a GENERIC kernel using ZFS as well as GELI full disk encryption. > Good to know, thanks! > >> >> I'm curious if you've been bitten somehow by recently enabling EFIRT >> in GENERIC. Can you try setting efi.rt.disabled=1 at loader prompt and >> see where that gets you? > > > i did attempt to set that in loader.conf - and it progressed farther but > kernel panic'd when trying to bring up my iwn wireless interface. > Interesting... out of side curiosity, what does this panic look like? Can you also try running a kernel >= r337773 with kib's patch from [1] applied to make sure this the EFI part of this isn't already solved? > > i'm building an older version in an attempt to bisect this issue (i have a > skylake system running a checkout from monday without issues, so testing > that now). if i am still running into problems i'll boot with > efi.rt.disabled=1 and will post the gdb panic string here. > Excellent. > -pete > Thanks, Kyle Evans [1] https://lists.freebsd.org/pipermail/freebsd-current/2018-August/070660.html