Bug 23303 (sapienslinux) - Dri enabled freezes my computer
Summary: Dri enabled freezes my computer
Status: RESOLVED INVALID
Alias: sapienslinux
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/r200 (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high critical
Assignee: Default DRI bug account
QA Contact: Alfredo Cabrera
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2009-08-14 07:01 UTC by Alfredo Cabrera
Modified: 2016-02-26 02:27 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Xorg log when it crash (87.53 KB, text/plain)
2009-08-14 07:01 UTC, Alfredo Cabrera
Details
Xorg log when Dri is enabled (90.30 KB, text/plain)
2009-08-14 07:18 UTC, Alfredo Cabrera
Details
Xorg conf disabling Dri an Exa acceleration (2.16 KB, text/plain)
2009-08-14 07:20 UTC, Alfredo Cabrera
Details
Xorg conf with Dri and EXA acceleration method (2.72 KB, text/plain)
2009-08-14 07:24 UTC, Alfredo Cabrera
Details
Xorg log running AGP mode (50.44 KB, text/plain)
2009-08-14 08:34 UTC, Alfredo Cabrera
Details

Description Alfredo Cabrera 2009-08-14 07:01:19 UTC
Created attachment 28625 [details]
Xorg log when it crash

Computer freezes withing minutes when I enabled Dri using Radeon free driver.

When I'm using my computer (visit web-sites, see my e-mail, etc) xorg work correctly during about 10 minutes and then xorg hang and the screen display "Out of range" error. I don't use VLC and Compiz. Compiz can run and VLC too. I tried upgrading radeon driver to 6.12.99 but the problem wasn't solved. 
Then I tried editing xorg.conf:

 - I put Option "AGPMode" "4" in Device section Results: screen display "Without signal error"
 - I change value to 8 Results: screen display "Without signal" error Results: screen display "Without signal error"
 - I change value to 0 Results: screen display "Without signal" error Results: screen display "Without signal error"
 - I change value to 2 Results: screen display "Without signal" error Results: screen display "Without signal error"
 - I change value to 1 Results: screen display "Without signal" error Results: screen display "Without signal error"
 - I delete Option "AGPMode" "4" and I put Option "BusType" "PCI" Results: the problem persist
 - I add Disable "dri2" in Module section Results: the problem persist
 - I remove Disable "dri2" and I add Disable "dri" 

--> Results: problem solved but Compiz can't work and others 3D applications.

Old versions of Ubuntu (8.04 LTS) don't appear this problem

Additional Information:

Distribution: Ubuntu Jaunty 9.04
Graphic card: ATI Radeon 9200 Series
Xorg version: 1.6.3
Screen resolution: 1440x900

Xorg conf now:

# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# Note that some configuration settings that could be done previously
# in this file, now are automatically configured by the server and settings
# here are ignored.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "Device"
Identifier "ATI Technologies, Inc. Radeon 9200"
Driver "radeon"
Option "BusType" "PCI"
EndSection


Section "Monitor"
	Identifier	"Configured Monitor"
EndSection

Section "Modes"
  Identifier   "Modes[0]"
  Modeline      "1024x768" 76.16 1024 1080 1192 1360 768 769 772 800
  Modeline      "1024x768" 64.11 1024 1080 1184 1344 768 769 772 795
  Modeline      "1440x900" 100.000 1440 1456 1464 1480 900 916 924 940 -hsync -vsync
EndSection


Section "Screen"
Identifier "Default Screen"
Device "Yuraku"
Monitor "Generic Monitor"
DefaultDepth 24
Option "AddARGBGLXVisuals" "True"
SubSection "Display"
    Depth      15
    Modes      "1440x900" "1024x768"
  EndSubSection
  SubSection "Display"
    Depth      16
    Modes      "1440x900" "1024x768"
  EndSubSection
  SubSection "Display"
    Depth      24
    Modes      "1440x900" "1024x768"
  EndSubSection
  SubSection "Display"
    Depth      32
    Modes      "1440x900" "1024x768"
  EndSubSection
  SubSection "Display"
    Depth      8
    Modes      "1440x900" "1024x768"
  EndSubSection 
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection

Section "Module"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dbe" #para compiz
Load "extmod"
Load "glx" #para compiz
Load "int10"
Load "vbe"
Disable "dri"
Disable "dri2"
EndSection

Section "DRI"
Group "video"
Mode 0666
EndSection

Section "ServerFlags"
	Option	"DontZap"	"False"
EndSection
Comment 1 Jerome Glisse 2009-08-14 07:08:13 UTC
According to your log DRI is disabled. Please provide a Xorg log with DRI enabled.
Comment 2 Alfredo Cabrera 2009-08-14 07:18:22 UTC
Created attachment 28626 [details]
Xorg log when Dri is enabled
Comment 3 Alfredo Cabrera 2009-08-14 07:20:50 UTC
Created attachment 28628 [details]
Xorg conf disabling Dri an Exa acceleration
Comment 4 Alfredo Cabrera 2009-08-14 07:24:18 UTC
Created attachment 28631 [details]
Xorg conf with Dri and EXA acceleration method
Comment 5 Jerome Glisse 2009-08-14 07:29:12 UTC
So it lockups even when Forced to PCI ? Or only when in AGP ? Please also
provide a Xorg log when in AGP mode.

      
Comment 6 Alfredo Cabrera 2009-08-14 08:34:11 UTC
Created attachment 28634 [details]
Xorg log running AGP mode
Comment 7 Alfredo Cabrera 2009-08-14 08:36:55 UTC
(In reply to comment #5)
> So it lockups even when Forced to PCI ? Or only when in AGP ? Please also
> provide a Xorg log when in AGP mode.
> 
> 
> 

Xorg hang during startup with AGP mode forced. Xorg work during 5 minutes and then hang with PCI mode forced.
Comment 8 Alfredo Cabrera 2009-08-15 08:11:00 UTC
(In reply to comment #0)
> Created an attachment (id=28625) [details]
> Xorg log when it crash
> 
> Computer freezes withing minutes when I enabled Dri using Radeon free driver.
> 
> When I'm using my computer (visit web-sites, see my e-mail, etc) xorg work
> correctly during about 10 minutes and then xorg hang and the screen display
> "Out of range" error. I don't use VLC and Compiz. Compiz can run and VLC too. I
> tried upgrading radeon driver to 6.12.99 but the problem wasn't solved. 
> Then I tried editing xorg.conf:
> 
>  - I put Option "AGPMode" "4" in Device section Results: screen display
> "Without signal error"
>  - I change value to 8 Results: screen display "Without signal" error Results:
> screen display "Without signal error"
>  - I change value to 0 Results: screen display "Without signal" error Results:
> screen display "Without signal error"
>  - I change value to 2 Results: screen display "Without signal" error Results:
> screen display "Without signal error"
>  - I change value to 1 Results: screen display "Without signal" error Results:
> screen display "Without signal error"
>  - I delete Option "AGPMode" "4" and I put Option "BusType" "PCI" Results: the
> problem persist
>  - I add Disable "dri2" in Module section Results: the problem persist
>  - I remove Disable "dri2" and I add Disable "dri" 
> 
> --> Results: problem solved but Compiz can't work and others 3D applications.
> 
> Old versions of Ubuntu (8.04 LTS) don't appear this problem
> 
> Additional Information:
> 
> Distribution: Ubuntu Jaunty 9.04
> Graphic card: ATI Radeon 9200 Series
> Xorg version: 1.6.3
> Screen resolution: 1440x900
> 
> Xorg conf now:
> 
> # xorg.conf (X.Org X Window System server configuration file)
> #
> # This file was generated by dexconf, the Debian X Configuration tool, using
> # values from the debconf database.
> #
> # Edit this file with caution, and see the xorg.conf manual page.
> # (Type "man xorg.conf" at the shell prompt.)
> #
> # This file is automatically updated on xserver-xorg package upgrades *only*
> # if it has not been modified since the last upgrade of the xserver-xorg
> # package.
> #
> # Note that some configuration settings that could be done previously
> # in this file, now are automatically configured by the server and settings
> # here are ignored.
> #
> # If you have edited this file but would like it to be automatically updated
> # again, run the following command:
> #   sudo dpkg-reconfigure -phigh xserver-xorg
> 
> Section "Device"
> Identifier "ATI Technologies, Inc. Radeon 9200"
> Driver "radeon"
> Option "BusType" "PCI"
> EndSection
> 
> 
> Section "Monitor"
>         Identifier      "Configured Monitor"
> EndSection
> 
> Section "Modes"
>   Identifier   "Modes[0]"
>   Modeline      "1024x768" 76.16 1024 1080 1192 1360 768 769 772 800
>   Modeline      "1024x768" 64.11 1024 1080 1184 1344 768 769 772 795
>   Modeline      "1440x900" 100.000 1440 1456 1464 1480 900 916 924 940 -hsync
> -vsync
> EndSection
> 
> 
> Section "Screen"
> Identifier "Default Screen"
> Device "Yuraku"
> Monitor "Generic Monitor"
> DefaultDepth 24
> Option "AddARGBGLXVisuals" "True"
> SubSection "Display"
>     Depth      15
>     Modes      "1440x900" "1024x768"
>   EndSubSection
>   SubSection "Display"
>     Depth      16
>     Modes      "1440x900" "1024x768"
>   EndSubSection
>   SubSection "Display"
>     Depth      24
>     Modes      "1440x900" "1024x768"
>   EndSubSection
>   SubSection "Display"
>     Depth      32
>     Modes      "1440x900" "1024x768"
>   EndSubSection
>   SubSection "Display"
>     Depth      8
>     Modes      "1440x900" "1024x768"
>   EndSubSection 
> EndSection
> 
> Section "Extensions"
> Option "Composite" "Enable"
> EndSection
> 
> Section "Module"
> Load "i2c"
> Load "bitmap"
> Load "ddc"
> Load "dbe" #para compiz
> Load "extmod"
> Load "glx" #para compiz
> Load "int10"
> Load "vbe"
> Disable "dri"
> Disable "dri2"
> EndSection
> 
> Section "DRI"
> Group "video"
> Mode 0666
> EndSection
> 
> Section "ServerFlags"
>         Option  "DontZap"       "False"
> EndSection
> 

Update 15/8/2009: I can use AGP Mode without problems disabling Dri
Comment 9 Alex Deucher 2009-08-17 07:39:50 UTC
(In reply to comment #8)
> 
> Update 15/8/2009: I can use AGP Mode without problems disabling Dri
> 

The AGPMode option is only relevant when the dri is enabled.  Are you saying your system works now with the DRI enabled?  If so, what AGPMode fixed the problem?
Comment 10 Alfredo Cabrera 2009-08-17 08:35:43 UTC
(In reply to comment #9)
> (In reply to comment #8)
> > 
> > Update 15/8/2009: I can use AGP Mode without problems disabling Dri
> > 
> 
> The AGPMode option is only relevant when the dri is enabled.  Are you saying
> your system works now with the DRI enabled?  If so, what AGPMode fixed the
> problem?
> 

No. Dri only run with PCI mode but it work during 5 minutes and then Xorg hang.
Only I can use AGP Mode WITHOUT Dri because it causes X hang during startup.
Comment 11 Alex Deucher 2009-08-17 08:57:31 UTC
(In reply to comment #10)
> Only I can use AGP Mode WITHOUT Dri because it causes X hang during startup.
> 

The AGPMode option does nothing when the DRI is disabled.
Comment 12 Alfredo Cabrera 2009-08-17 09:10:31 UTC
(In reply to comment #11)
> (In reply to comment #10)
> > Only I can use AGP Mode WITHOUT Dri because it causes X hang during startup.
> > 
> 
> The AGPMode option does nothing when the DRI is disabled.
> 

I don't understand. I can run Xorg correctly with AGP Mode without Dri.
Comment 13 Alex Deucher 2009-08-17 10:15:15 UTC
(In reply to comment #12)
> I don't understand. I can run Xorg correctly with AGP Mode without Dri.
> 

The AGPMode option is only relevant when the DRI is enabled since AGP gart is only used when the DRI is enabled.  When the DRI is disabled, the driver ignores the AGPMode option.
Comment 14 Alfredo Cabrera 2009-08-17 10:22:27 UTC
(In reply to comment #13)
> (In reply to comment #12)
> > I don't understand. I can run Xorg correctly with AGP Mode without Dri.
> > 
> 
> The AGPMode option is only relevant when the DRI is enabled since AGP gart is
> only used when the DRI is enabled.  When the DRI is disabled, the driver
> ignores the AGPMode option.
> 

OK. But the problem persist.
Comment 15 Christopher M. Penalver 2016-02-26 02:27:04 UTC
Alfredo Cabrera, Ubuntu Jaunty reached EOL on October 23, 2010. For more on this, please see https://wiki.ubuntu.com/Releases .

If this is reproducible in a supported release, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.


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.