From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752343AbdLUNga (ORCPT ); Thu, 21 Dec 2017 08:36:30 -0500 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:38446 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751622AbdLUNgY (ORCPT ); Thu, 21 Dec 2017 08:36:24 -0500 Subject: Re: [Regression 4.15-rc2] New messages `tpm tpm0: A TPM error (2314) occurred continue selftest` From: Mimi Zohar To: Paul Menzel , Jason Gunthorpe Cc: Alexander.Steffen@infineon.com, linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org Date: Thu, 21 Dec 2017 08:36:00 -0500 In-Reply-To: References: <32b0e6c1292f4818825e9e0e9bff4d39@infineon.com> <20171207183743.GB16884@ziepe.ca> <37b47bbcce5d4cf1b1fad32576e501d4@infineon.com> <20171208155641.GA2883@ziepe.ca> <20171208161814.GB2883@ziepe.ca> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.5 (3.20.5-1.fc24) Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-TM-AS-GCONF: 00 x-cbid: 17122113-0020-0000-0000-000003E26276 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17122113-0021-0000-0000-000042737E8E Message-Id: <1513863360.5221.53.camel@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-12-21_06:,, 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 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1712210185 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Paul, On Mon, 2017-12-11 at 13:54 +0100, Paul Menzel wrote: > Dear Jason, > > > On 12/08/17 17:18, Jason Gunthorpe wrote: > > On Fri, Dec 08, 2017 at 05:07:39PM +0100, Paul Menzel wrote: > > > >> I have no access to the system right now, but want to point out, that the > >> log was created by `journactl -k`, so I do not know if that messes with the > >> time stamps. I checked the output of `dmesg` but didn’t see the TPM error > >> messages in the output – only `tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, > >> rev-id 4)`. Do I need to pass a different error message to `dmesg`? > > > > It is a good question, I don't know.. If your kernel isn't setup to > > timestamp messages then the journalstamp will certainly be garbage. > > > > No idea why you wouldn't see the messages in dmesg, if they are not in > > dmesg they couldn't get into the journal > > It looks like I was running an older Linux kernel version, when running > `dmesg`. Sorry for the noise. Here are the messages with the Linux > kernel time stamps, showing that the delays work correctly. > > ``` > $ uname -a > Linux Ixpees 4.15.0-041500rc2-generic #201712031230 SMP Sun Dec 3 > 17:32:03 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux > $ sudo dmesg | grep TPM > [ 0.000000] ACPI: TPM2 0x000000006F332168 000034 (v03 Tpm2Tabl > 00000001 AMI 00000000) > [ 1.114355] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4) > [ 1.125250] tpm tpm0: A TPM error (2314) occurred continue selftest > [ 1.156645] tpm tpm0: A TPM error (2314) occurred continue selftest > [ 1.208053] tpm tpm0: A TPM error (2314) occurred continue selftest > [ 1.299640] tpm tpm0: A TPM error (2314) occurred continue selftest > [ 1.471223] tpm tpm0: A TPM error (2314) occurred continue selftest > [ 1.802819] tpm tpm0: A TPM error (2314) occurred continue selftest > [ 2.454320] tpm tpm0: A TPM error (2314) occurred continue selftest > [ 3.734808] tpm tpm0: TPM self test failed > [ 3.759675] ima: No TPM chip found, activating TPM-bypass! (rc=-19) > ``` I've sort of been following this thread, but just want to make sure that once the self test is/was fixed, that you aren't seeing the IMA message. Assuming this is fixed, could someone provide the commit that fixes it? thanks, Mimi