From: Jussi Laako <jlaako@pp.htv.fi>
To: "Ryan W. Maple" <ryan@guardiandigital.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: VIA 686B/Data Corruption
Date: Fri, 29 Jun 2001 01:15:01 +0300 [thread overview]
Message-ID: <3B3BAC65.3ED4CBEF@pp.htv.fi> (raw)
In-Reply-To: <Pine.LNX.4.10.10106281741070.11750-100000@mastermind.inside.guardiandigital.com>
"Ryan W. Maple" wrote:
>
> I remember hearing something about Red Hat disabling UDMA on VIA chips
> across the board. Maybe that has something to do with it?
Dunno, if the kernel lies. There are four HDs on Promise and one HD and one
CDROM on VIA. This is from currently running 2.4.2-2:
----------VIA BusMastering IDE Configuration----------------
Driver Version: 3.20
South Bridge: VIA vt82c686b
Revision: ISA 0x40 IDE 0x6
BM-DMA base: 0xb800
PCI clock: 33MHz
Master Read Cycle IRDY: 0ws
Master Write Cycle IRDY: 0ws
BM IDE Status Register Read Retry: yes
Max DRDY Pulse Width: No limit
-----------------------Primary IDE-------Secondary IDE------
Read DMA FIFO flush: yes yes
End Sector FIFO flush: no no
Prefetch Buffer: no no
Post Write Buffer: no no
Enabled: yes yes
Simplex only: no no
Cable Type: 40w 40w
-------------------drive0----drive1----drive2----drive3-----
Transfer Mode: UDMA PIO 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: 60ns 90ns 90ns 90ns
Transfer Rate: 33.3MB/s 22.2MB/s 22.2MB/s 22.2MB/s
PDC20265 Chipset.
------------------------------- General Status ----------------------------
Burst Mode : enabled
Host Mode : Normal
Bus Clocking : 33 PCI Internal
IO pad select : 10 mA
Status Polling Period : 0
Interrupt Check Status Polling Delay : 2
--------------- Primary Channel ---------------- Secondary Channel --------
enabled enabled
66 Clocking enabled enabled
Mode PCI Mode PCI
FIFO Empty FIFO Empty
--------------- drive0 --------- drive1 -------- drive0 ---------- drive1 -
DMA enabled: yes yes yes yes
DMA Mode: UDMA 4 UDMA 4 UDMA 4 UDMA 4
PIO Mode: PIO 4 PIO 4 PIO 4 PIO 4
- Jussi Laako
--
PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B 39DD A4DE 63EB C216 1E4B
Available at PGP keyservers
prev parent reply other threads:[~2001-06-28 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 1:57 VIA 686B/Data Corruption FAQ Gareth Hughes
2001-06-28 10:03 ` Alan Cox
2001-06-28 21:27 ` VIA 686B/Data Corruption Jussi Laako
2001-06-28 21:29 ` Alan Cox
2001-06-28 21:41 ` Ryan W. Maple
2001-06-28 21:48 ` Alan Cox
2001-06-28 22:15 ` Jussi Laako [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=3B3BAC65.3ED4CBEF@pp.htv.fi \
--to=jlaako@pp.htv.fi \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ryan@guardiandigital.com \
/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