From: Jerry Snitselaar <jsnitsel@redhat.com>
To: Christian Bundy <christianbundy@fraction.io>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Greg KH <gregkh@linuxfoundation.org>,
Jason Gunthorpe <jgg@ziepe.ca>, Peter Huewe <peterhuewe@gmx.de>,
Stefan Berger <stefanb@linux.vnet.ibm.com>,
stable-commits@vger.kernel.org, linux-integrity@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Patch "tpm_tis: reserve chip for duration of tpm_tis_core_init" has been added to the 5.4-stable tree
Date: Fri, 3 Jan 2020 14:47:20 -0700 [thread overview]
Message-ID: <20200103214720.nf2ahcpk3t2d7lua@cantor> (raw)
In-Reply-To: <be07a1e4-c290-4185-8c23-d97050279564@www.fastmail.com>
On Tue Dec 31 19, Christian Bundy wrote:
>> Christian, were you having any issues with interrupts? You system was going
>> into this code as well.
>
>Unfortunately I'm now unable to test, sorry for the trouble. I replaced my BIOS
>with UEFI firmware and the problem has disappeared. Please let me know if there
>is anything else I can do to help.
>
>Christian
>
That is interesting. Is the tpm functioning, or did the firmware change disable it?
Is there any output from 'dmesg | grep -i tpm' or anything in /sys/class/tpm/ ?
next prev parent reply other threads:[~2020-01-03 21:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1577122577157232@kroah.com>
2019-12-23 19:46 ` Patch "tpm_tis: reserve chip for duration of tpm_tis_core_init" has been added to the 5.4-stable tree Dan Williams
2019-12-27 6:05 ` Jarkko Sakkinen
2019-12-27 6:11 ` Jarkko Sakkinen
2019-12-28 15:15 ` Jarkko Sakkinen
2019-12-28 17:17 ` Dan Williams
2019-12-30 7:41 ` Dan Williams
2019-12-30 23:28 ` Jarkko Sakkinen
2019-12-31 0:33 ` Jerry Snitselaar
2019-12-31 1:02 ` Jerry Snitselaar
2019-12-31 16:00 ` Jarkko Sakkinen
2019-12-31 19:47 ` Christian Bundy
2020-01-02 17:20 ` Jarkko Sakkinen
2020-01-02 19:20 ` Dan Williams
2020-01-03 5:04 ` Dan Williams
2020-01-03 22:20 ` Jerry Snitselaar
2020-01-03 22:55 ` Jarkko Sakkinen
2020-01-03 21:51 ` Jarkko Sakkinen
2020-01-03 20:24 ` Jerry Snitselaar
2020-01-03 22:56 ` Jarkko Sakkinen
2020-01-03 23:07 ` Jarkko Sakkinen
2020-01-03 23:30 ` Jarkko Sakkinen
2020-01-03 21:47 ` Jerry Snitselaar [this message]
2019-12-31 0:30 ` Jerry Snitselaar
2020-01-01 22:55 ` Dan Williams
2019-12-28 23:39 ` Jerry Snitselaar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200103214720.nf2ahcpk3t2d7lua@cantor \
--to=jsnitsel@redhat.com \
--cc=christianbundy@fraction.io \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=stable-commits@vger.kernel.org \
--cc=stefanb@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).