Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp11021860imu; Mon, 31 Dec 2018 11:12:41 -0800 (PST) X-Google-Smtp-Source: AFSGD/V9pkKlIzYQ+COC53esN9vrbYlbTM4QUWwkNZBTD3Ly6MP3aphDi/e6fWJkmAUJqhxoVeq4 X-Received: by 2002:a62:546:: with SMTP id 67mr38182385pff.99.1546283561457; Mon, 31 Dec 2018 11:12:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1546283561; cv=none; d=google.com; s=arc-20160816; b=iD35ZIPNCSPcqA9hb77VBuxqYYEjikOHh4HA2iYGK3fY0excxm+raF0dIwetPkUu2m LdYkU/vRmquKRt+g2e059UemoApUr8mn73ESw+J1VFfsyiWlO11dSqIH+dAoPp7g+l5L n/kD6AKtIJrdNjK+lqh4nDVVgBuoVa5JZMYnyLX71je1qVsq55/A5hHz38El3TLxpccK jNiI+MTbsmz2dlHWBrgfz9c9Z6qWqk172v01/sAg7+bIJuOJ07oNSLsBoJeeYTzV73F1 DFdykSbbsNNWk4lWfbcFRNs0MWnbgndJOKBNsjxZ3vSra2Hzkwo7OULJ3lqJp5ngf4IX j/iA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date:from :references:to:subject; bh=FZwW3CFvR6160AAGcnzLL1gOn3CUU07tiClMFZO4xXQ=; b=dXXo9ignpe9UDoWFLrha3n5b/ZzuBUKy4EFXIj/llRsBOGByiYl01uV2GnCvrkeAfk pYfjUr3cDnr0NkViC6Lj1Teyv609eq2IvNsvEdZfKgK3GHs4JUHIeZY7H6UcPaeZd7H2 W6V++SV7zySYfa8uGU02c5v/XoD1PcK+5kM0Sqaj4Yfv7gF2sXXsvH8gqcZFvuEdyPwi 07Bo407puLL8/kxb10mYAT9QlRbwPZsPZ85nOla2GN4vx+cz/3r10CEDb/ZU2szpH8xZ XCvzxGUk2bdxP4gQMss5/zPEWiiLNhmFLQqiS+1fMnXWWrxmJ7aeY/TI+pL6/H8sDiBy 5LRA== 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=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id bj2si43352685plb.27.2018.12.31.11.12.26; Mon, 31 Dec 2018 11:12:41 -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=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727566AbeLaR4J (ORCPT + 99 others); Mon, 31 Dec 2018 12:56:09 -0500 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:52570 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726722AbeLaR4J (ORCPT ); Mon, 31 Dec 2018 12:56:09 -0500 Received: from pps.filterd (m0098413.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id wBVHmtIf037642 for ; Mon, 31 Dec 2018 12:56:07 -0500 Received: from e12.ny.us.ibm.com (e12.ny.us.ibm.com [129.33.205.202]) by mx0b-001b2d01.pphosted.com with ESMTP id 2pqkpfhjw5-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 31 Dec 2018 12:56:07 -0500 Received: from localhost by e12.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Mon, 31 Dec 2018 17:56:07 -0000 Received: from b01cxnp22035.gho.pok.ibm.com (9.57.198.25) by e12.ny.us.ibm.com (146.89.104.199) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Mon, 31 Dec 2018 17:56:04 -0000 Received: from b01ledav001.gho.pok.ibm.com (b01ledav001.gho.pok.ibm.com [9.57.199.106]) by b01cxnp22035.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id wBVHu3cb24576074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 31 Dec 2018 17:56:03 GMT Received: from b01ledav001.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id CD25B28059; Mon, 31 Dec 2018 17:56:03 +0000 (GMT) Received: from b01ledav001.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 9E7A32805E; Mon, 31 Dec 2018 17:56:03 +0000 (GMT) Received: from [9.77.128.220] (unknown [9.77.128.220]) by b01ledav001.gho.pok.ibm.com (Postfix) with ESMTP; Mon, 31 Dec 2018 17:56:03 +0000 (GMT) Subject: Re: tpm_tis TPM2.0 not detected on cold boot To: Mimi Zohar , linux-integrity@vger.kernel.org, linux-kernel References: <1f281756bb1f041e55be8dd090670a1a7b1d1c94.camel@mniewoehner.de> <1545519232.3940.115.camel@linux.ibm.com> <1546140837.4069.81.camel@linux.ibm.com> From: Ken Goldman Date: Mon, 31 Dec 2018 12:56:03 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <1546140837.4069.81.camel@linux.ibm.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TM-AS-GCONF: 00 x-cbid: 18123117-0060-0000-0000-000002F0F9A7 X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00010323; HX=3.00000242; KW=3.00000007; PH=3.00000004; SC=3.00000272; SDB=6.01139808; UDB=6.00593076; IPR=6.00920018; MB=3.00024914; MTD=3.00000008; XFM=3.00000015; UTC=2018-12-31 17:56:05 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18123117-0061-0000-0000-000047C04996 Message-Id: <94e4968b-0b19-f0ca-24d8-e8105c1af704@linux.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-12-31_10:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=963 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1812310158 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/29/2018 10:33 PM, Mimi Zohar wrote: > But the problem you've described is on a cold boot, not a soft reboot. >  Both the soft reboot and kexec are working properly.  It seems the > difference is that on a cold boot, the TPM takes longer to initialize. I would expect this. The TPM doesn't even see a 'soft reboot' right? OTOH, a 'cold boot' hits the TPM Init pin, which causes the take several actions. Probably the one with the most impact is resetting the state of self test. Thus, the TPM will require a function to be self tested before it can be used, adding delays.