From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: bob.picco@hp.com
Subject: Re: ATI X600 on 2.6.15
Date: Thu, 05 Jan 2006 20:56:53 +1100 [thread overview]
Message-ID: <1136455013.4840.73.camel@localhost.localdomain> (raw)
In-Reply-To: <20060105014229.GB10726@localhost>
On Wed, 2006-01-04 at 20:42 -0500, Bob Picco wrote:
> I have machine lockups on 2.6.15 with gentoo bits and lastest x11-org
> bits. A simple startx with three xterms doesn't even render the fonts
> correctly. Eventually the machine wedges and can't be pinged.
> Switching the xorg.conf driver from radeon to vesa works and creates a
> reasonable environment. This seems to have manifested itself since
> 2.6.15-rc1.
>
> The laptop is a Compaq NX9600 with maximum memory and a large disk.
>
> Should anyone care for further data captured from /proc, config, logs
> and etc., I'll be glad to forward them along. I'd also be willing to
> debug and/or test whatever suggestions might be made.
Is DRI enabled ? If yes, try disabling it. Recent kernels have the r300
enable DRM, thus X will automatically enable use of CCE acceleration
even for simple 2D, but that isn't very stable on those cards yet.
Ben.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2006-01-05 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 1:42 ATI X600 on 2.6.15 Bob Picco
2006-01-05 9:56 ` Benjamin Herrenschmidt [this message]
2006-01-05 11:31 ` Bob Picco
2006-01-05 20:30 ` Michal Suchanek
2006-01-05 22:27 ` Benjamin Herrenschmidt
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=1136455013.4840.73.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=bob.picco@hp.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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.