From: Vojtech Pavlik <vojtech@suse.cz>
To: Ignacio Monge <ignaciomonge@navegalia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PIO disk writes using 100% system time and performing poorly with VIA vt82c686b on kernels 2.2 & 2.4
Date: Wed, 25 Apr 2001 00:12:36 +0200 [thread overview]
Message-ID: <20010425001236.A2888@suse.cz> (raw)
In-Reply-To: <20010424191941.5e719746.ignaciomonge@navegalia.com>
In-Reply-To: <20010424191941.5e719746.ignaciomonge@navegalia.com>; from ignaciomonge@navegalia.com on Tue, Apr 24, 2001 at 07:19:41PM -0400
On Tue, Apr 24, 2001 at 07:19:41PM -0400, Ignacio Monge wrote:
> I have VIA686a too and a UDMA100 hard disk.
> This is my cat /proc/ide/via:
>
> ----------VIA BusMastering IDE Configuration----------------
> Driver Version: 3.23
> South Bridge: VIA vt82c686a
> Revision: ISA 0x22 IDE 0x10
> Highest DMA rate: UDMA66
> BM-DMA base: 0xb800
> PCI clock: 33MHz
> -----------------------Primary IDE-------Secondary IDE------
> Enabled: yes yes
> Cable Type: 40w 40w
> -------------------drive0----drive1----drive2----drive3-----
> Transfer Mode: DMA UDMA PIO PIO
> Address Setup: 30ns 30ns 120ns 120ns
> Cmd Active: 90ns 90ns 480ns 480ns
> Cmd Recovery: 30ns 30ns 480ns 480ns
> Data Active: 90ns 90ns 330ns 330ns
> Data Recovery: 30ns 30ns 270ns 270ns
> Cycle Time: 120ns 60ns 600ns 600ns
> Transfer Rate: 16.5MB/s 33.0MB/s 3.3MB/s 3.3MB/s
>
> As you can see, l use UDMA66 instead UDMA100.
You use UDMA33 dor your second drive and MWDMA16 for your first.
Check your BIOS UDMA enable settings.
> I don't know why. Maybe VIA vt82c686a doesn't support it?
Yes, it supports modes only up to 66 MB/sec.
> I have answering in this list a days ago about this problem. but none seems to have a question. Like you, my system goes down when I try to compile something (I have a 394 Mb of RAM and a 1 Ghz processor).
> Although, my hdparm output is this:
> /dev/hde2:
> Timing buffer-cache reads: 128 MB in 0.79 seconds =162.03 MB/sec
> Timing buffered disk reads: 64 MB in 2.44 seconds = 26.23 MB/sec
> and sometime looks better.
26 megabytes per second is quite surprising in your setup
> I don't know is this is a problem with the VIA kernel driver or not. But the system doesn't seem to work fine since 2.4.2 or 2.4.1 kernel. I hope (plz!) this problem will be fixed in future.
You can disable the VIA driver.
> PS: in cat /proc/ide/via I see "Cable Type: 40w 40w"... Is it right? I have a 80w cable, not 40.
Check your BIOS settings, if you have disabled UDMA in the BIOS, the
driver can't detect the cable. If that doesn't work, use "ide0=ata66"
on the kernel command line.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2001-04-25 6:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 23:19 PIO disk writes using 100% system time and performing poorly with VIA vt82c686b on kernels 2.2 & 2.4 Ignacio Monge
2001-04-24 21:45 ` Francois Cami
2001-04-24 22:12 ` Vojtech Pavlik [this message]
[not found] <fa.hn82icv.1i1uioa@ifi.uio.no>
2001-04-24 15:37 ` John Weber
-- strict thread matches above, loose matches on Subject: below --
2001-04-24 14:00 Thomas Ford
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=20010425001236.A2888@suse.cz \
--to=vojtech@suse.cz \
--cc=ignaciomonge@navegalia.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