public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Hartmann <andihartmann@freenet.de>
To: linux-kernel@vger.kernel.org
Subject: Problem with DMA or agpgart on VIA686a-boards consists with kernel 2.4.2?
Date: Sun, 25 Feb 2001 16:21:20 +0100	[thread overview]
Message-ID: <01022515592800.00283@athlon> (raw)

Used hardware:
AMD Athlon 800
VIA KX133-Chipsatz with AGP

Chipset: ATI 264LT Pro (3D Rage LT Pro) (Port Probed)
Memory:  8192 Kbytes
RAMDAC:  ATI Mach64 integrated 15/16/24/32-bit DAC w/clock
                 (with 6-bit wide lookup tables (or in 6-bit mode))
                 (programmable for 6/8-bit wide lookup tables)
Attached graphics coprocessor:
                Chipset: ATI Mach64
                Memory:  8192 Kbytes


used software-versions:
- Kernel 2.3.x until 2.4.2
- Kernel 2.4test
- activated support for VIA82Cxxx and using DMA by default
- X 3.3.6
- agpgart-module
- glx from sourceforge.net with DMA and agpgart
- reiserfs
- DMA-mode of the hd (WDC WD205AA) is turned on with hdparm and runs 
   in UDMA4-mode.




Hallo all,

I already found in some 2.3-versions or in the 2.4test-versions the following 
problem:
The X-screen suddenly begins blinking and can't be stabilized without 
rebooting the machine (which did not freeze!). A restart of X-Server doesn't 
help. The problem persists.
Unfortunately I couldn't find any error-log. A hint maybe the output of the 
glx.log when started in "damaged" situation (negative benchmarks):

   119:dma buffer transfer speed:
 13698:DmaBenchmark 0xfde00 bytes, 0.010 sec: 97 mb/s
 15092:DmaBenchmark 0xfde00 bytes, -0.019 sec: -51 mb/s
 13647:DmaBenchmark 0xfde00 bytes, 0.010 sec: 103 mb/s

In not damaged situation, you can find something like this:
   119:dma buffer transfer speed:
 20007:DmaBenchmark 0xfde00 bytes, 0.016 sec: 61 mb/s
 10397:DmaBenchmark 0xfde00 bytes, 0.006 sec: 163 mb/s
 10296:DmaBenchmark 0xfde00 bytes, 0.006 sec: 164 mb/s

Some information to glx:
glx provides 3D-functions under X 3.3.6 with my graphic-chip and uses 
therefore DMA and agpgart. glx uses too a "little" file in the 
/tmp-directory, which resides on a reiserfs-partition.

There are no problems with kernel 2.2.x and the special IDE-patches from 
Andre Hedrick.

Now some interesting information perhaps:
The patches from Alan Cox 2.4.1ac9 or ac17 (I didn't test the others) are 
working fine. I couldn't find any problem with these patches.

I would be very appreciated if the related patches of Alan Cox could find 
there way in the official kernel!

Kind regards,
Andreas Hartmann

                 reply	other threads:[~2001-02-25 15:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=01022515592800.00283@athlon \
    --to=andihartmann@freenet.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