From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 29140] [rs690] Freeze at Xorg startup when using KMS and
multiple screens
Date: Mon, 9 Aug 2010 06:00:26 -0700 (PDT)
Message-ID: <20100809130026.644841300DF@annarchy.freedesktop.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from annarchy.freedesktop.org (annarchy.freedesktop.org
[131.252.210.176])
by gabe.freedesktop.org (Postfix) with ESMTP id 85ED49E7B3
for ;
Mon, 9 Aug 2010 06:00:26 -0700 (PDT)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=29140
--- Comment #8 from steckdenis@yahoo.fr 2010-08-09 06:00:25 PDT ---
Created an attachment (id=37722)
--> (https://bugs.freedesktop.org/attachment.cgi?id=37722)
Strace output when running Xorg
Hello,
I tried today to reproduce this bug using Xorg Git, Linux 2.6.35 and Mesa Git.
The bug happened again, except that I have some very interesting informations
for you.
GDB wasn't helpfull because the bug is in the radeon kernel module. I
discovered that Linux prints to dmesg a complete kernel stacktrace when an
application is locked up by a mutex. By chance, it is just what is happening
with Xorg, so I have a stack trace :
INFO: task Xorg:2948 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Xorg D 00000000ffffc694 0 2948 1 0x00400005
ffff8800683e7788 0000000000000082 ffff880001814f00 ffff8800683a1180
0000000000014f00 0000000000014f00 ffff8800683e7fd8 ffff8800683e7fd8
ffff8800683e7fd8 ffff88006c1df780 ffff8800683e7fd8 0000000000014f00
Call Trace:
[] __mutex_lock_slowpath+0x13f/0x310
[] mutex_lock+0x11/0x30
[] radeon_ring_lock+0x25/0x50 [radeon]
[] r300_gpu_is_lockup+0x71/0x190 [radeon]
[] radeon_fence_wait+0x33e/0x3d0 [radeon]
[] ? autoremove_wake_function+0x0/0x40
[] ? radeon_fence_emit+0xe5/0x130 [radeon]
[] radeon_pm_set_clocks+0x3c8/0x5f0 [radeon]
[] ? __mutex_lock_slowpath+0x233/0x310
[] radeon_pm_compute_clocks+0xd8/0x270 [radeon]
[] atombios_crtc_mode_fixup+0x23/0x40 [radeon]
[] drm_crtc_helper_set_mode+0x15b/0x3f0 [drm_kms_helper]
[] ? r100_cs_packet_next_reloc+0x4a/0x1e0 [radeon]
[] drm_crtc_helper_set_config+0x797/0x820 [drm_kms_helper]
[] ? drm_mode_object_find+0x5f/0x80 [drm]
[] drm_mode_setcrtc+0x2cf/0x3a0 [drm]
[] drm_ioctl+0x37c/0x460 [drm]
[] ? drm_mode_setcrtc+0x0/0x3a0 [drm]
[] vfs_ioctl+0x3c/0xd0
[] do_vfs_ioctl+0x7c/0x500
[] sys_ioctl+0x79/0x90
[] tracesys+0xd9/0xde
To be even more complete, I launched Xorg with strace, to see when all things
are happening. I attached the strace output to this bug.
The last line, that is not complete, is when Xorg tries to call the
DRM_IOCTL_MODE_SETCRTC. The two previous ioctls are DRM_IOCTL_MODE_ADDFB
followed by DRM_IOCTL_MODE_SETGAMMA.
This bug doesn't happen when I use only one monitor (the internal LVDS), but
only when I also use my external VGA monitor (without it, I think
DRM_IOCTL_MODE_SETCRTC is never called).
I use an ATI Radeon X1270 (rs690m with 128Mio sideport memory) on a Packard
Bell Dot/MA.FR netbook (it's the same as the Gateway Gateway LT3103u, but with
a Packard Bell logo on it :) ).
I hope these informations will help you.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.