Date: Tue, 14 Aug 2018 21:06:28 -0700 From: Pete Wright <pete@nomadlogic.org> To: Kyle Evans <kevans@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection Message-ID: <adf110c6-1206-c5d7-ca53-a084e711cbf5@nomadlogic.org> In-Reply-To: <CACNAnaGDhxuUjOc-uD_X8JyQjMS2sXQXsmvvKhG0afGzMZnpFg@mail.gmail.com> References: <b0f55e2f-8764-7407-4f21-bc738f91619c@nomadlogic.org> <CACNAnaHKVwcHZc-n%2B1Y=e%2BnqPsMiX07xbH4za-TL4px4hLxKkg@mail.gmail.com> <ba2e52df-e60c-9e12-337c-2f36bfb6779f@nomadlogic.org> <CACNAnaEFp_yRF-QWF4qiZ_s3tq3qpvfY5%2BzjYLuAR3TCkN-ubQ@mail.gmail.com> <68a10054-44a6-c363-8e05-01aa7f8201c3@nomadlogic.org> <CACNAnaGDhxuUjOc-uD_X8JyQjMS2sXQXsmvvKhG0afGzMZnpFg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -p -- Pete Wright pete@nomadlogic.org @nomadlogicLA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?adf110c6-1206-c5d7-ca53-a084e711cbf5>