Keith Packard schrieb: > On Wed, 2008-12-03 at 23:52 +0100, Pierre Willenbrock wrote: >> Keith Packard schrieb: >>> Here's a patch which switches from using pipestat to using iir to see >>> vblank interrupts. I'm wondering what this will do on machines where >>> people are seeing interrupts get stuck on (and then disabled by the >>> kernel). >>> >>> If you're having any IRQ issues, please give this a try and let me know >>> what you discover. >> With this patch, my machine behaves essentially the same as without. >> After some time the irq gets stuck. Adding the 1000 loop delay at the >> end of the for loop(see bug 18609) helped, meaning i am still waiting >> for the irq to get stuck. > > What chip is this? Are you on MSI? What happens when you remove the > looping behaviour from the IRQ handler?
Not looping in the irq-handler seems to work (so far, at least). This is a GM965(pci product-id: 2a02, revision 0x0c). Kernel is currently from git: drm-intel, for-airlied: 728ced8c47f99a2287cdd0d3e77f5ae1a3d410e6, with the addition of my agp patch(currently in airlieds git: agp-2.6, agp-fixes), your patch from the initial mail, and some unrelated patches. I guess this answers the question for MSI? In userland, i am using git of xserver, mesa, drm, xf86-video-intel, all updated fairly recently. Regards, Pierre ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
