linux-kernel - Re: [Intel-gfx] Excessive WARN()s in Intel 915 driver

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: <Pine.LNX.4.44L0.1401301051000.1833-100000@iolanthe.rowland.org>
Date:	Thu, 30 Jan 2014 10:52:04 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Daniel Vetter <daniel@...ll.ch>
cc:	Ville Syrjälä 
	<ville.syrjala@...ux.intel.com>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: [Intel-gfx] Excessive WARN()s in Intel 915 driver

On Thu, 30 Jan 2014, Daniel Vetter wrote:

> Ok, I seem to have been truly blind all the time. This seems to have been
> fallout from
> 
> commit b6c5164d7bf624f3e1b750787ddb983150c5117c
> Author: Daniel Vetter <daniel.vetter@...ll.ch>
> Date:   Fri Apr 12 18:48:43 2013 +0200
> 
>     drm/i915: Fixup Oops in the pipe config computation
> 
> Meanwhile we've moved the overall infrastructure ahead again quite a bit,
> so I think it's time to give the full atomic modeset paths another shot.
> But I'll be travelling to fosdem the next few days, so this will take a
> bit of time.
> 
> As long as there's not real bad side-effects I guess we simply need to
> live with the WARN for a tad longer.

Okay.  Let me know when you've got something else ready to test.

Alan Stern

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