From: Chris Wilson <chris@chris-wilson.co.uk>
To: Clemens Eisserer <linuxhippy@gmail.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: System freeze with 2.12 + 2.6.34
Date: Thu, 01 Jul 2010 16:09:21 +0100 [thread overview]
Message-ID: <89k77n$o7r22c@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <AANLkTimzRJLW87n9AxjU31wGOwAMP2qQ13jpxn1Jh-ly@mail.gmail.com>
On Thu, 1 Jul 2010 16:55:28 +0200, Clemens Eisserer <linuxhippy@gmail.com> wrote:
> During the 2.6.11.901 testing phase a few people reported system freezes.
> What was the result of that discussion?
>
> I still experience those freezes with kernel-2.6.34 + intel 2.12,
> quite frequently when watching high resolution flash videos.
>
> Any idea what the problem could be?
All depends upon the system. Jesse is working on a couple of patches that
address the change in handling of the vblank interrupt in some revisions
of the i945/i965 chipsets. That's the known failure mode...
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-07-01 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 14:55 System freeze with 2.12 + 2.6.34 Clemens Eisserer
2010-07-01 15:09 ` Chris Wilson [this message]
2010-07-01 15:34 ` Stephan Raue
2010-07-01 17:34 ` Jesse Barnes
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='89k77n$o7r22c@fmsmga001.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linuxhippy@gmail.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 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.