From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: "Konduru, Chandra" <chandra.konduru@intel.com>
Cc: David Airlie <airlied@linux.ie>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
"Vetter, Daniel" <daniel.vetter@intel.com>
Subject: Re: [i915]] *ERROR* mismatch in scaler_state.scaler_id
Date: Fri, 8 May 2015 21:41:38 +0900 [thread overview]
Message-ID: <20150508124138.GA527@swordfish> (raw)
In-Reply-To: <76A9B330A4D78C4D99CB292C4CC06C0E36FC8AC7@fmsmsx101.amr.corp.intel.com>
On (05/08/15 01:27), Konduru, Chandra wrote:
> > there are no specific steps, happens during boot and every time the screen goes
> > unblank. attached dmesg, .config.
> >
> OK, I am able reproduce the mismatch scaler id log on HSW system.
> Though, this log doesn't affect system functionality, but it is an unnecessary
> annoyance. This check is targeted for SKL and shouldn't happen for HSW.
> Submitted a patch to limit the check for skl+:
> http://patchwork.freedesktop.org/patch/48858/
jfi, the usual patch exchange happens in mailing lists.
`git am <email>' vs. `browsing some pages and downloading attached patches'.
back to the patch: no more mismatch warnings.
Reported-and-tested-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
-ss
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-05-08 12:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-02 1:05 [i915]] *ERROR* mismatch in scaler_state.scaler_id Sergey Senozhatsky
2015-05-06 11:09 ` Daniel Vetter
2015-05-07 0:40 ` Konduru, Chandra
2015-05-07 11:24 ` Sergey Senozhatsky
2015-05-08 1:27 ` Konduru, Chandra
2015-05-08 12:41 ` Sergey Senozhatsky [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=20150508124138.GA527@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=airlied@linux.ie \
--cc=chandra.konduru@intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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