From: Anders Karlsson <anders@trudheim.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.69
Date: 05 May 2003 07:31:46 +0100 [thread overview]
Message-ID: <1052116306.31300.50.camel@marx> (raw)
In-Reply-To: <Pine.LNX.4.44.0305042137370.6183-100000@home.transmeta.com>
[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]
On Mon, 2003-05-05 at 05:41, Linus Torvalds wrote:
> Make sure to also test with regular 1x AGP (and no fast write stuff etc).
> A lot of motherboards really aren't going to like 4x and some other
> settings (in particular, enabling fast writes seems to be a very iffy
> proposition indeed).
Will try that in case that fixes the problems I see.
> Also, check if the same setup is stable under 2.4.x and possibly using the
> DRI CVS tree. Radeon in particular seems to be a lot stabler in DRI these
> days than it has historically been.
>
> Indeed, one of the reasons it took me so long to figure out the stability
> issues I saw was simply that there have been real bugs in direct
> rendering, and I was blaming them instead and I spent a lot of time trying
> to chase down the bug as an AGP or DRI issue.
Would you think that the problems I have been seeing with a Radeon
Mobility LY on kernel 2.4.2[01] could be down to exactly these issues as
well?
The problems are that the X server can be started only once and that
there seems to be a chance of it locking the machine hard at start after
that, especially after unloading the radeon.o module.
I will do more testing on that to find out exactly what does what, but
would 2.5.69 be a good test to see what has been fixed?
Regards,
/Anders
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2003-05-05 6:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 0:48 Linux 2.5.69 Linus Torvalds
2003-05-05 4:30 ` Florin Iucha
2003-05-05 4:41 ` Linus Torvalds
2003-05-05 6:31 ` Anders Karlsson [this message]
2003-05-05 7:08 ` Anders Karlsson
2003-05-05 13:07 ` Florin Iucha
2003-05-05 13:20 ` Florin Iucha
2003-05-05 8:14 ` Benjamin Herrenschmidt
2003-05-05 21:05 ` John Cherry
2003-05-05 21:39 ` Sam Ravnborg
2003-05-05 21:45 ` Arnaldo Carvalho de Melo
2003-05-05 23:22 ` John Cherry
2003-05-06 10:08 ` Paweł Gołaszewski
2003-05-06 12:02 ` [PATCH] include/linux/sunrpc/svc.h compilation error Grzegorz Jaskiewicz
2003-05-06 12:12 ` Grzegorz Jaskiewicz
2003-05-06 12:58 ` Paweł Gołaszewski
2003-05-06 13:39 ` Linux 2.5.69 Roger Luethi
2003-05-06 14:08 ` David S. Miller
2003-05-06 18:24 ` Arnaldo Carvalho de Melo
2003-05-07 2:22 ` Rusty Russell
2003-05-07 19:44 ` Geert Uytterhoeven
2003-05-07 19:35 ` Ben Collins
2003-05-07 22:07 ` Linus Torvalds
2003-05-05 4:19 Voluspa
[not found] <fa.m5ekdiv.15gu98j@ifi.uio.no>
2003-05-05 13:00 ` walt
[not found] <3EB602ED.3080207@cox.net>
2003-05-05 15:56 ` Linus Torvalds
2003-05-05 16:02 ` William Lee Irwin III
2003-05-05 16:06 ` David van Hoose
2003-05-05 16:16 ` Steven Cole
2003-05-05 18:49 ` Dave Jones
2003-05-05 18:53 ` Linus Torvalds
2003-05-06 7:00 Voluspa
2003-05-06 22:03 Alan Cox
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=1052116306.31300.50.camel@marx \
--to=anders@trudheim.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).