Bug 22311

Summary: Both X servers hang when starting firefox in second X server with modeset enabled and DRI disabled
Product: xorg Reporter: Robin Green <greenrd>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED INVALID QA Contact: Xorg Project Team <xorg-team>
Severity: critical    
Priority: medium    
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Log from second X server none

Description Robin Green 2009-06-16 00:01:25 UTC 
Created attachment 26825 [details]
Log from second X server

How reproducable: Always

Steps to reproduce:
1. Boot (runlevel 5, graphical login)
2. Switch to virtual terminal 2
3. type "X :1&"
4. Switch back to virtual terminal 2
5. type "kwin&firefox"
6. Wait for disk activity to cease
7. Switch to second X server (on Fedora 11, this will be on virtual terminal 7 by default)

Results:
Cursor disappears, screen does not switch to X server, machine unresponsive, cannot switch virtual terminal or use CTRL+ALT+BACKSPACE, but ssh still works. Both X servers are at 50% CPU. If I kill the second X server, the first goes to 100% CPU and requires killing as well. After that the machine is unusable (except through ssh).

It all works if I add nomodeset to the kernel command line.
Comment 1 Robin Green 2009-06-16 03:40:39 UTC 
This occurred because DRI was disabled, because my Virtual was too big. I set
my Virtual to the same resolution as the physical screen, and now DRI works and
this hang does not occur.

Changed bug summary accordingly.
Comment 2 Alex Deucher 2010-10-19 17:26:57 UTC 
Is this still an issue with kms or a newer version of the driver?
Comment 3 Adam Jackson 2018-06-12 19:09:36 UTC 
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.

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.