intel graphics loosing msi interrupt on subsequent starts
shuvaev at physik.uni-wuerzburg.de
Mon May 4 22:32:04 UTC 2009
On Mon, May 04, 2009 at 02:05:41PM -0500, Robert Noland wrote:
> On Mon, 2009-05-04 at 20:40 +0200, Alexey Shuvaev wrote:
> > Hello all!
> > Sorry if it is already reported...
> > I have recently upgaded X server from 1.4 to 1.6
> > (ports from ~23.01.2009 -> 03.05.2009).
> > On the first start everything works ok (including [glx]gears).
> > On the second and subsequent starts everything looks working but jerky,
> > I need to move mouse around to get some windows redrawn,
> > [glx]gears print warning message about not getting vblank interrupts
> > and outputs something about 1-2 frames per 5 seconds.
> > The inspectation with vmstat -i has shown that the card generates
> > interrupts only during the first start of X server.
> > If I set hw.pci.enable_msi="0" everything is working fine (start X server
> > multiple times, switch consoles, [glx]gears, number of irq16-s
> > is increasing, ...).
> irq16 is likely shared, so this may or may not be true... At least in
> some cases, I was seeing the interrupt handler processing events when
> some other device on the shared interrupt fired. Interrupts on Intel
> have been a real pain. There is a drm specific tuneable for disabling
> msi hw.drm.msi=0. I have a patch which I'm currently using on my g45
> that overhauls the way that we handle interrupts.
> Reports have been mixed with this, but it is working for me...
So far works for me too...
irq256: vgapci0 7759 21
More information about the freebsd-current