From: Gian-Carlo Pascutto <gpascutto@nero.com>
To: linux-kernel@vger.kernel.org
Subject: ServerWorks CSB6 DMA problems
Date: Fri, 14 Jan 2005 22:39:57 +0100 [thread overview]
Message-ID: <41E83C2D.6070101@nero.com> (raw)
Hi all,
is anyone aware of the status of ServerWorks CSB6's chipset DMA support?
On a machine with a RHEL3 kernel (2.4.21-27.0.1.EL), the kernel seems to
enable UDMA33 on the first connected disk (Seagate 7200.7) but uses PIO
mode on the second (Maxtor 6Y080P0).
I found out this is for good reasons because after enabling UDMA100 on
both disks, via hdparm, filesystem corruption quickly resulted.
Googling turns up a lot of talk about buggy CSB4 chipsets, but nothing
about the CSB6, actually several posts claiming it should work ok. The
above experience and the kernel's selection suggest that's not the whole
story though.
Basically, I'm curious if there's any *safe* way to get some more
performance out of this configuration on Linux, or if I'm SOL. I mean,
the Maxtor in PIO mode works at about 2Mb/s... :-/
--
GCP
next reply other threads:[~2005-01-14 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 21:39 Gian-Carlo Pascutto [this message]
2005-01-15 0:33 ` ServerWorks CSB6 DMA problems Alan Cox
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=41E83C2D.6070101@nero.com \
--to=gpascutto@nero.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