Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1461818

Summary: Gnome core dumps on startup with llvmpipe crash due to llvm failing to clear high 16bits of correct register [RHEL-7.5]
Product: Red Hat Enterprise Linux 7 Reporter: Laszlo Ersek <lersek>
Component: llvm-privateAssignee: Tom Stellard <tstellar>
Status: CLOSED ERRATA QA Contact: qe-baseos-tools-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4-AltCC: ajax, dmalcolm, jbastian, jistone, jlinton, law, mcermak, mnewsome, mprchlik, tpelka, tschelle, yselkowi
Target Milestone: rc   
Target Release: 7.5   
Hardware: aarch64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: 1429050 Environment:
Last Closed: 2018-04-10 16:19:04 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:
Bug Depends On: 1486998, 1500113    
Bug Blocks: 1471969, 1485496    

Description Laszlo Ersek 2017-06-15 11:47:42 UTC
+++ This bug was initially created as a clone of Bug #1429050 +++

The exact same issue as described in bug 1429050 happens in RHEL-7.4 as well, using package "mesa-private-llvm-3.9.1-3.el7.aarch64".

Jeremy's patch in bug 1429050 comment 4 (direct link: attachment 1261680 [details]) applies to the above-mentioned RHEL-7.4 package (i.e., dist-git commit 6ec0b20b46c9) without conflicts, and works fine:

http://people.redhat.com/lersek/a95d492b-9f7a-4ba5-a6a4-a030f66bcae8-pegas10-aarch64-gnome.png

For RHEL-Alt-7.4, sibling bug 1461815 has been filed. For RHEL-7.5, please incorporate the patch normally.

Comment 2 Igor Gnatenko 2017-06-15 12:20:27 UTC
Please, can you create new bugs instead of cloning them? Me (and probably all others who were CCed on original bug) don't want to see RHEL-related bugs.

Comment 13 Miloš Prchlík 2018-01-22 13:23:55 UTC
The fix seems to be included in the sources, AFAICT after digging a bit into llvm srpm. I ran tests included in mesa-17.0.1-6.20170307.el7.src.rpm, no segfaults appeared. Switching to VERIFIED.

Comment 14 Miloš Prchlík 2018-01-22 13:24:44 UTC
Oh, and the llvm build tested was llvm-private-5.0.0-3.el7.

Comment 17 errata-xmlrpc 2018-04-10 16:19:04 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:0894