mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: GOTO Masanori <gotom@debian.org>
To: jfl@jfworld.net
Cc: linux-kernel@vger.kernel.org, gotom@debian.org
Subject: Re: UDMA problem with Maxtor 7200rpm disk
Date: Thu, 20 Dec 2001 10:28:08 +0900	[thread overview]
Message-ID: <w53k7viy91z.wl@megaela.fe.dis.titech.ac.jp> (raw)
In-Reply-To: In your message of "Wed, 19 Dec 2001 15:16:36 -0500" <20011219151636.50e930ac.jfl@jfworld.net>
In-Reply-To: <20011219151636.50e930ac.jfl@jfworld.net>

At Wed, 19 Dec 2001 15:16:36 -0500,
Jean-Francois Levesque <jfl@jfworld.net> wrote:
> I have a problem regarding my new Asus A7V266 board with VIA KT266 chipset.  Byron Stanoszek told me to ask my problem to this list so here it is :
> 
> My hard drive is a Maxtor 5T030H3 ATA DISK drive (30 gig).  The problem is that I'm not able to read more than 7 MB/sec :
> 
> [root@xyz jfl]# /sbin/hdparm -t /dev/hda
> 
> /dev/hda:
>  Timing buffered disk reads:  64 MB in  9.18 seconds =  6.97 MB/sec
> 
> 
> [root@xyz jfl]# /sbin/hdparm -d1 -X66 /dev/hda
> 
> /dev/hda:
>  setting using_dma to 1 (on)
>  setting xfermode to 66 (UltraDMA mode2)
>  using_dma    =  1 (on)
> [root@xyz jfl]# /sbin/hdparm -t /dev/hda
> 
> /dev/hda:
>  Timing buffered disk reads:  64 MB in  9.70 seconds =  6.60 MB/sec
> 
> [root@xyz jfl]# /sbin/hdparm /dev/hda
> 
> /dev/hda:
>  multcount    = 16 (on)
>  I/O support  =  1 (32-bit)
>  unmaskirq    =  1 (on)
>  using_dma    =  0 (off)
>  keepsettings =  0 (off)
>  nowerr       =  0 (off)
>  readonly     =  0 (off)
>  readahead    =  8 (on)
>  geometry     = 3736/255/63, sectors = 60030432, start = 0
> [root@xyz jfl]#
> 
> I also have some idebus errors.
> 
> The problem seems to be the DMA (ATA100 compatible board and disk).

BIOS parameter of your machine is set as "DISK auto detection" ?  If
you so, would you try to change your BIOS setting as "this disk have
ultra DMA mode 4 (or 5, if your disk is ATA100)" explicitly ?

These behavior is very similar to my enviroment.
I have Asus KT133A board, and I had this problem, but I changed BIOS
setting, all problems were gone and became happy.
If my suggestion is totally wrong, I apologize...
(However, if my suggestion is relevant, then what's the problem?
 IDE driver, or hardware problem?)

> PS: My disk also "freeze" my system for a few seconds (from 1/2 to maybe 3sec) while checking some data.

IMHO, the reason is that writing disk with PIO mode 4 (IIRC, 6.60MB/s
is corresponding with PIO mode 4) invites CPU occupation.
Andrew Morton also fixed 'low latency read problem', which is already
resolved the latest 2.4.17-rc2.

-- gotom

  parent reply	other threads:[~2001-12-20  1:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 20:16 Jean-Francois Levesque
2001-12-20  0:47 ` Tim Moore
2001-12-20  1:25 ` Jean-Francois Levesque
2001-12-20  1:28 ` GOTO Masanori [this message]
2001-12-20  2:43   ` Jean-Francois Levesque
2001-12-20  3:18     ` Timothy Covell
2001-12-20  1:38 ` Jean-Francois Levesque
2001-12-20  9:10 ` Sergey S. Kostyliov
2001-12-23 21:53 Andy Furniss

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=w53k7viy91z.wl@megaela.fe.dis.titech.ac.jp \
    --to=gotom@debian.org \
    --cc=jfl@jfworld.net \
    --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®