[Bug 29140] [rs690] Freeze at Xorg startup when using KMS and multiple screens

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=29140

--- Comment #8 from steckdenis at 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:
 [<ffffffff81356bef>] __mutex_lock_slowpath+0x13f/0x310
 [<ffffffff81356dd1>] mutex_lock+0x11/0x30
 [<ffffffffa04feba5>] radeon_ring_lock+0x25/0x50 [radeon]
 [<ffffffffa0511f01>] r300_gpu_is_lockup+0x71/0x190 [radeon]
 [<ffffffffa04e753e>] radeon_fence_wait+0x33e/0x3d0 [radeon]
 [<ffffffff8106f610>] ? autoremove_wake_function+0x0/0x40
 [<ffffffffa04e6f85>] ? radeon_fence_emit+0xe5/0x130 [radeon]
 [<ffffffffa0545a58>] radeon_pm_set_clocks+0x3c8/0x5f0 [radeon]
 [<ffffffff81356ce3>] ? __mutex_lock_slowpath+0x233/0x310
 [<ffffffffa0546908>] radeon_pm_compute_clocks+0xd8/0x270 [radeon]
 [<ffffffffa04dadf3>] atombios_crtc_mode_fixup+0x23/0x40 [radeon]
 [<ffffffffa044a06b>] drm_crtc_helper_set_mode+0x15b/0x3f0 [drm_kms_helper]
 [<ffffffffa0506a7a>] ? r100_cs_packet_next_reloc+0x4a/0x1e0 [radeon]
 [<ffffffffa044abe7>] drm_crtc_helper_set_config+0x797/0x820 [drm_kms_helper]
 [<ffffffffa03e6ccf>] ? drm_mode_object_find+0x5f/0x80 [drm]
 [<ffffffffa03e7f9f>] drm_mode_setcrtc+0x2cf/0x3a0 [drm]
 [<ffffffffa03da99c>] drm_ioctl+0x37c/0x460 [drm]
 [<ffffffffa03e7cd0>] ? drm_mode_setcrtc+0x0/0x3a0 [drm]
 [<ffffffff8112d04c>] vfs_ioctl+0x3c/0xd0
 [<ffffffff8112d62c>] do_vfs_ioctl+0x7c/0x500
 [<ffffffff8112db29>] sys_ioctl+0x79/0x90
 [<ffffffff8100a017>] 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.