From owner-freebsd-current@freebsd.org Wed Aug 29 13:25:27 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 211A1108A3EE for ; Wed, 29 Aug 2018 13:25:27 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 C79688CEBD for ; Wed, 29 Aug 2018 13:25:26 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lj1-f178.google.com (mail-lj1-f178.google.com [209.85.208.178]) (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 6553514626 for ; Wed, 29 Aug 2018 13:25:26 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lj1-f178.google.com with SMTP id f1-v6so4359343ljc.9 for ; Wed, 29 Aug 2018 06:25:26 -0700 (PDT) X-Gm-Message-State: APzg51BrmcWq5qxFqeAGn01q85kKeDW8ZJXc6xOkO06vEpXx05Gpk4TP bIaZagq8Z87jgTLsR77hhPGDLXuTfNf4xAFt/1c= X-Google-Smtp-Source: ANB0VdYfi4L6koX4OSjiCMlmtlBxehjxvniCndtYyQBzEZw8l1LM0iFu7IzmgbomTBs8d8M8MnALrDtPc2v8X1U/BVU= X-Received: by 2002:a2e:144c:: with SMTP id 12-v6mr4552930lju.122.1535549123991; Wed, 29 Aug 2018 06:25:23 -0700 (PDT) MIME-Version: 1.0 References: <499f05f4-4fab-9b31-5d37-83ecb554013c@yuripv.net> <23535142-fcd6-a37f-c1d6-70ae68b3872f@gwdg.de> In-Reply-To: <23535142-fcd6-a37f-c1d6-70ae68b3872f@gwdg.de> From: Kyle Evans Date: Wed, 29 Aug 2018 08:25:11 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: r336921 broke booting on MBP 2017, EFIRT related To: rhurlin@gwdg.de Cc: yuripv@yuripv.net, 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, 29 Aug 2018 13:25:27 -0000 On Wed, Aug 29, 2018 at 8:20 AM Rainer Hurling wrote: > > Am 29.08.18 um 11:37 schrieb Yuri Pankov: > > Hi, > > > > I've noticed that all recent snapshots (ALPHA3, ALPHA2, ALPHA1, > > 20180802) fail to boot on MBP 2017: > > > > kbd0 at kbdmux0 > > netmap: loaded module > > nexus0 > > > > Fatal trap 12: page fault while in kernel mode > > cpuid = 2: apic id = 02 > > fault virtual address = 0x74c64a50 > > fault code = supervisor read data, page not present > > instruction pointer = 0x20: 0x7abece31 > > stack pointer = 0x28: 0xffffffff82b2f7c0 > > frame pointer = 0x28: 0xffffffff82b2f810 > > code segment = base 0x0, limit 0xfffff, type 0x1b > > = DPL 0, pres 1, long 1, def32 0, gran 1 > > processor eflags = interrupt enabled, resume, IOPL = 0 > > current process = 0 (swapper) > > [ thread pid 0 tid 100000 ] > > Stopped at 0x7abece31: calll *0x18(%rax) > > db> > > > > Sadly, there's no support for internal keyboard yet (it's connected via > > SPI), and external USB one stops working. > > > > A (not so quick) bisect is pointing at r336921, which enabled EFIRT. > > > > Some questions here: > > - is this something that can/should be fixed? > > - can we print some "enabling EFIRT" message to the console to make > > guesses about the problem source a bit easier? > > > I have almost exactly the same trap on a DELL Latitude E6520 with ALPHA3. Hmm... that's a good data point. I might have a nearby Dell on-hand with same firmware to reproduce with, then. > Only _with_ 'OPTIONS EFIRT' enabled in the kernel _and_ deactivating it > via efi.rt.disabled=1 in /boot/loader.conf, it works for me. > > An oddity is, that the spelling of the loader tuneable has to be > efi.rt.disabled, not efi.rt_disabled (note the dot instead of an > underscore!). The one with the underscore, as mentioned in UPDATING, > does not work for me. Isn't this a typo somewhere in the code? > The UPDATING entry was later amended to reflect the new spelling ("efi.rt.disabled") Thanks, Kyle Evans