Bug 1645903 - Unknown TPM error during boot of UEFI system
Summary: Unknown TPM error during boot of UEFI system
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 30
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-04 19:24 UTC by Fred J. Tydeman
Modified: 2020-05-26 17:45 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-05-26 17:45:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Fred J. Tydeman 2018-11-04 19:24:45 UTC
Description of problem:
During boot of system, get (about 10 times) on the console:
error: ../../grub-core/kern/efi/tmp.c: 255: Unknown TPM error
After that, the system continues to boot OK and runs OK.

Version-Release number of selected component (if applicable):
Fedora 29

How reproducible:
Happens every time I boot.  My system has Windows 10, Fedora 25, 26, 27, 28, 29 on it.  I get the message every time I boot any of the Fedora systems using the entries I added to /boot/efi/EFI/fedora/grub.cfg.  It does not happen if I use the entries created during the install of Fedora 29.

Steps to Reproduce:
1.  Add entries like

menuentry 'Fedora 29 (fjt)' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_gpt
	insmod ext2
        search --no-floppy --fs-uuid --set=root 1528e723-888d-4c62-9d41-23864748786f
        configfile /boot/grub2/grub.cfg
}

to /boot/efi/EFI/fedora/grub.cfg

2. Boot the system and pick that entry; rather than the entry:
menuentry 'Fedora (4.18.16-300.fc29.x86_64) 29 (Twenty Nine)' --class fedora...

Actual results:
The above error message on the console about 10 times.  Sometimes, it is followed by: Press a key to continue.

Expected results:
No error message.

Additional info:
This problem first happened when I installed Fedora 28 (but only to 28; not to 25, 26, 27).  now that I have installed 29, it happens with all 5 Fedoras.

Hardware is:  Lenovo ThinkPad X1 Carbon 5th gen with latest BIOS.

My system is setup so that the primary boot menu lets me pick which partition to boot.  Once that partition is picked, I then get another boot menu that lets me pick which kernel to boot.  See bug 1488204.

Comment 1 sam0hack 2019-05-01 18:04:20 UTC
I fixed this problem by reinstalling the grub



~]# dnf reinstall grub2-efi shim

Rebuild the grub.cfg file by running the grub2-mkconfig -o command as follows:

    On BIOS-based machines, issue the following command as root:

    ~]# grub2-mkconfig -o /boot/grub2/grub.cfg

    On UEFI-based machines, issue the following command as root:

    ~]# grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg

Comment 2 Ben Cotton 2019-10-31 19:28:00 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fred J. Tydeman 2019-11-01 17:08:25 UTC
I still am getting the TPM error messages after installing Fedora 30.  It happens during the boot
of either 30 or 29.

Comment 4 Ben Cotton 2020-04-30 20:47:21 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2020-05-26 17:45:05 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.