System Environment: -------------------------- --Platform: g965 --Architecture(32-bit): ia32 --2D driver: git commit:d9df93578b74785c08ba860b4c9aa23b0c89c91c --3D driver: Mesa master commit:e54329233522591bbe8aad8a3fd6bcdc1e430f03 --DRM: git commit:2db6400396ea5c8a5ce54fe9e211b9d01a11d506 --Xserver: git commit:7ef7727b800fa4715b80a82850d65b88fde5fe6c --Kernel: 2.6.23 Bug Description: when Xtest run to case "XCloseDisplay 28" on g965(32bit) with git source code. It will stop at there until you kill the process by hand. Reproduce step: 1 X & 2 xterm & 3 tcc -e xts5 XCloseDisplay
Created attachment 13276 [details] xorg log file
like bug #13765.following Xserver commit import this problem: commit c8feb73f5841e7812d8dfdb91f1064e2033d028c Merge: 9a7ce57... a125ce4... Author: Eamon Walsh <ewalsh@tycho.nsa.gov> Date: Thu Dec 13 18:38:25 2007 -0500 Merge branch 'master' into XACE-SELINUX Conflicts: Xext/EVI.c Xext/bigreq.c Xext/cup.c Xext/dpms.c Xext/fontcache.c Xext/mitmisc.c Xext/xcmisc.c Xext/xf86bigfont.c Xext/xtest.c configure.ac dbe/dbe.c hw/darwin/darwin.h hw/darwin/darwinEvents.c hw/darwin/iokit/xfIOKit.h hw/darwin/iokit/xfIOKitCursor.c hw/darwin/quartz/fullscreen/fullscreen.c hw/darwin/quartz/fullscreen/quartzCursor.c hw/darwin/quartz/quartz.c hw/darwin/quartz/quartzCommon.h hw/darwin/quartz/quartzCursor.c hw/darwin/quartz/xpr/dri.c hw/darwin/quartz/xpr/dristruct.h hw/darwin/quartz/xpr/xprCursor.c hw/darwin/quartz/xpr/xprFrame.c hw/xfree86/modes/xf86RandR12.c include/cursor.h miext/rootless/rootlessCommon.h miext/rootless/rootlessScreen.c miext/rootless/rootlessWindow.c render/picturestr.h Trying to pick up the pieces from the darwin churn here...
Can't reproduce. On Intel 32-bit with intel driver, xserver compiled from master, XCloseDisplay test terminates and xserver does not crash. Try updating from master and retesting. Perhaps the fix for bug #13765 fixed the problem.
(In reply to comment #3) > Can't reproduce. On Intel 32-bit with intel driver, xserver compiled from > master, XCloseDisplay test terminates and xserver does not crash. > Try updating from master and retesting. Perhaps the fix for bug #13765 fixed > the problem. No, the problem still exist even appling the patch which can fix bug #13765.
this problem also can happen on g965(64bit) [root@x-g965 results]# tcc -e xts5 XCloseDisplay tcc: journal file is /GFX/Test/Xtest/xts5/results/0159e/journal *** glibc detected *** /GFX/Test/Xtest/xts5/tset/Xlib3/clsdsply/Test: corrupted double-linked list: 0x0000000000537ab0 *** ======= Backtrace: ========= /lib64/libc.so.6[0x3cb906bb13] /lib64/libc.so.6[0x3cb906e00d] /lib64/libc.so.6(malloc+0x7d)[0x3cb906f74d] /lib64/libc.so.6[0x3cb905ddfa] /GFX/Test/Xtest/xts5/tset/Xlib3/clsdsply/Test[0x416a5f] /GFX/Test/Xtest/xts5/tset/Xlib3/clsdsply/Test[0x40ae26] /GFX/Test/Xtest/xts5/tset/Xlib3/clsdsply/Test[0x40b38a] /GFX/Test/Xtest/xts5/tset/Xlib3/clsdsply/Test[0x40a728] /lib64/libc.so.6(__libc_start_main+0xf4)[0x3cb901d084] /GFX/Test/Xtest/xts5/tset/Xlib3/clsdsply/Test[0x4032e9] ======= Memory map: ======== 00400000-00427000 r-xp 00000000 08:02 1718549 /GFX/Test/Xtest/xts5/tset/Xlib3/clsdsply/Test 00527000-0052c000 rw-p 00027000 08:02 1718549 /GFX/Test/Xtest/xts5/tset/Xlib3/clsdsply/Test 0052c000-0056b000 rw-p 0052c000 00:00 0 [heap] 3cb8e00000-3cb8e19000 r-xp 00000000 08:02 825637 /lib64/ld-2.4.so 3cb8f19000-3cb8f1a000 r--p 00019000 08:02 825637 /lib64/ld-2.4.so 3cb8f1a000-3cb8f1b000 rw-p 0001a000 08:02 825637 /lib64/ld-2.4.so 3cb9000000-3cb913f000 r-xp 00000000 08:02 825638 /lib64/libc-2.4.so 3cb913f000-3cb923f000 ---p 0013f000 08:02 825638 /lib64/libc-2.4.so 3cb923f000-3cb9243000 r--p 0013f000 08:02 825638 /lib64/libc-2.4.so 3cb9243000-3cb9244000 rw-p 00143000 08:02 825638 /lib64/libc-2.4.so 3cb9244000-3cb9249000 rw-p 3cb9244000 00:00 0 3cb9500000-3cb9502000 r-xp 00000000 08:02 825640 /lib64/libdl-2.4.so 3cb9502000-3cb9602000 ---p 00002000 08:02 825640 /lib64/libdl-2.4.so 3cb9602000-3cb9603000 r--p 00002000 08:02 825640 /lib64/libdl-2.4.so 3cb9603000-3cb9604000 rw-p 00003000 08:02 825640 /lib64/libdl-2.4.so 3cbbd00000-3cbbd0d000 r-xp 00000000 08:02 825643 /lib64/libgcc_s-4.1.0-20060304.so.1 3cbbd0d000-3cbbe0d000 ---p 0000d000 08:02 825643 /lib64/libgcc_s-4.1.0-20060304.so.1 3cbbe0d000-3cbbe0e000 rw-p 0000d000 08:02 825643 /lib64/libgcc_s-4.1.0-20060304.so.1 2b417fe80000-2b417fe82000 rw-p 2b417fe80000 00:00 0 2b417fe82000-2b417fe8a000 r-xp 00000000 08:02 1927604 /opt/X11R7/lib64/libXi.so.6.0.0 2b417fe8a000-2b417ff8a000 ---p 00008000 08:02 1927604 /opt/X11R7/lib64/libXi.so.6.0.0 2b417ff8a000-2b417ff8b000 rw-p 00008000 08:02 1927604 /opt/X11R7/lib64/libXi.so.6.0.0 2b417ff8b000-2b417ff90000 r-xp 00000000 08:02 1927640 /opt/X11R7/lib64/libXtst.so.6.1.0 2b417ff90000-2b4180090000 ---p 00005000 08:02 1927640 /opt/X11R7/lib64/libXtst.so.6.1.0 2b4180090000-2b4180091000 rw-p 00005000 08:02 1927640 /opt/X11R7/lib64/libXtst.so.6.1.0 2b4180091000-2b41800a1000 r-xp 00000000 08:02 1927590 /opt/X11R7/lib64/libXext.so.6.4.0 2b41800a1000-2b41801a1000 ---p 00010000 08:02 1927590 /opt/X11R7/lib64/libXext.so.6.4.0 2b41801a1000-2b41801a2000 rw-p 00010000 08:02 1927590 /opt/X11R7/lib64/libXext.so.6.4.0 2b41801a2000-2b41802a4000 r-xp 00000000 08:02 1927553 /opt/X11R7/lib64/libX11.so.6.2.0 2b41802a4000-2b41803a3000 ---p 00102000 08:02 1927553 /opt/X11R7/lib64/libX11.so.6.2.0 2b41803a3000-2b41803a9000 rw-p 00101000 08:02 1927553 /opt/X11R7/lib64/libX11.so.6.2.0 2b41803a9000-2b41803ab000 rw-p 2b41803a9000 00:00 0 2b41803d6000-2b41803d7000 rw-p 2b41803d6000 00:00 0 2b41803d7000-2b41803d9000 r-xp 00000000 08:02 1927562 /opt/X11R7/lib64/libXau.so.6.0.0 2b41803d9000-2b41804d8000 ---p 00002000 08:02 1927562 /opt/X11R7/lib64/libXau.so.6.0.0 2b41804d8000-2b41804d9000 rw-p 00001000 08:02 [root@x-g965 results]#
Reassigning to XTest. If I can get packet captures to compare (pre-bad commit versus post-bad commit) or line-number information for the crash, that will help me find the source of the problem in the xserver. But I did not modify the XTest program as part of my work, so the immediate problem is a bug in XTest.
I committed a patch to xserver master to fix some protocol error values. Please update from master and retry the XCloseDisplay test.
One more thing: I noticed that you ran an xterm before you started the CloseDisplay test. This is not the proscribed behavior. The test expects to be run on a new X server with no other clients connected. Retry without running the xterm client first. You might see that the X server crashes because of bug #14418. I have made that bug a blocker for this one.
(In reply to comment #8) > One more thing: I noticed that you ran an xterm before you started the > CloseDisplay test. This is not the proscribed behavior. The test expects to > be run on a new X server with no other clients connected. Retry without > running the xterm client first. > > You might see that the X server crashes because of bug #14418. I have made > that bug a blocker for this one. > I tried without xterm openning.the case still hang there.in bug #14418, peter give a patch. i will wait that result.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/test/xts/issues/14.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.