From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Gian-Carlo Pascutto <gpascutto@nero.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ServerWorks CSB6 DMA problems
Date: Sat, 15 Jan 2005 00:33:25 +0000 [thread overview]
Message-ID: <1105744528.9838.37.camel@localhost.localdomain> (raw)
In-Reply-To: <41E83C2D.6070101@nero.com>
On Gwe, 2005-01-14 at 21:39, Gian-Carlo Pascutto wrote:
> 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.
That all suprises me a great deal, although the modes are normally BIOS
selected by the Serverworks and then read by the kernel. CBS5/CSB6 IDE
should be very reliable indeed (OSB4 is a much older chipset and the
problem it has is OSB4 specific)
I'd also suggest you raise it with your RHEL support and/or
bugzilla.redhat.com
Alan
prev parent reply other threads:[~2005-01-15 1:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 21:39 ServerWorks CSB6 DMA problems Gian-Carlo Pascutto
2005-01-15 0:33 ` Alan Cox [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=1105744528.9838.37.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=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