dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29140] [rs690] Freeze at Xorg startup when using KMS and multiple screens
Date: Thu, 12 Aug 2010 09:57:45 -0700 (PDT)	[thread overview]
Message-ID: <20100812165745.605FF1300EF@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-29140-502@http.bugs.freedesktop.org/>

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

--- Comment #9 from steckdenis@yahoo.fr 2010-08-12 09:57:45 PDT ---
Hello,

I think I found the problem, but I am unfortunately unable to fix it (I don't
know the radeon module enough).

A change between the 2.6.34 and 2.6.35 kernels added a bunch of functions in
drivers/gpu/drm/radeon/radeon_pm.c. The function that causes troubles to me is
radeon_pm_set_clocks(struct radeon_device *rdev); .

This function begins by locking three mutexes, including rdev->cp.mutex.

My card is a r300, so the code goes through the "else" branch of the if. This
branch contains a call to radeon_fence_emit.

Now in radeon_fence.c . I don't know how, but this function happens to call
radeon_fence_wait. The problem is that radeon_fence_wait calls
r300_gpu_is_lockup, by branching in "if
(unlikely(!radeon_fence_signaled(fence))) {".

In r300.c : r300_gpu_is_lockup, called by radeon_fence_wait, calls
radeon_ring_lock, because it wants to write in the ring.

In radeon_ring.c : radeon_ring_lock begins by calling
"mutex_lock(&rdev->cp.mutex);", the exact same mutex as the one already locked
by radeon_pm_set_clocks. That seems to be the problem.

Cheers.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2010-08-12 16:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-18 14:34 [Bug 29140] New: [rs690] Freeze at Xorg startup when using KMS bugzilla-daemon
2010-07-18 16:09 ` [Bug 29140] " bugzilla-daemon
2010-07-23  9:05 ` bugzilla-daemon
2010-08-06  9:52 ` bugzilla-daemon
2010-08-06  9:52 ` [Bug 29140] [rs690] Freeze at Xorg startup when using KMS and multiple screens bugzilla-daemon
2010-08-09 13:00 ` bugzilla-daemon
2010-08-12 16:57 ` bugzilla-daemon [this message]
2010-08-12 23:17 ` bugzilla-daemon
2010-08-13  7:55 ` bugzilla-daemon
2010-08-13 14:54 ` bugzilla-daemon
2010-08-16 17:15 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100812165745.605FF1300EF@annarchy.freedesktop.org \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox