Bug 30259 - compiz issue when kill X in gnome after run glxgears using DP
Summary: compiz issue when kill X in gnome after run glxgears using DP
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium major
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: 2011BRB_Reviewed
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-18 19:58 UTC by wang,jinjin
Modified: 2015-06-16 20:09 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description wang,jinjin 2010-09-18 19:58:26 UTC
System Environment:
--------------------------
Arch:           i386
Platform:       Capella
OSD:            Fedora release 13 (Goddard)
Libdrm:         (master)2.4.21-21-g7ec9a1effa4f551897f91f3b017723a8adf011d9
Mesa:           (7.9)d46b7c9f6f91f80b7349067dd5be52f0af736ec1
Xserver:                (master)xorg-server-1.9.0
Xf86_video_intel:               (master)2.12.0-87-g08c2caca48323d6d5701dcef3486f850619d7905
Cairo:          (master)cb0bc64c16b3a38cbf0c622830c18ac9ea6e2ffe
Libva:          (master)6772bdb4406edaf55da2e3604003c9eafff31c36
Kernel: (master)9fe6206f400646a2322096b56c59891d530e8d51

Bug detailed description:
---------------------------
With Dp I start gnome and run glxgears. Then, if I kill X directly, compiz file a error and the previous screen had no display.

Reproduce steps:
----------------
1.xinit& 
2. gnome-session&
3.satr a term in gnome 
4.glxgears&
5.pkill X

message:
compiz[16669]: segfault at 48 ip 432ad0e3 sp bfd62750 error 4 in libICE.so.6.3.0
Comment 1 Chris Wilson 2010-09-19 01:08:34 UTC
Before step 5, you will need to vt switch to a console and attach gdb to compiz (gdb --pid=`pidof compiz`), then switch back to X and pkill.

Then you should be able to get the backtrace (bt full) for the crash.
Comment 2 wang,jinjin 2010-09-19 22:19:32 UTC
compiz message:
-----------------------
(gdb) c
Continuing.
xterm:  fatal IO error 11 (Resource temporarily unavailable) or KillClient on X server ":0"
xinit:  connection to X server lost.

waiting for X server to shut down
Program received signal SIGHUP, Hangup.
0xb77fd424 in __kernel_vsyscall ()
(gdb) ..........

xinit:  X server slow to shut down, sending KILL signal.

waiting for server to die ...

xinit:  Can't kill server

NOTE:The bug also have the following situation:
When I killed X, all the video output have no display including LVDS and DP with the backtrace:
term:  fatal IO error 11 (Resource temporarily unavailable) or KillClient on X server ":0"
xinit:  connection to X server lost.

waiting for X server to shut down
Backtrace:
0: X (xorg_backtrace+0x3b) [0x809a67b]
1: X (0x8048000+0x5dac5) [0x80a5ac5]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb779740c]
3: X (FreeClientResources+0xed) [0x806fd0d]
4: X (FreeAllResources+0x60) [0x806fde0]
5: X (0x8048000+0x1a2b6) [0x80622b6]
6: /lib/libc.so.6 (__libc_start_main+0xe6) [0x42bfbcc6]
7: X (0x8048000+0x19e61) [0x8061e61]
Segmentation fault at address (nil)

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting

waiting for X server to shut down ..........
Comment 3 Jeremy Huddleston Sequoia 2011-10-06 11:07:46 UTC
I don't reakky grok what you're reporting.

It looks like you kill X and it has some issue shutting down cleanly.  Is that 
right?

Is this still reproducing on current versions of xorg-server?

While this is a SIGSEGV, I'm only marking major since it's during shutdown.
Comment 4 Chris Wilson 2015-06-16 20:09:46 UTC
Looks like an old DRI2 crash, presuming fixed long ago.


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.