From: Jani Nikula <jani.nikula@linux.intel.com>
To: Rami Vanguri <rami.vanguri@gmail.com>, intel-gfx@lists.freedesktop.org
Subject: Re: Screen Flicker i915 with drm-intel-nightly
Date: Tue, 07 Feb 2017 11:24:47 +0200 [thread overview]
Message-ID: <87mvdywdy8.fsf@intel.com> (raw)
In-Reply-To: <CADDcH28x9To=wbPpxSs9odvNE+0fL0M0saf9QKMTBbWHRrZ1Zw@mail.gmail.com>
On Tue, 07 Feb 2017, Rami Vanguri <rami.vanguri@gmail.com> wrote:
> [1.] One line summary of the problem:
> Screen flickering under highest resolution (3840x2160) with external
> monitor connected to DisplayPort. This is with an X1 Carbon (3rd
> generation) and flickering only happens on external monitor and only
> on highest resolution.
>
> [2.] Full description of the problem/report:
> No real additional information from the one line summary. Sometimes
> screen goes completely blank for a second or so.
>
> [3.] Keywords (i.e., modules, networking, kernel): Please do not put
> anything here. This is how Kernel.org uses an undocumented keyword
> system, which has nothing to do with Ubuntu Tags system.
>
> [4.] Kernel version (from /proc/version):
> Linux version 4.10.0-994-generic (kernel@gomeisa) (gcc version 6.2.0
> 20161005 (Ubuntu 6.2.0-5ubuntu12) ) #201702052101 SMP Mon Feb 6
> 02:02:51 UTC 2017
>
> [5.] Output of Oops.. message (if applicable) with symbolic
> information resolved (see Documentation/oops-tracing.txt)
>
> Attached is dmesg.txt with drm.debug=14 on.
Please file a bug at [1] and be sure to add all this stuff there.
Thanks,
Jani.
[1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-02-07 9:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 23:30 Screen Flicker i915 with drm-intel-nightly Rami Vanguri
2017-02-07 9:24 ` Jani Nikula [this message]
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=87mvdywdy8.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rami.vanguri@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox