Received: by 10.223.185.116 with SMTP id b49csp6527324wrg; Thu, 8 Mar 2018 08:52:51 -0800 (PST) X-Google-Smtp-Source: AG47ELv66/+QICk+4FUSWbtGbDWN5gJQ/YBmEEWjqGbcDr+4yPBd30+4TN/uXwEOugcGC62t+aVF X-Received: by 10.99.180.3 with SMTP id s3mr21495868pgf.258.1520527971710; Thu, 08 Mar 2018 08:52:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520527971; cv=none; d=google.com; s=arc-20160816; b=g7Yx4vr2pFABspYnRuYoj4OcHC8vSpwY67Y/5N5zwlc9IUmDHswxOqv21FMsW0UqV/ heo71dli4dnzQWWVmF4l5usl7+ilXyABY4TFai45R6N6VJarCBIl4ZGq+ZY0/+rBBUBa q2HVPfF4u6jI/w4VkHVgb9uNpd8lmaC52quS+cY9TQLC8qtqUPd1vRSf6U2iwQwVxe4B X+lowh1Fa/yBkiaQFo+V2A9Tl3XA5gYtlWclCP/yud1Ki0ZWPpRkuVO1gGDQqoSR0l+v 1x1n6Ckt6NJrqcbVJfrZH8VUI3A3iveCn9m3AN8SrGr+Hd+jcgVF5qifZ13fHTxPO5z8 5mZA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:references:to:subject:from:arc-authentication-results; bh=8+1Zan42X9wNw98HJmUW7Wa4vMTlheOH3MWhkHh5yiw=; b=SILfR1/Nl7beN8lelCPsoI6NNpAn/OngdPkT4l6JPgLOOY35gcB1+Al1KuC1XmglS6 ko/AM1BJI+JFIauWGSblBrwBK444MMwtW87ChvTjT7IKvONPn2K5ljWa4yNMZayUWK7+ 9rNVfA0M868k9mz98HkiYEXdis1NxLV8z55oCHlbh9m4vdAejoSG4zKdXdew7ligV+jM LYvszJmXA5Rw6G7a+ei00XV/HHPsjhKQD2y1yx3IyeRk9MuTytPY6R5L9peqkMDbnwzw UN43CC6YOowPbBBMoBcveNpGkfHiQaOMuFbjrGBvxIiUyptk2QGADBAbhbHY/fU+sJNg Ts/Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p25si13109677pgn.151.2018.03.08.08.52.34; Thu, 08 Mar 2018 08:52:51 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934120AbeCHQu2 (ORCPT + 99 others); Thu, 8 Mar 2018 11:50:28 -0500 Received: from mail-wm0-f43.google.com ([74.125.82.43]:53978 "EHLO mail-wm0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752133AbeCHQu0 (ORCPT ); Thu, 8 Mar 2018 11:50:26 -0500 Received: by mail-wm0-f43.google.com with SMTP id e194so525930wmd.3 for ; Thu, 08 Mar 2018 08:50:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=8+1Zan42X9wNw98HJmUW7Wa4vMTlheOH3MWhkHh5yiw=; b=fz+yVmlWI0gIZYhY7V3jsXEmLRDce7RwFA9OX/wJnf4PSDpqh97W7vn9RJaMKN/90r PRSw8usVbCHVoghrGeLxpG22s9pFE90gUu4xmmuXHL2vAoRnnlwJI37E7mis8TRQt8bj Bjun4uhEGb6C7u9OWT5u8iR0U3+5gykCjT8KMzq1aShEX7IpD4McRMxerbdDii1z4vxZ XUNMBTWSGjeSwJWMY8t4iL0MN3C4LmOMyk42Dh1xJL2Tc/xhmnrt85/2ExMAoE0VbQus 4gdgr13gjR6mTV6uaGVbjVeFr8S46Py9R9JXC0sLRu0H1JZoxgw7g7njbOsj1V/Q01mt HibQ== X-Gm-Message-State: APf1xPC0HJlxALljn4gkbJlq4KQAxymAWg14rq+Te+LS+69fItXpSdD8 mFLs+vMTk/saUOD1w2PPzxyhJIGibm4= X-Received: by 10.80.164.216 with SMTP id x24mr32753761edb.19.1520527824754; Thu, 08 Mar 2018 08:50:24 -0800 (PST) Received: from shalem.localdomain (546A5441.cm-12-3b.dynamic.ziggo.nl. [84.106.84.65]) by smtp.gmail.com with ESMTPSA id h9sm15064563edi.79.2018.03.08.08.50.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 08 Mar 2018 08:50:24 -0800 (PST) From: Hans de Goede Subject: Re: Regression from efi: call get_event_log before ExitBootServices To: Javier Martinez Canillas , Jeremy Cline , Thiebaud Weksteen , Jarkko Sakkinen , linux-efi@vger.kernel.org, linux-integrity@vger.kernel.org, tpmdd-devel@lists.sourceforge.net, Linux Kernel Mailing List References: <01000161fc0b4755-df0621f4-ab5d-479a-b425-adf98427a308-000000@email.amazonses.com> Message-ID: Date: Thu, 8 Mar 2018 17:50:23 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 07-03-18 12:34, Javier Martinez Canillas wrote: > On 03/07/2018 12:10 PM, Hans de Goede wrote: >> Both according to the BIOS and to the /sys/class/tpm/tpm0/device/description >> file it is a TPM 2.0. >> > > I see, so you can choose enabling the TPM 1.2 or TPM 2.0 device? At least that's > the case on my X1 Carbon laptop. I've both a hardware TPM 1.2 and a firmware TPM > 2.0 that's implemented as an Intel ME application (AFAIU). This device only has the firmware TPM 2.0 implementation. >> I'm actually amazed that this machine has a TPM at all, a quick internet >> search shows that it is a software implemented TPM running as part of the >> TXE firmware. >> > > A quick search suggests that it comes with Windows 10? Yes, it comes with Windows 10. >>> For start, can you please check if you can boot a v4.16-rcX kernel with the >>> TPM device enabled? That way we will know that at least that it consistently >>> fails on this machine and is not and isolated issue. >> >> I just tried and v4.16-rc3 boots fine for me, repeatedly. >> > > That's an interesting data point. > >> I guess Jeremy's model may actually have something in the TPM log > > I don't think so. The UEFI firmware already does some measurements and also > does shim. So you *should* have some logs. > >> while my TPM log is empty... Is there anyway to make sure the TPM >> log has some info to retreive? >> > > Are you also able to read the TPM event logs? > > $ hexdump /sys/kernel/security/tpm0/binary_bios_measurements Yes for me that outputs a lot of hex :) > The UEFI firmware does some measurements and so does shim. So you should > have some event logs. What version of shim are you using? And also would > be good to know if it's the same shim version that Jeremy is using. That is a very good question, I'm using: shim-ia32-13-0.7.x86_64, which is the last version for F27 AFAICT. But Jeremy's tablet might very well be not using the shim at all, as I manually installed Fedora 25 on the tablet he now has, before Fedora supported machines with 32 bit EFI. I then later did a "dnf distro-sync" to Fedora-27. Jeremy might also very well still be booting using a grub binary I build manually back then, without any shim being involved. Jeremy what does efibootmgr -v output on your device ? Regards, Hans