Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Wolfgang Draxinger <wdraxinger.maillist@draxit.de>,
	dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Closing and repoening laptop lid causes scanout corruption (regression since 4.15.12)
Date: Thu, 05 Apr 2018 11:05:51 +0300	[thread overview]
Message-ID: <87fu4aulgg.fsf@intel.com> (raw)
In-Reply-To: <e222040b-e179-6a8a-b500-177b637c8e7e@draxit.de>

On Wed, 04 Apr 2018, Wolfgang Draxinger <wdraxinger.maillist@draxit.de> wrote:
> ever since I upgraded my system to kernel version 4.15.12 I'm
> experiencing a kind of interesting problem with my laptop's graphics
> output.

Please file a bug at [1], including the description below. Add
drm.debug=14 module parameter, attach dmesg from boot.


BR,
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

           reply	other threads:[~2018-04-05  8:05 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <e222040b-e179-6a8a-b500-177b637c8e7e@draxit.de>]

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=87fu4aulgg.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=wdraxinger.maillist@draxit.de \
    /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