From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-11.2 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3768EC433E0 for ; Fri, 29 Jan 2021 23:01:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CD43664DED for ; Fri, 29 Jan 2021 23:01:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232887AbhA2XBl (ORCPT ); Fri, 29 Jan 2021 18:01:41 -0500 Received: from mail.kernel.org ([198.145.29.99]:33840 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231296AbhA2XBg (ORCPT ); Fri, 29 Jan 2021 18:01:36 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id DB55D6024A; Fri, 29 Jan 2021 23:00:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1611961255; bh=DZaxE07pVtdgl2l/Xugpjwng1nKYpg85qZ+3fPvMYts=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=p6fKmzQTPtYtS13E+2KWrZc9ffEFVmA/2UL4CEdRIXsUmyWJo+6YOL66kelLBOyOc 50ajn+BXQKDC74PWlHL/bxknlbG+aVyiQdqLvYwGxok2j7ITF++I/I6BvYpj1aLVYJ OHNcjkT8Lp8iD2tmjukTt0ldOMBirFXRQja5GpubbknOHOypN5BCh39imBt54TebUu LR13hMRRh1EB2ne+9EatdtxfqO+E92MXnPY4VcBEk4kNQU0RUVSchUu57fu7uTXQCq uYMuWeRjE6n+GKSwaXVlWnITWTf6cAyQ/jbIlekGm/Ea7SBXFeJll9vDFqT3AWfwI4 KPpEG9KLQmLWQ== Date: Sat, 30 Jan 2021 01:00:50 +0200 From: Jarkko Sakkinen To: =?utf-8?Q?=C5=81ukasz?= Majczak Cc: Guenter Roeck , Peter Huewe , Jason Gunthorpe , linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org, Radoslaw Biernacki , Marcin Wojtas , Alex Levin , James.Bottomley@hansenpartnership.com Subject: Re: [PATCH] tpm_tis: Add missing start/stop_tpm_chip calls Message-ID: References: <20210123014247.989368-1-lma@semihalf.com> <20210125171846.GA31929@roeck-us.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jan 30, 2021 at 12:59:09AM +0200, Jarkko Sakkinen wrote: > On Tue, Jan 26, 2021 at 04:46:07PM +0100, Ɓukasz Majczak wrote: > > Hi Jarkko, Guenter > > > > Yes, here are the logs when failure occurs - > > https://gist.github.com/semihalf-majczak-lukasz/1575461f585f1e7fb1e9366b8eceaab9 > > Look for a phrase "TPM returned invalid status" > > > > Guenter - good suggestion - I will try to keep it as tight as possible. > > > > Best regards, > > Lukasz > > Is it possible for you try out with linux-next? Thanks. It's a known > issue, which ought to be fixed by now. > > The log message is harmless, it'a warning not panic, and does not > endanger system stability. WARN()'s always dump stack trace. No oops > is happening. The regression itself originates from 2006. It has just been unmasked with "improved" logging. /Jarkko