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=ham 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 C0F5FC433E9 for ; Fri, 29 Jan 2021 23:00:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6E19664DED for ; Fri, 29 Jan 2021 23:00:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231367AbhA2W7w (ORCPT ); Fri, 29 Jan 2021 17:59:52 -0500 Received: from mail.kernel.org ([198.145.29.99]:33536 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232747AbhA2W7w (ORCPT ); Fri, 29 Jan 2021 17:59:52 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id D336264DED; Fri, 29 Jan 2021 22:59:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1611961151; bh=RMzrLYS0dhIFza5IZGjzDLcAAAHAc2oc8FO0sqO3xJY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=evJaiOBztm/TbR7DtHnUCr6qIvlyko0D3G4vNnVnO7DBrXSaORnY1ZgLAjsKPaKZp AI1QhjWborSuJPu1aQPlJOz6e7MD7NRiv4k3Cf8hRaaYMw0VM6g70vpPg1LlgYgByB OdW0nezuxevHo6/HMHVRHUQDqMGMfFjCrKHHYfgtdMhWL/3hG2YYJme8VeL9ED+K6f 57NoS1q8U9gTqKUUqjmQTKjRGg7/pS8KbhgYxFsHzidu06zj4S1Ym8t/SP/YqOHxw2 Pm1Inq0FoGk4xcwrjDlfxB2XQzEVZUtNmXTdas5VlyoDWcZTImYdSOJRrSL+y3n+3K XFILrEDCqy8Hg== Date: Sat, 30 Jan 2021 00:59:06 +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-integrity@vger.kernel.org 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. /Jarkko