All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [i915] WARNING: [...] drivers/gpu/drm/i915/intel_display.c:9948 intel_get_pipe_from_connector
Date: Tue, 3 Dec 2013 16:19:35 +0100	[thread overview]
Message-ID: <20131203151935.GD27344@phenom.ffwll.local> (raw)
In-Reply-To: <1386007525.9830.4.camel@x41.thuisdomein>

On Mon, Dec 02, 2013 at 07:05:25PM +0100, Paul Bolle wrote:
> On Mon, 2013-12-02 at 15:23 +0100, Daniel Vetter wrote:
> > On Mon, Dec 2, 2013 at 10:53 AM, Paul Bolle <pebolle@tiscali.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?

I'd like to confirm the actual cause (I suspect that we switch
pipes&planes around) for why you see this but other machines don't show
this to augment the commit message. But I've merged the fix already.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: "Daniel Vetter" <daniel.vetter@ffwll.ch>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"David Airlie" <airlied@linux.ie>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [i915] WARNING: [...] drivers/gpu/drm/i915/intel_display.c:9948 intel_get_pipe_from_connector
Date: Tue, 3 Dec 2013 16:19:35 +0100	[thread overview]
Message-ID: <20131203151935.GD27344@phenom.ffwll.local> (raw)
In-Reply-To: <1386007525.9830.4.camel@x41.thuisdomein>

On Mon, Dec 02, 2013 at 07:05:25PM +0100, Paul Bolle wrote:
> On Mon, 2013-12-02 at 15:23 +0100, Daniel Vetter wrote:
> > On Mon, Dec 2, 2013 at 10:53 AM, Paul Bolle <pebolle@tiscali.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?

I'd like to confirm the actual cause (I suspect that we switch
pipes&planes around) for why you see this but other machines don't show
this to augment the commit message. But I've merged the fix already.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2013-12-03 15:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-30 20:38 [i915] WARNING: [...] drivers/gpu/drm/i915/intel_display.c:9948 intel_get_pipe_from_connector Paul Bolle
2013-12-01  9:58 ` Daniel Vetter
2013-12-01  9:58   ` Daniel Vetter
2013-12-01 16:57   ` Paul Bolle
2013-12-01 16:57     ` Paul Bolle
2013-12-02  7:33     ` Daniel Vetter
2013-12-02  7:33       ` Daniel Vetter
2013-12-02  9:08       ` [PATCH] drm/i915: Take modeset locks around intel_modeset_setup_hw_state() ville.syrjala
2013-12-02 10:00         ` Paul Bolle
2013-12-02 10:00           ` Paul Bolle
2013-12-02 12:12           ` Ville Syrjälä
2013-12-02 12:12             ` Ville Syrjälä
2013-12-02 18:01             ` Paul Bolle
2013-12-02 18:01               ` Paul Bolle
2013-12-02  9:53       ` [i915] WARNING: [...] drivers/gpu/drm/i915/intel_display.c:9948 intel_get_pipe_from_connector Paul Bolle
2013-12-02  9:53         ` Paul Bolle
2013-12-02 14:23         ` Daniel Vetter
2013-12-02 14:23           ` Daniel Vetter
2013-12-02 18:05           ` Paul Bolle
2013-12-02 18:05             ` Paul Bolle
2013-12-03 15:19             ` Daniel Vetter [this message]
2013-12-03 15:19               ` Daniel Vetter
2013-12-03 22:03               ` Paul Bolle
2013-12-03 22:03                 ` Paul Bolle
2013-12-03 22:13                 ` Daniel Vetter
2013-12-03 22:13                   ` Daniel Vetter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131203151935.GD27344@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.