Bug 1373543 - [GM206] Xorg killed by SIGSEGV when running piglit
Summary: [GM206] Xorg killed by SIGSEGV when running piglit
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: xorg-x11-server
Version: 7.3
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Adam Jackson
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-06 14:43 UTC by Tomas Hudziec
Modified: 2020-12-15 07:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:45:30 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Tomas Hudziec 2016-09-06 14:43:40 UTC 
Description of problem:
When running piglit tests, Xorg was killed by SIGSEGV and it caused logging off the session.

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.17.2-22.el7
kernel-3.10.0-501.el7.x86_64

How reproducible:
once

Steps to Reproduce:
1.run piglit-run_and_report as regular user

Actual results:
After longer time, cca in 95% of piglit tests I was logged out from the session. Bug occured.
BUG: Xorg killed by SIGSEGV
folder with details available here:
http://download.eng.brq.redhat.com/scratch/thudziec/ccpp-2016-09-06-16:19:00-2671.tar.gz

Expected results:
Piglit should finish and ask for information to report.

Additional info:
NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401]
Comment 2 Tomas Hudziec 2016-09-07 09:06:57 UTC 
Happened for the second time.
Comment 3 Tomas Hudziec 2016-09-07 12:00:37 UTC 
Happened for the third time at piglit test 26966/27703.
Comment 6 RHEL Program Management 2020-12-15 07:45:30 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.