Bug 22941 - [945GME KMS] Sending SIGINT to single process running in X hangs tty console.
Summary: [945GME KMS] Sending SIGINT to single process running in X hangs tty console.
Status: RESOLVED DUPLICATE of bug 20516
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Eric Anholt
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-24 17:19 UTC by Eric Smith
Modified: 2009-09-24 19:42 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Eric Smith 2009-07-24 17:19:15 UTC 
I'm using 2.6.31-rc4 with libdrm, xorg-server, xf86-video-intel, and all X related packages built from git masters.

My tty console will hang and not respond to the keyboard after killing a single X program with crtl-c.  I can recover by sshing in and starting another X session.

Steps to reproduce:
1. tty1: X &
2. ctrl-alt-1 to return to tty1
3. tty1: export DISPLAY=:0
4. tty1: xterm
5. tty1 ctrl-c


Trace from my Xorg.0.log:
Backtrace:
0: X(xorg_backtrace+0x28) [0x469d18]
1: X [0x46da9e]
2: /lib/libpthread.so.0 [0x7f7172bd31b0]
3: /usr/lib/libdrm_intel.so.1(drm_intel_bo_alloc+0x3) [0x7f716ff499c3]
4: /usr/lib64/xorg/modules/drivers/intel_drv.so [0x7f717018a46f]
5: /usr/lib64/xorg/modules/drivers/intel_drv.so [0x7f717018afc6]
6: /usr/lib64/xorg/modules/drivers/intel_drv.so [0x7f717017d477]
7: /usr/lib64/xorg/modules/drivers/intel_drv.so [0x7f7170183f48]
8: X(AddScreen+0x1cf) [0x42c5ef]
9: X(InitOutput+0x797) [0x47c0a7]
10: X [0x425e4d]
11: /lib/libc.so.6(__libc_start_main+0xfd) [0x7f71719a2a3d]
12: X [0x425b79]
Segmentation fault at address (nil)

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting
Comment 1 Eric Anholt 2009-09-24 19:42:56 UTC 

*** This bug has been marked as a duplicate of bug 20516 ***

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.