Bug 13215

Summary: [intel-2.1.99]Two xservers can not coexist
Product: xorg Reporter: WuNian <nian.wu>
Component: Driver/intelAssignee: Jesse Barnes <jbarnes>
Status: VERIFIED FIXED QA Contact: Jesse Barnes <jbarnes>
Severity: normal    
Priority: medium CC: jbarnes
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Bug Depends on:    
Bug Blocks: 13027, 13493    
Attachments:
Description Flags
xorg log file none

Description WuNian 2007-11-13 00:44:30 UTC
System Environments:
Kernel: 2.6.23.1
Drm: 2.3.0
Mesa: 7.0.2-rc1
Xf86-video-intel: 2.1.99(2.2 pre-release)
Xserver: 1.4

Bug Descrption:
Two startx(using command:startx -- :n) servers can't coexist:the first one can start as normal,then you start the second one,the screen blink several seconds without any output,then go back to console and display following error messages:
(==) Log file: "/opt/X11R7/var/log/Xorg.2.log", Time: Tue Nov 13 08:38:12 2007
(==) Using config file: "/etc/X11/xorg.conf"
(WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found
(II) Module "ddc" already built-in
(II) Module "i2c" already built-in
(II) Module "ramdac" already built-in
(EE) [drm] Could not set DRM device bus ID.
(EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.
(EE) intel(0): Couldn't allocate video memory

Fatal server error:
AddScreen/ScreenInit failed for driver 0

XIO:  fatal IO error 104 (Connection reset by peer) on X server ":2.0"
      after 0 requests (0 known processed) with 0 events remaining.

at this time,the first xserver still exist and work as normal.

Reproduce steps:
1 startx -- :1
2 startx -- :2
Comment 1 WuNian 2007-11-13 00:47:12 UTC
Created attachment 12499 [details]
xorg log file
Comment 2 WuNian 2007-11-13 00:51:42 UTC
The gm965(64-bit) with the same modules as 915gm(bug machine) doesn't has this problem.
Comment 3 Gordon Jin 2007-11-13 02:01:57 UTC
This is a bit different than bug#12758. The second startx exits immediately.
Comment 4 WuNian 2008-02-14 18:00:27 UTC
The bug does not exist. See bug #12758.

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.