From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Mimi Zohar <zohar@linux.ibm.com>, Markku Savela <msa@moth.iki.fi>,
linux-integrity@vger.kernel.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "Peter Hüwe" <PeterHuewe@gmx.de>
Subject: Re: IMA fails to see TPM chip (rpi3, linaro optee)
Date: Thu, 07 Mar 2019 09:15:16 -0800 [thread overview]
Message-ID: <1551978916.2983.35.camel@HansenPartnership.com> (raw)
In-Reply-To: <1551183277.27819.66.camel@linux.ibm.com>
On Tue, 2019-02-26 at 07:14 -0500, Mimi Zohar wrote:
> On Tue, 2019-02-26 at 10:12 +0200, Markku Savela wrote:
> > In case anyone is interested, I got IMA to accept TPM chip in my
> > special
> > case (linaro optee kernel) by changing
> >
> > clk-bcm2835.c: core_initcall -> susbsys_initcall
> > raspberrypi.c: subsys_initcall -> core_initcall
> >
> > At first check, the system seems to be ok. Maybe some combination
> > of initcalls could work, but this is enough for me.
>
> Thank you for sharing this!
I've just had one of these on x86: a Dell Inspiron 7000 that I got for
my wife. This is the dmesg:
cottony:~ # dmesg|grep -i tpm
[ 0.000000] ACPI: TPM2 0x000000008A595160 000034 (v03 DELL CBX3 00000001 AMI 00000000)
[ 1.628559] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
I haven't investigated what type of TPM this is yet, but I suspect the
bus is attaching after IMA activates. The TPM works normally after
this.
James
prev parent reply other threads:[~2019-03-07 17:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 9:36 IMA fails to see TPM chip (rpi3, linaro optee) Markku Savela
2019-02-18 10:13 ` Markku Savela
2019-02-20 8:14 ` Markku Savela
2019-02-21 9:08 ` Markku Savela
2019-02-21 12:49 ` Mimi Zohar
2019-02-21 13:17 ` Markku Savela
2019-02-21 13:23 ` Markku Savela
2019-02-26 8:12 ` Markku Savela
2019-02-26 12:14 ` Mimi Zohar
2019-02-26 12:38 ` Ard Biesheuvel
2019-02-26 14:04 ` Mimi Zohar
2019-02-26 18:09 ` Jarkko Sakkinen
2019-02-26 19:05 ` Mimi Zohar
2019-03-07 17:15 ` James Bottomley [this message]
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=1551978916.2983.35.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=PeterHuewe@gmx.de \
--cc=ard.biesheuvel@linaro.org \
--cc=linux-integrity@vger.kernel.org \
--cc=msa@moth.iki.fi \
--cc=zohar@linux.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).