From: Paul Bolle <pebolle@tiscali.nl>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
Jani Nikula <jani.nikula@linux.intel.com>,
David Airlie <airlied@linux.ie>
Cc: linux-thinkpad@linux-thinkpad.org,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: drm/i915: "Wrong MCH_SSKPD value: 0x16040307"
Date: Wed, 30 Jul 2014 20:49:07 +0200 [thread overview]
Message-ID: <1406746147.2406.50.camel@x220> (raw)
0) A ThinkPad X220 I use prints these messages at every boot and at
every resume:
[drm] Wrong MCH_SSKPD value: 0x16040307
[drm] This can cause pipe underruns and display issues.
[drm] Please upgrade your BIOS to fix this.
These messages can be seen for every kernel that's still in the logs
(the oldest is v3.11 based).
1) I'm not sure whether I actually run into "pipe underruns" or "display
issues". Is there something specific I should look for?
2) Now it happens that this laptop already runs the latest BIOS. So, if
I were to contact Lenovo to see if they could release a BIOS update to
fix this, what should I ask them to do?
Paul Bolle
reply other threads:[~2014-07-30 18:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1406746147.2406.50.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-thinkpad@linux-thinkpad.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