public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com,
	intel-gfx@lists.freedesktop.org,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 5.2: display corruption on X60, X220
Date: Thu, 6 Jun 2019 10:37:35 +0200	[thread overview]
Message-ID: <20190606083735.GA975@amd> (raw)
In-Reply-To: <87v9xj15d9.fsf@intel.com>

[-- Attachment #1: Type: text/plain, Size: 963 bytes --]

On Thu 2019-06-06 11:32:18, Jani Nikula wrote:
> On Mon, 03 Jun 2019, Pavel Machek <pavel@ucw.cz> wrote:
> > In recent kernels (5.2.0-rc1-next-20190522, 5.2-rc2) I'm getting
> > display corruption in X. Usually in terminals, but also in title bars
> > etc. Black areas with white lines in them, usually...
> >
> > Same configuration worked properly in ... probably 4.19? Then I got
> > some graphics-crashes on X220 that prevented me from testing :-(.
> 
> It's pretty hard to say anything based on the above.
> 
> Anything in the logs with drm.debug=14 added?

I see. It looks like hard-to-debug issue.

Oh, interesting part is that corruption _is_ visible if I make a
screenshot.

Will try with drm.debug=...

Do you do some kind of testing that would catch similar issues?

Thanks,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      reply	other threads:[~2019-06-06  8:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03  7:40 5.2: display corruption on X60, X220 Pavel Machek
2019-06-06  8:32 ` Jani Nikula
2019-06-06  8:37   ` Pavel Machek [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=20190606083735.GA975@amd \
    --to=pavel@ucw.cz \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rodrigo.vivi@intel.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