Bug 1929308 - [Hardware Error]: Platform Security Processor Ext. Error Code: 62 - system unexpectedly reboots
Summary: [Hardware Error]: Platform Security Processor Ext. Error Code: 62 - system un...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 33
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-16 16:23 UTC by Martin
Modified: 2021-11-30 18:07 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-30 18:07:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg output from session on 2021-02-15, prior to crash/reboot (129.10 KB, text/plain)
2021-02-16 16:23 UTC, Martin
no flags Details

Description Martin 2021-02-16 16:23:23 UTC
Created attachment 1757286 [details]
dmesg output from session on 2021-02-15, prior to crash/reboot

1. Please describe the problem:

My system has started to experience unexpected reboots within the last several weeks. MCE errors are being logged, but I do not know if they are related to the issue. Example:

kernel: mce: [Hardware Error]: Machine check events logged
kernel: [Hardware Error]: Corrected error, no action required.
kernel: [Hardware Error]: CPU:0 (17:71:0) MC25_STATUS[-|CE|MiscV|-|-|-|-|CECC|-|-|-]: 0x98004000003e0000
kernel: [Hardware Error]: IPID: 0x000100ff03830400
kernel: [Hardware Error]: Platform Security Processor Ext. Error Code: 62
kernel: [Hardware Error]: cache level: RESV, tx: INSN


2. What is the Version-Release number of the kernel:

5.10.15-200.fc33.x86_64


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

My system had been stable for nearly one year, and there have not been any changes in physical components. The unexpected reboots started to occur several weeks ago, around the time I moved from kernel 5.10.8-100.fc32.x86_64 to 5.10.12-100.fc32.x86_64 (I have since upgraded to Fedora 33). Around the same time, I updated my BIOS to version 3204.


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

I disabled IOMMU, SR-IOV, and "Above 4G Decoding" in the BIOS and the frequency of the unexpected reboots seems to have dropped significantly - my system was stable yesterday, but experienced an unexpected reboot overnight while nobody was actively using the system.


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

Not attempted, please advise if you think this would be helpful.


6. Are you running any modules that not shipped with directly Fedora's kernel?:

vmmon and vmnet kernel modules required by VMware Workstation.


7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Kernel logs are attached here as "20210215_dmesg.txt". According to `last`, the system crashed 16 minutes after the last message in this log.

I made a comment on this kernel.org bug that you may find interesting: https://bugzilla.kernel.org/show_bug.cgi?id=206903#c155

---

OS: Fedora 33
Mesa 20.3.4-1.fc33

CPU: AMD Ryzen 5 3600X
Graphics Card: AMD Radeon RX 5700
Motherboard: ASUS Pro WS X570-ACE (BIOS version 3204, AGESA 1.2.0.0)
Memory: Crucial Ballistix Elite 4x8GB DDR4 3600MHz
Internal Storage: Crucial P1 1TB 3D NAND NVMe PCIe M.2 SSD
PSU: Seasonic PRIME Ultra 1000 Titanium

Comment 1 Martin 2021-02-28 16:41:59 UTC
(In reply to Martin from comment #0)
> 4. Can you reproduce this issue? If so, please provide the steps to reproduce
>    the issue below:
> 
> I disabled IOMMU, SR-IOV, and "Above 4G Decoding" in the BIOS and the
> frequency of the unexpected reboots seems to have dropped significantly - my
> system was stable yesterday, but experienced an unexpected reboot overnight
> while nobody was actively using the system.

After enabling the CPU TPM in the BIOS settings, the system has been stable for 7 days. No unexpected reboots, and no errors in the journal.

Comment 2 Ben Cotton 2021-11-04 15:01:01 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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 '33'.

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 33 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 Ben Cotton 2021-11-04 15:59:42 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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 '33'.

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 33 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 4 Ben Cotton 2021-11-30 18:07:50 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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.