mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Karl Vogel <karl.vogel@gmail.com>
To: Eric Anholt <eric@anholt.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: i915 lockup / extreme delay
Date: Mon, 22 Mar 2010 09:11:06 +0100	[thread overview]
Message-ID: <bad735c81003220111y44bfb828vfd4c9fbbcabf3419@mail.gmail.com> (raw)
In-Reply-To: <87wrx5m1h3.fsf@pollan.anholt.net>

On Mon, Mar 22, 2010 at 5:20 AM, Eric Anholt <eric@anholt.net> wrote:
> On Sat, 20 Mar 2010 14:41:41 +0100, Karl Vogel <karl.vogel@gmail.com> wrote:
>> The 'effect' is that only the mouse pointer works in the X server. The
>> cpu usage on the laptop during the sluggishness is minimal. When I
>> suspend the game with winedbg, the X server slowly becomes responsive again.
>>
>> The output from latencytop seems to point to i915 being the culprit:
>
> If there's some code doing glFlush()es, it's probably that code at
> fault.  You don't need to do that unless you're doing frontbuffer
> rendering, and if you're doing frontbuffer rendering you should really
> be doing backbuffer rendering.  I don't see a kernel issue here.

That doesnt explain why the box completely locks up on 2.6.34-rc2
though, where only a cold reboot works.

It also seems a bit odd that 1 opengl application is able to entirely
lockup user interaction of the X server, then again that might be more
of an X issue than a kernel one.. or is it expected behaviour?
(the only thing you can do is wiggle the pointer, nothing else.. no
window selection, no window dragging, not even start new apps that
open windows)

  reply	other threads:[~2010-03-22  8:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-20 13:41 Karl Vogel
2010-03-20 13:52 ` Rafael J. Wysocki
2010-03-22  4:20 ` Eric Anholt
2010-03-22  8:11   ` Karl Vogel [this message]
2010-03-22 15:34     ` Eric Anholt
2010-03-27  9:54       ` Karl Vogel
2010-04-01 13:09         ` Andy Lutomirski
2010-04-01 13:35           ` Karsten Wiese

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=bad735c81003220111y44bfb828vfd4c9fbbcabf3419@mail.gmail.com \
    --to=karl.vogel@gmail.com \
    --cc=eric@anholt.net \
    --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

all inboxes | Powered by JetHome®