Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
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-private | Assignee: | Tom Stellard <tstellar> |
Status: | CLOSED ERRATA | QA Contact: | qe-baseos-tools-bugs |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.4-Alt | CC: | 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
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. 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. Oh, and the llvm build tested was llvm-private-5.0.0-3.el7. 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 |