Bug 12652 - RV370 [FireGL V3100 (PCIE)] Xorg Crash with Option "DRI" "false"
Summary: RV370 [FireGL V3100 (PCIE)] Xorg Crash with Option "DRI" "false"
Status: RESOLVED INVALID
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-02 08:09 UTC by Sebastien Valette
Modified: 2018-03-08 04:46 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
xorg.conf (2.57 KB, text/plain)
2007-10-02 08:10 UTC, Sebastien Valette 		Details
Xorg log (47.04 KB, text/plain)
2007-10-02 08:10 UTC, Sebastien Valette 		Details
gdb backtrace (6.98 KB, text/plain)
2007-10-02 08:11 UTC, Sebastien Valette 		Details
View All

Description Sebastien Valette 2007-10-02 08:09:22 UTC 
Hi,

I'm trying to get a stable way to use my video card. When disabling DRI (adding Option "DRI" "false" to xorg.conf, I can trigger an X crash when running two instances of:
/usr/share/vtk/Rendering/Python/assembly.py

which is a sample programm from the package "python-vtk" on Ubuntu.
the X crash occurs this way : 1- make the windows overlap 2- move one of the two windows so that rendering is triggered on the other window.

I already had such problems, but it was my fault. I hope (and think) that this time I did nothing bad. I join my xorg.conf, xorg log and a gdb backtrace of X.
Comment 1 Sebastien Valette 2007-10-02 08:10:06 UTC 
Created attachment 11861 [details]
xorg.conf
Comment 2 Sebastien Valette 2007-10-02 08:10:31 UTC 
Created attachment 11862 [details]
Xorg log
Comment 3 Sebastien Valette 2007-10-02 08:11:07 UTC 
Created attachment 11863 [details]
gdb backtrace
Comment 4 Alex Deucher 2007-10-02 08:23:19 UTC 
looks like a mesa bug.
Comment 5 Marek Olšák 2011-03-01 14:14:38 UTC 
Is this still an issue with current Mesa git?
Comment 6 Timothy Arceri 2018-03-08 04:46:58 UTC 
No response. Closing.

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.