All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Philipp Klaus Krause <pkk@spth.de>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Screen corruption regression from 3.0 to 3.1rc4
Date: Sat, 3 Sep 2011 12:43:35 +0200	[thread overview]
Message-ID: <CAKMK7uGf4qZ+E87aqX6KaZeksfj-irRA5YL+w8dwcOJHSkpT+g@mail.gmail.com> (raw)
In-Reply-To: <4E61F3D8.4080306@spth.de>

On Sat, Sep 3, 2011 at 11:31, Philipp Klaus Krause <pkk@spth.de> wrote:
> Am 31.08.2011 08:43, schrieb Philipp Klaus Krause:
>> In the free game simutrans, in fullscreen mode I see the following problem:
>> The lower about 2 cm of the screen don't update. They are black or carry
>> the image from the game startup screen. They flicker once in a while,
>> but otherwise the image stays the same.
>>
>> lspci output:
>> 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
>> Integrated Graphics Controller (primary) (rev 0c)
>> 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960
>> Integrated Graphics Controller (secondary) (rev 0c)
>>
>> glxinfo:
>> OpenGL vendor string: Tungsten Graphics, Inc
>> OpenGL renderer string: Mesa DRI Intel(R) 965GM
>> OpenGL version string: 2.1 Mesa 7.11
>>
>> Any ideas what I can do about this problem? Is it a known issue?

Lately there seem to be a few reports of "my screen doesn't update
anymore". One thing that seems to (temporary) fix the problem is to
switch to the kernel console and back to X. Does that help in your
case?

> This regression was introduced between 3.0 and 3.1rc1.

If it's a kernel regression, can you please try to bisect it?

Thanks a lot,

Daniel
-- 
Daniel Vetter
daniel.vetter@ffwll.ch - +41 (0) 79 364 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2011-09-03 10:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31  6:43 Screen corruption regression from 3.0 to 3.1rc4 Philipp Klaus Krause
2011-09-03  9:31 ` Philipp Klaus Krause
2011-09-03 10:43   ` Daniel Vetter [this message]
2011-09-03 10:52     ` Philipp Klaus Krause
2011-09-03 11:53       ` Daniel Vetter
2011-09-06 13:11       ` Philipp Klaus Krause
2011-09-06 15:53         ` Keith Packard
2011-09-07 17:16           ` Philipp Klaus Krause
2011-09-08 13:43             ` Eugeni Dodonov
2011-09-08 20:19               ` Philipp Klaus Krause

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=CAKMK7uGf4qZ+E87aqX6KaZeksfj-irRA5YL+w8dwcOJHSkpT+g@mail.gmail.com \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=pkk@spth.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.