Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp8581123ybc; Fri, 29 Nov 2019 13:05:44 -0800 (PST) X-Google-Smtp-Source: APXvYqzMAl9Zg7tBZSvK/fXu4ullrtW83ocEcgFwZP2GltJuYMhQeoBvtPX5pUM7hyyR6QS59LxF X-Received: by 2002:a1c:7507:: with SMTP id o7mr16098713wmc.163.1575061544340; Fri, 29 Nov 2019 13:05:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575061544; cv=none; d=google.com; s=arc-20160816; b=QK8wtQ1JBqEbUKIvyIfNqhJwbZQAxtuKa2cNg/ytcNFeaJIeUGbO9asBECx5JtHiTf oLe/QWEPaoq9MaRkbbzZ85yWFbwlC2T0y0Rd4Lah3q7d57xslH+RnX8d+j/hflE3ILXF qQHwmgJaUuvqsZvPKccFuI0UjhLH+ZtP1p2JSUukCZ9ed4dIO4xv+Mz4YdGyDbYA+G/j kmksqPj086BhQl81Rb0bAW8DuY103lJn+Yfb0N6AcXudC4Yh75131EdL0MaPJEh5Kp4B WUrD1tgKE2++1JmmgxiUPy10J/RI2hT8NxqiG0TAUCo0L2ZgW61HfAru08IYcdy7H6aD 6TGQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:organization:in-reply-to :content-disposition:mime-version:references:message-id:subject:to :from:date; bh=qibrz9JCI7VrUGg6aCh0on7sOucJYmVTzg4eApwH6wg=; b=guJ40sxJGaaas5re5ppOivvVPdAiF9Fs51kS5kR/z3ABevc2UA3OeLToz7PCR49ft4 lgAhd2lGNnwYbYOC02IIrlalU9WcPEbLeqKgs3nG9Dozb48ZyFnAXjAaFj9gmA33sofa yiTSni/ubsGE2PijPAnCkuTf1Kl6WnUb9uUYQhHICuUK2r4DxBJK3+4oobw5e7rJghP0 cwEAhRrTkmAH44EMsOBUC0x/hs+Fbwm4vQh0EEd/M1vtUErrsrZIgHjI3oQmjgTpDbdD +BJ3Q5c+xxMvAxnn/njdm8xdIrr5DUSJHAsp+OfScRzyOYgZ4Zoj2eEJA0sQdsYwsTw2 dGKQ== 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=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z16si2662582edq.340.2019.11.29.13.05.18; Fri, 29 Nov 2019 13:05:44 -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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727130AbfK2VEI (ORCPT + 99 others); Fri, 29 Nov 2019 16:04:08 -0500 Received: from mga02.intel.com ([134.134.136.20]:41812 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727073AbfK2VEH (ORCPT ); Fri, 29 Nov 2019 16:04:07 -0500 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Nov 2019 13:04:06 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,258,1571727600"; d="scan'208";a="199903920" Received: from kryanx-mobl1.ger.corp.intel.com (HELO localhost) ([10.252.22.23]) by orsmga007.jf.intel.com with ESMTP; 29 Nov 2019 13:04:02 -0800 Date: Fri, 29 Nov 2019 23:04:00 +0200 From: Jarkko Sakkinen To: Dan Williams , Linus Torvalds , Linux Kernel Mailing List , linux-integrity@vger.kernel.org, James Morris , Stefan Berger , stable Subject: Re: [GIT PULL] tpmdd updates for Linux v5.4 Message-ID: <20191129210400.GB12055@linux.intel.com> References: <20190902143121.pjnykevzlajlcrh6@linux.intel.com> <20191122161836.ry3cbon2iy22ftoc@cantor> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191122161836.ry3cbon2iy22ftoc@cantor> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 22, 2019 at 09:18:36AM -0700, Jerry Snitselaar wrote: > On Wed Nov 20 19, Dan Williams wrote: > > On Mon, Sep 2, 2019 at 7:34 AM Jarkko Sakkinen > > wrote: > > > > > > Hi > > > > > > A new driver for fTPM living inside ARM TEE was added this round. In > > > addition to that, there is three bug fixes and one clean up. > > > > > > /Jarkko > > > > > > The following changes since commit 8fb8e9e46261e0117cb3cffb6dd8bb7e08f8649b: > > > > > > Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma (2019-08-30 09:23:45 -0700) > > > > > > are available in the Git repository at: > > > > > > git://git.infradead.org/users/jjs/linux-tpmdd.git tags/tpmdd-next-20190902 > > > > > > for you to fetch changes up to e8bd417aab0c72bfb54465596b16085702ba0405: > > > > > > tpm/tpm_ftpm_tee: Document fTPM TEE driver (2019-09-02 17:08:35 +0300) > > > > > > ---------------------------------------------------------------- > > > tpmdd updates for Linux v5.4 > > > > > > ---------------------------------------------------------------- > > > Jarkko Sakkinen (1): > > > tpm: Remove a deprecated comments about implicit sysfs locking > > > > > > Lukas Bulwahn (1): > > > MAINTAINERS: fix style in KEYS-TRUSTED entry > > > > > > Sasha Levin (2): > > > tpm/tpm_ftpm_tee: A driver for firmware TPM running inside TEE > > > tpm/tpm_ftpm_tee: Document fTPM TEE driver > > > > > > Stefan Berger (2): > > > tpm_tis_core: Turn on the TPM before probing IRQ's > > > tpm_tis_core: Set TPM_CHIP_FLAG_IRQ before probing for interrupts > > > > Hi Jarrko, > > > > I'm replying here because I can't find the patches to reply to > > directly from LKML. > > > > Commit 7f064c378e2c "tpm_tis_core: Turn on the TPM before probing > > IRQ's" in the v5.3-stable tree caused a regression on a pre-release > > platform with a TPM2 device. The interrupt starts screaming when the > > driver is loaded and does not stop until the device is force unbond > > from the driver by: > > > > echo IFX0740:00 > /sys/bus/platform/drivers/tpm_tis/unbind > > > > I checked v5.4-rc8 and it has the same problem. I tried reverting: > > > > 1ea32c83c699 tpm_tis_core: Set TPM_CHIP_FLAG_IRQ before probing for interrupts > > 5b359c7c4372 tpm_tis_core: Turn on the TPM before probing IRQ's > > > > Which silenced the screaming interrupt problem, but now the TPM is reporting: > > > > [ 3.725131] tpm_tis IFX0740:00: 2.0 TPM (device-id 0x1B, rev-id 16) > > [ 3.725358] tpm tpm0: tpm_try_transmit: send(): error -5 > > [ 3.725359] tpm tpm0: [Firmware Bug]: TPM interrupt not working, > > polling instead > > > > ...at load, where it was not reporting this previously. Can you take a look? > > > > We've had an issue reported for a Lenovo t490s getting an interrupt storm > with the Fedora 5.3 stable kernel, so it appears to be impacting a number of > systems. Hi sorry for inactivity. I've had a renovation going on where I live which has caused some crackling in the comms but I'm catching up during the weekend. Which CPU model does T490S have? Can you paste /proc/cpuinfo? /Jarkko