On Sat, 6 Sep 2008 11:19:19 +0200 Roberto Oppedisano <[EMAIL PROTECTED]> wrote:
> When switching from kwin composite wm (KDE 4.1) to compiz I often hit the
> following error:
>
> Sep 6 10:24:31 poppero1 kernel: [ 186.138203] [drm:radeon_cp_idle] *ERROR*
> radeon_cp_idle called without lock hel
> > > > Sep 6 10:24:31 poppero1 kernel: [ 186.138774] [drm:radeon_cp_start]
> > > > *ERROR* radeon_cp_start called without lock held, held 0 owner
> > > > f726bc80 f68f6840
> > > > Sep 6 10:24:31 poppero1 kernel: [ 186.138968] [drm:radeon_cp_idle]
> > > > *ERROR* radeon_cp_idle called with
http://bugs.freedesktop.org/show_bug.cgi?id=17075
--- Comment #21 from Doron <[EMAIL PROTECTED]> 2008-09-09 01:42:58 PST ---
OK, better luck this time...
I read about no stripping and some compiler flags and re-compiled
X, DRM and xf86-video-ati (again...).
I also found the way to turn on the
http://bugs.freedesktop.org/show_bug.cgi?id=17075
--- Comment #23 from Michel Dänzer <[EMAIL PROTECTED]> 2008-09-09 02:41:36 PST
---
(In reply to comment #20)
> I'd like to report that I had pretty similar problems.
> Had them with kernels 2.6.25 and .26, but they happen randomly, when I use
On Tue, 9 Sep 2008 09:37:32 +0200 Roberto Oppedisano <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 08, 2008 at 09:08:36PM -0700, Andrew Morton wrote:
> > On Sat, 6 Sep 2008 11:19:19 +0200 Roberto Oppedisano <[EMAIL PROTECTED]>
> > wrote:
> >
> > > When switching from kwin composite wm (KDE 4.1) to co
http://bugs.freedesktop.org/show_bug.cgi?id=17075
--- Comment #22 from Michel Dänzer <[EMAIL PROTECTED]> 2008-09-09 02:33:45 PST
---
(In reply to comment #21)
> #3 0xb79d2534 in RADEONWaitForIdleCP (pScrn=0xa126fd0) at
> radeon_commonfuncs.c:697
Okay, so this does look like a GPU lockup af
Dave Airlie ha scritto, Il 09/09/2008 10.15:
> Sep 6 10:24:31 poppero1 kernel: [ 186.138774] [drm:radeon_cp_start]
> *ERROR* radeon_cp_start called without lock held, held 0 owner f726bc80
> f68f6840
> Sep 6 10:24:31 poppero1 kernel: [ 186.138968] [drm:radeon_cp_idle]
>
http://bugs.freedesktop.org/show_bug.cgi?id=17491
--- Comment #6 from Tomas Carnecky <[EMAIL PROTECTED]> 2008-09-09 03:58:43 PST
---
The 'error message' (Failed to initialize TTM buffer manager) is just a
warning. You are using a drm kernel driver that doesn't support TTM. But that's
nothing
http://bugs.freedesktop.org/show_bug.cgi?id=17075
--- Comment #24 from Doron <[EMAIL PROTECTED]> 2008-09-09 04:39:11 PST ---
(In reply to comment #22)
> Okay, so this does look like a GPU lockup after all. Can you get a backtrace
> with the DRI disabled as well? GPU lockups are unusual with t
http://bugs.freedesktop.org/show_bug.cgi?id=17491
--- Comment #7 from Maciej Józiewicz <[EMAIL PROTECTED]> 2008-09-09 04:54:48
PST ---
I emerged driconf and disabled vblank-sync. Everything seems to work now.
glxgears looks normal and does slightly over 600 fps. It's slow but it works :)
Sup
http://bugs.freedesktop.org/show_bug.cgi?id=17075
--- Comment #25 from Michel Dänzer <[EMAIL PROTECTED]> 2008-09-09 04:44:03 PST
---
(In reply to comment #24)
> I tried several times repeating it with DRI off. The problem is much more
> intense. ie- Once X hangs, gdb hangs as well, including
http://bugs.freedesktop.org/show_bug.cgi?id=17075
--- Comment #26 from Doron <[EMAIL PROTECTED]> 2008-09-09 07:07:02 PST ---
Hi Michel.
I tried RenderAccel off, but no real change.
So I remarked NoAccel, and added DRI off.
I'm attaching gdb log. I used RADEONEnterVT as a break point.
It look
http://bugs.freedesktop.org/show_bug.cgi?id=17075
--- Comment #27 from Doron <[EMAIL PROTECTED]> 2008-09-09 07:09:24 PST ---
Created an attachment (id=18782)
--> (http://bugs.freedesktop.org/attachment.cgi?id=18782)
gdb tracing with break point.
--
Configure bugmail: http://bugs.freedeskt
http://bugs.freedesktop.org/show_bug.cgi?id=17075
--- Comment #28 from Michel Dänzer <[EMAIL PROTECTED]> 2008-09-09 07:31:20 PST
---
(In reply to comment #26)
> Can you have a look and see ?
I've never seen this kind of gdb output, and looking at it I can't help but
feeling like looking for
http://bugs.freedesktop.org/show_bug.cgi?id=17075
--- Comment #28 from Michel Dänzer <[EMAIL PROTECTED]> 2008-09-09 07:31:20 PST
---
(In reply to comment #26)
> Can you have a look and see ?
I've never seen this kind of gdb output, and looking at it I can't help but
feeling like looking for
http://bugs.freedesktop.org/show_bug.cgi?id=17075
--- Comment #30 from Michel Dänzer <[EMAIL PROTECTED]> 2008-09-09 08:15:35 PST
---
(In reply to comment #29)
> Program received signal SIGUSR1, User defined signal 1.
> 0xb7f47424 in __kernel_vsyscall ()
> Run till exit from #0 0xb7f47424 in
On Thu, 2008-08-28 at 14:24 +0100, Johannes Engel wrote:
> Hi guys,
>
> since I do not quite know who is the culprit for that problem, I want to
> ask here first before filing a bug report. Maybe one of you has got an
> idea how to deal with that.
> The problem is as follows:
>
> Using kernel 2
http://bugs.freedesktop.org/show_bug.cgi?id=17426
Gordon Jin <[EMAIL PROTECTED]> changed:
What|Removed |Added
AssignedTo|dri-|[EMAIL PROTECTED]
http://bugs.freedesktop.org/show_bug.cgi?id=17415
haihao <[EMAIL PROTECTED]> changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
19 matches
Mail list logo
