From: Andrey Skvortsov <andrej.skvortzov@gmail.com>
To: Sitsofe Wheeler <sitsofe@gmail.com>
Cc: Paul Bolle <pebolle@tiscali.nl>, David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [BISECTED REGRESSION in 3.19-rc1] [drm/i915] WARNING: drivers/gpu/drm/drm_irq.c:1077 drm_wait_one_vblank
Date: Mon, 23 Feb 2015 23:28:02 +0300 [thread overview]
Message-ID: <20150223202802.GD3871@crion86> (raw)
In-Reply-To: <87bnkkrdns.fsf@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1707 bytes --]
On Mon, Feb 23, 2015 at 02:54:47PM +0200, Jani Nikula wrote:
> On Mon, 23 Feb 2015, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> > On Mon, 16 Feb 2015, Paul Bolle <pebolle@tiscali.nl> wrote:
> >> I still see this on v3.19. I booted with drm.debug=0x4. The almost 2K
> >> lines in dmesg containing either "[drm" or this WARNING are pasted
> >> below. I really know nothing about all this, but I do note that only the
> >> WARNINGS are preceded by:
> >> [drm:intel_calculate_wm] FIFO watermark level: -5
> >> [drm:i9xx_update_wm] FIFO watermarks - A: 26, B: 8
> >>
> >> But perhaps that's another symptom of the same issue. A bit of staring
> >> at the code couldn't help me determine that.
> >>
> >> Perhaps these debug messages help someone in discovering what might be
> >> going on here.
> >
> > Please try v4.0-rc1 or try cherry-picking this on top of v3.19 and
> > report back:
> >
> > commit f9b61ff6bce9a44555324b29e593fdffc9a115bc
> > Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Date: Wed Jan 7 13:54:39 2015 +0100
> >
> > drm/i915: Push vblank enable/disable past encoder->enable/disable
>
> https://bugs.freedesktop.org/show_bug.cgi?id=89108
>
Hi, Sitsofe,
you wrote in your bug report (#89108), that you've got a black screen, when you tried drm-intel-nightly branch.
Do you have black screen with v4.0-rc1 on your eeepc?
If so, is it similar to that I described here https://lkml.org/lkml/2015/2/3/594 ?
As we both had drm_wait_one_vblank warnings, I assume that we have the same or similar chipsets.
And your black screen could be potentially the same as mine.
--
Best regards,
Andrey Skvortsov
PGP Key ID: 0x57A3AEAD
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Andrey Skvortsov <andrej.skvortzov@gmail.com>
To: Sitsofe Wheeler <sitsofe@gmail.com>
Cc: "Paul Bolle" <pebolle@tiscali.nl>,
"Daniel Vetter" <daniel.vetter@intel.com>,
"David Airlie" <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Matt Roper" <matthew.d.roper@intel.com>,
"Jani Nikula" <jani.nikula@linux.intel.com>
Subject: Re: [BISECTED REGRESSION in 3.19-rc1] [drm/i915] WARNING: drivers/gpu/drm/drm_irq.c:1077 drm_wait_one_vblank
Date: Mon, 23 Feb 2015 23:28:02 +0300 [thread overview]
Message-ID: <20150223202802.GD3871@crion86> (raw)
In-Reply-To: <87bnkkrdns.fsf@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1707 bytes --]
On Mon, Feb 23, 2015 at 02:54:47PM +0200, Jani Nikula wrote:
> On Mon, 23 Feb 2015, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> > On Mon, 16 Feb 2015, Paul Bolle <pebolle@tiscali.nl> wrote:
> >> I still see this on v3.19. I booted with drm.debug=0x4. The almost 2K
> >> lines in dmesg containing either "[drm" or this WARNING are pasted
> >> below. I really know nothing about all this, but I do note that only the
> >> WARNINGS are preceded by:
> >> [drm:intel_calculate_wm] FIFO watermark level: -5
> >> [drm:i9xx_update_wm] FIFO watermarks - A: 26, B: 8
> >>
> >> But perhaps that's another symptom of the same issue. A bit of staring
> >> at the code couldn't help me determine that.
> >>
> >> Perhaps these debug messages help someone in discovering what might be
> >> going on here.
> >
> > Please try v4.0-rc1 or try cherry-picking this on top of v3.19 and
> > report back:
> >
> > commit f9b61ff6bce9a44555324b29e593fdffc9a115bc
> > Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Date: Wed Jan 7 13:54:39 2015 +0100
> >
> > drm/i915: Push vblank enable/disable past encoder->enable/disable
>
> https://bugs.freedesktop.org/show_bug.cgi?id=89108
>
Hi, Sitsofe,
you wrote in your bug report (#89108), that you've got a black screen, when you tried drm-intel-nightly branch.
Do you have black screen with v4.0-rc1 on your eeepc?
If so, is it similar to that I described here https://lkml.org/lkml/2015/2/3/594 ?
As we both had drm_wait_one_vblank warnings, I assume that we have the same or similar chipsets.
And your black screen could be potentially the same as mine.
--
Best regards,
Andrey Skvortsov
PGP Key ID: 0x57A3AEAD
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-23 20:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 21:16 [BISECTED REGRESSION in 3.19-rc1] [drm/i915] WARNING: drivers/gpu/drm/drm_irq.c:1077 drm_wait_one_vblank Andrey Skvortsov
2015-01-31 21:16 ` Andrey Skvortsov
2015-02-04 12:32 ` Paul Bolle
2015-02-04 12:32 ` Paul Bolle
2015-02-04 17:26 ` Andrey Skvortsov
2015-02-04 17:26 ` Andrey Skvortsov
2015-02-16 13:10 ` Paul Bolle
2015-02-16 13:10 ` Paul Bolle
2015-02-23 12:45 ` Jani Nikula
2015-02-23 12:45 ` Jani Nikula
2015-02-23 12:54 ` Jani Nikula
2015-02-23 12:54 ` Jani Nikula
2015-02-23 20:28 ` Andrey Skvortsov [this message]
2015-02-23 20:28 ` Andrey Skvortsov
2015-02-24 7:45 ` Jani Nikula
2015-02-23 19:52 ` Andrey Skvortsov
2015-02-23 19:52 ` Andrey Skvortsov
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=20150223202802.GD3871@crion86 \
--to=andrej.skvortzov@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=sitsofe@gmail.com \
/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.