From: Martin Wilck <mwilck@arcor.de>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel HD 4400] strongly irritating artefacts on 2560x1440 laptop display
Date: Thu, 29 Jan 2015 22:47:06 +0100 [thread overview]
Message-ID: <54CAAA5A.7000905@arcor.de> (raw)
In-Reply-To: <20150128094505.GG28132@nuc-i3427.alporthouse.com>
On 01/28/2015 10:45 AM, Chris Wilson wrote:
> From watching the video, and your comments here, it is clear this is not
> a driver bug (neither in the ddx nor opengl compositor). That leaves us
> with hardware misconfiguration, aka kernel bug. Some of the artefacts
> could be a display underrun. It would be good to check a drm.debug=0xe
> dmesg for any warnings (and the info itself will be useful). Another
> thing worth playing with is i915.enable_fbc=1 (though that is really
> just swapping one problem with another).
i915.enable_fbc=1 had no effect.
I agree with you that this is probably a low-level problem, although the
fact that the artefacts strongly depend on Window content doesn't fit
that theory.
Martin
PS: I have just done a thing I thought I'd never do - I am downloading
an evaluation copy of Windows in order to check whether my HW is faulty.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-01-29 21:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 21:49 [Intel HD 4400] strongly irritating artefacts on 2560x1440 laptop display Martin Wilck
2015-01-28 9:45 ` Chris Wilson
2015-01-29 20:57 ` Martin Wilck
2015-01-29 21:47 ` Martin Wilck [this message]
2015-01-31 12:52 ` Martin Wilck
2015-01-31 15:36 ` Jani Nikula
2015-01-31 17:26 ` Martin Wilck
2015-01-28 9:45 ` Jani Nikula
2015-01-29 21:10 ` Martin Wilck
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=54CAAA5A.7000905@arcor.de \
--to=mwilck@arcor.de \
--cc=chris@chris-wilson.co.uk \
--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 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.