linux-kernel - Re: [i915] WARNING: [...] drivers/gpu/drm/i915/intel_display.c:9948 intel_get_pipe_from

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: <1386007525.9830.4.camel@x41.thuisdomein>
Date:	Mon, 02 Dec 2013 19:05:25 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Daniel Vetter <daniel.vetter@...ll.ch>
Cc:	Ville Syrjälä 
	<ville.syrjala@...ux.intel.com>, David Airlie <airlied@...ux.ie>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>,
	dri-devel <dri-devel@...ts.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [i915] WARNING: [...] drivers/gpu/drm/i915/intel_display.c:9948
 intel_get_pipe_from_connector

On Mon, 2013-12-02 at 15:23 +0100, Daniel Vetter wrote:
> On Mon, Dec 2, 2013 at 10:53 AM, Paul Bolle <pebolle@...cali.nl> wrote:
> > This generated quite a bit of debug messages so I only copied the
> > WARNING and the drm (related) messages immediately preceding it. Please
> > feel free to prod again if that's insufficient.
> 
> Yeah, the beginning of the drm message would are wanted since I need
> to know what exactly your hardware claims to support ;-)
> 
> But the backtrace confirms my first hunch for now ... Just want to
> confirm before sending out a patch with commit message.

It seems Ville's patch ( https://lkml.org/lkml/2013/12/2/77 ) does the
trick. Do you still need the additional info?


Paul Bolle

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