From: Mike Maravillo <mike.maravillo@q-linux.com>
To: Ryan Hayle <hackel@walkingfish.com>
Cc: linux-kernel@vger.kernel.org, mike.maravillo@q-linux.com
Subject: Re: Poor IDE performance with VIA MVP3
Date: Tue, 6 Nov 2001 03:54:52 +0800 [thread overview]
Message-ID: <20011106035452.A1221@maravillo.q-linux.com> (raw)
In-Reply-To: <20011105005033.A10060@isis.visi.com> <01110516120000.00794@nemo> <20011105114242.A8099@isis.visi.com>
In-Reply-To: <20011105114242.A8099@isis.visi.com>; from hackel@walkingfish.com on Mon, Nov 05, 2001 at 11:42:43AM -0600
On Mon, Nov 05, 2001 at 11:42:43AM -0600, Ryan Hayle wrote:
> On Mon, 05 Nov, 2001 at 04:12:00PM +0000, vda wrote:
> > Are you saying that hdparm -T -t is yielding wildly varying results?
> > Looks similar to failing hd symptoms or bug in IDE layer causing retries
> > after error/timeout. What's in the logs?
>
> hdparm -T (buffer-cache reads) gives good numbers, 43v69 M/sec just
> now. But that's only mesuring reading from the drive's 2M cache (I
> believe?). It is the hdparm -t test (buffered disk reads) that is the
> problem. As I said, I don't receive any errors or retries
> whatsoever. Everything seems to be working perfectly, just very, very
> slow...
>
> > Well, I had problems with drives refusing to do [u]dma.
> > On my home machine I found out that compiling kernel with support for VIA
> > chipset allowed udma to work ok (hdparm -T -t = ~20mb/s). Without that
> > support, my hd was stuck in pio, ~6mb/s.
>
> That's the thing--it claims to be in UDMA mode, and again I get no
> errors. Even when I do 'hdparm -d1 -X66 /dev/hda", everything works fine,
> without errors, only the speed problems persist. Oh, and I have compiled
> my kernel with VIA IDE support, it makes no difference in the performance.
>
> It's sounding more and more like this isn't a driver/chipset problem, but
> something wrong with the HD itself. Thanks for your insight.
This has been a long-standing problem with my system as well. I
have an MS-5187 VIA MVP4 board and ST320413A UltraATA/100 drive.
Timing buffer-cache reads: 128 MB in 4.40 seconds = 29.09 MB/sec
Timing buffered disk reads: 64 MB in 13.06 seconds = 4.90 MB/sec
Model=ST320413A, FwRev=3.39, SerialNo=7ED05MNS
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=512kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=39102336
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 udma5
AdvancedPM=no
Drive Supports : Reserved : ATA-1 ATA-2 ATA-3 ATA-4
I remember trying out the drive on a Soltek 75KAV and got better
buffered disk results, ~25.0 MB/sec.
--
.--. Michael J. Maravillo office://+63.2.894.3592/
( () ) Q Linux Solutions, Inc. mobile://+63.917.897.0919/
`--\\ A Philippine Open Source Solutions Co. http://www.q-linux.com/
next prev parent reply other threads:[~2001-11-05 19:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-05 6:50 Ryan Hayle
2001-11-05 16:12 ` vda
2001-11-05 17:42 ` Ryan Hayle
2001-11-05 17:55 ` Daniel R. Warner
2001-11-05 19:54 ` Mike Maravillo [this message]
2001-11-06 11:50 ` vda
[not found] ` <Pine.LNX.4.10.10111051506270.13543-100000@coffee.psychology.mcmaster.ca>
2001-11-06 5:21 ` Ryan Hayle
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=20011106035452.A1221@maravillo.q-linux.com \
--to=mike.maravillo@q-linux.com \
--cc=hackel@walkingfish.com \
--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
all inboxes | Powered by JetHome®