Linux-Integrity Archive on lore.kernel.org
 help / color / Atom feed
From: "Safford, David (GE Global Research, US)" <david.safford@ge.com>
To: Matthew Garrett <mjg59@google.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
	"linux-integrity@vger.kernel.org"
	<linux-integrity@vger.kernel.org>,
	"jarkko.sakkinen@linux.intel.com"
	<jarkko.sakkinen@linux.intel.com>,
	"Wiseman, Monty (GE Global Research, US)" <monty.wiseman@ge.com>
Subject: [PATCH] tpm_crb - workaround broken ACPI tables
Date: Fri, 12 Jul 2019 19:05:22 +0000
Message-ID: <BCA04D5D9A3B764C9B7405BBA4D4A3C035EF7F56@ALPMBAPA12.e2k.ad.ge.com> (raw)
In-Reply-To: <CACdnJutmhRyGjiumXbzai1fTNqcYMRthzTfMsiQgzKFtu3+teA@mail.gmail.com>

> 
> I suspect the issue comes from AMD's reference code rather than multiple
> vendors all having made the same mistake. Unfortunate.

Yes.

> > But the laptop shows a new layout:
> > [    2.069539] tpm_crb MSFT0101:00: can't request region for resource
> > [mem 0xbd11f000-0xbd122fff]
> > [    2.069543] tpm_crb: probe of MSFT0101:00 failed with error -16
> > [    2.177663] ima: No TPM chip found, activating TPM-bypass!
> >
> > bbc64000-bd14afff : Reserved
> >   bd11f000-bd11ffff : MSFT0101:00
> >   bd123000-bd123fff : MSFT0101:00
> > bd14b000-bd179fff : ACPI Tables
> > bd17a000-bd328fff : ACPI Non-volatile Storage
> 
> Hmm, that's interesting. Is this a UEFI or BIOS system? Can you provide the
> e820 data from dmesg?

UEFI - the laptop dmesg e820 follows:

[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000009ec1fff] usable
[    0.000000] BIOS-e820: [mem 0x0000000009ec2000-0x0000000009ffffff] reserved
[    0.000000] BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
[    0.000000] BIOS-e820: [mem 0x000000000a200000-0x000000000a20afff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000000a20b000-0x00000000bbc63fff] usable
[    0.000000] BIOS-e820: [mem 0x00000000bbc64000-0x00000000bd14afff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000bd14b000-0x00000000bd179fff] ACPI data
[    0.000000] BIOS-e820: [mem 0x00000000bd17a000-0x00000000bd328fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bd329000-0x00000000bdbb0fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000bdbb1000-0x00000000beffffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000bf000000-0x00000000bfffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fd000000-0x00000000fdffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000feefffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000042effffff] usable
[    0.000000] BIOS-e820: [mem 0x000000042f000000-0x000000043effffff] reserved
[    0.000000] BIOS-e820: [mem 0x000000043f000000-0x000000043f33ffff] usable
[    0.000000] BIOS-e820: [mem 0x000000043f340000-0x000000043fffffff] reserved
[    0.000000] e820: update [mem 0xba4fd018-0xba50d057] usable ==> usable
[    0.000000] e820: update [mem 0xba4fd018-0xba50d057] usable ==> usable
[    0.000000] e820: update [mem 0xba4ef018-0xba4fc457] usable ==> usable
[    0.000000] e820: update [mem 0xba4ef018-0xba4fc457] usable ==> usable
[    0.000443] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000444] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000807] e820: update [mem 0xc0000000-0xffffffff] usable ==> reserved
[    0.574421] e820: reserve RAM buffer [mem 0x09ec2000-0x0bffffff]
[    0.574422] e820: reserve RAM buffer [mem 0x0a200000-0x0bffffff]
[    0.574422] e820: reserve RAM buffer [mem 0xba4ef018-0xbbffffff]
[    0.574423] e820: reserve RAM buffer [mem 0xba4fd018-0xbbffffff]
[    0.574423] e820: reserve RAM buffer [mem 0xbbc64000-0xbbffffff]
[    0.574424] e820: reserve RAM buffer [mem 0xbf000000-0xbfffffff]
[    0.574424] e820: reserve RAM buffer [mem 0x42f000000-0x42fffffff]
[    0.574424] e820: reserve RAM buffer [mem 0x43f340000-0x43fffffff]

  reply index

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-11 12:29 Safford, David (GE Global Research, US)
2019-07-11 14:10 ` Jarkko Sakkinen
2019-07-11 14:58 ` Jason Gunthorpe
2019-07-11 16:44   ` Safford, David (GE Global Research, US)
2019-07-11 18:50     ` Jason Gunthorpe
2019-07-11 19:31       ` Safford, David (GE Global Research, US)
2019-07-11 20:33         ` Matthew Garrett
2019-07-12 12:41           ` Safford, David (GE Global Research, US)
2019-07-12 15:06             ` Jason Gunthorpe
2019-07-12 15:48               ` Jarkko Sakkinen
2019-07-12 18:24             ` Matthew Garrett
2019-07-12 19:05               ` Safford, David (GE Global Research, US) [this message]
2019-07-12 20:36                 ` Matthew Garrett
2019-07-14 19:28                   ` Safford, David (GE Global Research, US)
2019-07-14 23:48                     ` Matthew Garrett
2019-07-15 19:44                       ` Matthew Garrett
2019-07-11 19:16 ` Jarkko Sakkinen

Reply instructions:

You may reply publically 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=BCA04D5D9A3B764C9B7405BBA4D4A3C035EF7F56@ALPMBAPA12.e2k.ad.ge.com \
    --to=david.safford@ge.com \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=mjg59@google.com \
    --cc=monty.wiseman@ge.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

Linux-Integrity Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-integrity/0 linux-integrity/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-integrity linux-integrity/ https://lore.kernel.org/linux-integrity \
		linux-integrity@vger.kernel.org linux-integrity@archiver.kernel.org
	public-inbox-index linux-integrity


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-integrity


AGPL code for this site: git clone https://public-inbox.org/ public-inbox