http://bugs.freedesktop.org/show_bug.cgi?id=27355
--- Comment #9 from Pauli <suok...@gmail.com> 2010-04-01 00:53:27 PST --- > --- Comment #8 from Rafael Antonio Porras Samaniego <sp...@distrobit.net> > 2010-03-31 12:00:24 PST --- > > I know that this is very basic information and possibly not very useful but I > don't know how can I extract more information from my system. Any hint would > be > appreciated. > You need debug symbols for all packages that are used in backtrace. That means --enable-debug when configuring xserver and making sure that symbols are not stripped. For video-ati and libdrm it most likely is just enough that the resulting modules are not stripped. But drmDMA is only called from one place in source. That is when allocating command buffer that will be submitted to GPU. So dmesg is showing that fence counter is not advancing show something is causing GPU hang. Maybe it is something incorrect in composite handler which causes the GPU hang. I don't know exactly but it would help if the currently in processing command buffer would be captured and analyzed what is going into GPU. > P.S.: I work as a coder and I've coded some Linux kernel modules and a driver > for Windows, so I could be more helpful, but I don't have any idea about the > Linux graphics drivers stack so I'm completely lost. Sorry! > PS. When you disable composite that operation is done in software which is expensive per pixel operation. It could be a lot better if disabling all render acceleration until the bug is fixed because fallback code is more expensive than pure software rendering. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
