s try to reproduce the problem, even if you aren't
> able to.
https://bugs.freedesktop.org/show_bug.cgi?id=32534
https://bugs.kde.org/show_bug.cgi?id=252817
https://bugzilla.redhat.com/show_bug.cgi?id=691084
--
==========
iscussion on xorg-devel. (Talk about
"making the perfect the enemy of the good!") I have posted my results
there; perhaps that will get things moving.
Thanks!
--
============
Ian Pilcher
35452>
>
> This affects other driver's too, right? Shouldn't the component gets
> changed in the bug report? (still re-reading the whole thread)
It definitely affects at least intel and radeon, and the fix is in the
X server, so that makes sense.
--
====
situation tends to make me believe
that it should be handled somehow.)
Any pointers are appreciated.
Thanks!
--
======
!
--
Ian Pilcher arequip...@gmail.com
"If you're going to shift my paradigm ... at least buy me di
stuck semaphore on blt ring
(Bugzilla'ed at https://bugzilla.redhat.com/show_bug.cgi?id=692334.)
--
========
Ian Pilcher arequip...@gmail.com
"If you're going to shift my par
On 03/31/2011 04:05 PM, Chris Wilson wrote:
> On Thu, 31 Mar 2011 15:01:53 -0500, Ian Pilcher wrote:
>>
>> Mar 30 20:47:16 ian kernel: [ 233.620717] [drm:i915_hangcheck_elapsed]
>> *ERROR*
>> Hangcheck timer elapsed... GPU hung
>
> Ah.
(My experience
with git is very limited.)
Also, with the latest Fedora kernel I now see the problem even with
drm.debug=14. dmesg is at
https://bugzilla.redhat.com/show_bug.cgi?id=692334.
Thanks!
--
==========
I can see gkrellm chugging along, but I'm
unable do actually do anything in X.
(Note, however, that the system is still OK. I can ssh in, downgrade
the mesa packages, restart X, and be up and running.)
Looks like I will be bisecting ...
--
=======
ve
done a bunch of "desktop cube" switches. Etc., etc.
Even with 7.10, which I had believed to be solid, I can easily produce
a GPU hang by moving a glxgears window.
:-(
--
========
Ian Pilcher
I be looking for?
Thanks!
--
========
Ian Pilcher arequip...@gmail.com
"If you're going to shift my paradi
On 04/18/2011 02:09 PM, Ian Pilcher wrote:
> http://lwn.net/Articles/283798/ mentions a DRM_IOCTL_GEM_CREATE ioctl,
> but it doesn't appear to actually exist on my system. Because of this,
> I'm currently logging DRM_IOCTL_GEM_{CLOSE,FLINK,OPEN}, but I'm unable
> to
obvious next step is to patch Mesa to report the error back to the
application. How is this done?
Thanks!
--
Ian Pilcher arequip...@gmail.com
"If you're going to shift m
13 matches
Mail list logo