From: "Marc Deop i Argemí" <damnshock@gmail.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [ANNOUNCE] xf86-video-intel 2.11.901
Date: Sat, 19 Jun 2010 18:35:37 +0200 [thread overview]
Message-ID: <201006191835.37999.damnshock@gmail.com> (raw)
In-Reply-To: <20100618130450.1045a6c2@virtuousgeek.org>
On Friday June 18 2010 22:04:50 Jesse Barnes wrote:
> Ok here are some updated ones.
Already tried the patches. Now they both apply correctly on kernel 2.6.35-rc3.
However, this is what I find on the Xorg.0.log:
[ 463.790] (EE) intel(0): Detected a hung GPU, disabling acceleration.
If I try to run glxgears the X window system crashes. This happens with both
2.11.0 and with 2.11.901RC
However, I'm trying right now the kernel 2.6.35-rc3 with the 2.11.901 RC and,
for now, it seems stable (I still get corruption if I try to rotate the screen
as well as in some KDE menus).
Regards
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
next prev parent reply other threads:[~2010-06-19 16:36 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 0:39 [ANNOUNCE] xf86-video-intel 2.11.901 Carl Worth
2010-06-15 9:18 ` Julien Cristau
2010-06-15 16:46 ` Carl Worth
2010-06-15 16:51 ` Julien Cristau
2010-06-15 17:16 ` Sergio Monteiro Basto
2010-06-15 17:31 ` Julien Cristau
2010-06-15 17:46 ` Sergio Monteiro Basto
2010-06-15 14:05 ` Marc Deop i Argemí
2010-06-15 14:18 ` Julien Cristau
2010-06-15 15:02 ` Marc Deop i Argemí
2010-06-15 16:47 ` Carl Worth
2010-06-15 17:12 ` Marc Deop i Argemí
2010-06-15 21:23 ` Carl Worth
2010-06-16 8:45 ` Marc Deop i Argemí
2010-06-16 13:10 ` Marc Deop i Argemí
2010-06-16 13:57 ` Chris Wilson
2010-06-16 16:12 ` Marc Deop i Argemí
2010-06-17 13:30 ` Marc Deop i Argemí
2010-06-17 21:34 ` Elias Gabriel Amaral da Silva
2010-06-18 6:09 ` Carl Worth
2010-06-21 5:09 ` Elias Gabriel Amaral da Silva
2010-06-21 6:08 ` Elias Gabriel Amaral da Silva
2010-06-21 6:37 ` Christopher James Halse Rogers
2010-06-22 18:42 ` Elias Gabriel Amaral da Silva
2010-06-21 5:31 ` Elias Gabriel Amaral da Silva
2010-06-25 6:23 ` Carl Worth
2010-06-25 8:53 ` Clemens Eisserer
2010-06-16 9:20 ` Chris Wilson
2010-06-16 11:25 ` Marc Deop i Argemí
2010-06-16 11:38 ` Andrew Lutomirski
2010-06-16 15:07 ` Andrew Lutomirski
2010-06-17 20:32 ` Jesse Barnes
2010-06-17 22:27 ` Marc Deop i Argemí
2010-06-18 0:17 ` Andrew Lutomirski
2010-06-18 0:20 ` Marc Deop i Argemí
2010-06-18 2:44 ` Jesse Barnes
2010-06-18 20:04 ` Jesse Barnes
2010-06-18 20:07 ` Jesse Barnes
2010-06-19 16:35 ` Marc Deop i Argemí [this message]
2010-06-20 15:29 ` Andrew Lutomirski
2010-06-21 20:32 ` Andrew Lutomirski
2010-06-23 16:07 ` Jesse Barnes
2010-07-01 20:55 ` Andrew Lutomirski
2010-07-01 21:21 ` Jesse Barnes
2010-07-01 21:34 ` Andrew Lutomirski
2010-06-15 14:54 ` Vasily Khoruzhick
2010-06-15 16:49 ` Carl Worth
2010-06-15 16:55 ` Vasily Khoruzhick
2010-06-15 17:36 ` Vasily Khoruzhick
2010-06-15 19:58 ` Clemens Eisserer
2010-06-15 20:15 ` Chris Wilson
2010-06-15 21:03 ` Clemens Eisserer
2010-06-15 21:26 ` Carl Worth
2010-06-15 21:40 ` Chris Wilson
2010-06-15 22:05 ` Clemens Eisserer
2010-06-15 22:24 ` Clemens Eisserer
2010-06-15 22:31 ` Chris Wilson
2010-06-15 22:56 ` Clemens Eisserer
2010-06-16 5:45 ` Vasily Khoruzhick
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=201006191835.37999.damnshock@gmail.com \
--to=damnshock@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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 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.