From: "René Herman" <rene.herman@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [BUG 2.6.38] drm/i915: rampant video-corruption on Intel 865G
Date: Wed, 23 Mar 2011 22:30:51 +0100 [thread overview]
Message-ID: <4D8A668B.9070302@gmail.com> (raw)
Good day.
2.6.38 (-final) unfortunately is largely unusable on Intel 865G, and
more old Intel graphics hardware as reported for example for Debian on
855G at:
http://www.linux-archive.org/debian-kernel/503229-bug-619022-linux-image-2-6-38-1-686-screen-corruption-i855.html
Most web pages won't render without corrupting, nor does scrolling a
terminal a few times. I see from the above Debian report that it is/was
known but it's indeed not fixed in final on 855/865 by anything which
may have happened in response.
I do not have the time currently to fully bisect this and I assume it's
known what the culprit is going to be anyway; I could revert specific
commits on command and/or test fixes on top of 2.6.38-final; for know
I've simply reverted to 2.6.37.4 where everything is fine.
(PS: most people using graphics hardware this plain/old will not deeply
care for graphics; I in fact once bought the machine specifically with
the "well supported, no-thrills" basic, integrated Intel graphics as a
reason but it has given me only grief in that department, with years of
X11 instability. This older hardware seems to receive little or no
testing from the Intel graphics developers and if it's holding back
development, I expect most users would not not mind or even welcome it
being split of into a separate, maintained but no longer "improved"
driver, both kernel- and X11-side).
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM
Controller/Host-Hub Interface (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated
Graphics Controller (rev 02)
00:03.0 PCI bridge: Intel Corporation 82865G/PE/P PCI to CSA Bridge (rev 02)
00:06.0 System peripheral: Intel Corporation 82865G/PE/P Processor to
I/O Memory Interface (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB
UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB
UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB
UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB
UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2
EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC
Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE
Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller
(rev 02)
00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus
Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER
(ICH5/ICH5R) AC'97 Audio Controller (rev 02)
02:01.0 Ethernet controller: Intel Corporation 82547EI Gigabit Ethernet
Controller
Regards,
Rene
next reply other threads:[~2011-03-23 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 21:30 René Herman [this message]
[not found] ` <849307$c4qsv5@azsmga001.ch.intel.com>
2011-03-24 7:56 ` [BUG 2.6.38] drm/i915: rampant video-corruption on Intel 865G René Herman
[not found] ` <849307$c4rj51@azsmga001.ch.intel.com>
2011-03-24 8:19 ` René Herman
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=4D8A668B.9070302@gmail.com \
--to=rene.herman@gmail.com \
--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