From: Jarkko S. <jar...@li...> - 2015-11-03 08:02:59
|
On Tue, Nov 03, 2015 at 08:27:59AM +0100, Peter Huewe wrote: > Hi, > > > Both of linux-tpm2(for-peter-v44 branch) and linux-tpmdd(for-james branch) > > kernel tree returned same log as follow: > > > > ------------------------- > > debian@debian:~$ dmesg | grep -i tpm > > [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.3.0-rc4+ > > root=UUID=a5e5e761-c2f2-41c3-9dfd-800a73e7a3e6 ro quiet > > tpm_tis.force=1 > > [ 0.000000] ACPI: TPM2 0x00000000A1F64EF8 000034 (v03 INTEL > > NUC5i5MY 00000001 AMI 00000000) > > [ 0.000000] Kernel command line: > > BOOT_IMAGE=/boot/vmlinuz-4.3.0-rc4+ > > root=UUID=a5e5e761-c2f2-41c3-9dfd-800a73e7a3e6 ro quiet > > tpm_tis.force=1 > > [ 0.844214] tpm_tis tpm_tis: 2.0 TPM (device-id 0x1A, rev-id 16) > > [ 1.026107] genirq: Flags mismatch irq 8. 00000080 (tpm0) vs. 00000000 (rtc0) > > [ 1.026110] tpm_tis tpm_tis: Unable to request irq: 8 for probe > > ------------------------- > > I ADDed tpm_tis.force=1 to kernel boot command. > > Does it show the same result, with and without the tpm_tis.force=1? The above is not a TPM driver error. It's a side effect how it probes the IRQ. /Jarkko |