Bug 2537 - Multiple X servers lock up Savage
Summary: Multiple X servers lock up Savage
Status: RESOLVED NOTABUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/savage (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-14 07:10 UTC by Maarten Wisse
Modified: 2005-04-13 08:18 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Log (37.82 KB, text/x-log)
2005-02-14 07:12 UTC, Maarten Wisse
no flags Details

Description Maarten Wisse 2005-02-14 07:10:27 UTC
Distro: Gentoo   
Xorg: 6.8.1.904   
CVS snapshot savage driver: 09-02-2005   
Hardware: Acer Aspire 1312LC with ProSavageDDR   
Kernel: 2.6.10-gentoo-r4   
 
When having logged in via kdm as normal user, I switch to vt 1 with 
Ctrl-Alt-F1, log in as root and type: 
 
$ startx -- :1 
 
X starts, but slows down and eventually locks up the machine. Apart from the 
DRI being disabled on :1, no strange things appear in Xorg.1.log (attached). 
 
This was possible with the older driver.
Comment 1 Maarten Wisse 2005-02-14 07:12:07 UTC
Created attachment 1900 [details]
Log
Comment 2 Felix Kühling 2005-04-09 05:37:02 UTC
I'm almost certain this problem is related to shadow status. It locks up on
ProSavageDDR when DRI is disabled, so your first Xserver works and your second
one without DRI locks up the chip.

In the latest driver you don't need to enable ShadowStatus explicitly any more.
It will be enabled automatically when DRI is available or disabled when DRI is
not available. Just update Xorg from CVS and remove (or comment out) the
ShadowStatus option from your xorg.conf.

I'm closing this as NOTABUG. Feel free to reopen it if this doesn't fix your
problem.
Comment 3 Maarten Wisse 2005-04-14 01:18:37 UTC
Solved according to your suggestions. Thanks. 


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.