From: Mike Dresser <mdresser@windsormachine.com>
To: Jesus Cea Avion <jcea@argo.es>
Cc: linux-kernel@vger.kernel.org, l-linux@calvo.teleco.ulpgc.es
Subject: Re: AX64 too (was: Re: Dma problems - Aopen Ax34pro VIA chipset seagate drive)
Date: Fri, 01 Dec 2000 14:01:04 -0500 [thread overview]
Message-ID: <3A27F570.D0FCB2E@windsormachine.com> (raw)
In-Reply-To: <3A1A354D.3927.5A09E7EB@localhost> <3A27EE7A.549543D5@argo.es>
I've got a motherboard with the same Via686a chipset, and i've never had a
problem with DMA when it's enabled.
Using a pair of 20 gig IBM drives on the secondary, and a 3.2 quantum primary,
17.2 gig maxtor. All using DMA, all work. Using ultra/33, I wasn't even
aware this chipset is ultra/66 capable, until last night. Going to acquire an
ultra/66 cable, and test udma/66 mode tonight. And find out what bios setting
makes the thing not _allow_ dma at all.
System used to be flaky with networking, did some memory timing adjustments,
seems to be ok now.
Celeron 300@450, 32 meg sdram.
/dev/hdc:
Model=IBM-DJNA-352030, FwRev=J58OA30K, SerialNo=GQ0GQF07566
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=34
BuffType=DualPortCache, BuffSize=1966kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39876480
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4
/dev/hdc:
Timing buffer-cache reads: 128 MB in 1.48 seconds = 86.49 MB/sec
Timing buffered disk reads: 64 MB in 4.33 seconds = 14.78 MB/sec
Not too bad for an old 20 gig. Same speeds whether i have -c3 -u1 or not.
Turn DMA off, it gets slow though
/dev/hdc:
Timing buffer-cache reads: 128 MB in 1.50 seconds = 85.33 MB/sec
Timing buffered disk reads: 64 MB in 14.90 seconds = 4.30 MB/sec
Jesus Cea Avion wrote:
> Please, if you respond, send me a copy to my mailbox, too.
>
> > Status: kernel 2.4.0-test10 (no patches added)
> > Problem: getting dma problems - having to run system with no dma
> > for disc access - seems to be a bus mastering problem.
> > Hardware: Aopen AX34Pro mother board, Via chipset with via686a,
> > Seagate Baracuda ATA66 20GB disc - Latest Bios for motherboard
> > Sony CDU4811 cdrom
>
> I have a comparable problem with an Aopen AX64 motherboard. Chipset
> via686a.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-01 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-20 22:11 Dma problems - Aopen Ax34pro VIA chipset seagate drive Stephen Carr
2000-12-01 18:31 ` AX64 too (was: Re: Dma problems - Aopen Ax34pro VIA chipset seagate drive) Jesus Cea Avion
2000-12-01 19:01 ` Mike Dresser [this message]
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=3A27F570.D0FCB2E@windsormachine.com \
--to=mdresser@windsormachine.com \
--cc=jcea@argo.es \
--cc=l-linux@calvo.teleco.ulpgc.es \
--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 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.