2009/9/6 david <span dir="ltr">&lt;<a href="mailto:gnome@hawaii.rr.com">gnome@hawaii.rr.com</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div class="h5">

Ray Rashif wrote:<br>
&gt; Nope, I don&#39;t have shared audio/video IRQs.<br>
&gt;<br>
&gt; And after further probing, it turns out the intel driver itself is the<br>
&gt; culprit alongside its usage of GEM and KMS in full.<br>
&gt;<br>
&gt; The older xf86-video-intel 2.3.2 has no problem.<br>
<br>
</div></div>Then a bug in the newer driver, or the newer driver is trying to do<br>
something with some hardware feature that stumbles because the newer<br>
driver is being more ambitious than the old?<br>
<div><div class="h5"><br>
--<br>
David<br>
<a href="mailto:gnome@hawaii.rr.com">gnome@hawaii.rr.com</a><br> authenticity, honesty, community</div></div></blockquote><div><br></div><div>Most probably the case, but I&#39;m afraid that it isn&#39;t really a bug for them. If someone could help pinpoint the interfering processes, then it might be worth a shot.</div>

<div><br></div><div>From what I know, there has been quite a lot of change for the better. Interestingly <a href="http://www.phoronix.com/scan.php?page=news_item&amp;px=NjQ3Ng">http://www.phoronix.com/scan.php?page=news_item&amp;px=NjQ3Ng</a> highlights dri_bufmgr, which might just be the one responsible. Then again, this is better discussed with the intel video team so I suppose I should file a feature request. Thanks for the aid!</div>