From owner-freebsd-current@freebsd.org Wed Aug 29 16:17:12 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 6FC74108E2B8 for ; Wed, 29 Aug 2018 16:17:12 +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 DCBA8730FD; Wed, 29 Aug 2018 16:17:11 +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 1191E20A70; Wed, 29 Aug 2018 12:17:11 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 29 Aug 2018 12:17:11 -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=W5o2U5JCdB6/OZ7sD73/zyluDWLeM 8L9xJycG7T57Q8=; b=aaj3NbwXTqqFHcrGNBAfc5U0K6PdIuQCT60zzogQQES/L fgzIrWwLzZocffSMgq53n7qisePjHmdc824QwgttPUp2wM0eFAioiam+Yv1npDHQ uJTNvEe7xdPxx8SP5mBCASD6vmDw20qgfgz+sf0ZZmmyF74Ip0ja7OG8JHyolp2p jgpH/V4Mp8+33QbM+7Ic1WveogQ+48TuByW47qBFxC40Lz8hfdqDF+CuImYbGMUt 1zoV6KWbpNfGV5LC4QaR4zdQpLlq8p4yeVt4kQt5dzLQ+4caXQddHwMNvQWElwN4 QZZKnd5T3ZqwNyVqMlctFKCPTWtjHAe0VELywN5Ig== 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=W5o2U5 JCdB6/OZ7sD73/zyluDWLeM8L9xJycG7T57Q8=; b=P0O+A5VxeJqneWLUlss0nA yHd59AHEEuBaNcC43oCyrkZw66iq17Hd/OQrrudEO/4dHfRPPv2PZpJ6OGtcK3li MzNy1XDVpuudYpivFdyQejaF6tiD6fhBhHADR7z9WwwFJtnikO2jCPIplItDdfL7 OZqO9QgSTRBR0iRW0YUoLgChJmdJIjJNH/LZ+BM7RC4x/jY4vk+8tqrHuNfKrZk7 Omce2GDdibA8w9Ib7Mb4Q9FnPSYQf8dIlSIuJB7Gx92lfzFs+Ty811lhXKQBkV1c XWBfqfvo9YzZnMrebWt6eFdkTEI0/a8BL97kwfECx7odaFSHAIrg5mD9er1yjKWQ == 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 2417A10292; Wed, 29 Aug 2018 12:17:08 -0400 (EDT) Subject: Re: r336921 broke booting on MBP 2017, EFIRT related To: Konstantin Belousov , Kyle Evans Cc: FreeBSD Current References: <499f05f4-4fab-9b31-5d37-83ecb554013c@yuripv.net> <20180829102727.GD2340@kib.kiev.ua> <20180829141914.GG2340@kib.kiev.ua> From: Yuri Pankov Message-ID: Date: Wed, 29 Aug 2018 19:17:07 +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: <20180829141914.GG2340@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 16:17:12 -0000 Konstantin Belousov wrote: > On Wed, Aug 29, 2018 at 09:12:37AM -0500, Kyle Evans wrote: >> I guess this patch might do it: >> https://people.freebsd.org/~kevans/efi-bootmap.diff >> >> Linux commit messages depict a tale in which they used to also only >> map RUNTIME entries, but they were effectively forced to back down on >> that because of buggy firmware that does exactly what you've described >> and they later reintroduced the restrictive mapping for i386-only >> where they'd not found such bugs. > > Orthogonal to the loader patch, please try the following. Even better, > try this with the stock loader. > > You need to remove efirt from the kernel config for now, instead load > efirt.ko, perhaps after the system booted into single user. I am interested > if the panic goes away. You should see some interesting message from > kernel about EFI realtime clock. > > If you have any binary modules like nvidia or vbox, do not load them > with the patched kernel. Done, getting exactly the same fault without any new messages printed (made sure I'm using the updated efirt using `nm | grep efirt_fault`).