From: "Steinar H. Gunderson" <steinar+dri@gunderson.no>
To: intel-gfx@lists.freedesktop.org
Subject: [BUG] Blinking display with 4.6-rc*
Date: Sat, 23 Apr 2016 11:31:42 +0200 [thread overview]
Message-ID: <20160423093142.GA1701@sesse.net> (raw)
Hi,
I have a Lenovo X240, which has Haswell integrated graphics. On upgrade from
4.5.0 to 4.6-rc1, I noticed an extremely irritating issue; about every
minute, the display shows black for a brief moment (perhaps one or two
frames), then reverts back to the correct display. There are no other ill
effects that I can see, in particular nothing in dmesg. I tried with 4.6-rc4,
and it has the same issue.
Do I need to run a full bisect to figure out what's causing this, or does it
ring a bell with someone?
/* Steinar */
--
Homepage: https://www.sesse.net/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2016-04-23 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 9:31 Steinar H. Gunderson [this message]
2016-04-25 8:23 ` [BUG] Blinking display with 4.6-rc* Jani Nikula
2016-04-25 8:44 ` Steinar H. Gunderson
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=20160423093142.GA1701@sesse.net \
--to=steinar+dri@gunderson.no \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox