linux-kernel - Re: [Intel-gfx] [3.14.0-rc4] regression: drm FIFO underruns

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]

Date:	Tue, 13 May 2014 17:46:31 +0100
From:	Damien Lespiau <damien.lespiau@...el.com>
To:	Jörg Otte <jrg.otte@...il.com>,
	Ville Syrjälä 
	<ville.syrjala@...ux.intel.com>, David Airlie <airlied@...ux.ie>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Dave Airlie <airlied@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [Intel-gfx] [3.14.0-rc4] regression: drm FIFO underruns

On Tue, May 13, 2014 at 06:38:32PM +0200, Daniel Vetter wrote:
> > Doesn't work for me, I still have an underrun at boot-up.
> 
> I'm at a loss tbh with ideas. We successfully disable both pipes, then
> enable pipe A and it all works.
> 
> Then we enable pipe B and _both_ pipes underrun immediately afterwards.
> Really strange. Can you please reproduce the issue again on
> drm-intel-nightly (latest -nightly should also have the display
> corruptions fixed, so good to retest anyway) and attach a new dmesg with
> drm.debug=0xe.
> 
> Meanwhile I'll try to come up with new theories and ideas.

I do remember a reporter saying a BIOS upgrade fixed that for him. This
is one of the reasons Paulo put that BIOS update message.

It's worth the try if you ask me (the BIOS update will bring new memory
latency values).

-- 
Damien
--
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/