linux-kernel - Re: [PATCH] drm/i915: Suppress spurious vblank interrupts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110201100833.3219687e@jbarnes-desktop>
Date:	Tue, 1 Feb 2011 10:08:33 -0800
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	unlisted-recipients:; (no To-header on input)
Cc:	Hugh Dickins <hughd@...gle.com>,
	Chris Wilson <chris@...is-wilson.co.uk>,
	Mario Kleiner <mario.kleiner@...bingen.mpg.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drm/i915: Suppress spurious vblank interrupts

On Tue, 1 Feb 2011 09:46:43 -0800
Jesse Barnes <jbarnes@...tuousgeek.org> wrote:

> On Tue, 1 Feb 2011 09:34:12 -0800 (PST)
> Hugh Dickins <hughd@...gle.com> wrote:
> > As you know (I went off-list to send more info at the weekend), this
> > behaviour is very elusive, probably depends on more than one issue,
> > comes and goes with irrelevant patches and config changes and reboots.
> 
> Are you still seeing underruns during normal activity?  I wonder if the
> ones you were seeing before were only reported at 60Hz due to vblank
> interrupt processing.  If we failed to clear the underrun status, we'd
> report one every time we got a vblank interrupt (since the underruns
> don't report interrupts by themselves).
> 
> If so, that may just be a red herring in this case.

More random questions arise from the info provided:
 - why are we ending up in the flip code at all?  fvwm shouldn't
   trigger that path...
 - what's with all the underruns?  it looks like we *do* ack those
   flags as needed, so apparently they're valid, but they indicate a
   serious problem with the display pipeline; maybe self-refresh
   shouldn't be enabled on your system (that would increase memory
   latency and potentially cause underruns), running with
   i915.powersave=0 would disable that feature

The lack of text really does sound like a render cache flushing
problem, but the other issues are worrying as well, and could be
compounding things.  And the last time I saw the issue, it was related
to compositing and required an X server fix.  But supposedly you're not
using compositing, so...

-- 
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/