Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 14 Aug 2018 23:01:57 -0500
From:      Kyle Evans <kevans@freebsd.org>
To:        Pete Wright <pete@nomadlogic.org>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection
Message-ID:  <CACNAnaGDhxuUjOc-uD_X8JyQjMS2sXQXsmvvKhG0afGzMZnpFg@mail.gmail.com>
In-Reply-To: <68a10054-44a6-c363-8e05-01aa7f8201c3@nomadlogic.org>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 14, 2018 at 10:56 PM, Pete Wright <pete@nomadlogic.org> wrote:
>
> On 8/14/18 8:45 PM, Kyle Evans wrote:
>>
>> On Tue, Aug 14, 2018 at 10:41 PM, Pete Wright <pete@nomadlogic.org> wrote:
>>>
>>> On 8/14/18 6:13 PM, Kyle Evans wrote:
>>>>
>>>> On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright <pete@nomadlogic.org>
>>>> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaGDhxuUjOc-uD_X8JyQjMS2sXQXsmvvKhG0afGzMZnpFg>