Bug 1840969

Summary: Segfault when executing segfault script on non-segfaulting cpu
Product: [Fedora] Fedora Reporter: 20004life
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 32CC: airlied, bskeggs, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, masami256, mchehab, mjg59, steved, y9t7sypezp
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-25 17:22:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Log of test results using the segfault tester. none

Description 20004life 2020-05-28 02:51:40 UTC
Created attachment 1692915 [details]
Log of test results using the segfault tester.

Segfault occurs when executing segfault script on non-segfaulting cpu

Script:  https://github.com/Oxalin/ryzen-test.git

This script is intended to force segfaults on CPUs with a segmentation fault bug i.e. some of the very first generation Ryzen CPUs before the bug was fixed. 

The CPU I am using in my Workstation is a Xeon E5-2660V3, which should never produce a segmentation fault.

I tested a different distribution which uses Kernel version 5.4, and was unable to reproduce the segmentation fault. 

Testing the latest rawhide kernel yielded similar results. The kernel was not using any third party modules during the test.

There are no abnormalities in the dmesg -T output.

Comment 1 Steve 2020-05-28 20:39:11 UTC
Thanks for testing this.

Please attach a log from the system under test after the segfault occurs:

$ journalctl --no-hostname -k > dmesg.txt  # Run as a user in group "wheel".

Also, does ABRT report any problems, and, if so, did you send a bug report?

$ gnome-abrt

BTW, the script should log the processor family, model, and stepping. One of these should work:

$ journalctl --no-hostname -k | grep 'family.*model.*stepping'

$ journalctl --no-hostname -k | grep 'smpboot: CPU0:'

Comment 2 Fedora Program Management 2021-04-29 16:54:08 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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 '32'.

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 32 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-05-25 17:22:02 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.