From: "J.A. Magallón" <jamagallon@able.es>
To: linux-kernel@vger.kernel.org
Cc: Andrea Arcangeli <andrea@suse.de>
Subject: Re: 2.4.21pre2aa1
Date: Thu, 26 Dec 2002 16:13:58 +0100 [thread overview]
Message-ID: <20021226151358.GA1607@werewolf.able.es> (raw)
In-Reply-To: <20021226010605.GA4223@dualathlon.random>; from andrea@suse.de on Thu, Dec 26, 2002 at 02:06:05 +0100
On 2002.12.26 Andrea Arcangeli wrote:
[...]
>
> Only in 2.4.21pre2aa1: 9990_hack-drop-x86-fast-pte-2
>
[...]
> I never noticed this problem before because I rarely use 3d (and usually
> I had mesasoft setup anyways). It's not specific to a certain graphics card,
> so it looks more like an agp generic problem or something, I can
> reproduce myself on my laptop i830 graphics card and i830 agp, on my
> desktop g450 with amd agp, and on my test box on a ati radeon 7500 and
> intel agp, so it doesn't look like a lowlevel driver problem, and it
> only hurts while using the agp and/or drm somehow. Many thanks to
> Srihari Vijayaraghavan who found the offending patch in the whole kit
> originally some time ago.
>
I saw it also using nVidia drivers, that do not touch drm. So I would vote for
agpgart.
--
J.A. Magallon <jamagallon@able.es> \ Software is like sex:
werewolf.able.es \ It's better when it's free
Mandrake Linux release 9.1 (Cooker) for i586
Linux 2.4.21-pre2-jam1 (gcc 3.2.1 (Mandrake Linux 9.1 3.2.1-2mdk))
next prev parent reply other threads:[~2002-12-26 15:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-26 1:06 2.4.21pre2aa1 Andrea Arcangeli
2002-12-26 2:26 ` 2.4.21pre2aa1 Eyal Lebedinsky
2002-12-26 4:22 ` 2.4.21pre2aa1: compile error in fs/buffer.c Eyal Lebedinsky
2002-12-26 4:33 ` 2.4.21pre2aa1: compile error in DAC960.c Eyal Lebedinsky
2002-12-31 0:49 ` Dave Olien
2003-01-07 19:38 ` Andrea Arcangeli
2002-12-26 15:13 ` J.A. Magallón [this message]
2002-12-26 15:26 ` 2.4.21pre2aa1 Marc-Christian Petersen
2002-12-31 11:25 ` 2.4.21pre2aa1 J.A. Magallon
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=20021226151358.GA1607@werewolf.able.es \
--to=jamagallon@able.es \
--cc=andrea@suse.de \
--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