All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ander Conselvan De Oliveira <conselvan2@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	DRI mailing list <dri-devel@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [git pull] drm tree for 4.2
Date: Mon, 29 Jun 2015 15:43:20 +0300	[thread overview]
Message-ID: <1435581800.3453.27.camel@gmail.com> (raw)
In-Reply-To: <CA+55aFw23R5xecHstn9tyNTLfbuY7hJ_BVVd6t8PMeSOhQg9bw@mail.gmail.com>

On Fri, 2015-06-26 at 14:43 -0700, Linus Torvalds wrote:
> On Thu, Jun 25, 2015 at 6:00 PM, Dave Airlie <airlied@linux.ie> wrote:
> >
> > This is the main drm pull request for v4.2.
> 
> It seems to work ok for me, but it causes quite a few new warnings on
> my Sony VAIO Pro laptop. It's (once more) a regular i5-4200U CPU (aka
> Haswell, aka 4th gen Intel Core i5)
> 
> Most of them are in check_crtc_state(), and I currently have 18 of
> these in my log:
> 
>   [drm:check_crtc_state [i915]] *ERROR* mismatch in
> dpll_hw_state.wrpll (expected 0x90280202, found 0x00000000)
>   WARNING: CPU: 0 PID: 115 at
> drivers/gpu/drm/i915/intel_display.c:12319
> check_crtc_state+0x8be/0xf60 [i915]()
>   pipe state doesn't match!
> 
> but there's a few others too:
> 
>   WARNING: CPU: 3 PID: 1871 at
> drivers/gpu/drm/i915/intel_display.c:1362 hsw_disable_ips+0x34/0x160
> [i915]()
>   plane A assertion failure (expected on, current off)
> 
>   WARNING: CPU: 3 PID: 1871 at drivers/gpu/drm/drm_irq.c:1162
> drm_wait_one_vblank+0x148/0x1a0 [drm]()
>   vblank not available on crtc 0, ret=-22
> 
> and the backtraces aren't all that interesting, but I'm attaching the
> cleaned-up dmesg, duplicate callchains and all.

Please provide a full dmesg with drm.debug=0x1f in the kernel command
line.

Thanks,
Ander

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Ander Conselvan De Oliveira <conselvan2@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: [git pull] drm tree for 4.2
Date: Mon, 29 Jun 2015 15:43:20 +0300	[thread overview]
Message-ID: <1435581800.3453.27.camel@gmail.com> (raw)
In-Reply-To: <CA+55aFw23R5xecHstn9tyNTLfbuY7hJ_BVVd6t8PMeSOhQg9bw@mail.gmail.com>

On Fri, 2015-06-26 at 14:43 -0700, Linus Torvalds wrote:
> On Thu, Jun 25, 2015 at 6:00 PM, Dave Airlie <airlied@linux.ie> wrote:
> >
> > This is the main drm pull request for v4.2.
> 
> It seems to work ok for me, but it causes quite a few new warnings on
> my Sony VAIO Pro laptop. It's (once more) a regular i5-4200U CPU (aka
> Haswell, aka 4th gen Intel Core i5)
> 
> Most of them are in check_crtc_state(), and I currently have 18 of
> these in my log:
> 
>   [drm:check_crtc_state [i915]] *ERROR* mismatch in
> dpll_hw_state.wrpll (expected 0x90280202, found 0x00000000)
>   WARNING: CPU: 0 PID: 115 at
> drivers/gpu/drm/i915/intel_display.c:12319
> check_crtc_state+0x8be/0xf60 [i915]()
>   pipe state doesn't match!
> 
> but there's a few others too:
> 
>   WARNING: CPU: 3 PID: 1871 at
> drivers/gpu/drm/i915/intel_display.c:1362 hsw_disable_ips+0x34/0x160
> [i915]()
>   plane A assertion failure (expected on, current off)
> 
>   WARNING: CPU: 3 PID: 1871 at drivers/gpu/drm/drm_irq.c:1162
> drm_wait_one_vblank+0x148/0x1a0 [drm]()
>   vblank not available on crtc 0, ret=-22
> 
> and the backtraces aren't all that interesting, but I'm attaching the
> cleaned-up dmesg, duplicate callchains and all.

Please provide a full dmesg with drm.debug=0x1f in the kernel command
line.

Thanks,
Ander


  reply	other threads:[~2015-06-29 12:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26  1:00 [git pull] drm tree for 4.2 Dave Airlie
2015-06-26  1:00 ` Dave Airlie
2015-06-26  8:05 ` Christian König
2015-06-26 20:37   ` Dave Airlie
2015-06-26 20:37     ` Dave Airlie
2015-06-26 20:41     ` Linus Torvalds
2015-06-26 20:41       ` Linus Torvalds
2015-06-26 21:43 ` Linus Torvalds
2015-06-26 21:43   ` Linus Torvalds
2015-06-29 12:43   ` Ander Conselvan De Oliveira [this message]
2015-06-29 12:43     ` Ander Conselvan De Oliveira
2015-06-29 14:50     ` Jani Nikula
2015-06-29 14:50       ` Jani Nikula
2015-06-29 15:35       ` [Intel-gfx] " Daniel Vetter
2015-06-29 15:35         ` Daniel Vetter
2015-06-30 13:00         ` Jani Nikula
2015-06-30 13:00           ` [Intel-gfx] " Jani Nikula
2015-06-30 13:10           ` [PATCH] drm/i915: Clear pipe's pll hw state in hsw_dp_set_ddi_pll_sel() Ander Conselvan de Oliveira
2015-06-30 13:10             ` Ander Conselvan de Oliveira
2015-06-30 13:47             ` Jani Nikula
2015-06-30 13:47               ` Jani Nikula
2015-06-30 14:22               ` [Intel-gfx] " Daniel Vetter
2015-06-30 14:22                 ` Daniel Vetter
2015-06-30 15:41                 ` Jani Nikula
2015-06-30 15:41                   ` Jani Nikula
2015-07-01 14:54                   ` Ander Conselvan De Oliveira
2015-07-01 14:54                     ` Ander Conselvan De Oliveira
2015-07-01 15:02                     ` Daniel Vetter
2015-07-01 15:02                       ` Daniel Vetter
2015-07-02  2:38             ` shuang.he

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=1435581800.3453.27.camel@gmail.com \
    --to=conselvan2@gmail.com \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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.