From: wzab <wzab@ise.pw.edu.pl>
To: wzab@ise.pw.edu.pl
Cc: "Bruno Prémont" <bonbons@linux-vserver.org>,
linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org
Subject: Re: Screen corrupted in Xorg with KMS on 945GM/GMS, 943/940GML chipset with kernel 2.6.38.2
Date: Thu, 14 Apr 2011 16:56:50 +0200 [thread overview]
Message-ID: <4DA70B32.1090505@ise.pw.edu.pl> (raw)
In-Reply-To: <4DA4832F.2090600@ise.pw.edu.pl>
W dniu 12.04.2011 18:51, wzab pisze:
> W dniu 12.04.2011 18:41, Bruno Prémont pisze:
>> [CCing intel-gfx]
>>
>> On Tue, 12 April 2011 Wojciech Zabołotny<wzab@ise.pw.edu.pl> wrote:
>>> After I've upgraded my kernel to 2.6.38.2, I started to experience very
>>> often screen corruption in X (it happened also earlier with 2.6.37.3,
>>> but now is very often.
>>> Hardware seems to be OK. I attach sample screendumps, configuration of
>>> my kernel, log of the X server and output of the lspci command.
>>
>> This looks similar to the xchat corruptions I see (on i855).
>>
>> Have a look at #34980 (also 945 family) and #35460 on
>> bugs.freedesktop.org.
>>
>> Bruno
>
> Yes, the similar symptoms have also been reported in Ubuntu
>
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/737900
>
> I have yet another machine, with an older chipset - VGA compatible
> controller: Intel Corporation 82865G Integrated Graphics Controller
> (rev 02) no corruptions occur in this machine.
Ooops, sorry, today I have noticed the same problems on the machine with
Intel Corporation 82865G Integrated Graphics Controller (rev 02).
Wojtek
prev parent reply other threads:[~2011-04-14 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4DA4243A.5030805@ise.pw.edu.pl>
2011-04-12 16:41 ` Screen corrupted in Xorg with KMS on 945GM/GMS, 943/940GML chipset with kernel 2.6.38.2 Bruno Prémont
2011-04-12 16:51 ` wzab
2011-04-14 14:56 ` wzab [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=4DA70B32.1090505@ise.pw.edu.pl \
--to=wzab@ise.pw.edu.pl \
--cc=bonbons@linux-vserver.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