View previous topic :: View next topic |
Author |
Message |
Melior n00b
Joined: 30 Jul 2006 Posts: 10
|
Posted: Tue Nov 06, 2007 11:12 am Post subject: ATI trouble: (EE) fglrx(1): [DRI] Locking deadlock. |
|
|
Hi to everybody,
recently I decided do update my xorg-server from 1.3 to 1.4 to solve the annoying dual monitor bugs (i.e. strange resolution, java crashing etc...).
I emerged the 1.4 with all the dependency... patch the ATI drivers ebuild to emerge the ati-drivers-8.40.4 and now I have this problem: when the second monitor is plugged, I have this message in Xorg.0.log
Quote: |
(EE) fglrx(1): [DRI] Locking deadlock.
Already locked with context 136875420,
trying to lock with context 2.
(II) fglrx(1): [drm] installed DRM signal handler
(II) fglrx(1): DRIScreenInit done
(EE) fglrx(1): Failed to allocate 2 sample depthMultiSampleBuffer buffer.
(EE) fglrx(1): Disabling Multisample.
|
All the software using OPENGL/3D and grlxinfo&co. freeze...
Any idea?!?
Currently I have installed:
gentoo-sources-2.6.22-r9
ati-drivers-8.40.4
xorg-server-1.4-r2
and my ATI card is a X600.
Note1: without the second monitor all works perfectly!!
Note2: I find another guy with the same problem (http://www.rage3d.com/board/showthread.php?p=1335208086), the only difference is the ati-drivers (he installed ati-drivers-8.42.3)... perhaps could it be a problem of xorg-server-1.4?!?!?
Thanks!!!
Melior |
|
Back to top |
|
|
Mit Apprentice
Joined: 13 Apr 2003 Posts: 260 Location: Under a rock.
|
Posted: Wed Nov 14, 2007 9:23 am Post subject: |
|
|
I get the same error on two machines here in the office, both of them are running dual screen with the latest FGLRX driver.
Code: |
(EE) fglrx(1): [DRI] Locking deadlock.
Already locked with context 153950604,
trying to lock with context 2.
(EE) fglrx(1): [DRI] Unlocking inconsistency:
Context 153950604 trying to unlock lock held by context 2
(EE) fglrx(1): [DRI] Locking deadlock.
Already locked with context 153950604,
trying to lock with context 2.
|
_________________ Tim
Personal Site
FeedJuggler - RSS Made Easy
The TV Guide |
|
Back to top |
|
|
verdeboy2k n00b
Joined: 27 May 2006 Posts: 23
|
Posted: Tue Nov 20, 2007 10:23 am Post subject: |
|
|
I had this problem with xorg-server-1.4-r2. Downgraded to xorg-server-1.3.0.0-r2 and all is well (DRI, AIGLX, the works). |
|
Back to top |
|
|
Mit Apprentice
Joined: 13 Apr 2003 Posts: 260 Location: Under a rock.
|
Posted: Thu Nov 22, 2007 10:05 am Post subject: |
|
|
Just tried with the newest ati drivers released yesterday - still no joy.
Already using xorg-server 1.3 _________________ Tim
Personal Site
FeedJuggler - RSS Made Easy
The TV Guide |
|
Back to top |
|
|
ok Guru
Joined: 11 Jul 2006 Posts: 390 Location: germany
|
Posted: Fri Nov 30, 2007 11:47 pm Post subject: |
|
|
Mit wrote: | I get the same error on two machines here in the office, both of them are running dual screen with the latest FGLRX driver.
Code: |
(EE) fglrx(1): [DRI] Locking deadlock.
Already locked with context 153950604,
trying to lock with context 2.
(EE) fglrx(1): [DRI] Unlocking inconsistency:
Context 153950604 trying to unlock lock held by context 2
(EE) fglrx(1): [DRI] Locking deadlock.
Already locked with context 153950604,
trying to lock with context 2.
|
| I have the same error. Still no solution with xorg-server-1.4-r2 and fglrx? |
|
Back to top |
|
|
OPelerin Guru
Joined: 17 Jul 2004 Posts: 354 Location: Belgium
|
Posted: Wed Dec 26, 2007 8:16 pm Post subject: |
|
|
Same on my
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
(II) ATI Proprietary Linux Driver Version Identifier:8.44.3
(II) ATI Proprietary Linux Driver Release Identifier: UNSUPPORTED-8.443.1
(II) ATI Proprietary Linux Driver Build Date: Dec 19 2007 21:29:14
(EE) fglrx(1): [DRI] Locking deadlock.
Already locked with context 137137588,
trying to lock with context 2.
(EE) fglrx(1): [DRI] Unlocking inconsistency:
Context 137137588 trying to unlock lock held by context 2
(EE) fglrx(1): [DRI] Locking deadlock.
Already locked with context 137137588,
trying to lock with context 2.
If only 1 screen is on..... No issues....
As well, I cannot use 1600x1050 resolution on screen 0 anymore.... Really wierd _________________ Olivier PELERIN |
|
Back to top |
|
|
OPelerin Guru
Joined: 17 Jul 2004 Posts: 354 Location: Belgium
|
Posted: Wed Dec 26, 2007 8:39 pm Post subject: |
|
|
Playing a bit, Now I've a workaround.
My previous xorg config [ where the issue is seen because using 2 different X engine ].
Quote: |
cat /etc/X11/xorg.conf.newgeneration
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "aticonfig-Screen[0]" 0 0
Screen "aticonfig-Screen[1]" Above "aticonfig-Screen[0]"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/OTF"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
EndSection
Section "Module"
Load "glx"
Load "extmod"
Load "xtrap"
Load "record"
Load "GLcore"
Load "dbe"
Load "dri"
Load "freetype"
Load "type1"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[1]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
BusID "PCI:1:0:0"
EndSection
Section "Device"
Identifier "aticonfig-Device[1]"
Driver "fglrx"
BusID "PCI:01:0:0"
Screen 1
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1680x1050"
EndSubSection
EndSection
Section "Screen"
Identifier "aticonfig-Screen[1]"
Device "aticonfig-Device[1]"
Monitor "aticonfig-Monitor[1]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection
|
Now after issueing aticonfig --dtop horizontal --overlay-on 1
then everything is fine..... No locks, glxgears works fast. All good
Quote: |
cat /etc/X11/xorg.conf
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/OTF"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
EndSection
Section "Module"
Load "glx"
Load "extmod"
Load "xtrap"
Load "record"
Load "GLcore"
Load "dbe"
Load "dri"
Load "freetype"
Load "type1"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[1]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
Option "DesktopSetup" "vertical"
Option "OverlayOnCRTC2" "1"
BusID "PCI:1:0:0"
EndSection
Section "Device"
Identifier "aticonfig-Device[1]"
Driver "fglrx"
BusID "PCI:01:0:0"
Screen 1
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1680x1050"
EndSubSection
EndSection
Section "Screen"
Identifier "aticonfig-Screen[1]"
Device "aticonfig-Device[1]"
Monitor "aticonfig-Monitor[1]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection
|
_________________ Olivier PELERIN |
|
Back to top |
|
|
ok Guru
Joined: 11 Jul 2006 Posts: 390 Location: germany
|
Posted: Fri Dec 28, 2007 12:14 am Post subject: |
|
|
I changed my aticonfig settings to bigdesktop, too. But this is only a workaround.
Now you can delete the unnecessary lines in xorg.conf, because you only use one screen, one monitor and one device.
If you are using different resolutions, the device-section have to be modified.
Bigdesktop can be supported by KDE: Control Center->Peripherals->Display->Multiple Monitors. |
|
Back to top |
|
|
OPelerin Guru
Joined: 17 Jul 2004 Posts: 354 Location: Belgium
|
Posted: Fri Jan 25, 2008 9:04 pm Post subject: |
|
|
Just tested latest greatest ATI 8.1 catalyst release.
Issue remains the same....
Anybody have any workaround to use 2 different X? _________________ Olivier PELERIN |
|
Back to top |
|
|
Johnny_Bit Apprentice
Joined: 30 Aug 2005 Posts: 246 Location: Poland
|
Posted: Sat Feb 09, 2008 10:17 am Post subject: |
|
|
Seems taht the best workaround is to use xorg-server 1.3 series until AMD/ATi fully supports 1.4 |
|
Back to top |
|
|
Chewi Developer
Joined: 01 Sep 2003 Posts: 886 Location: Edinburgh, Scotland
|
Posted: Fri Feb 15, 2008 12:09 am Post subject: |
|
|
Just tried 8.2 even though it hasn't hit Portage yet. The issue is still there. I've only just got this card so at least I now know that it SHOULD work. |
|
Back to top |
|
|
|