From owner-freebsd-current@freebsd.org Wed Aug 29 11:43:54 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 EB38D1086412 for ; Wed, 29 Aug 2018 11:43:53 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 9498788CF9 for ; Wed, 29 Aug 2018 11:43:53 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 1730F22077; Wed, 29 Aug 2018 07:43:53 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 29 Aug 2018 07:43:53 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=awYSUCje6aC11l06MVJmfJjvbJABm cT3o4ga90DSc+8=; b=R1NRLbwQ+obbAsv5mV7dxXSikq17ZreC6v75U8Bs2/WyA I2dbVP2x13x6fhXmbUsBrpO/Z7bsBrswxrc5GqPT2M9aNAHJXrCBrmf9AMWpAYu2 y5n3G+Ys3dgHwZMl78NA2OTgBUxOu6HLpf0UbtinrTLU5gZ+s5dzonIDxJ8GKy+H cgMCvz7TBN3oy16zkoil/SCojwprp0fBK22S17pawORyf3cRxjDW04yqDOxH8GUH kyadYj0gPeM5HSzq9w3Wpls9RhMRHVaOdfB3vYIYA0iv2Oe/sSOisPu9C+tFmwve E1RztBCbfHuXHElHHwhwB9MQelYnwtq5Z94d4kLNg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=awYSUC je6aC11l06MVJmfJjvbJABmcT3o4ga90DSc+8=; b=PhL1QmpdBM6fS4ZLqcvG2w hWOgnBvtz2BuKivKbvPb/Abe8iHT8GNolEZq1XkH2OrqYfhrfwhBZjZrkKgizec3 v3QnRTrWweYyBiGIa3R/Rr6bogt1oO8o+G75xD2M4vfBelt8tYUEaycvFRecVXqB yitYspFwWRgI34Mmj8lRGY9hAbv/s5kfHnVhz/exFKtiM3OYX8AZTvx2he0vhBVX 9w4VM/MemDcuPjVRxVJt7RCnhv1UIES7Lyf/eFXBGyb1dCLujP8AoTQDApx/m2sj xlVcOIRItKtH188XCWG3PuMkmSzZXnpd+6xPd2WYRSByAkYv9yHgsGMRq4BWk9rQ == X-ME-Proxy: X-ME-Sender: Received: from [192.168.1.2] (unknown [178.34.99.43]) by mail.messagingengine.com (Postfix) with ESMTPA id AB42B1029B; Wed, 29 Aug 2018 07:43:50 -0400 (EDT) Subject: Re: r336921 broke booting on MBP 2017, EFIRT related To: Konstantin Belousov Cc: freebsd-current References: <499f05f4-4fab-9b31-5d37-83ecb554013c@yuripv.net> <20180829102727.GD2340@kib.kiev.ua> From: Yuri Pankov Message-ID: Date: Wed, 29 Aug 2018 14:43:49 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <20180829102727.GD2340@kib.kiev.ua> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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 11:43:54 -0000 Konstantin Belousov wrote: > On Wed, Aug 29, 2018 at 12:37:52PM +0300, Yuri Pankov wrote: >> 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? > > It is not in 'enabling'. Looking at the faulting VA, I believe that > it occurs inside the BIOS code. > > Disable efirt by removing the kernel option, then try to load the module > at runtime. Does it still fault ? Also, get the efi mem map for the > machine and look at which region the faulting address and the faulting > instruction belong. kldload'ing the efirt module gets the same fault. Several top lines of backtrace: kernphys() at 0x7abece31 efi_get_time() at efi_get_time+0xd9 efirtc_probe() at efirtc_probe+0x17