From: Kyle McMartin <kyle@mcmartin.ca>
To: Matthew Reppert <arashi@sacredchao.net>
Cc: dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
airlied@linux.ie
Subject: Re: G33 graphics broken after 2.6.23-rc6
Date: Sat, 6 Oct 2007 00:42:21 -0400 [thread overview]
Message-ID: <20071006044221.GA14767@fattire.cabal.ca> (raw)
In-Reply-To: <4706D4B1.6050101@sacredchao.net>
On Fri, Oct 05, 2007 at 08:20:01PM -0400, Matthew Reppert wrote:
> It works fine in the Ubuntu kernels (pre 2.6.22-13) and in mainline through
> 2.6.23-rc6; since 2.6.23-rc7 (and Ubuntu 2.6.22-13), the X server won't
> start up, and I get this at the end of my Xorg.log:
>
AOL. And I was in the middle of watching a bloody movie too.
commit f443675affe3f16dd428e46f0f7fd3f4d703eeab
Author: Zhenyu Wang <zhenyu.z.wang@intel.com>
Date: Tue Sep 11 15:23:57 2007 -0700
intel_agp: fix stolen mem range on G33
G33 GTT stolen memory is below graphics data stolen memory and be seperate,
so don't subtract it in stolen mem counting.
Signed-off-by: Zhenyu Wang <zhenyu.z.wang@intel.com>
Acked-by: Dave Airlie <airlied@linux.ie>
Cc: Dave Jones <davej@codemonkey.org.uk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Looks to be the commit that breaks things.
Regards,
Kyle M.
next prev parent reply other threads:[~2007-10-06 4:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-06 0:20 G33 graphics broken after 2.6.23-rc6 Matthew Reppert
2007-10-06 4:42 ` Kyle McMartin [this message]
2007-10-06 5:34 ` Kyle McMartin
2007-10-06 5:42 ` Revert "intel_agp: fix stolen mem range on G33" Kyle McMartin
2007-10-06 10:41 ` Jiri Slaby
2007-10-06 15:59 ` Linus Torvalds
2007-10-06 19:29 ` Keith Packard
2007-10-07 10:05 ` Jiri Slaby
2007-10-07 12:17 ` Daniel Stone
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=20071006044221.GA14767@fattire.cabal.ca \
--to=kyle@mcmartin.ca \
--cc=airlied@linux.ie \
--cc=arashi@sacredchao.net \
--cc=dri-devel@lists.sourceforge.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