From owner-freebsd-current@freebsd.org Wed Aug 15 04:19:37 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 F227F1071D43 for ; Wed, 15 Aug 2018 04:19:36 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 5117077381; Wed, 15 Aug 2018 04:19:36 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.190] (cpe-23-243-162-239.socal.res.rr.com [23.243.162.239]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id e1b2aa38 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Tue, 14 Aug 2018 21:19:34 -0700 (PDT) Subject: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection From: Pete Wright To: Kyle Evans Cc: FreeBSD Current References: <68a10054-44a6-c363-8e05-01aa7f8201c3@nomadlogic.org> Message-ID: <337febb2-1c14-f679-1dd4-5d1c9ad73be1@nomadlogic.org> Date: Tue, 14 Aug 2018 21:19:30 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US 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:19:37 -0000 On 8/14/18 9:06 PM, Pete Wright wrote: > > On 8/14/18 9:01 PM, Kyle Evans wrote: >> >>>> 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? > > sure i can give that a spin. > > >>> 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. > > so i have reverted back to this git hash: > 90f37b39e4a > > https://github.com/freebsd/freebsd/commit/90f37b39e4ad481d3e5a059123f7d68ac153f0c5 > > > and i can confirm that i am able to boot with EFI enabled, do not > experience any issues bringing up my iwn interface and HDMI is > recognized according to xrandr.  so that solves my immediate problem! > :)  interestingly enough i still see the ACPI errors I reported > earlier, but perhaps that is a red herring. > > i'll go back to the tip of master and apply kib's patch and see how it > goes. > ok great (thank's ccache for making buildkernel fast :) ) so after applying the patch from kib i have the same behavior as i'm seeing on git hash 90f37b39e4a. i.e. boots fine with UEFI enabled, iwn interface comes up, HDMI output is detected by xrandr and interesting ACPI warning messages. i'll dogfood this patch tomorrow when i get into the office and validate connecting my HDMI display works as expected and will report any other issues i bump into. thanks for your help Kyle!  I didn't think to test kib's patch as i was assuming my issue was related to the ACPI errors, but this seems to get me back to where i need to be to work tomorrow so i'm good to go :) -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA