lkml.org 
[lkml]   [2012]   [May]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: i915_driver_irq_handler: irq 42: nobody cared
    On 04/11/2012 12:40 PM, Daniel Vetter wrote:
    > On Tue, Apr 10, 2012 at 01:34:11PM -0700, Jesse Barnes wrote:
    >> On Tue, 10 Apr 2012 22:32:12 +0200
    >> Daniel Vetter <daniel@ffwll.ch> 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:
    >>>> http://cgit.freedesktop.org/~ickle/linux-2.6/commit/?h=for-jiri&id=79710e6ccabdac80c65cd13b944695ecc3e42a9d
    >>>
    >>> 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).

    Hi and sorry for the delay. It stays INTx-. And I tested that with patch
    removing fencing.

    > Shot in the dark, let's disable msi a bit. Can you try the below patch?

    Yeah, no IRQ_NONE at the end of i915_driver_irq_handler now. So MSI is
    busted, either in the card, the chipset or the kernel. Any idea how to
    find out?

    thanks,
    --
    js
    suse labs




    \
     
     \ /
      Last update: 2012-05-03 22:21    [W:0.041 / U:1.364 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site