← Back to team overview

kernel-packages team mailing list archive

[Bug 1596469] Re: [Bug]tpm initialization fails on x86


Yakkety will pick this up naturally in v4.8

** Changed in: linux (Ubuntu)
       Status: Incomplete => Fix Released

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  [Bug]tpm initialization fails on x86

Status in intel:
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress

Bug description:
  When trying to test TPM with Ubuntu 16.04 on Intel x86_64 platform, there's tpm initialization failure found in kernel log:
  root@SKLU1-leg:~# dmesg | grep -i tpm
  [    0.000000] ACPI: SSDT 0x000000007FFE4000 0004D6 (v02 Intel_ Tpm2Tabl 00001000 INTL 20141107)
  [    0.000000] ACPI: TPM2 0x000000007FFE2000 000034 (v03                 00000000      00000000)
  [    2.532245] ima: No TPM chip found, activating TPM-bypass!
  [    3.489431] tpm_crb MSFT0101:00: can't request region for resource [mem 0xfed40040-0xfed4103f]
  [    3.489437] tpm_crb: probe of MSFT0101:00 failed with error -16

  which leads to tpm device missing under /dev:
  root@SKLU1-leg:~# ls -l /dev/tpm*
  ls: cannot access '/dev/tpm*': No such file or directory

  This error has been fixed with patch below, but not yet merged to upstream kernel:

  Patch 0af6e0a has dependency to this patch:
  So 0af6e0a has to be applied upon 3f94407, otherwise patch apply fails.

  I've verified with kernel 4.7-rc4 that above 2 patches can fix this TPM issue.
  So please Ubuntu team help on backporting these 2 patches into the kernel of their next release.

  PS, below are some information about Ubuntu & kernel & cpu info on my test server, for your reference:
  root@SKLU1-leg:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:	Ubuntu
  Description:	Ubuntu 16.04 LTS
  Release:	16.04
  Codename:	xenial
  root@SKLU1-leg:~# uname -a
  Linux SKLU1-leg 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to: