From: Karl-Johan Karlsson <creideiki+intel-gfx@ferretporn.se>
To: intel-gfx@lists.freedesktop.org,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Chris Wilson" <chris@chris-wilson.co.uk>,
"Daniel Vetter" <daniel.vetter@intel.com>,
"Jani Nikula" <jani.nikula@linux.intel.com>
Subject: 282dbf9b "drm/i915: Pass intel_plane and intel_crtc to plane hooks" breaks i945GM in 4.13 and above
Date: Thu, 11 Jan 2018 15:41:40 +0100 [thread overview]
Message-ID: <1549404.BeUqGaVtGp@maud> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2066 bytes --]
Hello,
I have an old Lenovo Thinkpad X60 laptop with a Core 2 Duo T7200 CPU and
i945GM integrated graphics whose graphics broke when I tried to update the
kernel to get the Meltdown fixes.
GRUB2 shows a graphical boot menu, and Linux displays the Tux boot logos
correctly at first. However, almost immediately after displaying the Tuxes,
the actively scrolling area of the display shifts about two text lines
downward, so that two decapitated penguin heads are left at the top of the
screen and new text appears below the lower edge of the screen. When X starts,
it too is shifted down the same amount, and only shows a black screen with a
(working) mouse cursor. My display manager (SDDM) never shows up. Sometimes,
while X is running, random pixels appear in the non-active area at the top of
the screen containing the decapitated penguin heads.
My hardware is:
$ grep name /proc/cpuinfo
model name : Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz
model name : Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz
# lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS,
943/940GML Express Integrated Graphics Controller (rev 03)
# grep Chipset: /var/log/Xorg.0.log
[ 33.085] (--) intel(0): Integrated Graphics Chipset: Intel(R) 945GM
$ xrandr | grep primary
LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y
axis) 250mm x 180mm
Kernel 4.12.14 does not have the bug. 4.13 and 4.14.11 have the bug in console
and X mode. 4.15-rc7 has the bug in console mode, but crashes (completely
black screen, Magic SysRq to reboot is the only thing that works) when
starting X.
Bisecting from 4.12 to 4.13 pointed to this as the first bad commit:
commit 282dbf9b017bc6d5fdaeadf14e534c2fe22fee2d
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date: Mon Mar 27 21:55:33 2017 +0300
drm/i915: Pass intel_plane and intel_crtc to plane hooks
But I know nothing about the driver internals to explain why.
--
Karl-Johan Karlsson
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2018-01-11 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 14:41 Karl-Johan Karlsson [this message]
2018-01-12 9:50 ` 282dbf9b "drm/i915: Pass intel_plane and intel_crtc to plane hooks" breaks i945GM in 4.13 and above Jani Nikula
2018-01-12 16:14 ` Ville Syrjälä
2018-01-13 14:03 ` Jani Nikula
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=1549404.BeUqGaVtGp@maud \
--to=creideiki+intel-gfx@ferretporn.se \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=ville.syrjala@linux.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