[lkml]   [2012]   [Apr]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: i915_driver_irq_handler: irq 42: nobody cared
    On Tue, 10 Apr 2012 22:32:12 +0200
    Daniel Vetter <> wrote:

    > On Tue, Apr 10, 2012 at 09:52:40PM +0200, Jiri Slaby wrote:
    > > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
    > > <TAbort- <MAbort- >SERR- <PERR- INTx-
    > >
    > > I tried 3.2 and 3.3. Although the spurious interrupts were always
    > > there, they occurred with frequency lower by a magnitude (15 vs. 300
    > > after X starts). So I bisected that and it lead to a commit which
    > > fixes bad tiling for me:
    > >
    > Pipelined fencing is pretty much just broken and we'll completely rip it
    > out in 3.5. Does this also happen with 3.4-rc2?

    Does INTx- stay that way? Or does it frequently read INTx+ if you
    sample it a lot? If it stays as INTx-, then something other than the
    GPU is getting stuck (though it's possible this could be related to
    pipelined fencing, if the fences are programmed to point at some funky
    memory space).

    Jesse Barnes, Intel Open Source Technology Center
    [unhandled content-type:application/pgp-signature]
     \ /
      Last update: 2012-04-10 22:37    [W:0.025 / U:2.156 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site