Bug 20351

Summary: [x700][EXA] lockups with >=xf86-video-ati-6.10.0
Product: xorg Reporter: Janos Zsitvai <zsitvaij>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: remi
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
URL: https://bugs.gentoo.org/show_bug.cgi?id=259991
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
xorg.conf none

Description Janos Zsitvai 2009-02-27 03:45:05 UTC
Created attachment 23366 [details]
xorg.conf

Steps to reproduce:

1. use EXA with EXAVSync option enabled
2. launch 1-2 instances of konsole or konqueror (3.5.10)

This results in an immediate lockup. Two cases:
a. If the kernel drm and radeon modules are loaded and DRI works, this means that the mouse can still move sluggishly across the screen, sysrq commands work, and commands will still work from an existing ssh session. It is not possible to switch to VT or launch a new and working X instance.

b. Without the kernel modules, the lockup is complete. No sysrq commands work, mouse doesn't move, ssh session is lost.

System:
OS: Gentoo
kernel: 2.6.28-gentoo-r2 (uvesafb is used with v86d-0.1.9)
xorg-server: 1.5.3-r2 (also tested with 1.6.0)
mesa: 7.3
libdrm: 2.4.5

Using git-bisect on xf86-video-ati, it seems that the guilty commit is http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/commit/?id=4d98acbca2e630056bf56cdcd0e23007fded2ced (between versions 6.9.0 and 6.10.0).

Bugs #13998 and #18664 might be related to this one.

Nothing shows up about the lockup in Xorg.0.log, dmesg or messages.

Removing EXAVSync from the device options means that no immediate lockup occurs on launching qt3 using applications, but that might only postpone it.
Comment 1 Janos Zsitvai 2009-02-27 04:03:48 UTC
(added originating Gentoo bug URL)
Comment 2 Alex Deucher 2009-02-27 06:07:56 UTC
There's a reason EXAVsync is disabled by default.

*** This bug has been marked as a duplicate of bug 19267 ***

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.