From: Will Dyson <will.dyson@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "Mark M. Hoffman" <mhoffman@lightlink.com>,
Paul Mackerras <paulus@samba.org>,
LKML <linux-kernel@vger.kernel.org>,
Dave Airlie <airlied@linux.ie>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [BUG] Xserver startup locks system... git bisect results
Date: Tue, 27 Dec 2005 02:48:41 -0500 [thread overview]
Message-ID: <8e6f94720512262348l698c6cfbs28841f3f1dc989f1@mail.gmail.com> (raw)
In-Reply-To: <1134712343.6316.2.camel@gaston>
On 12/16/05, Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> Finally fixes the radeon memory mapping bug that was incorrectly
> fixed by the previous patch. This time, we use the actual vram
> size as the size to calculate how far to move the AGP aperture
> from the framebuffer in card's memory space. If there are still
> issues with this patch, they are due to bugs in the X driver that
> I'm working on fixing too.
My amd64 machine with an agp radeon9200SE locks up tight on xserver
start (with an MCE) unless I revert both patches. I'm using x.org 6.9
compiled from the debian svn tree. The output of 'lspci -vv' is
available here:
http://www.lucidts.com/~will/lspcivv.txt
Please let me know of any testing I can do on x.org radeon DDX
patches, or any additional information I can provide.
--
Will Dyson
next prev parent reply other threads:[~2005-12-27 7:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 4:32 Mark M. Hoffman
2005-12-15 4:53 ` Benjamin Herrenschmidt
2005-12-15 5:07 ` Benjamin Herrenschmidt
2005-12-15 5:15 ` Benjamin Herrenschmidt
2005-12-15 9:03 ` Paul Mackerras
2005-12-16 3:50 ` Mark M. Hoffman
2005-12-16 4:43 ` Benjamin Herrenschmidt
2005-12-16 5:52 ` Benjamin Herrenschmidt
2005-12-16 6:59 ` Dave Airlie
2005-12-27 7:48 ` Will Dyson [this message]
2005-12-27 9:09 ` Benjamin Herrenschmidt
2005-12-15 13:45 ` Mark M. Hoffman
2005-12-15 7:55 ` Dave Airlie
2005-12-15 13:40 ` Mark M. Hoffman
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=8e6f94720512262348l698c6cfbs28841f3f1dc989f1@mail.gmail.com \
--to=will.dyson@gmail.com \
--cc=airlied@linux.ie \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhoffman@lightlink.com \
--cc=paulus@samba.org \
--cc=torvalds@osdl.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®