Bug 773195 - running all piglit tests leads to Xorg crash
Summary: running all piglit tests leads to Xorg crash
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-server
Version: 6.3
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Adam Jackson
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 842499
TreeView+ depends on / blocked
 
Reported: 2012-01-11 08:21 UTC by Matěj Cepl
Modified: 2017-12-06 11:59 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 11:59:13 UTC
Target Upstream Version:


Attachments (Terms of Use)
/var/log/Xorg.0.log.old with a backtrace (57.02 KB, text/plain)
2012-01-11 08:21 UTC, Matěj Cepl
no flags Details
output of dmesg command (491.30 KB, text/plain)
2012-01-11 08:25 UTC, Matěj Cepl
no flags Details
compressed /tmp/piglit directory (787.37 KB, application/x-tar)
2012-01-11 08:26 UTC, Matěj Cepl
no flags Details
compressed results directory from running all.tests with -c off (2.81 MB, application/zip)
2012-01-12 20:23 UTC, Matěj Cepl
no flags Details

Description Matěj Cepl 2012-01-11 08:21:52 UTC
Created attachment 552036 [details]
/var/log/Xorg.0.log.old with a backtrace

Description of problem:
When running

piglit-run tests/all.tests /tmp/piglit

overnight, I woke up to the login screen. Obviously Xorg crashed somewhere during the piglit run.

This is the backtrace:

Backtrace:
[365903.557] 0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x46aa58]
[365903.557] 1: /usr/bin/Xorg (0x400000+0x66899) [0x466899]
[365903.557] 2: /lib64/libpthread.so.0 (0x3ba3c00000+0xf4a0) [0x3ba3c0f4a0]
[365903.557] 3: /usr/lib64/xorg/modules/extensions/libglx.so (0x7faca1558000+0x40db4) [0x7faca1598db4]
[365903.574] 4: /usr/lib64/xorg/modules/extensions/libdri2.so (0x7faca0f3d000+0x2292) [0x7faca0f3f292]
[365903.574] 5: /usr/lib64/xorg/modules/extensions/libdri2.so (0x7faca0f3d000+0x22f8) [0x7faca0f3f2f8]
[365903.574] 6: /usr/bin/Xorg (TraverseTree+0x6c) [0x43b91c]
[365903.574] 7: /usr/lib64/xorg/modules/extensions/libdri2.so (DRI2SwapBuffers+0x1ad) [0x7faca0f401ad]
[365903.574] 8: /usr/lib64/xorg/modules/extensions/libdri2.so (0x7faca0f3d000+0x43b9) [0x7faca0f413b9]
[365903.574] 9: /usr/bin/Xorg (0x400000+0x39921) [0x439921]
[365903.574] 10: /usr/bin/Xorg (0x400000+0x21ebb) [0x421ebb]
[365903.574] 11: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x3ba341ecdd]
[365903.574] 12: /usr/bin/Xorg (0x400000+0x21a49) [0x421a49]
[365903.574] Segmentation fault at address 0xa8
[365903.574] 
Fatal server error:
[365903.574] Caught signal 11 (Segmentation fault). Server aborting

which translates to

In function __glXDRIinvalidateBuffers:
(from frame 3: /usr/lib64/xorg/modules/extensions/libglx.so (0x7faca1558000+0x40db4) [0x7faca1598db4])
428:     return &context->base;
429: }
430: 
431: static void
432: __glXDRIinvalidateBuffers(DrawablePtr pDraw, void *priv)
433: {
434: #if __DRI2_FLUSH_VERSION >= 3
435:     __GLXDRIdrawable *private = priv;
436:     __GLXDRIscreen *screen = private->screen;
437: 
438: >>>>>>>     if (screen->flush)
439: 	(*screen->flush->invalidate)(private->driDrawable);
440: #endif
441: }
442: 
443: static __GLXdrawable *
444: __glXDRIscreenCreateDrawable(ClientPtr client,
445: 			     __GLXscreen *screen,
446: 			     DrawablePtr pDraw,
447: 			     XID drawId,
448: 			     int type,


Frame 4: /usr/lib64/xorg/modules/extensions/libdri2.so (0x7faca0f3d000+0x2292) [0x7faca0f3f292]
	/usr/src/debug/xorg-server-1.10.4/hw/xfree86/dri2/dri2.c:543
	DRI2InvalidateDrawable
Frame 5: /usr/lib64/xorg/modules/extensions/libdri2.so (0x7faca0f3d000+0x22f8) [0x7faca0f3f2f8]
	/usr/src/debug/xorg-server-1.10.4/hw/xfree86/dri2/dri2.c:796
	DRI2InvalidateWalk
Frame 6: /usr/bin/Xorg (TraverseTree+0x6c) [0x43b91c]
	/usr/src/debug/xorg-server-1.10.4/dix/window.c:230
	TraverseTree
Frame 8: /usr/lib64/xorg/modules/extensions/libdri2.so (0x7faca0f3d000+0x43b9) [0x7faca0f413b9]
	/usr/src/debug/xorg-server-1.10.4/hw/xfree86/dri2/dri2ext.c:406
	ProcDRI2SwapBuffers
Frame 9: /usr/bin/Xorg (0x400000+0x39921) [0x439921]
	/usr/src/debug/xorg-server-1.10.4/dix/dispatch.c:431
	Dispatch
Frame 10: /usr/bin/Xorg (0x400000+0x21ebb) [0x421ebb]
	/usr/src/debug/xorg-server-1.10.4/dix/main.c:287
	main

Attaching also:
 * Xorg.0.log.old
 * dmesg-out.txt (output of dmesg command)
 * /tmp/piglit from the above mentioned command

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.10.4-6.el6.x86_64

How reproducible:
tried once

Steps to Reproduce:
1. run the above mentioned command
2. collect debugging info
3.
  
Actual results:
crashes

Expected results:
all tests should go through without crashing Xorg

Additional info:

Comment 1 Matěj Cepl 2012-01-11 08:25:39 UTC
Created attachment 552037 [details]
output of dmesg command

Comment 2 Matěj Cepl 2012-01-11 08:26:25 UTC
Created attachment 552038 [details]
compressed /tmp/piglit directory

Comment 4 Matěj Cepl 2012-01-12 20:23:57 UTC
Created attachment 552496 [details]
compressed results directory from running all.tests with -c off

After running 

./piglit-run.py -c off tests/all.tests /tmp/piglit-we-all-die

I've got no crash and these results

Comment 6 RHEL Program Management 2012-05-03 05:43:52 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 7 Jan Kurik 2017-12-06 11:59:13 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


Note You need to log in before you can comment on or make changes to this bug.